Logging Out-of-Realtime Physics Freezes [public-test]

@Neawoulf AVX is not a problem to you, just noticed at you are running on Ryzen, different thing on there.. Probably not using NUC either..no NUC used on GB boards, MSI will use..
 
That's a lot of info, thanks! Will test some of that some of that later. I already did those changes to the player.JSON file, but maybe disabling that RAM compression helps.
 
OdeFinn said:
@M Lynn which tricks you have tried for fixing it?
Ok my case stutters originally started alongside with some windows update, after that I have altered several settings and current situation is stutter free.
Kinda list of my changes,
dropped older nvidia driver (439 if recall right) because then newest wasn't working fluently with shadow play and older gives better performance.
Disabled cpu's "external" SA sniffer, chip on mboard, controlled thru USB2 logic (this makes dirt rally 2 stutter a lot)
Lockeed AVX 1:1 with cpu multiplier
Updated ignore list on antivirus
Switched off windows disk cache flush
Switched off replay compression - game
switched off texture compression - game
Switched off background delay timer - game
Switched off windows RAM Compression

What things you have tried?
Click to expand...

Thanks for the suggestions.

I've tried a lot of things, more than I should need to for a game that should work well with default settings. Most of this stuff we are trying should never be needed.

I tried installing new drivers for everything, turning off plugins, different video modes, using third-party apps, various tweaks. Hours spent testing, reading forum posts etc. One thing I found that cured the micro stutters for me was buffering replays to RAM. But, I still get the big freezes that end with the car running into a barrier, often but not always around 33 minutes into a session. So annoying when on a quick lap, but if it happens in a race then your race is over.

A lot of those things you mentioned are platform-specific so don't apply to me. Of the ones that do, I've now added my rF2 folder to AV exclusions, so we'll see on that one (not expecting much), I won't turn off disk cache flush (I shouldn't have to and I won't risk data loss), I've already tried turning off replay compression, I can't see windows RAM compression affecting anything but I'm willing to try it, I'll also try texture compression. Background delay timer is a new one on me, where do I change that please?
 
M Lynn said:
I won't turn off disk cache flush (I shouldn't have to and I won't risk data loss),
Click to expand...
Risk of losing current replay or other just waiting to be writed stuff isn't big deal, it just sounds scary thing, but actually it isn't, if you want to make sure at that is not a case, then do it a safe way, switch off entire caching for test, then you don't have any risks. That is the upper checkbox.
M Lynn said:
Background delay timer is a new one on me, where do I change that please?
Click to expand...
Player.json around 207 row.
 
Ah, you mean Inactive Sleep Time? Can't see that helping, it only does anything when rF2 isn't the active application.
 
New log. I turned off texture compression, went into a session, 33 minutes later, surprise surprise, big freeze and crashed into a barrier. So, texture compression does nothing to fix this problem for me. The full log and replay are here https://www.dropbox.com/s/1hfz4fu4rcv38qi/Zandvoort Freeze at 33 Minutes.7z?dl=0

The freeze is at the end of the replay.

Note the remaining time on the dash of a 2 hour session.
 

Attachments

  • Clipboard Image.jpg
    Clipboard Image.jpg
    239.2 KB · Views: 294
Last edited:
M Lynn said:
New log. I turned off texture compression, went into a session, 33 minutes later, surprise surprise, big freeze and crashed into a barrier. So, texture compression does nothing to fix this problem for me. The full log and replay are here https://www.dropbox.com/home/Public?preview=Zandvoort+Freeze+at+33+Minutes.7z

The freeze is at the end of the replay.

Note the remaining time on the dash of a 2 hour session.
Click to expand...
It would be very good if you could share the link to the file. Not sure if this is your local link and it works. But we cant download it.
 
@M Lynn even some of those doesn't feel to make sense, please test all, then you know and us at those aren't your case.
I had freezing problems, not anymore, those are things what I did and get it end.
That repeatable ~30min sounds to me lot of data io problem, even disk writing, memory dumping, or even schedule memory scan, but definitely data io problem.
There is two windows services which are acting bit on that way, for testing those could be disabled, full memory scan, run by AT scheduler, and superprefetcher service, names aren't probably correct, but I can check those later and put here. Those aren't suggested by me, only for testing purposes, because those deactivate bit more windows functionality, nothing drastically.
 
@OdeFinn Thanks, I'll try your suggestions. I'm aware of superfetch and I have that enabled, not sure about full memory scan though. I agree that it could be IO related.

@Jimmi Allison I'm on the current non-beta branch at the moment, old UI.

@lagg Thanks, I've just looked at that thread. Sounds like the same problem, although it also happens offline.
 
OdeFinn said:
Windows+rf2=mismatch, props to microsoft.
Still going to data io, memory io, disk io, all are data io :), windows wants to do something what makes cpu hang on simultaneous processes, fighting cpu time.
Click to expand...

You could be right. It can't all be down to Microsoft though, other games aren't doing it, there must be some sort of workaround.
 
M Lynn said:
You could be right. It can't all be down to Microsoft though, other games aren't doing it, there must be some sort of workaround.
Click to expand...
Rf2 base is older than any current other sims, older than win10 and tweaks inside windows memory management. Probably some urgent 0day vulnerability patch broke something.. Who knows, but I'm willing to believe at main reason is on windows and they broke something old what rf2 is still actively using.

lagg said:
Yes but why at the same time?
It's strange.
Click to expand...

There's ton of different timed triggers on AT scheduler tasks, huge amount of different triggers waiting to break when we're gaming.
Is it counting "idle" time wrong end launches something.. Who knows.
 
But why would Windows cause a freeze that always repeated at the exact same time while in the game? If it was something in Windows, you'd think it would trigger sporadically. This sounds like something that can only be fixed inside the game, actually there was an attempted fix at this here. I wouldn't waste time trying to turn Windows services off. Btw, there are lots of old games out there, iRacing has used more or less the same base for 10 years as well, so I don't think it's much of a problem.
 
@stonec and that occurs only few persons and few recovered from by rollbacking nvidia driver.. Well, dunno, just trying to help, mine is currently working fine, no stutters.. Maybe DDU?
 
Tried last night lot of different graphical settings for optimising VR and found two weird things (another old known, but not reported it before, coz windows/bios).
Starting point where everything works nice and fluently on 60Hz VR, just like train with nearly maximized graphics settings and 40 visible but "only" 19 AI + me on track, rain and track as Nurburgring Sprint.
Lift to 90Hz and started to drop graphics to get game frame renders match to needed "180 frames", everything went fine until I touch on AA setting, that broke whole game, after lowering from my AA5 setting first to 4 and then to 3 game was having just crazy stuttering, and it didn't recover from it at all, rolling all back to known fluently working 60Hz didn't help, constant stuttering was there to stay.
Recover from that I needed to shut down cpu totally and with known good settings aplied before starting game it recovered to normal state. Booting procedure neded tweak, as decribed below.

Another way to get random stutters was to start game aftet power up soon as getting windows desktop and stsrting game, if you came from cold start.
A way to avoid those is to start cpu from power off state to desktop and do a soft boot, aka rstart cpu from menu, this has been a normal thing for me a long time period, after BIOS introduced RAM timing autoconfig, it will do bit overoptimistic timings (sub timings) on cold DDR4 sticks, and that for I'm normally booting cpu up from cold to desktop and leaving there for few minutes (when all startup sheduled windows parts have run thru) and then restarting cpu and again letting it to run thru all startup stuff before starting any game.

So one windows/bios crap and one weird rf2 fail.. Is it on shaders?
 
You must log in or register to reply here.
Back
Top