Low Frame-Rate with GTX1080 + i7 6700 + HTC Vive

OK, I disabled Interlaced Reprojection and experienced no improvement.
I used ctrl + f to view framerate and found that my framerate is an acceptable 60 fps in stations. I used to play on the DK2 which looked fluid at that frame rate, therefore I conclude low FPS is not the cause. Instead, it appears frames are being dropped.

I see that Nvidia just released a new driver: 375.70. I will install that and try again.

EDIT: An update to 375.70 drivers did not fix the issue.

If your FPS is at 60 with Asynch on then you might be talking about Jitter/stutter like behavior most prominent when you drop from Hyperspace (happens for few secs after drop) or jumps. This seems to be a loading/unloading/networking issue and is        to troubleshoot. Is it what you mean? or do you have a constant stutter.
 
Last edited:
If your FPS is at 60 with Asynch on then you might be talking about Jitter/stutter like behavior most prominent when you drop from Hyperspace (happens for few secs after drop) or jumps. This seems to be a loading/unloading/networking issue and is        to troubleshoot. Is it what you mean? or do you have a constant stutter.

I've clarified my initial post. To clarify, the perceived frame rate is consistently low in all situations, including the hanger/main menu.
 
My frame rates are quite stable at 90 fps most of the time. I've had hick-ups which seemed to be related to missing USB drivers (rather default Windows-drivers) for the additional cards I have put in. So I've made sure to have the latest drivers for NICs and USB cards, which was quite an improvement.
But still there are sometimes those sudden drops in fps which make me dizzy. If this happens I close my eyes for 1-2 seconds.
I also think that the display is too bright.
 
Did FDev say anything about it at all?

Look up the bug report thread that was posted and all the merged reports in there. Other than "we are aware and looking into it" they improved it a bit in beta 6 or 7 but eventually left major issues (stuttering when dropping at a station, glide, etc.) in when they deployed to production. I think they just buffed the min. requirements for VR, but also ppl. get that poor perf. with high tech gaming rigs, so its ridiculous. 2.1 was far from perfect but it was very smooth (and readable with targetRenderMultiplier applied). Now, without steamVRbeta 2.2 has been "unplayable" (as in very immersion breaking) for me.
 
Last edited:
Has anybody upgraded their SteamVR in the last 12 Hours?

I can run it on VR ULTRA setting pretty smooth since today. Previously I was stuck with a mix of mediums and lows.

Specs: MSI Tobii Dominator Laptop

- intel I7 6700 @ 2.6 Ghz
- 16 Gb DDR 4 Ram
- Geforce 1070 (8 Gig)
- Windows 10 64 Bit.
 
Has anybody upgraded their SteamVR in the last 12 Hours?

I can run it on VR ULTRA setting pretty smooth since today. Previously I was stuck with a mix of mediums and lows.

Specs: MSI Tobii Dominator Laptop

- intel I7 6700 @ 2.6 Ghz
- 16 Gb DDR 4 Ram
- Geforce 1070 (8 Gig)
- Windows 10 64 Bit.

Might and sounds like the asynchronous reprojection has gone from beta to release, similar as to ASW for the cv1.
Even though you can crank up from before and still feels smooth, I would recommend dialing down a bit cause if you do drop below the needed response times for 45fps, what you end up with much worse than before.
 
Might and sounds like the asynchronous reprojection has gone from beta to release, similar as to ASW for the cv1.
Even though you can crank up from before and still feels smooth, I would recommend dialing down a bit cause if you do drop below the needed response times for 45fps, what you end up with much worse than before.

I've noticed that it's still called SteamVR Beta, probably next iteration. Up until yesterday sitting in the station and just looking around and keeping head motions to a minimum , I had frequent (about once a minute) "gray-outs" which an annoying little wobbly motion right before each grey-out. Needless to say it induced motion sickness.

These grey outs have now almost disappeared; I say almost because it happend one more time in about 2 hours of gameplay. This is a big improvement and almost negligible.
 
Last edited:
Those grey outs are, where perhaps, a problem.
I would get them sometimes as well, and usually just when I was about to bare down on anew npc.
Instead of a killshot I grey out and hope it pops in again before I get killed :/
 
Last edited:
I have created a support ticket, and will keep this thread up-to-date. I was hoping new driver releases, or an update to ED would fix the issue, but to no avail so far.
 
You migh want to check for a newer driver. The october release had a bug that caused Pascal cards not raising their mem clocks.
 
Just a quick thought - is the GPU or CPU getting too hot and clocking themselves down ? Both will reduce their clock-rate to avoid over-heating. The fans on your laptop should be running quite fast and chucking out plenty of heat. Is the laptop well ventilated and sitting on a hard surface ? Soft surfaces can get too close to under-side cooling vents and severely limit the laptops ability to cool itself.

Oops - sorry - replied to wrong thread - just ignore me LOL
 
Last edited:
Raise your default fan profile to blow faster, sooner.

What are your SS settings in-game and in Steam? I run 1.5 SS in SteamVR and .65 in-game on a GTX980Ti without issue.

I installed 2.2 today . I am playing without Horizons.
Do I take this to mean you are running 1.7 not 2.2?
 
Last edited:
Raise your default fan profile to blow faster, sooner.

What are your SS settings in-game and in Steam? I run 1.5 SS in SteamVR and .65 in-game on a GTX980Ti without issue.


Do I take this to mean you are running 1.7 not 2.2?

Good question. I am not home to check. I would have assumed I'd have grabbed that number from somewhere, but maybe I was assuming my version, given that Steam updates the game automatically.

My SS in Steamvr is 1.5. My in-game is 1.0. I have reduced Steam VR to 1.0 to trouble shoot this issue, but it didn't have any perceptible result.
 
CMDR Sticks from Team ED emailed me today. Not a bad response time, good job guys! One of my cats is named Sticks, btw.

Sticks suggested three things.
1. Turn V-sync off.
2. Set Steam VR SS settings to 1.0.
3. Revert back to non-beta Steam VR.

I turned off V-sync in game, and made sure v-sync was not being forced by nvidia 3d settings. No change.
I reverted back to non-beta SteamVR, whch also coincided with the Steam VR SS settings being reset to 1.0. Problem solved!

I've changed Steam VR SS settings to 1.0 before, recently in fact, in an attempt to trouble shoot this issue. It didn't work on my previous attempts. Therefore, I conclude it was the combination of Steam VR BETA + SS settings set at 1.5 causing the issue. I may try some other settings, but right now I'm just happy to see ED running smooth. I took a celebratory trip around a star.

Too bad I couldn't get this solved soon enough for the black Friday sale. I would have picked up Horizons if I had known Ed would be playable again. :(
 
I'm sure you've tried this but:

- SteamVR Beta: Disable Interweaved Reprojection
- SteamVR Beta: Disable Always On Reprojection (if it's on)
- SteamVR Beta: Enable Async Reprojection
- SteamVR Beta: Make sure the steamvr.settings file is set to 1.0 SS
- RivaTuner: Make sure this isn't set to limit framerates (if installed)

I have the same CPU and GPU. It's butter smooth when configured like this up to 1.0 default + 1.75 SS and the usual mix of settings. I found horrible stuttering if I had Interweaved AND Async reprojection on at the same time. Also had horrible framerates when I forgot RTSS was limiting framerates to 60.

Hope that helps.
 
CMDR Sticks from Team ED emailed me today. Not a bad response time, good job guys! One of my cats is named Sticks, btw.

Sticks suggested three things.
1. Turn V-sync off.
2. Set Steam VR SS settings to 1.0.
3. Revert back to non-beta Steam VR.

I turned off V-sync in game, and made sure v-sync was not being forced by nvidia 3d settings. No change.
I reverted back to non-beta SteamVR, whch also coincided with the Steam VR SS settings being reset to 1.0. Problem solved!

I've changed Steam VR SS settings to 1.0 before, recently in fact, in an attempt to trouble shoot this issue. It didn't work on my previous attempts. Therefore, I conclude it was the combination of Steam VR BETA + SS settings set at 1.5 causing the issue. I may try some other settings, but right now I'm just happy to see ED running smooth. I took a celebratory trip around a star.

Too bad I couldn't get this solved soon enough for the black Friday sale. I would have picked up Horizons if I had known Ed would be playable again. :(
Thanks for posting a possible solution.
I found, that Vsync and frame rate limit options in ED are bugged. Meaning, vsync being active even though the menu shows "off"´.
 
Reviving this from the dead. I've updated the main post with the symptoms, and with actions taken in an attempt to solve the issue. Any help would be appreciated.
 
Back
Top Bottom