[REL] FOTRS Ultimate Project

[merc4ulfate]

Originally Posted by propbeanie

I sailed from Midway, January 14, 1943 merc, went to Kyushu via the Mariannas, and now I'm going northeast along the coast, pretending to be the Galloping Ghost... no issues whatsoever thus far. I have noticed one thing though: if you use TC over 2048, the audio stream can and does go whonky at times, just like in Stock... I have not sunk anything yet, thank you very much BuOrd... sheesh. Two under-runners, and two klunkers... No explosions even.

What are your system specs merc4ulfate? Are you certain that the LAA is set correctly on the SH4.exe file? Do you ever "shell-out" to Windows with the Windows key, the <alt> or <Ctrl><Tab> combinations? Even if your game is "paused"

Windows 7 Professional 64 bit
Intel Pentium Dual 2.4GHZ
8 Gigs Ram
GPU Radeon R7 360
All drivers up to date
4gig patch
The game is installed on a non system 500 gigabyte SSD drive 200gig Volume
The game is ran from a clean install with only FOTRSU as a mod.


My mother told me before I was born she wasn't going to let me out of her unless I promised never to shell out of Silent Hunter 4. I never do it.

[hauangua]

Hmmm.... is it just me or many "strange bugs" have one thing in common ... ssd ?.....

[Fifi]

Originally Posted by hauangua

Hmmm.... is it just me or many "strange bugs" have one thing in common ... ssd ?.....

I had plenty strange issues installing SH3 on my SSD ... i solved it installing back on normal drive
SH4 might be same « delicate » boy... only SH5 seems to appreciate SSD drive here.

[hauangua]

Originally Posted by Fifi

I had plenty strange issues installing SH3 on my SSD ... i solved it installing back on normal drive
SH4 might be same « delicate » boy... only SH5 seems to appreciate SSD drive here.

Interesting this and in fact Sh3 and SH4 are practically "built on the same engine" while SH5 is completely different
capnscurvy, Jeff groove ,propbeanie ,gap or other experts
programmers could understand if it's just "random happenstance "

[merc4ulfate]

Originally Posted by hauangua

Hmmm.... is it just me or many "strange bugs" have one thing in common ... ssd ?.....

Interesting theory. What is it that you think might make the two incompatible? The fault code on my CTD can be caused by DEP, Ram, Physical Drives, Windows system file corruption, security update, etc. It is one of the most widely seen fault codes.

As for floating ships that is in the game or mod.

[propbeanie]

You know what they say, there's three things that are important - timing, timing and timing. I don't know if it would be a read and / or write cache on the drive itself, or what. I do know that they are faster than a regular SATA drive. Years ago, you didn't want write caching enabled on a hard drive for some of the old games, because that would confuse the games' internals somehow (my RAM is losing its charge, and I can't remember details... - a matter of little consequence at this time). Front Runner has an SSD, and tried disabling write caching on it, and that didn't matter, but when he swapped the install to a regular SATA drive, no problems. Go figure... I used to know all that stuff back in the DOS int13 and Norton Tools days, but now it's worthless info, lost somewhere in the dregs of the upper bucket...

[torpedobait]

Originally Posted by Sniper450

odd...my tc maxes out at 2048.

Check the "Main.cfg" in your SH4 file under "My Documents" or wherever your system keeps it. That overrides whatever is set by the base game and FOTARSU mod.

[torpedobait]

Originally Posted by Fifi

I had plenty strange issues installing SH3 on my SSD ... i solved it installing back on normal drive
SH4 might be same « delicate » boy... only SH5 seems to appreciate SSD drive here.

Hmm. I installed a new SH4 Gold downloaded from Amazon to the second of my two SSDs, this one to the (D just this last weekend. Works just fine, with no difficulties with the installation.

I reserve the first SSD (C strictly for Win7 and any "utilities", and use D: for games (in fact, that's what I named it). I now have both SH3 and SH4 on the D: drive. Both were easy and quick installs, and seem to run just fine.

Not trying to start an argument - just giving you my experience with multiple SSDs so far.

EDIT: Both drives are set to whatever settings were put in place by Falcon-Northwest. I never mess with them.

[propbeanie]

It would be interesting to know the different configurations of the different manufacturer's drives. There are some that have a conventional hard drive "attached" to the SSD. I'm thinking it might be more to do with write-caching on the drives, if it's enabled. I have not tried an SSD myself yet, so I am not familiar with them at all. I still have IDE drvies in most of my computers, and (not counting the laptops) only one is SATA only... My computing is stuck in 2010l... 'Course, my heart is still in the 60's, my lungs are in the 70's and my brains are in the 80's...

[Jeff-Groves]

Originally Posted by hauangua

Interesting this and in fact Sh3 and SH4 are practically "built on the same engine" while SH5 is completely different
capnscurvy, Jeff groove ,propbeanie ,gap or other experts
programmers could understand if it's just "random happenstance "

SH5 is not as completely different as you may think. Yes it has more bells and whistles. Has some different things added to enhance or update it.
Some improvements here and there.
However.
It's still built on the same base code as Sh3.
They didn't re-invent the wheel. Just took it from wooden era wheels to a modern day steel belted radial.
And it still gets flats!


On the SSD issue? I don't have that issue. I run SH3/4/5 off my SSD and have no issues.

[cdrsubron7]

On the SSD issue? I don't have that issue. I run SH3/4/5 off my SSD and have no issues.

Same here.........

[hauangua]

Originally Posted by cdrsubron7

Same here.........

Ok thanks for the feedback mates, ssd is not guilty

[Front Runner]

Originally Posted by hauangua

Ok thanks for the feedback mates, ssd is not guilty

I'm running a career on my C-Drive (RAID 0 SSD) other than the Q/S/L/R issue, which is now "suspended", the game runs OK. I'm still keeping my Frame Rate at 30 fps. Note: this is an "old" career started before the Q/S/L/R "fix."

[gutted]

SSD here and no issues either.

[propbeanie]

Empirical evidence suggests no issues with SSD, as compared to SATA (or IDE ). Does anyone else have CTD as merc4ulfate has, as in

Originally Posted by merc4ulfate

Hey Prop I just had my third CTD

I can't tell you exactly where I was. I left midway Dec. 1942 and was off Hokkaido for a five day stay at the Tojo Astoria. It is now Jan. 1943

I had found some rich fishing and had about 50,000 tonnes. A German Large Oiler and Diasura (or something like that) 25mm Were two of the many ships to go down. The Diasura (SP) was a tiny gun boat with AA cannons. I sank it with one deck gun hit at 4000 yards. It did not ride in the water properly however:



YES IT IS OUT OF THE WATER


Upon leaving the area I was spotted by two fighter bombers and dove to avoid them. At about 60 feet the game crashed.

Same fault I had on the last one. c0000005

Another odd issue I discovered was the Diasura at periscope depth was spotted 7900 yards away by the crew while a merchant 1000 yards off my bow was not reported.

-or-

Originally Posted by merc4ulfate

Darn another CTD.

Aug. 1942 leaving Midway in a Gar Class heading to 11-B clear sailing until I was about 85nm from the star then crashed with a c0000005 error.

Faulting application name: sh4.exe, version: 1.5.0.0, time stamp: 0x476a5ca9
Faulting module name: sh4.exe, version: 1.5.0.0, time stamp: 0x476a5ca9
Exception code: 0xc0000005
Fault offset: 0x0017fa3f
Faulting process id: 0xafc
Faulting application start time: 0x01d4b014f1352c2c
Faulting application path: D:\Silent Hunter 2019\sh4.exe
Faulting module path: D:\Silent Hunter 2019\sh4.exe
Report Id: 7e2e7851-1c0e-11e9-b219-8c89a588d336

Rerunning the mission to see if it replicates.

-or-

Originally Posted by merc4ulfate

I'm running the Gar out of Midway and I have had one CTD while on patrol. No CTD with Tambor. Could be a whale fluke.

KaleunMarco did find an issue with a Polar Circuit mission (Patrol Patrol_Kuriles_03) assigned out of Midway, that had an Objective name in the mission that did not match the name in the TSR, which would most likely cause an issue. The mission orders read:

Search the designated area for five (5) days continuous time, East of the Kurile Islands. Conduct anti-shipping operations if any enemy presents themselves. Report any and all enemy activity immediately. Be on the look-out, and be careful of Russian vessels. They are NOT to be sunk.

So if you got that, it could be the cause. This is in a tentative "fix" in the pipeline now...

But let us know of any CTD or other issues SAP please!