But no - once this was fixed, the “jumping” went away completely. I though that maybe my peripheral vision is more “sensitive” to FPS, and that’s why I see some “jumping” instead of a smooth motion on intense parts. ASW makes it feel as “something is off, though not sure what this is”. Interestingly, ASW actually played a negative role here by masking the issue - I suspect I’d immediately notice this without ASW. You can prove it by constraining it to 3–4 cores & pinning something else stealing the CPU time to the same cores - once you get 30 … 40 FPS, you’ll see lots of false misses. the larger % of missed frames, the more likely Beat Saber is to classify an actual hit as a miss. It feels almost as ~ you play songs on maybe 5–10% lower speed moreover, I understood that this FPS drop was actually the reason of some % of false misses - i.e. The issue manifests itself quite similarly both on 24-core AMD Ryzen Threadripper 3960x and on 6-core Intel Core I7–8700K, though the problem is a bit less pronounced on the later.Īs for the actual impact, fixing the issue made a very substantial difference for me. Pinning to 5+ cores seems to make things worse - the more cores you give after 4, the further it creeps back to 15ms+ territory.If you pin it to just 2 cores, the game itself feels fine, but there are noticeable periods of “freezing” in menus.App timings are the smallest ones when you pin the process to 2.4 different physical cores.I experimented with a few different options for CPU affinity, and: allows the game to render ~ up to 400 FPS. Overall, this workaround drops application timings from 15–17ms to 2.2–2.7ms in my case, i.e. In addition, it makes sense to set the priority of Beat Saber process to High.That’s nearly how it should look in Task Manager: You need to pin Beat Saber process to 4 different physical cores “physical” means you shouldn’t pin it to the virtual/hyperthreaded cores sharing the same physical hardware.Luckily, my very first rain dance (apparently, experience matters even if you do a rain dance!) in an attempt to address this brought exactly what I needed: And somehow Ryzen 3960x consuming 6.13W per core is not enough for it. ![]() But how, if that’s a 24-core monster? Moreover, the game runs smoothly on Oculus Quest delivering ~ same 75 FPS there relying on Snapdragon 835 with its ~ 3.5W of total power consumption.
0 Comments
Leave a Reply. |