Page 1 of 2
Returning to play - problems with saved games (SOLVED)
Posted: Sun May 16, 2010 9:57 am
by tinker
After many months away from the Ooniverse I fired up my 1.72 build and found problems with missing libraries, it was going to be more of a problem finding them than updating so I now have a shiny new 1.74.3 version.
First thing I noticed from the log were a couple of oxps were no longer compatible so I updated them and then tried to load a saved game.
None of the games I have invested hundreds of hours of game play in will load as my ship, a Fer de Lance M2, was not available. Checking the logfile showed up many problems.
As most of the oxps I was running had newer versions I updated all of them and downgraded OSE beta 2 to Realistic Shipyards 3.02. I still cannot load any save game due to my ship being missing, the ship is listed in RS and the log shows RS is loaded.
I read on the forum about all sorts of recent problems with OSE and RS but had hoped that I could still run it even though it is no longer available for d/l. Is RS broken in some way that does not show up in the logfile?
There are still about 20 errors and warnings in the logfile but they are mostly connected with Commies.oxp or simple file naming errors that I can correct later, but I would like to get my ship back, I know it is only a rusty second hand tub, but I got used to calling it home, I had even painted the toilet and decorated the bulkheads with fridge magnets.
Can anyone point me in the right direction.
Posted: Sun May 16, 2010 10:59 am
by Thargoid
Firstly back-up your save game in case things get even more broken (so you have a fall-back) and then open it in a suitable text editor (usual comments about not using Notepad under Windows and recommending Notepad++ etc apply).
Search for the line <key>ship_desc</key>, and the one immediately following it (<string>caduceus-omega-player</string> or <string>cobra3-player</string> or something similar. This is the unique ship key for the ship you are flying.
Next open the RS/OSE/OE OXP folder, go to config and open shipdata.plist in your text editor, and try and find the ship you think you should be flying (make sure it's the player version, not the NPC one, it should list the roles as "player"). At the very top of the entry for that ship (not the top of the file necessarily) you should see <key>xxxx-player</key> or something similar, where xxxx is the ship in question and the whole line is the unique ship key for that particular ship.
Now you need to make a note of that, and ensure that this key matches the one in your save game. If it doesn't, then Oolite won't be able to find the ship your saved commander is trying to fly and so can't load it (you'll get the spinning yellow question mark). Once you know what the shipdata.plist key should be, edit your save game file and change the value of ship_desc to match.
You should then be able to load your saved commander again and continue...
Re: Returning to play - problems with saved games
Posted: Sun May 16, 2010 1:09 pm
by Eric Walch
tinker wrote:After many months away from the Ooniverse I fired up my 1.72 build and found problems with missing libraries, it was going to be more of a problem finding them than updating so I now have a shiny new 1.74.3 version.
First thing I noticed from the log were a couple of oxps were no longer compatible so I updated them and then tried to load a saved game.
None of the games I have invested hundreds of hours of game play in will load as my ship, a Fer de Lance M2, was not available.
I assume you mean 1.73.4. With that version I can confirm that Oolite crashes on loading an unknown ship. It used to work correct in 1.72. And it already works correct in trunk.
Only thing you can do is running an older Oolite version and buy there an other ship. Or use Thargoids method above top edit your save file.
In current trunk I noticed it does not default to the cobra when the old ship is missing, but to a ship the player possessed in the past. (The save file keeps a record of all those ships.) I noticed 1.73 also tried that but than crashed when I switch screens.
Posted: Sun May 16, 2010 3:48 pm
by tinker
Sorry for the version typo I did mean 1.73.4.
I had initially considered that it might be a Linux case error and had checked the shiip names. All the save files have this entry
Code: Select all
<key>ship_desc</key>
<string>ferdelanceM2-player</string>
The shipdata.plist from RS has this entry
Code: Select all
</dict>
<key>ferdelanceM2-player</key>
<dict>
As far as I can see these two lines are the same ship but the save games just give the yellow ?, if I persist in trying to load the game it starts a new game with a cobra, which does not crash as Eric says.
Posted: Sun May 16, 2010 3:56 pm
by Thargoid
Is there anything in latest.log which gives any more clue? For example is there any report of problems with shipdata.plist for your RS installation.
Posted: Sun May 16, 2010 4:30 pm
by tinker
There is nothing that I can see that relates to RS. The OXP search paths gives all the oxps including RS. After this there are several errors listed.
Code: Select all
[dataCache.rebuild.explicitFlush]: Cache explicitly flushed with shift key. Rebuilding from scratch.
[shipData.load.begin]: Loading ship data...
[shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "comlimesc" has a broken flasher definition "*FLASHER*" (should have 8 tokens, has 5). This flasher will be ignored.
[shipData.load.error.badSubentity]: ***** ERROR: subentity declaration for ship comlimesc specifies no subentity_key.
[shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "comlimesc" has a broken flasher definition "*FLASHER*" (should have 8 tokens, has 6). This flasher will be ignored.
[shipData.load.error.badSubentity]: ***** ERROR: subentity declaration for ship comlimesc specifies no subentity_key.
[shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "comlimesc" has a broken flasher definition "*FLASHER*" (should have 8 tokens, has 6). This flasher will be ignored.
[shipData.load.error.badSubentity]: ***** ERROR: subentity declaration for ship comlimesc specifies no subentity_key.
[shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "ambassador-pod" has a broken flasher definition "*FLASHER*" (should have 8 tokens, has 5). This flasher will be ignored.
[shipData.load.error.badSubentity]: ***** ERROR: subentity declaration for ship ambassador-pod specifies no subentity_key.
[shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "ambassador-pod" has a broken flasher definition "*FLASHER*" (should have 8 tokens, has 6). This flasher will be ignored.
[shipData.load.error.badSubentity]: ***** ERROR: subentity declaration for ship ambassador-pod specifies no subentity_key.
[shipData.load.warning.badFlasher]: ----- WARNING: the shipdata.plist entry "ambassador-pod" has a broken flasher definition "*FLASHER*" (should have 8 tokens, has 6). This flasher will be ignored.
[shipData.load.error.badSubentity]: ***** ERROR: subentity declaration for ship ambassador-pod specifies no subentity_key.
[shipData.load.error.badSubentity]: ***** ERROR: the shipdata.plist entry "velocity96-sub" has a broken subentity definition "velocity96-sub" (should have 8 tokens, has 1).
[shipData.load.error.badSubentity]: ***** ERROR: subentity declaration for ship velocity96-sub specifies no subentity_key.
[shipData.load.error]: ***** ERROR: the shipdata.plist entry "dock-factory" specifies non-existent model "comfactory_dock.dat".
[shipData.load.error]: ***** ERROR: the shipdata.plist entry "PAGroove-dodecahedron-reference" specifies no model.
[shipData.load.error]: ***** ERROR: the shipdata.plist entry "PAGroove-coriolis-reference" specifies no model.
[shipData.load.error]: ***** ERROR: the shipdata.plist entry "thargoid-player" specifies no roles.
[shipData.load.error]: ***** ERROR: the shipdata.plist entry "Spiv-Player" specifies non-existent model "Spiv2.dat".
[shipData.load.error]: ***** ERROR: the shipdata.plist entry "PAGroove-icosahedron-reference" specifies no model.
[shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "thargoid-player" does not have a corresponding shipdata.plist entry, ignoring.
[shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "sv_ship_vector_player" does not have a corresponding shipdata.plist entry, ignoring.
[shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "Spiv-Player" does not have a corresponding shipdata.plist entry, ignoring.
[shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "nemesis-player" does not have a corresponding shipdata.plist entry, ignoring.
[shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "hitsadder-player" does not have a corresponding shipdata.plist entry, ignoring.
[shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "mongoose-player" does not have a corresponding shipdata.plist entry, ignoring.
[script.load.notFound]: ***** Could not find a valid script file named Missiles&Bombs.js.
[script.load.world.listAll]: Loaded 61 world scripts: "AsteroidStorm" 3.55, "behemoth" 2.5.4, "blackbaron" 1.70, "Bounty Scanner1.07" 1.07, "buoyRepair" 1.02.5, "Cargo_test", "clipperschedule", "communist_population", "deep_space_dredger" 2.0, "dredger_appearance", "ExecutiveFlightSchedule", "free-trade-zone", "frog_show", "GalNavy" Build 0139, "hatchling_show", "hofd" GalNavy Build 118 / HOFD Build 55, "hoopy_casino" 1.1, "ionics_v_rlf", "long_way_round", "missionaries", "OO-Haul Escort" 1.60, "oolite-cloaking-device" 1.73.4, "oolite-constrictor-hunt" 1.73.4, "oolite-nova" 1.73.4, "oolite-thargoid-plans" 1.73.4, "oolite-tianve" 1.3, "oolite-trumbles" 1.73.4, "oreProcessor" 1.55, "OXPConfig" 1.08, "Pi-Forty-Two Con stores" 4.1.2, "Random_Hits", "SalezaPatrol", "SIRFYardStation0", "SIRFYardStation1", "SIRFYardStation10", "SIRFYardStation11", "SIRFYardStation12", "SIRFYardStation13", "SIRFYardStation14", "SIRFYardStation2", "SIRFYardStation3", "SIRFYardStation4", "SIRFYardStation5", "SIRFYardStation6", "SIRFYardStation7", "SIRFYardStation8", "SIRFYardStation9", "spy_hunter", "supercobra_placement", "System Redux 1.0" 1.2, "taranis_one", "TigersTurf" 0.52d, "transportschedule", "trident_down", "ups_container" 1.6, "ups_docs" 1.6, "ups_parcel" 1.6, "ups_slaves" 1.6, "ups_sun" 1.6, "vector" 1.3.1, "Welcome Information Script" 0.7
[dataCache.willWrite]: About to write data cache.
[dataCache.write.success]: Wrote data cache.
Most of these errors are probably case errors which I will fix manually once the main problem is solved but none are directly related to RS I think.
Posted: Sun May 16, 2010 4:37 pm
by Eric Walch
tinker wrote:The shipdata.plist from RS has this entry
Code: Select all
</dict>
<key>ferdelanceM2-player</key>
<dict>
As far as I can see these two lines are the same ship but the save games just give the yellow ?, if I persist in trying to load the game it starts a new game with a cobra, which does not crash as Eric says.
That ship and 1.73 worked for me. Originally its not RS but mPackRedux.oxp. In the wiki named as M-Pack (rusties). When installing that instead of RS things should also work. When not, there is some other weird thing happening.
EDIT: Updating commies.oxp will fix half of your warnings. But none of them should be fatal.
Posted: Sun May 16, 2010 5:16 pm
by tinker
Mmmm I removed RS and replaced it with M-Pack (rusties) and the save games still do not load, yellow ? instaed of ship.
I thought I had updated commies yesterday but obviously missed it, that did remove all the flasher errors. As you say these were not critical. One extra error did pop up with M-Pack (rusties) installed
Code: Select all
[shipData.merge.failed]: ***** ERROR: one or more shipdata.plist entries have like_ship references that cannot be resolved: ATU, ATU-leader, batkov-shuttle, delaney-ship, enemy-nuke-bomber, esw-assassin, esw-gemini, esw-leader, nuke-bomber, playfair-ship, saiph-escort
Not sure where this error came from they are not part of M-Pack (rusties).
Posted: Sun May 16, 2010 5:18 pm
by Thargoid
Can you upload your save game file somewhere so we can grab a copy and test run it ourselves and check for errors?
Posted: Sun May 16, 2010 6:40 pm
by tinker
Not sure if this will work but try
http://rhima.net/Tinker.oolite-save
I think you will need to right click and save as.
Posted: Sun May 16, 2010 7:50 pm
by Eric Walch
Your save file is fully correct. I don't have RS but I have the rusties installed. It opens and launches with the fer de lance without a problem when using 1.73.4.
..
Posted: Sun May 16, 2010 8:26 pm
by Lestradae
Hi tinker,
Welcome back & sorry to hear about your problems.
If you have the old RS V3.02b, that one should work fine, if you need it again drop me a PM and I give you a download link.
Whatever the problem, as the ship keys in your savegame and in shipdata plist are the same, I suspect the problem to be something else - if the original rusties work, RS supposedly should, too.
No idea what could be the problem
Posted: Sun May 16, 2010 9:59 pm
by tinker
I think maybe I will try to d/l the source and build again.
Solved
Posted: Mon May 17, 2010 10:52 am
by tinker
I had installed via synaptic from the unofficial repository, I have now used the x86_6a package using the Autopackage Software Installer and the saved games now load OK.
It seems the error lies with the deb installer.
Re: Solved
Posted: Mon May 17, 2010 11:11 am
by Lestradae
tinker wrote:... I have now used the x86_6a package using the Autopackage Software Installer and the saved games now load OK
