* V9 Changes
* Converted Ktons back to Tonnage, Noticed I never changed its title in its note either, since I used to have it that way...
* Guilty of same with force kkms, shows the obtained speed in km/sec, but forcing it in thousands - changed retitled to km/s, and changed to km/s entry, rather than kkm/s entry.
* Moved Missile Data Velocity, Range, Endurance, and Boost to immediately after "Want Hit Chance"
* Moved Fleet Comp Engine EPH a few columns right to just after the Engine Mod
* Goofed the number formatting for missile boost, it only showed integers if more/less boost would improve range, fixed in excel.
* Sensor Data: Replaced the graph prep result NA() with if(info("version"), , na()). Google sheets was graphing NA()'s, but ignoring blanks. Excel graphs blanks as zeroes but ignores NA(). Excel doesn't throw a fit over info(), sheets does, so I can test for which the formula is executing under, and give the correct "ignore me" value.
* At a glance, About, Sensor Data, Fleet Composition, PD Turret Calculator, and Missile Data appear to be mathematically functional and in agreement between sheets and excel.
* Sheets also appears to be reasonably quick all things considered. Definitely slower than excel on my machine, noticeably so, but its still responsive in sheets.
* Known issues with Sheets version:Widths sometimes are a bit wonky, probably won't be too fussy about that until I run out of stuff to try and update the sheet with.
* The Conditional formats applied to 'Missile Data'!Engine Boost are not applying in sheets. Have not investigated deeper yet — the boost (in/de)crease suggestion formats are not functional in sheets.
* The light blue row line formats are inconsistently applying in sheets, instead of spanning the whole width, some cells lack them, some have them, do not know why yet.
* V8 changes:
*
* Tug Mass was not being multiplied into tons as it was supposed to be, so it required entry as tons, rather than kTons as indicated. Fixed
* V7 changes:
*
* Found another spot where I still had some lingering formulas in cells expecting entry - cleared it.
* Rewrote the missile AGI/ENG MSP calcs to use a stepped method, reduced rows needed from 1450 to 150.
* Leveraged the now considerably shorter AGI/ENG cals to do two additional complete passes, one with .05 more boost, and one with .05 less, sheet can now indicate if raising or lowering boost will increase range. And even still, it is ~70% less workload than previous.
* "5.9 x " where x is an up arrow indicates increased range with 5.95 boost
* "5.9 x " where x is a down arrow indicates increased range with 5.85 boost
* V6 Changes:
*
* Got my hands on the FastExcel Profiler Bundle trial and went a murderin', lol. Took the nastiest formula from 4,000ms, to the worst being 108ms.
* Rewrote the boolean for the sensor graph prep work.
* Punted the grunt work for TUG mass to a pair of helper cells. Determining maximum tonnage mil/civ happens in just two cells now, rest look at those.
* Used an excel profiler: 80% of the book's workload was in the missile data, specifically, the visual indicator for min AGI/ENG cost. Reworked it. Update changed just those 30 columns costing 3773.82 millisec, to the entire workbook costing 839msec, and those columns down to just 63 millisec total. Still pretty volatile though, work continues to trim fat.
* Pulled apart the AGI, ENG, and visual indicator to isolate some row by row constants, and stashed them at the very bottom to reference rather than repeat the effort, yet more gains had.
* V5 changes:
* Moved all the C# toggles to put the entry in cell C3....because reasons.
* Sensor Data
* Had missed a column in verifying a given tonnage had a sensor to graph.
* Eliminated a case that existed from when the graph limits had a minimum range - never did get excel to let me move the minimum Y axis dynamically without VB.
* Simplified the formulas for the graphing prep work - punted the repeated lookups for max range and resolution to helper cells
* Fleet Composition:
* Added a note for Subdivide Tanks -> H5
* Had been re-calculating engine quantity four times each boost, now just once and reference the one result.
* Found and fixed a bug in the formula for engine EP necessary per boost - one cell reference to max boost was row locked, should not be.
* Converted Armor Type, Engine Type, Max Eng HS, Armor Tons, Want Speed, Engine Power, Desire Range, to use named ranges instead of cell ranges.
* Converted Role range, K tons, Build This, Military references to named ranges
* Added some more missing notes -> Role column headers
* Pushed the Ship-Role row-match out to a helper so it gets done once rather than 5 times.
* Moved tug mass formula from sitting in the user entry, to an assumed value when user entry is not given, added column to over-rule it.
* Rewrote TUG Mass to be a bit less convoluted.
* Added isTUG column to Roles so its not locked to a name anymore. - Military ships with an isTUG role use maximum military ship tonnage, likewise for civilian using civilian.
* Missile Data:
* Was repeating the lookup for Engine EP/MSP for missiles in Velocity, Range_mkm, and ENG_PWR, now has a helper cell next to ENG_PWR.
* Changed ENG_EP to use a named range rather than cell reference for both c# and 7.1
* The C# toggle wasn't shaded, should be since its a user setting.
* Converted Engine Tech, and every missile ENG_HS lookup, to use named ranges instead of cell ranges.
* Added another row to the Missile Tech, to store and reuse the looked up missile configuration row, rather than look it up 15 times per missile.
V4 Changes:
* 'Sensor Data'!H5:H14, 'Sensor Data'!N5:N14, and 'Fleet Composition'!R6:S85 are now validated TRUE/FALSE as well.
V3 changes:
* Added in some missing notes.
* Found some typos.
* Cleaned up some of the number formats a bit more in both fleet composition and missile data.
* Changed 'PD Turret Calculator'!H27:H30 to show actual bonus gained, rather than relative percentage (actual bonus vs actual bonus / max bonus)
* Forgot to shade in 'PD Turret Calculator'!C26:C27 and 'PD Turret Calculator'!E27:E30
* Made the sensor HS in for an active PD sensor in 'PD Turret Calculator' work with 7.1 sensors - for quasar when its ready.
* Switched 'PD Turret Calculator' reactor output tech entry in 'PD Turret Calculator' to use the tech name, rather than the corresponding 1hs output.
* 'PD Turret Calculator' now supports Quasar tracking bonuses — using 7.1's expected outcomes, am aware 7.1 is broken, it doesn't use them.
* Found and removed a couple more random values I had scattered around.
* Converted all cell references in the About sheet to manipulate named ranges - I shouldn't have to adjust text nor the hyperlinks after this - your own edits might also not break the links and so keep the help relevant.
V2 changes:
* Wiped out some personal preference formulas that should have been killed before I set it loose.
* Corrected 'Sensor Data'!B5's dependents so b5 works correctly again
* Unhid Fleet Composition Column D(engine tech power rating) and moved it to safety in the main calculations section before it gets deleted accidentally.
* Punted the shield fraction from Roles - While I used it that way, the formula in a cell expecting entry should probably die.