Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Dracasis

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have a feeling its CPU related and, more specifically, the 'turbo boost' setting that allows the system to overclock your CPU for short bursts of extra processing power. My main PC dose not have a turbo boost and worked perfectly fine with the wireless and my new AMD motherboard/CPU that also dose not use turbo boost has had no issues with this. I would have liked to research it a bit more but my VR motherboard didnt seem to have a way to turn off turbo boost for me to try and run it stability and I didnt have another board to test it on that did. Thus take this as speculation but, since the VR compositor appears to use all additional available CPU power, it may have been pushing into the turbo boost range. Since TB is only supposed to be used for quick bursts of speed (3 seconds?), it then hitches when the boost timer ends. But I have a Noctua CPU cooler that kept the hardware cold enough that it just immediately makes TB available again perhaps. Setting the VRcompositor to high priority means, when the TB drops, the compositor is less likely to be the one to suffer from the sudden malnourishment of processing power. If you have a Turbo Boost CPU and can disable it in BIOS, might be worth giving it a try. Not an ideal solution if that happens to be the case but better than flying blind.
  2. Cool. Spent a few hours trying to narrow down the issue. Some hardware and software adjustments and the final thing that worked was giving 'high' CPU priority to the vrcompositor. Kinda happened by accident cause 'above average' didn't do anything. Downloaded a program to give it high priority permanently and seems to be resolving the issue. I'm guessing something in the latest steamvr update buggered CPU allocation. Hopefully that'll help someone in the future.
  3. Its a brand new PC I bought specifically to do VR and it was working fine for about a month. I was playing Beat Saber, modded SkyrimVR and Arizona Sunshine on it without a hitch and this problem litteraly popped up out of nowhere. Because it was working previously I have a harder time believing its hardware related. Motherboard is an ASRock H370 Pro4 https://www.asrock.com/MB/Intel/H370 Pro4/index.asp Cards inserted into the MB are Wi-Gig, GPU, Wireless adapter. Not sure what you mean by 'fix your CPU' speed. The i5-9400F is a 2.9GHz processor currently turboclocked to 3.9GHz. Unfortunately I cant effect what CPU usage the compositor is chugging: at just the idle screen it chews 60% of the CPU but when in an actual application it usually falls back to 30-50%. I can only assume its using all available CPU for its own processes and just dials back when other applications need it. There's no way the compositor should need to use 60% of a 6 core 3.9GHz processor doing 'nothing'. Setting CPU priority did not change the effect or I dont know what application needs priority. Steamtours.exe is the steam home application which quits on its own when a new VR application is run. Force quitting it did not effect the stutter for me either.
  4. Any updates with this? Am having the exact same issue that only seemed to start occurring with the Steam VR 1.7.15 update. There is likely some sort of interference or hiccup that I cant figure out as it worked before and dosent now. This video shows the display when using Steams "Display VR View" https://www.youtube.com/watch?v=c_HtaS8ghwE This video shows the view looking through the lens (recorded with a phone). The regular pixelated fuzzing/jumping is what you see and its quite distracting. https://www.youtube.com/watch?v=53FRWnWYylE Its very consistent in its timing. Not sure why but the compositor eats up as much CPU as possible when anything is running, I've seen up to 60% so not sure if that's part of the issue. Lastly, I noticed the same peeking in my network tab as well, regular and consistent with the fuzzing issue. Disabling the wifi card entirely doesn't change the issue though. If I exit Steam VR but leave the VIVE Wireless program running, the network peaks go away. If I have Steam VR running but no program (including no Steam Home so its just the borealis area) the fuzzing goes away. I really have no idea how to fix this and, since there's no way to roll back to a previous version of Steam VR, I have no way of knowing if its something to do with the update. Sheet Specs: Win10 Home Intel Core i5-9400F 2.9GHz (OC to 3.9) 16GB SDRAM DDR4 2666 1TB SATA III 3D NAND (SSD) NVIDIA GeForce RTX 2070 Super TP-LINK 802.11ac Wireless Network Adapter And, of course, the Intel Wireless Gigabit VR Adapter card If ya'lls have any ideas that would be awesome :) Thanks,
  • Create New...