Page 1 of 2 12 LastLast
Results 1 to 15 of 25

Thread: Oculus rift cv1 stuttering while moving my head while and after using starport services...

  1. #1

    Oculus rift cv1 stuttering while moving my head while and after using starport services...

    Hello,

    So... after reading many threads regarding oculus setup for my card gtx 980 I managed to set it to run smoothly, however... when I am using starport services for mission etc, suddenly my oculus go nuts - it distort the view of the startport services interfaces and stutter when moving head even slightly. After I turn off services it stay for couple of minutes like that. When I minimize game or press escape sometimes it go back to running smoothlu but not always. The stuttering and distortion also appears while landing on planets - its nearly impossible to land with this performance. I have ss to 1.0 and hmd view to 1.25 most of options to high, blur aa to off. Do you have any idea why this issue occurs mostly after using startport services?

  2. #2
    Sounds a lot like the creators game mode rearing its ugly head and forcing elite to run at 60fps.

    The rift is not even remotely tuned for this so it looks absolutely terrible.

    https://forums.frontier.co.uk/showth...96#post6108296

    It' might not be this precisely but definitely sounds very close to what I experienced.
    When I was hit by this.
    Sometimes I could get it off by changing a graphics settings, but would only last for a few seconds.
    The method above has worked flawlessly for months.

  3. #3
    Thank you for the reply and suggestion but unfortunately i had this options disabled and that did not solve my problem. That is really weird... It runs very nice with 90fps and suddenly after choosing services or flying near planet it drops performance and stay like this for long while. I dont know if its relevant or not but when it comes to starport services it also takes long time to load.

  4. #4
    Something changed in the last few updates and it has caused this, for some reason the station services menu seems to be a massive hog of resources and at some point will kill fps for no apparent reason.

  5. #5
    not noticed any change on my system.. 4770k @ 4.5 32gig 2400 gtx1080

  6. #6
    Well.
    It's a loose suggestion but I have over the past while experienced a noticeable decrease in performance not so much from a patch to another as much as from the patching process itself

    Before season dropped I had been experiencing pauses and judder when I loaded the game and occasionally I got this when jumping into a new system.
    It got a little worse after the 3.0 patch as well.

    A little while later I cleanly uninstalled the full game. Wiped the directories completely and downloaded the full game from scratch.
    And I haven't had a single pause or significant judder since.

    So I recommend to reinstall on occasion, personally I will do this for each new feature update now.
    But I'm also fortunate to not be on a metered 300/300 FIOS connection.

    In fact just downloading the whole game is faster than patching...

  7. #7
    Actually this is clean install as I jumped back to ED . Got my oculus week ago and wanted to try it out. I have few ideas based on some threads I read
    1) Is it relevant which install of ED I have ? Should I have steam version or oculus version?
    2) I heard that rollback to 388.59 nvidia drivers helps. Did someone notice that ? I am asking because I want to know that it actually helped someone - its a big impact to install couple of months old driver so I want to be sure.

  8. #8
    Originally Posted by J4ckdaw View Post (Source)
    Actually this is clean install as I jumped back to ED . Got my oculus week ago and wanted to try it out. I have few ideas based on some threads I read
    1) Is it relevant which install of ED I have ? Should I have steam version or oculus version?
    2) I heard that rollback to 388.59 nvidia drivers helps. Did someone notice that ? I am asking because I want to know that it actually helped someone - its a big impact to install couple of months old driver so I want to be sure.
    Odd.
    What install you have should not be important.
    I personally just use the standard FD launcher myself.
    Just make sure you are NOT running steamvr as well as the oculus software that would easily put another 30% load for your oculus that you don't need.

    The Nvidia driver bug has been for a different non game specific issue.
    It would chiefly present itself as a completely back set of screens in the rift as soon as you fire it up at all so if you had this bug you wouldn't be able to use the rift at all.

    No harm to go back though if you are just ruling stuff out.

  9. #9
    Originally Posted by TorTorden View Post (Source)
    Odd.
    Just make sure you are NOT running steamvr as well as the oculus software that would easily put another 30% load for your oculus that you don't need.
    You mean not not to run them simultaneously ? Because depending on the what headseat software(oculus or steamvr) game is installed it requires to be running to work in VR. Oculus home needs to be turned on for the headset to work properly or I am wrong ?

    Anyway I decided to rollback drivers to 388.59 and I must say that as I did not believe it will help in any way I am surprised to see an improvement. For the 2h of playing only once for 10 seconds I experienced stuttering while moving my head and in wasn't so intense as before .Start port services hud has no longer distortion. I will test this further because I am afraid this could be just coincidence and problem will occur again today.

  10. #10
    Not an expert, but what the OP has described reads like a classic frame rate problem due to any of:

    - graphics settings too high.
    - insufficient Vram.
    - CPU limitations (e.g. an i5).

    The problem isn't obvious until your rig is asked to process a high number of polygons, which is exactly what star ports and planetary landings have (e.g. your card is processing 100's of polygons inside a station, repeating this numerous times when your ship creeps forward and then doing it twice over because of the two high res monitors parked in front of your eyeballs). Simply stated, ED in VR is resource hungry in a number of places.

    The GTX 980 can do VR, but it is at the low end of the VR specs. It will struggle to run all scenes in ED VR smoothly on anything more than low settings.

  11. #11
    Op clearly states he has a cv1.
    Dunno why some people think so but surprisingly many seem to think that since they have ed on steam.
    They need to run steamvr.

    For oculus that means there is whole other vr runtime running on top of the oculus's native one costing significant performance headroom.

    So figured it would be best to mention it just in case.

    If I had a dollar for every time I had asked "is the power plugged in?" and gotten "yeah of course" only to two minutes later get "wait. forgot the other end of the power cable."

  12. #12
    Not sure if it helps op but I get frame drops with gtx 1080. Driver 388.59 (or a couple earlier) does help a bit. Quite a few people have mentioned the star port services resource hog. Smooth into station then stuttering and warping once the menu opens. Hopefully, FD can look into it.

  13. #13
    I can confirm that in my case 388.59 driver helps but not for 100%. For 2h of gameplay only one time stuttering/distortion occurred while browsing startport services and couple of minutes after closing it. Whats interesting, during this gameplay I visited the same station couple of times for testing and no issues except this one time. I figured out that minimizing and maximizing game during this stuttering helps so I created command for voice attack for hitting alt tab twice - while using vr googles its invisible for me so its good solution for now.

    Originally Posted by A D View Post (Source)
    Not an expert, but what the OP has described reads like a classic frame rate problem due to any of:

    - graphics settings too high.
    - insufficient Vram.
    - CPU limitations (e.g. an i5).

    The problem isn't obvious until your rig is asked to process a high number of polygons, which is exactly what star ports and planetary landings have (e.g. your card is processing 100's of polygons inside a station, repeating this numerous times when your ship creeps forward and then doing it twice over because of the two high res monitors parked in front of your eyeballs). Simply stated, ED in VR is resource hungry in a number of places.

    The GTX 980 can do VR, but it is at the low end of the VR specs. It will struggle to run all scenes in ED VR smoothly on anything more than low settings.

    My graphic serttings are low/mid with blur off / AA off / DOF off / shadow low and rest medium. SS 1.0 HMD 1.25
    I am aware that 980 is not the newest graphic card but I read many topics that people can run ED in VR with 970 on low without fps drops. Besides If this issue occurs only one for couple of time its hard for me to believe that cause of the problem is mainly my card. I will test on all low settings and check if this issue will repeat.

  14. #14
    Originally Posted by TorTorden View Post (Source)
    If I had a dollar for every time I had asked "is the power plugged in?" and gotten "yeah of course" only to two minutes later get "wait. forgot the other end of the power cable."
    I affectionately call this the Maytag check... I don't know how many times I've been told a PLC program has changed (spontaneously, no doubt) and almost every time it's a wiring problem or a mechanical/electrical failure. The first troubling shooting step in a system that has been running along fine for a while is what changed... And it ain't the program!

  15. #15
    Originally Posted by J4ckdaw View Post (Source)
    I can confirm that in my case 388.59 driver helps but not for 100%. For 2h of gameplay only one time stuttering/distortion occurred while browsing startport services and couple of minutes after closing it. Whats interesting, during this gameplay I visited the same station couple of times for testing and no issues except this one time. I figured out that minimizing and maximizing game during this stuttering helps so I created command for voice attack for hitting alt tab twice - while using vr googles its invisible for me so its good solution for now.




    My graphic serttings are low/mid with blur off / AA off / DOF off / shadow low and rest medium. SS 1.0 HMD 1.25
    I am aware that 980 is not the newest graphic card but I read many topics that people can run ED in VR with 970 on low without fps drops. Besides If this issue occurs only one for couple of time its hard for me to believe that cause of the problem is mainly my card. I will test on all low settings and check if this issue will repeat.
    Good idea. The main settings to watch are:

    - Model draw distance - about 25%
    - Shadows - low
    - Ambient occlusion - low
    - Anti-aliasing - none (but if you cant stand the jaggies use FXAA only)
    - SS - 1.0
    - HMD - 1.0
    - Terrain draw distance - 25%

    The rest won't matter too much, but keep them on a low setting.

    Then give it a good go. Totally ignore the picture quality for now, just focus on "smoothness" in various situations (inside stations, planet landings, conflict zones, asteroid belts, flying close to other ships, etc.). If nothing else, this will give you a bench mark for your card's performance in VR. Everything should be stutter free regardless of where you are in the game and how fast you move your head (within limits of course). You can then tweak the settings ONE AT A TIME and see what works and what does not.

    Just to help with your wind up of settings afterwards (one by one):
    - start with AA - FXAA only and use your graphics control panel to "enhance application setting". Choose 2x or 4x (no higher).
    - Up the model draw distance - no higher than 50% (you will have to accept some pop up on planet surfaces).
    - Shadows - keep low or medium at most.
    - Terrain draw distance - up to 50% (no higher).
    - HMD to 1.25 or if you're doing well 1.5 max.

    Obviously the effects are cumulative, so if you hit a setting that introduces noticeable stutter, review that setting along with those you have already changed. That way you can prioritise between them as you prefer. Don't use SS with AA or HMD. If you want to try SS as an alternative, put it at 1.5 with no AA or HMD. A word of encouragement - this process can take some time if done properly, so if you want to muck around with different settings or do something else, make a note where you left off so you are not repeating steps or going around in circles.

    Just to be sure and before you start, check your Oculus sensors or redo the sensor set up. It's a drag to grind through your settings only to find that your sensor setup was a bit dodgy. If you only have one sensor, then that could make a big difference, so be certain it is well placed and working properly.

Page 1 of 2 12 LastLast