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

PC:
AMD 8350 FX
8 GB RAM
Asus 1060 GTX 6GB
Main rFactor2 build (no beta)
Lenovo Explorer VR

I have a Lenovo Explorer headset and an old PC. All graphics are at minimum and the Nvidia configuration are at performance (not quality). I've been playing rFactor2 for 8 months with VR and I had not any problems. But, since two weeks ago, every 3 or 4 laps the screen turns off and sometimes turns on again after 3 seconds and sometimes it stays off and doesn't turn on again. Then, I restart the VR program and it appears as if the VR headset were at rest.

Today, I've had this problem again on a race and I had to leave on lap 13/47... . I attached the qualy logs (Q1 and Q2). I lost the race log because I didn't enter the game again, but had the same problem on Q2.

https://drive.google.com/open?id=1pchLFtDLjGMWFHEfVHbTt5Gcu8P9blAj

Thanks for your help
 
Hello.
Long live RF!. It's the best so far!
BUT...here are my replay and csv files (RealTimeLogging {1}) during a small test in Mills with the Clio.
Included the specific second in both tries (readme.txt).
https://drive.google.com/file/d/1ZrDvyaRctWOkgsSTWiTYhVrbonJA8JoI/view?usp=sharing
https://drive.google.com/file/d/1oaZZ0iC48gQAq61296Zifpvd_HD1Qwwp/view?usp=sharing
Comp. specs
Imagen1.png
 
Major freeze 4-5s long that affected Kweg in 2nd place. He jumps back to 4th place just after replay position 1684.75 (lap 29). Unfortunately I didn't have the trace enabled for multiplayer but here are the realtime logs and replay. If you need to know what steam mods we were using to watch the replay. I can ask Kweg if he has any logs on his end, PM me any questions.

https://www.dropbox.com/s/8usv1rj6776spba/Pocono Raceway R1 2_RealTimeLogging.zip?dl=0
 
Last edited:
PC Spec:
- Intel(R) Core(TM) i5-4670K CPU @ 4.0 GHz
- MSI Z87-GD65 GAMING (MS-7845)
- 16GB DDR3
- MSI NVIDIA GeForce GTX 1070 Ti 8GB
- Samsung SSD 840 Pro
- Samsung monitor 23" (using single monitor 1920*1080)
- Microsoft Windows 7 (6.1) Professional 64-bit Service Pack 1 (Build 7601)

RF2 Spec:
- Plugin: https://drive.google.com/open?id=1kctFohMNuKpgPJ2YM8vtrJHsK2owCH4K
- Video Setting: https://drive.google.com/open?id=1Whx3AQaAWjbLc4WwjsEi4S_9E3A1krxJ
- Dispaly Setting: https://drive.google.com/open?id=1hzILt0d7RWNW9pbKcIn4Ly1bFFqU7d9h

Log and Replay:
https://drive.google.com/open?id=12fH1TISAVpeQbCI8oVU2CrAWs23RNXtc

Mod and Track:
URD DTM2018
Lausitzring 2016 v1.061

Yesterday I had massive out-of-time in qualify on a server with 23 drivers. No other driver had this massive out-of-time. I had to quit race after qualify because it was impossible to drive. In the video below you can see last 3 laps of my qualify, I got out-of-time everywere, almost all turns and in some straight.


In every race I have always some minor out-of-time specially in turns but yesterday was massive and everywere.
It happens only when there are more than 5/6 other driver on server, so I only on race day I know if I can race or not, because in practice sessions there are usually no more than 2/3 other drivers and I can drive without problems.
 
Hey guys, I've just got an issue last Monday while racing on a league. I was in 8th place than I was set back to 9th in the first lap.
I was recording myself. Let me know if this is the issue you are looking for, than I'll send the logs.
Regards,
Renato
 
4thworld said:
Using another thread for force feedback it's a setting that is hidden from the main menu.
In order to reduce the cost of the force feedback, you can open the Controller.json file inside Userdata\player folder,

look for the following lines

"Use thread":false,
"Use thread#":"Use a separate thread to issue FFB commands which may block with some drivers"

and change it to:

"Use thread":true,
"Use thread#":"Use a separate thread to issue FFB commands which may block with some drivers"

This will instruct rFactor to use a separate channel to communicate with the device.
You can try that now if you want, from the next public-test build it will be default on.
Click to expand...

Why is this not enabled by default?
Are there any drawbacks by issuing the FFB commands in a seperate thread?
In today's CPU architectures it is advantageous to distribute those async tasks to different threads. Or is this the drawback coz in a ideal world you want to have your FFB synchronous with your main thread?

So if you have no issues would it be also better to set use Thread to TRUE? Or better keep defaults?

Frey
 
I've recently started having issues after upgrading my PC.

My old system was an i7-3570K paired with an old HD7950, with which I have never experienced any stuttering issues in 7/8 years of playing rF2.

I've recently upgraded to a Ryzen 7 1700 and a 1080Ti, and a Rift CV1. I'm now getting regular freezes in the headset of 4-5 seconds (enough to end a race).

Last night I saw the worst performance of rF2 I've ever experienced. When restarting the weekend on a server, the whole game froze/crashed. This resulted in me having to close SteamVR, and the Oculus software. This then happened a further two times, each needed CTRL-ALT-DEL to close the programs.

I don't know if this is just a SteamVR/Oculus issue, or whether something is running in Windows after an update that I'm not aware of, or if it is rF2 itself causing these issues. But it destroyed an evening of racing/testing.

For context, I fired up War Thunder after this, which ran silky smooth for 90 minutes in VR with no issues at all.

I'll do some more testing and get some logs files next time.
 
Sometimes i get some stuttering, when an app with overlay like discord kinda steal the focus for a split second, i have to double alt-tab to fix it.
 
This was my 13 year old son's first taste of online racing.
Doing great until freezes messed up his race totally :(
Using public test and real time logging enabled

Freezes at positions 550 , 972 on the replay, there was at least another one I don't have the time to look for right now sorry.
https://mega.nz/#!x6hVCaIR!qyTjlBrFOVUCNRyv0WtKv0TS7lg2KfV1g8oZIearSrA

Log files
https://mega.nz/#!A34VUCzL!xVloGdWXdq0Tk4g-inzykjWy6_JbAkXhIOGkVzZJuo8

Also worth mentioning the lags happened during people quitting the race and leaving the server.
For the record, a severe source of lag that happens during practice is when people go into the car select section and change an upgrade.
People lag upon them returning to the track with the new upgrade installed.
 
Last edited:
Another massive Out-of-Realtime in Hockneheim with DTM car, this time more on race than qualify.
I had a crash at turn one (not my fault) at 2° lap so I spend 20min repairing on a 37min race, so I did only last 10 min of race because I absolutely wanted to post this log.

Out-of-Realtime is present mostly on sector 3 and sector 1 (like in my previous post in Lausitzring) and car is almost undrivable.
This time I set "RealTimeLogging" to 1 in player.json so is more accurate.

PC Spec:
- Intel(R) Core(TM) i5-4670K CPU @ 4.0 GHz
- MSI Z87-GD65 GAMING (MS-7845)
- 16GB DDR3
- MSI NVIDIA GeForce GTX 1070 Ti 8GB
- Samsung SSD 840 Pro
- Samsung monitor 23" (using single monitor 1920*1080)
- Microsoft Windows 7 (6.1) Professional 64-bit Service Pack 1 (Build 7601)

RF2 Spec:
- Plugin: https://drive.google.com/open?id=1kctFohMNuKpgPJ2YM8vtrJHsK2owCH4K
- Video Setting: https://drive.google.com/open?id=1Whx3AQaAWjbLc4WwjsEi4S_9E3A1krxJ
- Dispaly Setting: https://drive.google.com/open?id=1hzILt0d7RWNW9pbKcIn4Ly1bFFqU7d9h

Mod and Track:
- URD DTM2018
- Hockenheimring

Log and Replay:
- Log: https://drive.google.com/open?id=1ETT-ISNnyNqA5YmnFtol8BUxxwIr9C7a
- Server replay: https://drive.google.com/open?id=1CX1_qjgshXvFrxE3Q0vnMSkxWg_FOxpo
- My replay: https://drive.google.com/open?id=12zd7ITSByZzdBe8n7asR9CB0yW1P58w2

Video:
 
Constant freezes/stuttering in build released today using Oreca in Lemans, unplayable. I will do a fresh install, without mods, only subscribed in Oficial Content and test it again, I hope this solves
 
You must log in or register to reply here.
Back
Top