lenidcamper

That would work. However not a short term solution since Starlink is currently projecting delivery in my area "2023 or later" 😥

The rolling cache is essential with a 10Mbps internet connection. (the joys of limited choice of rural ISP. We will update our technology any day now) I use a 30GB cache. First flight over an area will show highly variable frame rate and stutters. Second flight will be much more consistent frame rate and network monitor shows no internet access.

I am content to stay on OpenXR runtime 107.2109.10010 for the moment as I can switch 2D <--> VR at will. (as long as I don't use DX12 beta). The DX12 was DOA. I got a CTD every time I switched back to 2D.

I have noticed blackouts that seem to be correlated with controller timeout. The idle controller will buzz and then 10-15 seconds of blackout. Anybody else see this?

Depends if your GameServices has applied it's latest update. See linked thread.

thanks I scanned the list but missed that post entirely. My excuse is that I was gritting my teeth so hard I could not see straight 😬

Yesterday afternoon I started up MSFS and was presented with the "London rainbow" image and before moving on to the "new in this release" images it pops up a "CHOOSE YOUR ACCESSIBILITY SETTINGS" dialog with only a Next button. I thought that was strange since I have started up many times since the last update without seeing this dialog. I was forced to accept the generic settings or reset them to what I had already configured months ago. I hit next and then it got worse. It brings up a "CHOOSE YOUR GRAPHICS SETTINGS" dialog with Low/Medium/ High/Ultra options, where again I need to accept generic settings or reconfigure. It repeats these steps for Service, Controls and Assistance preferences. Eventually it gets to the Welcome screen. I thought "well at least that is over". I went in and (maybe) undid the preference mayhem this had caused. I proceeded to fly and eventually exited MSFS. Later when I started up again I was presented with the "CHOOSE YOUR ACCESSIBILITY SETTINGS" dialog once again and had to repeat the painful process. offensive initials not allowed. It's like it thinks I have never used MSFS befor,e although when I finally get through that process I am logged in with my MS account, my profile shows all my previous activity. Has anyone else encountered this? More importantly does anyone know how to stop it??? It seems like some sort of first_login flag was set and is not being cleared. This happened in the hour interval between one flight and the next with no changes to the system (other than the pilot eating lunch).

Just got anther 2D<=> VR CTD Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6027b4a3 Faulting module name: CoherentUIGT.dll, version: 0.0.0.0, time stamp: 0x5fc6aa59 Exception code: 0xc0000005 Fault offset: 0x000000000013f1c3 Faulting process id: 0x3554 Faulting application start time: 0x01d706eb3fe74ee3 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.16.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll Report Id: 1b4052d4-0516-4064-89bc-5782f90677a7 Faulting package full name: Microsoft.FlightSimulator_1.13.16.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App This was after a two hours flight with a dozen switches back and forth between 2D and VR

I have not seen a crash during startup where the audio service is implicated, but I have multiple CTD's at "12f0f" in PerceptionDevice.dll_unloaded I do switch 2D <=> VR quite often (MSI AfterBurner and LittleNavMap) so it does seem to be VR context swapping related. This mornings flight was more than 2 hours, switching to 2D and back to VR at least a dozen times before the crash.

It is possible to launch LittleNavMap in its own follow-me VR window which is a better size than the Desktop window (there is still a minimum resize limit), but unfortunately it does not respond properly to mouse pan or zoom.

I had a number of CTD's at the same offset with Reverb G2 and WMR Have not been able to determine a fault scenario I have some other popular offsets 0x0000000001245abb 0x0000000001e0fd8b Twelve instances in the past week

The problem with "follow me" is that the resolution of the floating window is reduced so it is hard to read text.

If I want to consult LittleNavMap I do not bother to take off the VR headset. With the G2 and WMR I can pause the simulation, exit VR mode and select the Desktop in the WMR Portal and view the LittleNavMap. With VoiceAttack commands for pause/resume and mode changes I do not need a keyboard. With Oculus it is even easier. The Oculus toolbar allows you to bring up a 2d image of any running window while in VR I find that a lot easier than taking off the VR headset, getting up from my sim cockpit and going over to the desk.

The Add-On-Linker has the added benefit that you can use a folder tree in the outboard "my-addon-location" folder to organize add-ons by asset type or geographical categorization. You don't have to deal with a flat Community folder with hundreds of obscurely named add-ons.

It would be nice if MSFS displayed a "Flight Simulator starting" box right away so we don't have to wonder "did I actually click on the shortcut?" until we get the black full screen window some time later.