Purely a guess, but maybe regressions only during the beta don’t get mentioned in the final SU5 release notes, because they’re not fixes for anything broken in SU4.
Or maybe they just broke something else without knowing it, and it happened to fix the click spots bug 
In SU5 it’s a nightmare to click external items, like removing rotor covers, etc. I have to switch to 2d remove them and then back to vr.
Maybe. I always assumed they would also mention fixes between betas. In fact I believe I’ve seen them do that before.
Your other theory also seems very possible 
Or they just forgot to put it in the notes.
This is correct. If there is a delta between the final SU4 build and the final SU5 build, then it will be documented in the SU5 release notes. If there is a regression from SU4 in one SU5 beta build that is subsequently fixed in another build (i.e. players who were not enrolled in the SU5 beta would have never experienced it), then it will not be listed in the final SU5 release notes since it isn’t a change from SU4, only from an earlier test build.
Thanks,
MSFS Team
I am having problems in the PMDG 777
OK, makes sense. But what about regressions between two SU5 betas? Are these not mentioned when they are fixed in a subsequent beta?
Hello @BearsAreCool510,
Yes, those will typically be mentioned in the release notes for a beta build when the regression was addressed. For example, one of the earlier SU5 beta builds caused an issue that prevented WASM aircraft from working correctly. This was fixed in a subsequent beta build (and mentioned in the release notes), but the fix was not listed in the final SU5 release notes since that regression applied to the beta only and was not a delta between SU4 and SU5.
Thanks,
MSFS Team
Yes all aircraft I have flown so far include this issue. I have noticed it most on battery, avionic, and alternator switches on GA aircraft.
I have this same problem. Often cannot click items in the virtual cockpit in VR, then it works at random later. The cursor animates showing the click was detected, but the switch doesn’t move.
But I also noticed that my mouse input often fails if I try to pan the view by holding the right mouse button, or by middle clicking. That happens in 2D too. I almost feel like the mouse clicks are ignored intermittently. May be unrelated.
I also saw another post, which might be related to this issue of not being able to click things in VR:
But that was merged into this thread which is in the SU5 Beta forums - not sure if will get any attention there, so thought I’d link it in with this one for consideration.
This has to be a different thing then my post with the external clickspots, as all internal clickspots are working for me at least in the planes that I fly, since the final release. May I ask in which aircraft you experiencing this problem Mustang242Sqn?
I have exactly the same issue. Definitely not present in SU4. Do you found a workaround?
It was the Piper Dakota. I struggled to remove anything on the walkaround in VR (no click spots found or click spots blocked by the flaps or tyre inspection tooltips instead), and sometimes struggled to click cockpit items like the large battery switch, fuel switch and lights. Got the pointer tooltips but clicking mostly failed to trigger any response.
The click spots also seemed slightly off at the time, shifted ‘up’ slightly. I’ve seen people report VR click spots issues in the main SU5 feedback thread. Perhaps that’s what they mean.
As I’ve been only ‘testing’ in 2024 to see if it’s ready to replace 2020 for my regular flying, I’ve had Dev Mode enabled much of the time (normally don’t go near it). I wonder if my mouse cursor was activating menu items at times, which I couldn’t see in VR. That could have been a factor though I’m not sure it fully explains it. But I’m open minded to the possibility. Will check it again next time I’m at the PC.
Just to quote myself a moment:
But I also noticed that my mouse input often fails if I try to pan the view by holding the right mouse button, or by middle clicking. That happens in 2D too. I almost feel like the mouse clicks are ignored intermittently. May be unrelated.
I now believe this behaviour is 100% related to having Dev Mode windows open. If you click in a floating Dev Mode window, the main sim window kind of ‘loses focus’ such that right click and drag (or middle click) don’t do anything to move the view or enable mouse panning.
It’s necessary to left click in the 3D view to re-focus it (the Dev Mode window loses its outlined border at this point) at which point the view panning works again.
Just some unexpected behaviour that I hadn’t come across before as I rarely use Dev Mode (except during the World Hub alpha for 2020 but that’s a distant memory, sadly).
So let’s get back to the core problem and ignore that particular issue! 
Feeling a little foolish, I suppose but was able to reach external click spots in VR, at least for the Vision Jet. Just had to crouch then lean forward being careful not too hit desk with headset to get “face” close enough to chock left wheel, then walk to back of plane, clicking pitot cover on the way. Bringing ‘face’ up close (by standing up from seated position) to rear engine cover click spots is revealed and both front and back covers are gone. I suppose this is “more realistic” as doing these actions in real life would not be possible in a seated position, I think?
Not really when most of us are playing in a seated position, it’s not like we’re standing in our rooms walking around taking covers off 
The point is there is no reference to a change in the patch notes so it’s either A) a bug/issue or B) a change was made but not noted so if B) then C) Whose idea was it? Because the clicks spots were working far better before this change.
But as it was reported then Bug Logged during the SU5 beta suggests it’s a new issue, that unfortunately yet again the developers don’t deal with during the beta as they should be doing.
Last time I was in the sim, in walkaround mode I noticed that my mouse cursor was floating about 1 metre in front of me. It didn’t ‘jump’ closer (nor further) when hovering over interactive surfaces, like it would in the cockpit.
Maybe that’s also normal pre-SU5, I don’t actually remember, but as described above by others, I found that I could only interact with chocks etc. by leaning forwards - which in turned moved the cursor ‘deeper’ into the world - until the cursor basically ‘touched’ the object, such as the chock. Then they were clickable.
It’s as if there is no ray cast from the VR camera position, through the cursor, to objects behind. The cursor is just stuck on a 2D plane at a fixed distance from the viewpoint.
You have a mouse pointer in walkaround mode? Must be nice! Haven’t seen one in a while.
When you are in walk around mode, right click and that generally will give you the mouse cursor. Right now though, its pretty useless unless you can hug the plane around the click spot.
I do indeed! I have to middle-click to get it to show sometimes, but I do have one.
I took some screenshots the other day so I even have evidence 
Chock not clickable. Cursor depth is about 1-2ft short of the chock in 3D space:
Starting to clip through the wing leading edge (seen top left) with my head (this was in VR), cursor getting closer but still not clickable:
And now my head is completely clipping through the wing, but I can finally get a ‘hand’ cursor and click the chock! 
I don’t think that works for me. The thing is, it’s there, I can use it to click stuff on the toolbar if I can correctly guess where it is. It’s just invisible, it’s a bug. Luckily I never really need it while walking around.
