Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes I have the same problem, though it is not only in VR. Sometimes (very rare) it happens also in 2D.
Provide extra information to complete the original description of the issue:
I can reproduce this error in VR if you end a flight, choose another Plane and start a new flight.
If you stay in VR during the above steps, the button is always missing on the second flight.
For me it occurs since SU12 (beta and Release).
If relevant, provide additional screenshots/video:
Screenshot was already taken by OP
Additionally the nameplates in Multiplayer and the Ready to fly Button has another design sometimes as shown in another screenshot here. Maybe it has somebody to do with it (wrong Font Initialization?)
I started having the “Ready to Fly” button not appearing about 2 weeks ago. In my case I also found that my vram usage was at/over 100% (12GB with a rtx 3080 ti). Fixing my vram saturation problem solved this issue completely. Clearing all the nvidia caches, as shown here, and switching to DX11 solved my vram usage problems. In its current state, using DX12 beta increases my vram use by 50%!
Dx12 is certainly causing problems with VRAM, as has been remarked in other threads, so you may have a point,
I have a GTX1080Ti which has 11Gb, higher than the 8Gb which is common on video cards which seem to have problems with Dx12. Normally my VR seems to run OK, although very occasionally in the 787 I need to exit and re-enter VR when I start getting melting images - there does look to be a memory leak either on my Quest 2 or in the sim. I am certainly running near the limit on the VRAM, and maybe over it on occasions.
I cannot run VR on Dx11 (I get artefacts which make it unuseable), so this is not an option for me.
Asobo seem to have got Dx12 sort of working, released it as a beta, and then lost interest. They said in a Q&A they will take it out of beta once they get the number of CTDs down. This may involve some improvement in the VRAM management I suppose, but maybe not. However, leaving it in its current state for so long is really inexcusable.
@AcidBath6450 Good Point with DX12. Thanks. I will try to run it on DX11 and see if that solves the problem for me, too.
But as ExtraPilot6480 already stated it would also a trade off for me as I think DX12 runs all in all smoother and takes more advantage of modern Hardware (Multithreading, HAGS to mention a few).
About the VRAM: I am running a 4090. If this card would running out of VRAM every card on the market would I think.
And yes. I found out the same about the cache. If you siwtch between DX11 and 12 in MSFS or vvice versa it is always better to delete the Nvidia cache.
::Edit AND not to forget DLSS in DX12 which is what I am using…
Also having this issue in VR where there is no “Ready to fly” button about 60% of the time. I find it happens mostly on the first flight. If I restart / reload the flight (not the sim) it will usually fix it 99% of the time but then the fly now button appears messed up, although it is clickable. The toolbar is also then displayed in a strange white text format like another poster mentions above.
I replied above that fixing vram saturation problems I was having solved this problem for me. Well now it seems my “fix” only prevented the problem from happening nearly all the time, for now it seems to occur once in about every 9 or so flights. Definitely it’s sort of random. Clicking on or very near the text that appears in place of the button starts the flight and all becomes as expected after that. This is now an “oh well” for me, but it’d be nice not to have to deal with it.
Like you, I believe the root of the problem is likely to be the shortage of available VRAM, but how I can fix it on my system is not obvious. I just hope Asobo will spare some time to fix the video memory problem in DX12, but they just seem to be ignoring it at the moment. This despite the reports that many users are unable to use DX12 at all due to VRAM shortage problems.
I cannot say for certain that the messed up “ready to fly” problem is solely due to using DX12 or saturated vram, since neither is now happening when I see the problem occur. But I totally agree that the current state of DX12 in MSFS is unacceptable (to say it politely). LOTS of users like yourself are stuck ‘with their back to the wall’ having to take a big step backwards in the visuals to deal with it (or pony up $$$$ for a 4090). Lucky for me, DX11 works fine for my needs.
Also, to confirm this issue is still present in SU14 beta. Wasn’t expecting a fix given nothing in the release notes - just confirming it’s still around! (DX11 and 12 with a 4090!)
This is so annoying. Half the time when I try to work around it by temporarily switching to 2d the game just crashes. I don’t understand why we need to this ready to fly button in the first place. So pointless.
