bbrock, I recently compared FCC (1.1.0.7) data to commodity info snarfed from the LR site, and found over 400 errors in FCC (and about 30 on LR; this is out of the 6118 datapoints; 161 bases x 38 items). I checked all the discrepancies against the game and sent corrections to Darren, the FCC author... he says he'll put them in there. Look for an update soon. I also asked him for a bunch of tweaks, like the ability to filter out factions; I hope he can do some of them. Darren says he got his info out of the official strategy guide, so we can blame it. Also I sent fixes to Christian for the LR site... he's moving IRL so it may take a couple days.
About the same time, Holger of Datastorm told me how the pricing info is sitting right there in Datastorm as an Access .mdb I can open up... it reads info directly from the game and was a great final check that I (and thus, soon, FCC and LR) have all the commodity info right. Actually there's some little rounding error in calculations that cause 265 of them to be low by 1 but that may be fixed soon.
I am toying with the idea of finding a way to calculate travel times, either with FreelancerDB or Datastorm... the idea of making a pathfinding app is probably way more than I can do, but at the least, it ought to be possible to use them for 'measurements' and then relate them to in-game terms (e.g., it takes x minutes to go y km in free space or trade lanes or whatever). Then, some time could be spent turning 'highly travelled' main lines (e.g. Tokyo to Berlin etc.) into approximate times... and after a while, a person could probably get to where they are just taking segments of already-computed routes and then calc a final leg, as they consider the time for particular routes that look promising already on e.g. FCC. It won't be perfect, and it would still be a goodly amount of 'manual' work, but it would probably beat trying to fly all those routes, lol. For that matter though, somebody who simply wants to spend a day flying around and using a stopwatch on 'mainlines' would approximate a lot of the same info... if you know e.g. how long it takes to move through NY going from Colorado to California, it becomes a 'known quantity' for any routes that use it.
An even rougher approximation is to simply make a table of how many systems each system is from the other, and use that as a rough approximation of 'time'. (E.g., London is 4 systems from NY.) Maybe double it for systems without tradelanes, and call a route between bases within a system, 0.5, or something... anyway, it'd be rough, but it could would probably lead to some interesting possibilities that could be checked in the game. Unfortunately, it would be a matrix of, what are there, 43 systems?... 43*42/2=903 datapoints to fill in, lol. I told Darren that if he promised to include a "profit/systems" in FCC, I'd make the matrix for him, but only if he promised, since it's so much work, laugh... if anybody else wants to make it, I have profit info in an Access db and will be happy to swap tit for tat
Okay, enough rambling for now,
CAPT H