Thanks for the very nice bug report. I see the problem and will have a fix for it soon.
The problem turned out to be more complicated than I thought. Didn't manage to get it done in time for 4.11-4, hopefully next release.
Was just about to check out 4.11-4, no worries and thank you for keeping us posted!
Still not in 4.11-5, but I'm working on it :)
I guess the release window for 4.11-6 was also too short, wasn't it?
Yeah, not yet, sorry. I have it completed, but we haven't had time to do a QA pass on it yet. If you're curious, I pushed the branch over here https://github.com/aeikum/Proton/tree/proton_4.11-vrclient
Hooray, this should be fixed in 4.11-7. Thanks for your patience. Please retest (you may need to restart the Steam client for it to update).
Played yesterday 2h of Beat Saber on stream and no signs of the NullReferenceException in the log files anymore. I also have the impression it has helped with most of my frame drops. Thank you very much!
Thanks for retesting, closing as fixed.
proton 4.11x1 2019-09proton 3.16-9x1 2019-09proton 4.11-3x1 2019-09PROTON_LOG=1x1 2019-09
Since Proton 3.16-9 the log file under
SteamLibrary/steamapps/compatdata/620980/pfx/drive_c/users/steamuser/AppData/LocalLow/Hyperbolic Magnetism/Beat Saber/output_log.txtgets filled with these exceptions:Here the log files for Proton 4.11-3 and 3.16.9:
output_log-4.11-3.txt
output_log-3.16-9.txt
This seems not to happen with 3.7-8:
output_log-3.7-8.txt
Here are the corresponding proton log files, with
PROTON_LOG=1 %command%:steam-620980-3.7-8.log
steam-620980-3.16-9.log
steam-620980_4.11-3.log
When using mods with Beat Saber, these error messages are duplicated into the log files of the mods as well, letting them grow quickly into hundreds of megabytes, which might cause side effects, especially with performance.
My steam system information:
system_information.txt
Steam VR system report:
SteamVR-2019-09-08-PM_02_24_18.txt