@badun and @lagg , so far it sounds like related to the latest windows update, lagg if you can confirm that person has updated that would help. Though honestly I'm not sure why a windows update would cause such an issue - the main thing the plugin is doing during building is reading and writing files, so when that slows down I tend to suspect antivirus interfering (scanning after each round of writes, for example). The person reporting it on Discord (can't remember who it was... I'll try and trawl back through the history later) said only windows defender was in use, which makes that less likely but I guess still not impossible.
badun, and lagg too, can you confirm the usage method? I have logging on the whole time so it builds each log when I go back to the garage. Badun it sounds like you're switching logging off when in the car so it builds while you're driving, or is it still building the last one when you jump back in the car and takes another 1.5 laps?
It's going to be a tough one to nail down I think. Plus who knows when my own windows will update and possibly replicate the issue...
Lazza, with the Windows Defender deactivated, my friend has the same problem.
Hi Lazza, first of all thanks for your great plugin! We are fully in preparation for the 24 hours of next weekend so telemery like this is very goodI did a clean windows install Saturday and now it doesn't work anymore. It still starts recording telemetry so that's fine, but when it is longer than 1 lap it doesn't stop it anymore, or sometimes it also stops while driving so very weird. I didn't have this issue before the fresh windows install. Then when closing the sim it just crashes and I need to reboot it. When not using the Damplugin it doesn't crash while closing, even when I do 100 laps. This seems like the issue of the guys above? So your call is to just go back to a previous windows version? Or do you think there is any way how to fix this in the near feature. Thanks for all your help to the community!
You have to use a previous version of the plugin. Not a previous version of Windows.@Lazza I'm the guy that pinged you on the discord channel. It eventually rolled back to windows 1909 version. I disabled windows defender as test and the problem persisted. It feels like windows kinda hard deprecated a file api by making it extremely slow or some kind of security prevention system not allowing such a big file write.
@Lazza I'm the guy that pinged you on the discord channel. It eventually rolled back to windows 1909 version. I disabled windows defender as test and the problem persisted. It feels like windows kinda hard deprecated a file api by making it extremely slow or some kind of security prevention system not allowing such a big file write.
I'm quite confident it has something to do with the latest big update from windows 10 (version 2004). I skimmed through the change logs but I cannot see anything obvious.I think there are two different issues:
- Some sort of malfunction or slowdown, possibly caused by the way I'm doing multithreading in the latest version. This appears to cause long build times, though it's not happening to me and I suspect many others (yet). This does seem to be a recent thing so may be windows update related.
- Exit "crash" or stalling. This can happen with interrupted logging and old files. The plugin tries to find and rebuild old files on exit, but broken files it will keep trying to rebuild on every exit (these are logged in the output file, but removing .ldtemp files should do it). I think I need to disable this happening automatically because the freeze is causing confusion, and rF2 crashes (Which lead to those interrupted logs) are relatively rare these days. That won't help problem 1 though.
Its creating a file every time I hit drive. So now I have many short log files over 1 session. How to fix this ?