FOTRS Ultimate Edition Limit Time Compression?
 

Alright, hopefully an easy question here...

Does FOTRS prevent you from reaching time compressions greater than 4096x? I found the main.cfg file, changed the maximum value at the bottom of the time compression section to 8192. It made no difference. Is that something that can be changed elsewhere? Just trying to cut down the time for long journeys...

Go into your save game folder in your documents and choose the sh4 folder
There is another main u need to modify with the same nr 8192

Ailly,

there has been considerable discussion on the effects of Time Compression when playing FOTRSU as well as other mod-sets. you should check out the main discussion forum for that release and read it for yourself. https://www.subsim.com/radioroom/showthread.php?t=243064

it is the concerted opinion of many of us-Kaleuns that 1024 is the highest "safe" TC you should use while playing. as the forum discussion will show you, many odd and bad things can occur when a player uses higher than 1024 TC.

whatever you decide, good luck.
:Kaleun_Salute:

Are these bad things merely contact related, or something more seedy? Compression rarely gets above 1024 if there's any chance of enemy contact. The 8k compression is for the long trans-oceanic voyages.

Time Compression (TC) is very, very computer dependent. But the relative "strength" of the computer isn't as important as its configuration. The more that runs in the background on a computer while playing an SH game, the more issues that will be encountered. Member Front Runner a while back was running into issues with his install of FotRSU. If you really want to get bored to tears (unless you find the details and findings as we went interesting, of course), refer to "Base Time 2018".

Suffice to say, the game is an old DirectX v9.0c game, and a lot of its internal code uses dll library files in DirectX v9.0c for its "timing". The old "target", if you will, was a display that showed 30 frames per second, based upon the display card's "clock". Newer vid cards run much faster than the old cards of even just a few years ago, and that "clock" does matter to the game. Further complicating things is the temporary buffer "streams" used by the game for video, audio, and memory management (among other resources, I'm sure). The 'modern' OS uses "virtual space" much more than XP did, which is what SH4 was written to, and things can get mixed-up there, which is why it is recommended to not swap out to Windows while playing the game.

Then just the math of TC comes into play, as you suggest, with the "contacts". I have seen instances where the submarine had traveled completely beyond the contact, suffered damage from the enemy, and is then in a sad state. We used to have the game capped at 2048x TC, and still recommend a player use no more than 1024x, but have since raised the max to 4096. All of those "streams" used by the game can and do get out of "sync" with each other, and most times after the use of high TC (which "high" is relative for the computer), you will lose audio that doesn't restore until after a Save, Exit, restart & Load, and all sorts of graphics anomalies might be encountered. Even the AI response can be thrown out of whack. Again, computer dependent. If you want to raise it to 8192, you edit the "Main.cfg" in the Data / Cfg folder of the game, prior to starting a career. If you are already playing, you would have to find all of the instances of "[Time Compression]" in the Save folders, which are usually in "C:\Users \UserName \Documents \SH4", unless you've used MultiSH4, and then it would be whichever folder you used there.

bad thing about tc if it don't slow down for a contact you miss it or get damage blown out of the water or run into a island that you didnt see on the map

IMO, more seedy.
For example, sunrises and sunsets have their times moved to ungodly hours.