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

For some time we are aware that a few people are having problems that cause the physics code to slow down or temporarily freeze. The consequence of this issue in online races is that your car will suddenly warp backwards, sometimes into the path of a following car. Because reproducing this was problematic, we have now enabled logging to help diagnose this.

If you think you are experiencing the issue above in an online or offline session, after the session ends, go to your UserData\Log folder where we will record one or more physics report files (.csv) for your last 5 sessions. By default, we only log some basic data, but if you know you have these issues, please open our player.json file and set "RealTimeLogging" to 1 (default is 0). That will generate more logging that should help us pinpoint the issue.

Here's a screenshot of the folder with these files:

upload_2019-3-19_16-23-28.png


Please upload your csv files, compressed (you will need to use Dropbox, WeTransfer or another upload service if the file size exceeds 30 MB). Additionally please upload the replay where you've had an issue, and if you can identify the approximate timestamp (ET) on the replay where it occurred that would help us a lot.

These tests no longer require a special beta: Select 'opt-out' in the betas menu.
Please keep uploading logs and reporting any issues with freezes.

Thanks from the S397 Team :)
 
Last edited:
Good to see the investigation being done. I’ve forwarded this to our league. :)

Some details on my side. It freezes once or twice each race here, and when it does multiple people on the server get a freeze between a few seconds from each other. Almost all freezes happen at either 20:35 or 21:05 or 21:35 and so on. So it looks like some sort of periodic thing that is causing it. Let’s hope these logs tell us more.
 
Last edited:
Same here, we've had issues in BVTCC on and off for last few seasons so we'll submit anything we can to help.
 
For some time we are aware that a few people are having problems that cause the physics code to slow down or temporarily freeze. The consequence of this issue in online races is that your car will suddenly warp backwards, sometimes into the path of a following car. Because reproducing this was problematic, we have now enabled logging to help diagnose this.

If you think you are experiencing the issue above in an online or offline session, after the session ends, go to your UserData\Log folder where we will record one or more physics report files (.csv) for your last 5 sessions. By default, we only log some basic data, but if you know you have these issues, please open our player.json file and set "RealTimeLogging" to 1 (default is 0). That will generate more logging that should help us pinpoint the issue.

Here's a screenshot of the folder with these files:

View attachment 21995

Please upload your csv files, compressed (you will need to use Dropbox, WeTransfer or another upload service if the file size exceeds 30 MB). Additionally please upload the replay where you've had an issue, and if you can identify the approximate timestamp (ET) on the replay where it occurred that would help us a lot.
Can the logging be completely deactivated too?
I would appreciate that, because i don't like unnecessary activities being done. :)
 
Can the logging be completely deactivated too?
I would appreciate that, because i don't like unnecessary activities being done. :)
hehe that's the first thing I checked while re-reading Chris' post, how to disable :) It should be neglegeable at 0 however :)
 
I my case, some times the image freezes for a few seconds, generating a sound loop, and after that the game reminds lagged the rest of the session. The only way to stop it is rebooting the game.
 
Just tested it:
Setting 0, which means off, generates a file already.
So i would like to have 3 options:
0 = deactivated
1 = generates a basic log
2 = generates an accurate log
@Christopher Elliott can we get that?

It's necessary I guess. 2h online alone on the server means ~200 MB written at exit (at 0 setting, setting 1 generates literally GBytes of logs).
 
Thankful for bugs being looked into but would be nice to not have files being generated for those that dont want it. Im on tight space with my dedicated SSD so please if we could turn this logging off completely that would be super nice.
 
Since they find the cause of the freezes/lag i don't mind, glad they're looking into this annoying old bug...
But i and also others do mind. ;)
No question, to have the possibility to log things is great!
But it also is great, to be able to deactivate it, if it's not necessary.
 
This is a great feature to have, but like others have said, it would be perfect if you could totally disable it when not needed. I've never had a freeze and I'm also running on an SSD with limited space, plus every performance hit counts to me.
 
Back
Top