And regardless how many times you repeat this, YOU DID NOT DO what we the VR users were asking for and for that reason so did many non-vr users ask for it too, so stop saying that ! You came up with something else that had 100% nothing to do with what we've asked for ! NOTHING WHAT SO EVER !
And regardless how many times YOU keep repeating that, the only thing we changed was exactly what ALL those users ( except you ) asked, and ALL of them confirmed the change FIXED what they initially reported as broken.
Because, as explained so many times, the ONE and ONLY change was:
- the X icon didn't really close the menu, it just hide it. THIS ( and only THIS ) was the thing all users, reported to have "broken VR" and THIS, and only THIS was the latest change, which ALL users reported to have "fixed VR": the X icon now really closes the toolbar icon instead of hiding it, but ONLY in VR. In standard mode, the menu is only hidden. That's the one and only change.
Your sentence "navigraph will cause a momentary pause as it loads, but then since it doesnt hide on you and you never need to close it again for the rest of the flight" clearly confirm you keep confusing the way the menu works now ( always disappearing, regardless of the method used, hidden or turned off ), with the eventual availability of a PINNED MENU FEATURE!
Which as explained so many times already and as clearly indicated in the Sticky "Roadmap" thread, IT IS PLANNED for VR, but I already explained countless of times why is not a quick fix.
Regardless this is not the point of this post ! The point of this post is why does using hot key to bring menu back on screen causes such a big long pause !
Of course is the point of this post.
The hotkey results in a pause, because each time the menu reopens on screen, there are many things going on, from communicating between the menu and the rest of the program code ( due to the lack of proper integration between the JS/HTML framework and Simconnect that requires several workarounds that reduce speed ), but also Simbrief is checked when the toolbar gets active so no, a pause of JUST 0-5-1 seconds is really not much all considering.