Odyssey VR specific bug reports - please contribute!

[Helmut Grokenberger]

Interesting, never experienced that fleet carrier management interface camera issue either, also am on a HP Reverb G2.

From some of the comments in here, it's looking like a Quest issue. @DeckerSolo and I both have it, even though they use Virtual Desktop and I don't, whilst none of you Reverb folks have seen it before.

To be honest, it's way down on the list of issues for me personally, just mentioned it because FDEV "fixed" it.

So, funny thing.... today, out of the blue, I've suddenly seen my carrier tipped on its nose and way above my head when I opened my management screen. I've never seen that bug before, and I am 100% sure that when I closed down the game last time the carrier management screen was fine.

Now I really wonder what triggers this bug.

 

[Arioch]

I’ve just had a fly around in Update 18.01 to check the undocumented fixes remain fixed (they are ) and I’ve noticed a change in behaviour of the horrible flickering shadows - the strobing mid-range shadows are no longer trying to induce seizures…but they appear to be totally absent instead

It looks like the blobby long distance shadows are there, then the shadows disappear, then the detailed close-range stuff pops in (settings at Ultra). Easy to see when approaching a Station or after going through the docking slot, and when flying around planetary surfaces with the local star low on the horizon.

This new behaviour is preferable to the eye-straining old version that we’ve had since 2022 and hopefully it’s a sign that the issue is being worked on - maybe the problem occurring for flatscreen CMDRs since U18 will be of benefit for us goggleheads

Edit: looks like I wrote too soon! After altering the graphics options the flickering mid-range shadows are back

 

[pFVD]

So, funny thing.... today, out of the blue, I've suddenly seen my carrier tipped on its nose and way above my head when I opened my management screen. I've never seen that bug before, and I am 100% sure that when I closed down the game last time the carrier management screen was fine.

Now I really wonder what triggers this bug.

Also interestingly, since I'm more Titan war involved at the moment, I decided to switch up my carrier livery for something more aggressive looking. Take a guess where my carrier was on the livery screen ...
Yup, up above and slightly behind. This was fixed 2 or 3 patches ago iirc, maybe more? Now it seems the "fix" in 18 that didn't fix the carrier position in carrier management for me, has unfixed the carrier position in the carrier livery screen. It was certainly fine in 17 for me, but not now in 18/18.01.

Doh.

I don't have time to test things right now, but I wonder if headset resolution/supersampling has anything to do with triggering this? Or maybe OpenComposite? Those are the only things I can think of that are external for me that might make FDEV think it's fixed as it wouldn't likely be in their testing purview.

 

[Arioch]

I’ve had a further fiddle around with shadows; deleting GPUworktable and allowing it to regenerate has got rid of the flickering mid-range shadows at the cost of them not actually being there, but then something curious occurred while doing orbits of an Orbis - after a few minutes of flying around the Station all the shadows seemed to start working correctly. I’m going to see if something similar happen planetside, as well as other locations.

Edit: no luck, flickering is not going away now. Jumping to an Orbis Station I can see the super long distance grey-ish shadows flickering, then solid black lo-res shadows kick in at about 8km from the target. At about 5km the flickering starts again (or sometimes shadows are totally absent) until the detailed shadows are rendered at close range. Weird thing is I can sometimes get the mid-distance shadows to be solid black as they should be depending at what angle my view frustum is to them, which is possibly why I thought they were all working fine earlier.

 

[Arioch]

If your FC in VR is FU* when looking at the management screen, then please add a confirmation to the new issue report:

Issue Tracker

issues.frontierstore.net

…and hopefully it can get shifted into its correct position

*Fairly Upwards

 

[Arioch]

New issue report from a user who cannot see the planetary info panel when using the system map in VR - although they say they haven’t another VR headset to check if it’s type-specific, they neglect to mention what headset is actually being used.

Issue Tracker

issues.frontierstore.net

I’ve got no issues bringing up the info panel in my Quest 3, just checked.

 

[Darkfyre99]

New issue report from a user who cannot see the planetary info panel when using the system map in VR - although they say they haven’t another VR headset to check if it’s type-specific, they neglect to mention what headset is actually being used.

Issue Tracker

issues.frontierstore.net

I’ve got no issues bringing up the info panel in my Quest 3, just checked.

I just checked as well, and I'm not having any issues either. Which isn't surprising, since I'm out exploring, and still have to use the system map if I want to find information about my planetary target... rather than the target information panel in the cockpit.

Mine's the HTC Vive.

 

[Dragsham]

Neither of us has this lssue. Missus has a quest lll I've got a Hp g2 reverb.

 

[Arioch]

Fleet carrier management screen issue has now reached the voting stage - if you’ve got votes in for either spot shadows or HUD double image then please consider moving them as those problems are currently fixed

 

[JR250]

Done.

And may I say, if there's ever an "ED Most Valuable Player" award, you'd be in it. Putting in the extra effort of adding possible fixed issues to unvote is just tops. Thank you!!

 

[Arioch]

Good news from the player who had problems getting planetary info to display in VR - it was just the control method changing between flatscreen (click with the mouse) and VR (use WSAD and select with Spacebar).

 

[Esare Kranse]

Anyone else noticing an issue in GalMap when selecting a system in VR, you can't press to route to the system, unless you first zoom in and out a little? Same thing is happening in both FC and ship Gal Mal for me. Doesn't happen in Flatscreen.

Noticed since I switched to a Quest 3. It could possibly be something odd with my HOTAS, I also had an odd issue that in VR, a double keybind for Pips was adding a Weapon pip on every Jump in and out of FSD, but it was fine in Flat with the same controller. Removed the secondary binding and it's stopped now.

Shadow flickering is possibly worse currently, my Corvette nose is flickering like crazy unless the light source is below the ship, the game seems much better if the ship I fly doesn't have anything in front of the canopy.

 

[Arioch]

Anyone else noticing an issue in GalMap when selecting a system in VR, you can't press to route to the system, unless you first zoom in and out a little? Same thing is happening in both FC and ship Gal Mal for me. Doesn't happen in Flatscreen.

Noticed since I switched to a Quest 3. It could possibly be something odd with my HOTAS…

Hi EK, I’m not able to duplicate your problem with my Quest 3 and Xbox controller - once my selection circle is over a system I can press+hold A button (or hold SPACEBAR) to plot a course, no zooming required.

 

[DeckerSolo]

Hi EK, I’m not able to duplicate your problem with my Quest 3 and Xbox controller - once my selection circle is over a system I can press+hold A button (or hold SPACEBAR) to plot a course, no zooming required.

I can't replicate the reported issue in selecting and routing to a system in the galmap with my Quest 3 / HOTAS.

 

[JR250]

Anyone else noticing an issue in GalMap when selecting a system in VR, you can't press to route to the system, unless you first zoom in and out a little? Same thing is happening in both FC and ship Gal Mal for me. Doesn't happen in Flatscreen.

Let's see if I got this right. If I did, it has been an issue since an early update. In general, ED has quite a few of issues with menu window/object focus, this is one more:

1. Open Galmap, type a target system name in the search field, press your select/enter button in the binding
2. Galmap scrolls and shows the target system
3. At this point you can't open the system or do nearly anything else in Galmap until you move the selected target a little to the side. Yep.
4. Once you do, the submenu for the target system becomes available. Things like opening the bodies, stations within, etc.

Where this gets to be fun is when you're trying to jump your carrier. You go through the above and on step #2 the system will be selected as your FC destination and a jump is scheduled, not giving you a chance to select a final destination within the system. In this case, press select on step #2 and be ready to shift/move Galmap to the side as soon as it lands on the target system. If you move the focus from target system quick enough, the FC won't schedule a jump.

I have other ED bug workarounds but they involve heavy chanting and a medicine wheel so it's best to leave those out.

 

[Helmut Grokenberger]

Let's see if I got this right. If I did, it has been an issue since an early update. In general, ED has quite a few of issues with menu window/object focus, this is one more:

1. Open Galmap, type a target system name in the search field, press your select/enter button in the binding
2. Galmap scrolls and shows the target system
3. At this point you can't open the system or do nearly anything else in Galmap until you move the selected target a little to the side. Yep.
4. Once you do, the submenu for the target system becomes available. Things like opening the bodies, stations within, etc.

I've had the same behavior since.... forever. So long that it's become part of my muscle memory to nudge my Stick a little once the Galmap has finished scrolling and is displaying the target.

Where this gets to be fun is when you're trying to jump your carrier. You go through the above and on step #2 the system will be selected as your FC destination and a jump is scheduled, not giving you a chance to select a final destination within the system. In this case, press select on step #2 and be ready to shift/move Galmap to the side as soon as it lands on the target system. If you move the focus from target system quick enough, the FC won't schedule a jump.

I have other ED bug workarounds but they involve heavy chanting and a medicine wheel so it's best to leave those out.

I don't have that. I can select my FC bookmark fine and the Galmap displays the system it is in, from there it's like always - nudge the stick to be able to select the system. Usually I do plot to the carrier by finding its bookmark and just holding the UI select.

 

[JR250]

I don't have that. I can select my FC bookmark fine and the Galmap displays the system it is in, from there it's like always - nudge the stick to be able to select the system. Usually I do plot to the carrier by finding its bookmark and just holding the UI select.

Yep, if you bookmark the destination and select it from the FC nav menu, it works great. I do this when FC jumping is particularly busy, like during CG, as things feel like they become sluggish and twitchy - maybe I'm seeing things.

I'm not sure this is a VR-only issue though. I've heard flat-Earth screeners complain about it, too.

 

[Arioch]

Just had a quick check of the new patch - the undocumented fixes from U18 are still fixed, but it looks like all outstanding VR issues (that I can duplicate) are still standing out. If anyone spots anything, please let me know

Had a quick go with one of the new FSDs on my Cobra and almost re-enacted the Epstein Drive discovery scene from The Expanse By the time I’d gone from “I wonder if I just press the normal boost button?” to actually figuring out how to switch it off, I was almost totally out of fuel, taking stacks of damage from being at several hundred percent heat levels, and several AU beyond my intended “little test hop” destination

 

[Arioch]

One thing I’m seeing with spot shadows on seated NPCs at Station concourses that I think is fairly recent behaviour (I think since player spot shadows got fixed): they used to be really poor (as in, just some odd blobs that would occasionally update due to NPC motion) but are now of very nice quality - but they completely disappear when you move more than a few meters away from the character. There’s no LOD level by the looks of it, it’s either top whack or nothing.

If anyone can duplicate this in either flatscreen or virtual flatscreen, I’ll rustle up an issue report Perhaps it’s intended behaviour in an effort to gain performance, but I’d like to know if it’s a bug.

 

[jojon]

Well, not quite the same, but I have had several double-takes the last week or two, over the draw distance willing shadows from hangar structures into existence along with the landing pad's traversal, but couldn't say whether that is new, or it just never bothered me quite as much before...

I used to be rather annoyed with concourse interior shadows ceasing to draw, at a distance of a few paces, and assume my brain has simply incorporated that behaviour into its model of how the world works in Elite...

(I have also seen more than I am accustomed to, of entire mountain ranges strobing between day and night, when the light comes in low...)