Strangley, you can Disembark into on foot mode and access the menu from the Wheel thing and it then works....a workaround, but a pain no less.
It’s interesting to note that it’s now into the second tier of the popularity pyramid - along with https://issues.frontierstore.net/issue-detail/204 (FSS orbit lines) we may be in danger of breaching the Top 20 list 
It reads to me like VR is crashing when dropping from Glide? A quick trawl through Issue Tracker shows several Expired similar issues and current Confirming problems with invisible planets causing Orange Sidewinders - so this new bug is possibly not VR specific.It is VR specific. I could land there in pancake without problems. The game was crashing VR part only of itself.A new issue report:
https://issues.frontierstore.net/issue-detail/42056 - Some planet landings causing CTD - 0/10
The provided example planet is about 5000 ly from my current position, so just a touch too far for me to bob over and check
Thanks for clearing that up!
Thanks for clearing that up!
Hopefully some other CMDRs can check this out - by the time I’d make it out there the issue would be in danger of Expiring
I'm on my way to Sgr A*. So if I encounter more location-specific bugs in the future it will be even harder to confirm . Though I doubt this is location specific (i.e., it's an engine bug, that is triggered in more complex planets or some planet types).
Can you share any of the planet details? I can see the system on EDDB but there’s no further info - if I can find a similar body then I’ll quite happily check it outSorry
I've assumed that the bugs I submit to the tracker are being looked also by FDev QA... but now that I re-read what I just wrote I can just say that I was naïve
Edit: just checked FAQ "When an issue has been “Confirmed” by players, our internal team will review the issue"... should have done it before submitting issues, wouldn't bother.
Can you share any of the planet details? I can see the system on EDDB but there’s no further info - if I can find a similar body then I’ll quite happily check it out
Good luck with the journey - let me know if you get the same VR weirdness I experienced at Sag A* when I went out there
One of the Expired issue reports gave a location: BD-05 2778 1 - an atmospheric HMC world, not too different to your problem planet. It’s not very far from where I was, so I popped over for a look - the system actually has two landable HMCs with atmospheres and I was able to drop down to both of them without issue (and very nice looking they were tooThanks
I think something didn't sync up from my end to edsm I re-scanned journals and now info should be there: https://www.edsm.net/en/system/bodi...idB/336506627/nameB/Byua+Euq+DC-R+b22-0+ABC+2 (if it isn't for you than idk what's wrong)
Here are some screenshots:
View attachment 258406
View attachment 258405
).Thanks for checking it!One of the Expired issue reports gave a location: BD-05 2778 1 - an atmospheric HMC world, not too different to your problem planet. It’s not very far from where I was, so I popped over for a look - the system actually has two landable HMCs with atmospheres and I was able to drop down to both of them without issue (and very nice looking they were too
For what it’s worth, I’ve got a 3070ti (driver 471.68) and running a Quest 2 through the standalone launcher.
Were you getting the crash after exiting Glide?
I know this sounds like switching it off and on again advice but seriously, every now and again its good practice to isolate you pc from the power supply (uplug it from the wall) and disconnect your Hdmi cables from both ends if possible, weird static buildup can cause all sorts of issues. this simple solution has saved my sanity on several occasions and although it may not help in your case and it may indeed be software related... it never hurts to try the simplest solution first
I’ve still got my Rift S so I’ll unbox it tomorrow and see if that’s the issue.
