Morning (PDT)

-----Original Message-----
From: Derek Wildstar
Sent: Thursday, April 30, 2015 5:58 AM
To: xxxxxx@simplelists.com
Subject: Re: [TML] T4 QSDS Question

On Apr 29, 2015, at 7:39 PM, xxxxxx@comcast.net wrote:
>> May I send anything my digging into T4 that might be errata to Donald
>> McKinney for review and hopefully inclusion in a future update to the
>> Consolidated T4 Errata?

> Absolutely!

Thank you for your permission to provide Donald McKinney with updates to the
Consolidated T4 Errata.

> I have the Word documents and master Excel spreadsheet for QSDS, so one
> option for fixes would be to produce a QSDS 1.6 document.  :-)

I have the copy of 1.5e that I got from Donald McKinney for a T4 project he
did back in 2011, if I've translated my dating of the folders correctly.
When I could not find my QSDS 1.5e my searching led me to BITS archive and
found this:

"QSDS v1.5.1
This is the Quick Ship Design System from T4, with all the errata fixed
including the HEPlaR fuel error in the original release. Build starships for
your T4 game without the need to use the detailed 'Fire, Fusion and Steel 2'
system. (Author Guy 'Wildstar' Garnett, PDF 128 kb).
I've located a copy on BITS which is identified as QSDS 1.5.1. QSDS 1.5.1 is
the same document I received from Donald."

Producing QSDS 1.6 may help to bring others into using T4 QSDS for quick
ship design.

>I also still have the QSDS Big Book of Hulls add-on that I used to make
>available on my web site.  QSDS as published included a variety of hulls
> designed to cover the standard Traveller starships and some widely-useful
> options.  The Big Book of Hulls lists hull data for every possible
> combination of tech level, configuration and streamlining, stressed for 3G
> and 6G, for every hull from 100 tons to 900 tons in 100-ton increments,
> and
> 1000 tons to 5000 tons in 1000-ton increments.

Another thank you is in order for the work and the BITS archive has

"QSDS Big Book of Hulls
This document expands the basic list of hulls in QSDS with a further 56 (!)
pages of different hull forms from 100dT through to 5,000dT (Author Guy
'Wildstar' Garnett, PDF 903kb). "

I'm not sure if I have your web site stashed in my IE folder and appear to
have missed the url if it is in the replies made here.

>> If I have the right idea an AEMS with a short range of 480,000 km would
>> convert to a USD of 5 and means that my use of Sensor Short Range divided
>>  >> by 30,000 km is out to lunch.  Looks like I will have to redesign my
>> spreadsheet for sensors.

> Let me know what comes out of that.  I haven't been able to find the
> sensor spreadsheet referenced in my QSDS notes; however I'm fairly certain
> that
> that (missing) spreadsheet is what generated the sensor systems data for
> QSDS and probably SSDS as well.

Looks like I am making an error in getting the Sensor USD using the
information provided as:

"Included in those notes are a set of USD values for sensors, that relates
the USD to the FF&S short range so that FF&S_Range = 3km * 10 ^ USD_Value.
In other words:

USD  FF&S Range
0    3km
1    30km
2    300km
3    3000km
4    30,000km
5    300,000km
6    3000,000km
7    3,000,000km"

QSDS 1.5e has the active sensor of the TL-10 through TL-12 medium military
package as being A16. Using the equation 3 km x 10^16 equals
30,000,000,000,000,000 km. The best TNE FF&S Active sensor short range is
480,000 km provided by the AEMS. Doing a reverse lookup on the chart above
the Active USD is 5 not 16.

As mentioned earlier when I converted the 480,000 km to TNE Space Combat
hexes using the equation Short Range 480,000 km divided by one 30,000 km
combat hex I was able to match the QSDS A16 USD value.

Where did I go off the track here.

>>> One item I have not tried to figure out is the Crew requirement for the
>>> jump drive, maneuver drives, or the sensors. How where the crew
>>> requirements calculated for  the jump drive, maneuver drives, sensors,
>>> communicators, bay weapons, meson screens, and power plants?
>>
>> Now I have another reason to work on the spreadsheets I'm creating.

> Crew calculations involving the TL-dependent crew factor are probably the
> same as TNE FF&S.  Variation from this (for example, using TL-12 crew
> modifiers for the TL-9 bay meson gun) are probably my error, and should be
> included in errata.

TNE FF&S Step 9. Crew & Life Support Crew Requirements.

Engineering Crew Ce = (Power Plant Peak Output MW x Computer Control
Multiplier) / 30
Electronics Crew Cl = (Number of Installed Communicators + Number of
Installed Sensors) x Computer Control Multiplier
Maneuvering Cm = 1 if a maneuver drive installed or 1 if a jump drive is
installed, or 2 if both a jump drive and maneuver drive is installed

How about this to explain the crew. The TL-9 meson gun bay has been upgraded
to TL-12 standards which changed the crew requirements.:-)

> Crew for drives (1 per 30 tons if under 50 tons, or 1 + 1 per 100 tons
> otherwise) is probably new for T4.  Drives using this rule almost all have
> an
>  "oldCrew" column in my spreadsheet which uses the TNE FF&S crew
> calculation.

To be honest I have not gone back to the jump and maneuver drives to check
their crew requirements yet, but I have started checking out the crew
requirement for the sensors. Unfortunately, I am having a problem with the
Basic crew calculation.

Using the instructions below I cam match the TL-9 improve, small and medium
military sensor packages crews. Unfortunately, my calculation for the basic
package does not match.

"Sensors and Communicators
  - Crew is # of systems times TL-dependent crew size modifier value
  - For sensors, the number of systems is hard-coded in the spreadsheet
(basic=1, improved=2, sm.mil=4, med.mil=5).
  - For communicators, spreadsheet computes crew based on systems included
in the package (basic/improved=2, advanced=4)

TL  Crew Modifier
9   0.66
A   0.45
B   0.30
C   0.20
D   0.13
E   0.08
F   0.05"

Basic Sensor # = 1 x TL-9 Crew Mod is 0.66 = 0.66 rounding to one decimal
place the crew is 0.7 the QSDS crew requirement is 1.3
Improved Sensor # = 2 x TL-9 Crew Mod is 0.66 = 1.32 rounding to one decimal
place the crew is 1.3 the QSDS crew requirement is 1.3
Small Military Sensor # 4 x TL-9 Crew Mod is 0.66 = 2.64 rounding to one
decimal place the crew is 2.6 the QSDS crew requirement is 2.6
Medium Military Sensor # 5 x TL-9 Crew Mod is 0.66 = 3.30 rounding to one
decimal place the crew is 3.3 the QSDS crew requirement is 3.3

To get the Basic Sensor crew to match the hard-coded value would be 2 not 1.

Have I missed something?

Tom Rux