[propbeanie]

Originally Posted by Gray Lensman

Okay... What I meant by "temporary deletion" of the Users/Name/Documents/SH4/ folder was to Cut and Paste it elsewhere on the hard drive so that Silent Hunter would create a new one in its place. When that was done, I reentered the game and just temporarily started a new career to see if the "sonar" UI bug described previously persisted. It didn't, which indicated that the bug was in a corrupted file in the SH4 folder that I had pasted aside. When I had confirmed that the "new" /SH4 folder was not corrupted, I deleted that new /SH4 folder and copy/pasted the bugged /SH4 folder back in place, restarted the game, loaded up a previously saved game and checked it one more time and the sonar UI bug was back. So "Yes" you can temporarily delete the folder for testing purposes and restore it when done testing. I just didn't "advance" the game beyond retesting the saved games for this "sonar" bug to isolate where the corrupted file might be located. (Basically, since it was affecting ALL the previously saved games, I wanted to know if a file in the Steam installation folder had been corrupted or the /SH4 folder)

This "mouse" UI sonar bug, once introduced affected all the half dozen or so saved games that I had previously made "that had been just fine" until the bug was introduced, so it wasn't the actual saved game files themselves. It had to be in one of the other files in the /SH4 folder itself that had been written to and corrupted such that it universally affected ALL the previously saved games, not just the last one. I've had saved game corruption errors before, but only rarely and it usually only affected the one particular saved game and maybe persisted in those that follow, NOT those made before the corruption took place.

1. SH4 installed in the Steam folder (Not in Program Files AND neither is Steam. I've been running SH4 in Steam for at least 5 years or more with no problems.
2. My OS is Windows 10 64-bit AND I'm running the LAA SH4 executable. Again, no problems for 5 years playing TMO.
3. Each time I encounter these corruption bugs. I totally uninstall/reinstall SH4, Wolves update, and recreate the Mod folder from scratch. I also delete the /Users/Name/Document/SH4 folder.
4. I was attempting to use the 100_FalloftheRisingSun_UltimateEdition_v1.24_EN version.
5. Circumstances described above in previous post.


Not trying to "dis" on FOTRS. It looks and feels fantastic compared to TMO, and the additional content is fabulous, but it gets very aggravating uninstalling/reinstalling after corruption bugs which seem more numerous in FOTRS than TMO. My 2 cents, and I could be wrong, but it appears this MOD may be attempting to actually do too much in regards to data writes to the /SH4 folder, maybe a timing issue when the sub status data gets written/rewritten/overwritten.


edit> Trying to decide if I really want to continue with FOTRS or not. I could mitigate the corruption issues by literally copying the entire /SH4 folder and renaming and date/time stamping elsewhere each time I saved but that might be more trouble than it's worth. I really like the added content and graphics.... Hmmm... decisions, decisions... ah ha, .bat file(s) may be useful.

OK, the sonar bug is different from what is usually found in a broken "Stock" game, and is definitely not part of FotRSU... You have the install in what looks to be a good location, and all other descriptions seem to be correct. All I can suggest to try is to make certain that the LAA did indeed set correctly on SH4.exe. The SH4.exe file cannot be write-protected. If you load it back into LAA once again, and see if it is indeed "True". Beyond that, cross-contamination in the Save folder is about the only way I can think that you are getting this trouble...

Originally Posted by Macgregor the Hammer

I'm up and running! 2 items may be responsible:

1. I MAY NOT have run the basic SH4 install before I installed the mods. I'm pretty sure I did though.

2. One of the mods was corrupted and may have mucked up the works.

This time, I installed 1.24 tested then the patch and tested, then each mod. Kind of long way around but the only sure way.

Thanks!

I have trouble with the "camera" mod on my Win10 laptop, but not on the desktop - which I do not understand...

Originally Posted by torpedobait

See Thumbnail - skin on this torpedoed Aux Transport is the weirdest I've ever see in any version of SH3 or SH4!

Patrol History: USS Gato (SS-212) left Brisbane on 05/24/1943 to patrol the Bismarck Sea for 5 days. Arrived in Patrol Area and on 06/04/1943 at approximately 0700 encountered 2 enemy vessels, a Medium Modern Composite Freighter and an Aux Transport, travelling side by side in stead of in trail as I would have expected. No escort. Location was 149-00E; 01-34S.

Set up at 90 degrees to their course and let them each have one Mk14, low speed, contact detonator. Both were hit and exploded. The freighter blew up normally and started sinking. The Aux Transport gave out a truly massive blast so big the normal explosion effects were greyed out by an apparent round ball of gas. After the explosion cleared I could see the remarkable skin that was left. Looks like a drunken circus clown tried to paint it to look like a long Rubic's Cube.

There's no harm done, except it does not look right. Perhaps one of the Skin Guys could look it over and find something to fix, in their copious free time, of course!

Generic Mod Enabler - v2.5.0.150
[G:\Ubisoft\Silent_Hunter_IV\MODS]

100_FalloftheRisingSun_UltimateEdition_v1.24_EN
101_Patch_v1.2To_v1.26p
399_NoScrollNavMap
450_Lite Fog v2 + 300' Underwater Visability
452_MoonlightzSonarLines
801_UMark Invisible
901_strategic_map_symbols

That is an old damage model on your Auxiliary Transport... Here is what I get when I run a mission with it:

3rd Torp hits amidships on Auxiliary Transport, one dud on bow, one exploded on rudder

Damage on hull below the water line on Auxiliary Transport.

Traveling companion Medium Modern last gasp after 3rd hit, 2 of which exploded

Looking back at Auxiliary Transport as it plummets beneath the waves

After all is said and gone

I am not 100% certain, but when you get finished with your campaign, I would do a full fresh SH4, v1.24 & 1.26p, and the mods you'll use, empty the Save folder, and then do a new career. The only way I have been able to corrupt my game, and thus far it is with little visual "glitches", is by doing Discord with s7rikeback while testing (lots of shelling-out to Windows), and by adding mods, such as 301_MoreDifficultAI01 or 399c_NoScrollNavMap - Same Sized Dials, while on patrol and not in the office...

My one piece of advice is to only apply mods while in the Captain's Office, and I'm not even certain about that anymore... We've been experimenting with a flag mod, changing mod configurations while underway, and changing something as simple as the flag while on patrol can apparently cause issues under certain situations...