Warthog_Farmer

Double vision tracking jitter is only resolved by rolling back nVidia drivers to 388.59 . This is the last set where it doesnt screw the tracking. Is this fix for you? Well - if you get tracking jitter in game and then come back to Oculus home and it is still jittering even there (until PC restart or Oculus services restart) then the driver rollback should fix it. Absolute pain in the butt.. But hey ho

I think your problem might be running ASW off with <90fps. Supposedly the headset will only display 45fps as Vsync is hard coded to prevent tearing in VR. YOU MIGHT BE RENDERING 60fps but you are not displaying it. That is as far as I understand. With 8086k/1080Ti I can’t get 90fps in Rift. I hate ASW glitches so I must run a jagged sim until optimisation happens. I tend to play PUBG now because of this instead... which is a shame. Just re-read and realised you said you get 90fps. As long as they are constant I am not sure of your issue. I had the same issues before the driver issues and it was purely performance causing it. Run Oculus debug tool overlay and make sure your performance headroom is never below 0

nVidia drivers 388.59 is the solution. Google it for the download. It's a fairly common problem. They are the latest version to not suffer from the jitter-bug. It's a shame cos the newest version seems to offer a better framerate - but the jitter is unplayable. Eagerly awaiting new drivers.

It seems to be tied to frame rate right now I think, probably to prevent "jumping" and making you feel sick. I think I have strong enough VR legs now to deal with a little stutter for quicker zoom though. I'd like the option - or a file edit to try it out.

Hey, Long time VR user here (since DK2). I am really struggling with DCS in recent times and kinda gave up on it for a while.. but the F18 has me back. I really dislike ASW and disable it every time I use DCS. Previously I would have an entirely unlocked frame rate and it suited me. I would normally sit in a variable range from 60-90 unless sh*t was hitting the fan in the server. Nowadays - regardless of the aircraft - I seem to get 45fps consistently unless I am very high/very out to sea where it will pick up to 90. Is there a lock on the frame rate even with FPS disabled to sit at half the max refresh rate? Is anyone else experiencing this? I run a 4790k at 4.5, 1080Ti, SSD, 32Gb RAM, Win 8.1. My system is kept in fairly good condition and lean as far as unncessery software goes.

Hi! Just came up with an idea today... Is there any possibility the tooltip can be used to display the current active selection? For example - I own the Viggen but I can’t really use at as the small font on the rotary wheels used for weapons employment is too difficult to read. I have noticed some modules have a list on the tooltip which lists the selections. Off the top of my head the Harrier’s HUD symbology brightness selctor will show the switch ID in Tooltip and then show DAY/AUTO/NIGHT as these are the three selectable positions. I would like to see a box or a highlight put around the relevant option which reflects the switch position. Provided tooltips are updated across the board this would make every aircraft much more effective for VR users (IMO) Thanks!

Perhaps gamma setting is the issue. I’ll try it when I finish work tonight. Mines is set at 1.5 iirc. Anything higher makes daylight ops a very washed out affair. As for my point about VR NVGs making the cockpit unusable - this will continue to be the case.

In VR the NVGs are near useless as anything in cockpit (except HUD) is a blurry mess. It appears in VR the NVGs occupy 100% of the screen where as monitor users have the green circle but can see everything else around it unamplified/blurred. I am also wondering if VR users are the only ones suffering with NAVFLIR issues. Next time I’m on I plan on trying with and without my Rift on, and with and without Deferred Shading on. It’s pretty much unusable at night in VR in its current state due to not being granted ‘the green circle’. I’m not sure the blurring of the intstrument panel is intentional (perhaps too close to focus the HMD) or not - but either this effect needs removed for VR users or we are granted the circle.

I meant the VR subforum on here. Many people are reporting this issue across various modules on my bug report. It's nothing for RAZBAM to worry about =] The reason you are not having problems in the F15 is that it is not a clickable cockpit and therefore there are no tooltips

I assume you have checked the Input/Output // Virtual Reality section? You'll see that this is a bug of the OpenAlpha and not the Mirage module.

Just swallow the bitter taste and turn down your settings. I'm on 4790k/1080Ti and I get 60-70 average, occasionally smooth runs at 90fps and the occasional dips as ever. The upgrade from 980Ti to 1080Ti allowed slightly higher settings - but not as much as I had hoped. Overall smoother with slightly improved visuals - but still a while to go to 'perfect' Remember it's DCS! There's been a 1080Ti thread on here talking about just these issues since launch - I think you should not be expecting so much (wishing, perhaps ;) )

https://forums.eagle.ru/showthread.php?t=191310 If your Nevada/Normandy is crashing you out on the latest update then turn off mouse tooltips!

Have to say I am impressed with the improvements to average FPS.. but unfortunately the lows are just as low. Single player testing was delightful - but jump on Blue Flag or a WWII server and it's just as much of a strain. I can't stand ASW so I disable it. Perhaps that is where we see things differently. Absolutely fresh windows, Oculus software and DCS install upon installing 1080Ti and it feels a bit 980Ti during the lows - but much smoother on the highs. This really is a coding issue. No matter how much hardware you throw at it... it's still gonna suffer at the low end. The current clouds issue is crippling on some servers =[

Problem solved... Please delete :) I would report it but it says it isn't to be used for that

Confirmed here too! I thought it was something I was doing wrong.