SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
|
|
Thread Tools | Display Modes |
|
01-16-19, 01:12 PM | #1 |
XO
Join Date: Mar 2007
Location: The FREE State of FLORIDA
Posts: 401
Downloads: 217
Uploads: 0
|
The "Quit/Start/Load/Reload" Issue (FOTRSU)
For those interested, and, for those unfamiliar with this "issue," the "issue" is a failure to (serially) "re-load" a save game with Waypoints, Celestial Sphere, Navigation marks etc, accurate, correct and intact. I call it the "Quit/Start/Load/Re-load" test. The save games either "Pass" the test by Quitting the game, Starting the game, loading correctly and then re-loading correctly (Q/S/L/R) , or, "Fail" the test by Quitting the game, Starting the game, loading correctly once, but then failing to re-load correctly a second time (Q/S/L but NOT /R.) For example, waypoints missing, navigation marks missing, daylight when the Base time clock accurately indicates night time hours, etc.
My latest testing results reveal that it appears to only affect some versions of FOTRSUv* and only Campaign Careers starting Jan. 1, 1944 or later out of Pearl Harbor. It is not a failure of the save game data. It is a failure to re-load the exact same data (a serial re-load) that was just previously correctly loaded. I discovered this issue because I have a penchant for listening to Fred's Radio Stations while I am playing the game. While loading up a save game to start playing my session, the Radio came up already playing upon loading the game as it sometimes does. In times past, I could simply "re-load" that very same save game or a save game made just before (or after) with no problems. The "Radio already playing" bug is similar to the "Passing thermal layer" bug and sometimes requires a re-load of the save game file. When I re-loaded the save game, the Radio came up correctly, meaning that it was in the "Off" state, but, I had lost all of my navigation waypoints, and although I had saved at Sunset, the skies outside were now bright daylight with the Sun high in the sky, even though my Base time clock indicated it was "time" for sunset. To discover this issue I had to be loading up a (FOTRSU) savegame from a Campaign Career, starting out of Pearl Harbor on Jan. 1, 1944 or later, and found it necessary to serially re-load an already successful (except for the Radio bug) save game. It helped that the savegame was made at Sunset, so after I had serially re-loaded the savegame, I went to the external view, and low and behold my beautiful sunset scenery was missing and it was broad daylight. Many, many, many tests later and I believe that I have narrowed it down to "something" in the FOTRSU Campaign layer which affects only those Campaigns starting out of Pearl Harbor after Jan. 1, 1944. propbeanie is hard at work helping me find the culprit! Anyone else who has experienced similar behavior and/or is simply interested in helping us track down this "bug" is more than welcome to chime in. Thanks.
__________________
"It is well war is so terrible, lest we should grow too fond of it" - C.S.A. General Robert E. Lee "Only the dead have seen the end of war" - Plato Gone but not forgotten, RIP Dave "LeoVampire". |
01-16-19, 02:54 PM | #2 |
Navy Seal
|
That's a weird one. No mod can mess with the game save routines as they are hardcoded in the .exe file. So when we find out what's working it's very doubtful whether we can do anything about it. At least the savegame routines aren't as bad as SHIII. But they can be wonky, for sure.
__________________
Sub Skipper's Bag of Tricks, Slightly Subnuclear Mk 14 & Cutie, Slightly Subnuclear Deck Gun, EZPlot 2.0, TMOPlot, TMOKeys, SH4CMS |
01-16-19, 03:56 PM | #3 |
The Old Man
Join Date: Apr 2005
Location: New Orleans, LA.
Posts: 1,364
Downloads: 475
Uploads: 11
|
Aye, i could never get a modded SH3 to load a save game without crashing. I always had to play missions in one go.
|
01-16-19, 05:02 PM | #4 | |
Sea Lord
|
Quote:
|
|
01-16-19, 08:30 PM | #5 | |
XO
Join Date: Mar 2007
Location: The FREE State of FLORIDA
Posts: 401
Downloads: 217
Uploads: 0
|
Quote:
[EDIT] If hardcoded, it would affect SH4 Stock, TMO, RFB, TMO/RSRD, TMO/RSRD/OTC/ISP, etc. It doesn't. Also, it doesn't affect FOTRSUv63. However, it does affect FOTRSUv71 and v80. Propbeanie mentioned the simulated "International Date Line" as a possible culprit. The thing is that Midway Campaigns work OK and Midway is East of the IDL. So, IDK. I'm wondering if there is a file in the "Documents/SH4/data/cfg" folder preventing the second load from reading into RAM correctly, in other words, portions of the RAM that have the correct information are being overwritten by Campaign start "default" information. No waypoints, no nav marks and 1300 Daylight sky. [EDIT] Perhaps "save.tmp" ?
__________________
"It is well war is so terrible, lest we should grow too fond of it" - C.S.A. General Robert E. Lee "Only the dead have seen the end of war" - Plato Gone but not forgotten, RIP Dave "LeoVampire". Last edited by Front Runner; 01-17-19 at 09:16 AM. |
|
01-16-19, 08:32 PM | #6 | |
DILLIGAF
Join Date: Feb 2007
Location: florida
Posts: 2,058
Downloads: 210
Uploads: 0
|
Quote:
__________________
Self-education is, I firmly believe, the only kind of education there is. ~Isaac Asimov~ Mercfulfate 将補 日本帝國海軍 |
|
01-17-19, 12:31 PM | #7 |
XO
Join Date: Mar 2007
Location: The FREE State of FLORIDA
Posts: 401
Downloads: 217
Uploads: 0
|
Test Results SH4 (Stock) FOTRSUv63 v71 v80
Simply put, a career started out of Pearl Harbor in January of 1944 using SH4 WOTP (Stock) and FOTRSUv63 "DO NOT" exhibit the issue. Both career starts begin at 1400 hours outside the harbor.
A career started out of Pearl Harbor in January of 1944 using FOTRSUv71 and FOTRSUv80 "DO" exhibit the issue. Both career starts begin at 1300 hours outside the harbor. The genesis of the problem seems to coincide with moving the Pearl Harbor career start time from 1400 to 1300.
__________________
"It is well war is so terrible, lest we should grow too fond of it" - C.S.A. General Robert E. Lee "Only the dead have seen the end of war" - Plato Gone but not forgotten, RIP Dave "LeoVampire". |
01-18-19, 12:46 AM | #8 | |
Silent Hunter
|
Quote:
im not calling you out but that doesnt make sense.
__________________
there are only two things in the world: submarines and targets. Fortis et stabilis et fidelis, semper ------------------------------------------------------------ Silent Hunter 4 1.5 Gold Edition on CDROM LAA enabled Dell XPS with 32 GB Ram running Win10 |
|
01-18-19, 07:40 AM | #9 | |
XO
Join Date: Mar 2007
Location: The FREE State of FLORIDA
Posts: 401
Downloads: 217
Uploads: 0
|
Quote:
Think of the failure of the second re-load as almost a CTD.
__________________
"It is well war is so terrible, lest we should grow too fond of it" - C.S.A. General Robert E. Lee "Only the dead have seen the end of war" - Plato Gone but not forgotten, RIP Dave "LeoVampire". |
|
01-18-19, 11:21 AM | #10 |
CTD - it's not just a job
|
It's an "internal data corruption", and I'd say it's similar to trying to switch from running The Museum and then going out on Patrol, or vice versa, where you try to run The Museum after having been on patrol. It usually does not "function as intended", apparently due to certain memory locations used by the game not getting "zeroed-out", or re-set if you will.
I have tried all sorts of different edits with several files in the mod that are different between v0.63 and v0.71. All that I can say conclusively is "don't load a Save after having loaded a Save." If you have to load a Save again, exit the game and try again. I have done several Starts in three versions (63, 71 & 80), and in each of them, upon loading a new career (emptied Save folder, new skipper name) I have gone to the NavMap on my boat, layed in a course to the southwest to the 20th parallel, and directly West from there, and then making a total of five waypoiints in the different versions. I then travel until sunset, stop the boat, take a picture through the Observation Periscope, Save, then exit. Start the game again, Load the Save and check the state of the game. In all three versions, everything is fine. Re-load the same Save, and in v0.63, everything is fine. In v0.71 & v0.80, it is now daylight-looking, still at about 1700 though, the sun is now at 295° instead of 335°, and elevated a good bit, just like it was at 1300 hours. The game has gotten confused. Of note, the Save in v0.71 & v0.80 is 368kb, while the Save in v0.63 is 276kb. Same sub, same name, same location, same number of waypoints on a very similar route, nearly the same traffic around Pearl upon departure, but nothing showing on sonar, radar or visual several hundred miles south and west of Pearl. Differences between the mods are Scout Planes on ships, and torpedo-shooting AI subs and ships... That's about it. For the time being, that is where I'm laying the "blame", is at the feet of the mod's data load size... I'm still "testing" though. |
|
|