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

I had some freezes in recent race, but I did not run log and situation is very excotic.
We use simsync to get a skinpack for that league. New skinpacks are made as new version of existing mod package. Here the problem start: simsync does not update the mod like a real installation would do (say delete the old one, install new one), it just adds. So you have V1.1, V1.2 ... .
On the server, as I know meanwhile, they delete the old mods. I did not know that this could cause issues.
Now: During race I saw at leat 5 other cars driving around with my own car and skin, and I know they did not drive the RSR. In the youtube stream (made by server observer) you can see them in the right car. So for my rf2 instance cars and skins where loaded wrong due to the version conflict, having multiple versions available for same mod (somehow, no expert in this case).
Now, whenever some of them driving my car and skin left the race (it was an 3h endu, some gave up), I had a freeze. I suppose the server said that guy is off driving a unique car design (server view), the car & skin was removed on my rf2, then my rf2 instance found ups there is still someone driving that design (at least me) and reloaded it, something like this
Very excotic situation but happened a few times for me
 
@pablos , yeah replay playback slowdown are a different issue.
Your logs showed some spikes while recording the replay, let us know how it goes with the replay turned off

@4thworld Here is log from today's drive: https://drive.google.com/open?id=1wDfSLtFZaR8XpIrxnjwtJe-3ydJmBWUx
I did about 12 laps and recorded only one freeze in the beggining of session, from results log I suggest the timestamp was between 120 and 250. Besides that everything ran smoothely.
 
@4thworld
That's a surprise. You don't have normal Download button like here?
UiXu48n.png


Anyway here's other source:
https://www.dropbox.com/s/ls8sy1w18ztegcn/test-build_test1.zip?dl=1
 
@Davvid thanks, your log shows that everything is ok.

We are using a little bit more of CPU resources when the physics load is lower in order to be more precise on starting the next physics step or recovering from being late on a previous one.
When the physics load is higher you shouldn't witness any issues, let us know if you encounter any.
Cheers.
 
Thanks @4thworld. Yeah, current test is ok-ish but that previous one really scared me, as I feared I'll need to upgrade my cpu really soon ;-) I think it shows that one should be watchful with those changes regarding cpu usage.
 
Build update ID [3788578] :
- Improvements to main thread , FFB thread and CPU load

@Davvid you can take a look to see if the idle CPU usage is lower for you.

branch name: public-test
password : UpERYPhIblEHorTiO
verify your files via Steam after joining the branch

1. Select rFactor 2 from steam game library, right click and select properties.
A dialog box with a number of tabs will appear, your looking for one that says "BETAS".
2. select the "BETAS" tab it by clicking on it.
You will see 2 things now, a drop down menu and a text box to enter a beta access code.
3. enter the password provided,
4. select public-beta from the dropdown menu
 
Yes it is, although not by that much. Maybe 5% or so. But it's better.

Edit:
This test build crashes rFactor2.exe when using 'Reset FFB' command while driving.
@4thworld
 
Last edited:
Yes it is, although not by that much. Maybe 5% or so. But it's better.

Edit:
This test build crashes rFactor2.exe when using 'Reset FFB' command while driving.
@4thworld
And my rF2 keep freezing when i alt-tab it and i return into it after some minutes, also it freezed heavily when someone joined the server, i have to close it thorugh the task manager. (I'm using borderless mode btw, this started to happens today after the last beta update).

It freezed right now when loading drivers list in the server, again i have to close it throught the task manager.

update
Trace file of a freeze (and again i needed to close rf2 through the task manager) occured when entering a server.

update
same issue, occured when i voted for a weekend restart, another trace and realtime logging attached as well now
 

Attachments

Last edited:
@4thworld System updated to build ...8578. Tested for the first time this morning and after a couple of minutes it crashed. The screen went black, but a loop of sound continued. The picture in VR was black, but on the screen was frozen and no response from any keys. Had to escape by closing SteamVR. No log generated unfortunately.
 
Build update ID [3791195] :
- Addressed some changes that caused issues.

Let me know if the build is ok for you now.
Thanks

branch name: public-test
password : UpERYPhIblEHorTiO
verify your files via Steam after joining the branch

1. Select rFactor 2 from steam game library, right click and select properties.
A dialog box with a number of tabs will appear, your looking for one that says "BETAS".
2. select the "BETAS" tab it by clicking on it.
You will see 2 things now, a drop down menu and a text box to enter a beta access code.
3. enter the password provided,
4. select public-beta from the dropdown menu
 
Build update ID [3791195] :
- Addressed some changes that caused issues.

Let me know if the build is ok for you now.
Thanks

branch name: public-test
password : UpERYPhIblEHorTiO
verify your files via Steam after joining the branch

1. Select rFactor 2 from steam game library, right click and select properties.
A dialog box with a number of tabs will appear, your looking for one that says "BETAS".
2. select the "BETAS" tab it by clicking on it.
You will see 2 things now, a drop down menu and a text box to enter a beta access code.
3. enter the password provided,
4. select public-beta from the dropdown menu

Problems fixed for me :)
 
Build update ID [3791195] :
- Addressed some changes that caused issues.

Let me know if the build is ok for you now.
Thanks

branch name: public-test
password : UpERYPhIblEHorTiO
verify your files via Steam after joining the branch

1. Select rFactor 2 from steam game library, right click and select properties.
A dialog box with a number of tabs will appear, your looking for one that says "BETAS".
2. select the "BETAS" tab it by clicking on it.
You will see 2 things now, a drop down menu and a text box to enter a beta access code.
3. enter the password provided,
4. select public-beta from the dropdown menu
@4thworld Fixed for me as well :)
 
Today I had reasonable freeze in online race when someone exiting server. My realtime logs for that here.

We are using Nascar 2016 mod, Watkins Glen track. Server was configured for fixed setups and fixed upgrades but upgrades wasn't fixed somehow and all drivers set them manually. Other drives also reported problems when others exiting server.

That moment on replay at 794 (26:59 on stream)
Second moment after the finish when other driver exit server at 3784 (1:16:47 on stream)


 
I experienced a similar experience. I thought the stutter was gone, but after about 10 minutes the AI jitter came back at Imola with ASR '93 F1 mod, and the after another minute or so I got a screen freeze. I'll upload my logs tonight.
 
public beta 3791195, confirmed I'm using that buildID and then verified the files via Steam after joining the branch. No stuttering, just wanted to post a new log with the latest public beta. Also "Realtime Controller Detection":false Loading any controller profile automatically sets this back to true and the stuttering returns.

Log and trace files of one lap with AI control and one lap my control around Silverstone in the C6R with Build ID 3791195:
https://www.dropbox.com/s/jzi57brt3puanyj/2019-04-24 RF2 Trace and RTL files ID3791195.zip?dl=0

Stream of the above 2 laps with CPU GPU and FPS data on and replay of those laps, any stuttering in the track replay is in the stream only:
 
Back
Top