[REL] Trigger Maru Overhauled Update BH

[KaleunMarco]

Originally Posted by Captain Wreckless

Yeah, I never had this many CTD before even with RSRD etc. I never even got to fire any fish.

I just tried again from a previous save and it happened again. This time the weather is crap, night with lots of wind and rain, and I never even sighted anything.

LAA is installed correctly. It created the save file, etc.....

Earlier I reloaded my save and snuck into Davao in crap weather at night and couldn't see anything. Well the IJN DD that ran over me and sank me saw me. This time when I sank, I got no CTD.

PC specs: MSI Laptop w/ Nvidia RTX 2060 and intel GPU; 32 GB Ram; 1 HDD, 1 SSD, 1 Hybrid SSD. This laptop will play any game on high graphics without any problems.

SH4 is set to use the Nvidia card only.


I'm trying different things to try and pin down what is happening. Sure wish the game created a crash file that I could read and see what is going on.

the only time i receive "unexplainable" CTD's is when:

1. i have changed mods or mod settings between missions in a career and i have not remembered to delete the cached files in the Save folders.
2. when Microsoft decides to run some sort of esoteric job and sucks up CPU cycles and creates hard drives delays. This creates CTD's because the UBI-designed simulation cannot seem to handle the competition for resources.
3. a corollary to the item above is how much/many unnecessary apps are running in the background, eating away at your under 4 gig memory. the fix for this requires that you know how to use Task Manager. if you DO know how to use it, i suggest that you run TM and look at all of the crap that your installation has for "updates" and "monitoring" and terminate them. suggestions are: Adobe Acrobat Update, HP Printer Ink Monitor, your pc-manufacturer's data collection monitor, etc. what you choose to remove is entirely up to you. if you mess-up and stop something that you need, just reboot.
4. when your under-4 gig memory is fragmented to a degree that the UBI-designed simulation cannot seem to acquire a chunk of memory large enough to satisfy its requirement, you should use the fix of last resort: reboot.

[Bubblehead1980]

I went to Davao a few minutes ago, no CTD for me with the invasion force.

[Captain Wreckless]

Originally Posted by KaleunMarco

the only time i receive "unexplainable" CTD's is when:

1. i have changed mods or mod settings between missions in a career and i have not remembered to delete the cached files in the Save folders.
2. when Microsoft decides to run some sort of esoteric job and sucks up CPU cycles and creates hard drives delays. This creates CTD's because the UBI-designed simulation cannot seem to handle the competition for resources.
3. a corollary to the item above is how much/many unnecessary apps are running in the background, eating away at your under 4 gig memory. the fix for this requires that you know how to use Task Manager. if you DO know how to use it, i suggest that you run TM and look at all of the crap that your installation has for "updates" and "monitoring" and terminate them. suggestions are: Adobe Acrobat Update, HP Printer Ink Monitor, your pc-manufacturer's data collection monitor, etc. what you choose to remove is entirely up to you. if you mess-up and stop something that you need, just reboot.
4. when your under-4 gig memory is fragmented to a degree that the UBI-designed simulation cannot seem to acquire a chunk of memory large enough to satisfy its requirement, you should use the fix of last resort: reboot.

#1. Not an issue. I normally don't do this.
#2. Possible
#3. I close all background running apps. I even have a program that does it for me. But possible some didn't close.
#4. I will remember this.


I'm still experimenting with some settings to trouble shoot.

[Captain Wreckless]

Originally Posted by Kal_Maximus_U669

Hey Captain Reckless..
Personally, I only use the 4go patch, as I said, it works much better for me... it's been a long time since I gave up the LAA...
it is true that backup problems are recurring when it starts...!!lol..
you have a solid config... but pay close attention to your windos and control what is running for nothing in the system... it eats your "Ram" for nothing can also be one of the causes of the problems...

The 4GB patch will only work on the gu.exe file. It says it can't open the sh4.exe file. If I start the game using gu.exe I notice it makes backups of gu.exe and sh4.exe.

Using LAA I use it only on sh4.exe, though I did use it on gu.exe this last time also. Save file shows both.

I'll play around with the 4GB patch and see what happens.

[Sandman_28054]

Great game so far, however.

I have noticed that returning to base, if I exit to main menu, go to the museum (yes I knowm the old "cheat" factor), then try to load the saved game, it crashes.

Fix?

[Pez volador]

Originally Posted by Bubblehead1980

Do you mean M35Hansa? Aka SEIA MARU? I don't see a H35Hansa on the roster. If so, I will check into it and see if model needs some adjustment.

That's right, it was a M35Hansa. 7590 ton. He is cultivating barnacles now

[propbeanie]

Originally Posted by Sandman_28054

Great game so far, however.

I have noticed that returning to base, if I exit to main menu, go to the museum (yes I knowm the old "cheat" factor), then try to load the saved game, it crashes.

Fix?

The game cannot go from one "mode" to another without restarting the game. In other words, playing the campaign, exit the game and then go into the Museum. After the museum, exit the game and try to load your Save. Otherwise, the game does not give up the resources the one part uses when you load the next, and you then run out of buffer for the game and it crashes. Old DirectX v9.0c game, only worse...

[Bubblehead1980]

Originally Posted by propbeanie

The game cannot go from one "mode" to another without restarting the game. In other words, playing the campaign, exit the game and then go into the Museum. After the museum, exit the game and try to load your Save. Otherwise, the game does not give up the resources the one part uses when you load the next, and you then run out of buffer for the game and it crashes. Old DirectX v9.0c game, only worse...

[Captain Wreckless]

Originally Posted by Sandman_28054

Great game so far, however.

I have noticed that returning to base, if I exit to main menu, go to the museum (yes I knowm the old "cheat" factor), then try to load the saved game, it crashes.

Fix?

It crashes even if you just go to the museum. Unmoded no crash. With the mod it crashes. It loads and then CTD after if finishes. Not a big deal.

[Captain Wreckless]

Does anyone enable Vsync in game options? I never use it. Seems games run better. My refresh rate on my laptop is 144 Hz anyway.

[Bubblehead1980]

Originally Posted by Captain Wreckless

It crashes even if you just go to the museum. Unmoded no crash. With the mod it crashes. It loads and then CTD after if finishes. Not a big deal.

Museum typically crashes only when on my end when try to enable it (as propbeanie mentioned) after running the sim. Occasional CTD does happen either way. The museum is quite sensitive to roster changes etc, which are abundant in the mod.

Museum is very sensitive lol.

[Captain Wreckless]

Originally Posted by Bubblehead1980

Museum typically crashes only when on my end when try to enable it (as propbeanie mentioned) after running the sim. Occasional CTD does happen either way. The museum is quite sensitive to roster changes etc, which are abundant in the mod.

Museum is very sensitive lol.

I figured with all of the changes from the mod that's what was happening.

[Bubblehead1980]

Some screenshots from V2.0.

Patrol was in Sea of Okhotsk in May-June 1944 with USS BARB SS-220.





Patrol area.



Crew morale was listed as "broken" or "shaken" for many after a severe depth charge attack.



Bow of Chidori hit by torpedo. Night surface attack from 3000 yrds. Target slowed in heavy seas, causing torpedo aimed for middle of target to hit the bow. Vessel was badly damage, traveled slow but managed to escape thanks to dawn breaking early in the polar areas, foul weather setting in. Then clearing, arrival of two DE called in to help after dawn, as well as a patrolling aircraft preventing from closing target. (see report) .


Small AK sinking after single torpedo hit (blew up nicely)





DC splashes.



Empty raft after sinking of small merchant. Raft was launched just as vessel capsized. Initially had a lone crew member in it. By time BARB surfaced to close, the raft was empty. Heavy seas so assumed the survivor was washed out.



Lone survivor, soon washed out of raft.



Rendezvous with USS Herring in Sea of Okhotsk 31 May 1944 1000.
(Wolfpack operations)


PBY at Midway



Shaken crew (see cursor on morale)





Storms in sea of Okhotsk



Fired a "up the kilts" shot with AOB 180 but unfortunately the drift of the Chidori in heavy seas, torpedo ran down the port side.



Wolfpack message received on convoy. Entire three ship one escort convoy sunk.

AI sub (packmate) "Herring" damaged one AK (had a hole in side of it when I located it) and crippled the escort (props and rudders blown off, later located). BARB sunk all three AK and the escort. Escort sunk by gunfire after dark after torpedo run below, showing draft too shallow.

[KaleunMarco]

Originally Posted by Captain Wreckless

Does anyone enable Vsync in game options?

in a word, no.

[Bubblehead1980]

Originally Posted by KaleunMarco

in a word, no.

Forgive the ignorance of the question lmao but what exactly does vertical synch do? ( I mean I have a idea but)