Release 17 has broken VR (Double image on Target Scanner)

Looks like Release 17 has broken VR. I'm getting a different image in my left eye vs my right eye when leaving stations (target scanner). This causes headaches (at best) and nausea (at worst). The game is basically unplayable for me. Others have reported this as well: https://issues.frontierstore.net/issue-detail/61993

Basically (for me), the ONLY reason for VR is Elite Dangerous -AND- the only way I play Elite Dangerous is in VR... Quite simply, its a 1:1 relationship for me. I have a custom built physical cockpit, chair, foot rest, etc. ...and I need to use contact lenses with a custom VR prescription. All this just for E.D. I also typically only play during the winter, low-daylight months because the configuration and physical prep is so demanding. When I sit down to do this, its at least for a couple of solid hours or game play.

Just to make matter worse...

1. I just upgraded my home PC and did a complete reinstall of everything (not a rolling upgrade). This includes a fresh install of Elite...
2. I also reinstalled Voice Attack, HTC Voice Packs (Kate/Singularity), EDMC.
3. I moved over all my key bindings and graphics settings
4. I reintegrated all my custom commands into HTC/VoiceAttack.
5. Installed/configured a new version of PiMax

Not a small investment. Several hours of reinstalling, reintegrating, tweaking, and "oh look, a new patch!" "Good", right?

...and just to add salt to the wound, just dropped almost $2K on a headset VR upgrade to replace my 8KX with a Crystal. Just to find out (surprise, surprise) that the most recent update basically broke VR with its FSR implementation. Put my shiny new Crystal on, "Nice image but, Uh Oh!" Did I mention VR is my only reason for ED (and Vice Versa)?

Anyway, I tried changing the frame generation methos from AMD FSR, to AMD CAS, to Normal. Only FSR is playable. The frame rates go into the toilet with CAS and the system pretty much locks up using "Normal". Yeah, these are not native limitations of my 4090 here...

I've also tried messing around with HMD Quality and Supersampling but none of these seem to mitigate the issue. I either get the left/right eye discrepancy or the game is totally unplayable.

Apparently, the devs are feeding their FSR implementation with two different visual sources at some point. It seems to get reset (properly) once you jump to supercurise - until you visit another station.

It appears that the only thing that will make the game playable in VR again is the Devs fixing their code.
 
U17 broke lots of things. I started a one week break just before it released. After reading about all the issues, I decided to extend my break.

I'll be back once things are sorted. Until then, I've got plenty of other uses for my most recent PC build (well over $6K). Building a setup specifically for one game is asking for issues IMO.
 
Just double-checked, and I don't have any such problems. ED works as usual, using a Quest 2 over Virtual Desktop on a 3070 here, 125% HMD quality, MSAA, shadows on low, no upscaling. Using Steam VR as runtime as I'm lazy and it's fast enough, and latest NVidia drivers (because of the security issues they fixed). It's odd though why only the left holo is misbehaving in the vid, I would suggest VR runtime or driver issues, but can't verify.

HTH, O7,
🙃

NB. Legacy drove me nuts the last time(s) I booted it, in the FSS, mouse coordinates were off and so I happily clicked around on the desktop without noticing, starting apps and such as the cursor was not caged to the window anymore, it seems. Repeatedly. Could have been a mouse problem (MX3 here), but EDO does not have the same issues.

EDIT: I remember a friend having similar problems, but with moving smoke effects, shadows and such, on his Valve Index when EDO came out. AFAIK it's fixed for him, and it seems to be device related. Oculus/Quest (had a Rift before) always worked without issues, Valve (also supported) not quite so, other HMDs are not supported and won't be (don't find the support statement right now, but FD said so).
 
Last edited:
This is the issue for me and others - the double image occurs when any sort of upscaling is applied.
Why is anyone using upscaling for VR in this day and age? VR is about fluid motion and clear visuals. Upscaling adds artifacts and load. Modern headsets have high native resolution. No nead for upscaling.

Native resolution should always be the goal, unless you have a headset with terrible native resolution of course.
 
Well, the OP apparently has a Pimax Crystal (~12K) and even a 4090 seems to be too weak to provide reasonable fps natively, so upscaling is the obvious solution here. At that resolution, I doubt that artifacts are a real problem anymore.

Btw did anyone hear of an update 18 so far or has the game silently come to its end, in the light of FD's economic 'streamlining'?

O7,
🙃
 
Last edited:
Why is anyone using upscaling for VR in this day and age? VR is about fluid motion and clear visuals. Upscaling adds artifacts and load. Modern headsets have high native resolution. No nead for upscaling.

Native resolution should always be the goal, unless you have a headset with terrible native resolution of course.
I don’t think it matters why anyone uses upscaling - it’s a bug that arrived with the latest Update and needs fixing.

If I use upscaling I get the visual error on the left-hand HUD element, if I don’t use upscaling I get the double image on the centre HUD element when the landing holo kicks in 👍
 
Why is anyone using upscaling for VR in this day and age? VR is about fluid motion and clear visuals. Upscaling adds artifacts and load. Modern headsets have high native resolution. No nead for upscaling.

Native resolution should always be the goal, unless you have a headset with terrible native resolution of course.
There are reasons to use upscaling, for me it was to get fluid movement when I didn't have the hardware to do native resolution and the visuals were good enough.

The bug also affects supersampling, so anything not 1:1
 
Horses for courses, I guess. I always aim for native resolution and then turn down graphical settings appropriately.

Has the OP tried native resolution with low settings? It seems like some people are too eager to pump up arbitrary settings at the cost of artifacts and overall performance. I'll take low settings at native resolution over high settings riddled with artifacts/upscaling any day of the week.
 
U17 broke lots of things. I started a one week break just before it released. After reading about all the issues, I decided to extend my break.
Speaking of, any word from Frontier if they plan to fix the cornucopia of new (and old) bugs anytime soon? I'm kinda maybe sorta tempted to buy Odyssey when it goes on sale in a week or two, but some of these bugs really turn me off to that idea.. If Frontier is committed to fixing at least the U17-specific bugs, that might help them make a few extra $$.

One of the things that frustrates me with this company is the quality of their updates. There's no reason an update should reintroduce bugs that were fixed years ago (things like security ships firing on everyone they scan, for example). There is something fundamentally broken with how Frontier handles its code base, versioning, etc. I wonder if they are running some sort of homemade SCM (probably written by the same people who created the issue tracker) rather than using Git or Subversion. There's just no good reason for reoccurring bugs.

Anyway, I hope they fix these, because for the first time since Odyssey was annoyed years ago, I'm actually, maybe, kinda, sorta, no promises, might be interested in it...
 
Speaking of, any word from Frontier if they plan to fix the cornucopia of new (and old) bugs anytime soon? I'm kinda maybe sorta tempted to buy Odyssey when it goes on sale in a week or two, but some of these bugs really turn me off to that idea.. If Frontier is committed to fixing at least the U17-specific bugs, that might help them make a few extra $$.
There's supposedly an update coming late this month. That's all we know. I have little faith in anything getting fixed, considering all the original bugs we're still dealing with. They might just surprise us though. I still remember how shocked I was after U15. It didn't create any new bugs for me. U16 wasn't too bad, but U17 definitely was.

I'm really not concerned with bugs so much. That's just a way of life in the ED universe. A bug-free game wouldn't feel right at this point. I just got burned out when my path to a major goal suddenly took a hard left turn (miscalculation on my part). I'm having a great time playing other (older) games right now. I'll be back eventually regardless, so the HOTAS is staying on the desk.
 
I'm really not concerned with bugs so much.
For me it's about very specific bugs rather than the generic term. When I read about something that I know will negatively affect my specific gameplay, that is when I become concerned. The bug mentioned in this thread, for example, is no concern to me, because there is no way I would be able to play Odyssey in VR (I'll be struggling to make it work on 1080p flatscreen). Other bugs, however..

That said, I totally support the OP, because I know how it feels when a specific bug ruins the game that you were enjoying before an update. So even if a specific bug doesn't "bug" me, I'll never be dismissive of someone else suffering because Frontier broke the game for them. Updates should make software BETTER, not worse...
 
Horses for courses, I guess. I always aim for native resolution and then turn down graphical settings appropriately.

Has the OP tried native resolution with low settings? It seems like some people are too eager to pump up arbitrary settings at the cost of artifacts and overall performance. I'll take low settings at native resolution over high settings riddled with artifacts/upscaling any day of the week.
The OP is in the same situation as me - they linked the issue report that I submitted.

These are not “artifacts” due to compression/performance that we are seeing, it is a doubled image in the left eye of a specific part of the HUD - either the target scanner (if using upscaling) or the landing scanner (if not using upscaling). For users with different systems it is reversed, but a double image is still occurring in the left eye. A very similar issue occurred in the Odyssey alpha.

It is a confirmed bug and Acknowledged by FDev 👍
 
The OP is in the same situation as me - they linked the issue report that I submitted.

These are not “artifacts” due to compression/performance that we are seeing, it is a doubled image in the left eye of a specific part of the HUD - either the target scanner (if using upscaling) or the landing scanner (if not using upscaling). For users with different systems it is reversed, but a double image is still occurring in the left eye. A very similar issue occurred in the Odyssey alpha.

It is a confirmed bug and Acknowledged by FDev 👍
Ah. Fair point. Good thing we still have Legacy, I suppose... 🙂
 
You're a way more aggressive door-to-door salesman of Legacy than I ever was for X4 or Space Engineers, LOL. Pushing Legacy a dozen times in every thread doesn't help fix Odyssey...
...and bears the danger of people getting annyoed by you. Or putting you on their ignore list. Or both. Like people complaining about engineering years after they stopped playing :).
 
You're a way more aggressive door-to-door salesman of Legacy than I ever was for X4 or Space Engineers, LOL. Pushing Legacy a dozen times in every thread doesn't help fix Odyssey...
Ah, well. Win some, lose some. :)

Edit: I will not be bothering this thread further. :)
 
Back
Top Bottom