Ben Russell

This is not optional advice. Failure to move X-Plane to another folder will result in long list of continuing problems where config files for various items cannot be saved correctly or are continually zapped back to defaults. X-Plane is a triple platform(Mac/Win/Lin) title and the existing trend is that all config data is stored within the X-Plane folder for all products from all makers. The upside is that each X-Plane folder is almost entirely self contained. The downside is that X-Plane doesn't like being in system owned folders on Windows. Thanks.

You need to move xplane out of the "program files" folder. This folder is protected by Windows. Do not simply run as administrator.

Your X-Plane folder is inside of a "Program Files" folder which Windows is probably protecting. This means the X-A activation process cannot save your license file, as indicated by this line: 0:03:15.850 G64: debug: Toast Message:(type:error) (X-Aviation Licensing) / (Could not save license data.) On my own system I have D:\SteamLibrary as the root folder for my extra steam content. Not D:\Program Files\ Here's a quick google result on how to move a steam app to another drive/folder: https://www.howtogeek.com/269515/how-to-move-a-steam-game-to-another-drive-without-re-downloading-it/#:~:text=To move an installed game,library and select “Properties”.&text=Click the “Local Files” tab,You're done. Please avoid the temptation to run X-Plane as administrator to override the Windows protection of your Program Files folder. Let us know if you need more help.

https://forums.x-plane.org/index.php?/forums/topic/116242-custom-views-file/

Don't run X-Plane as an admin. This would've worked: https://www.laptopmag.com/au/articles/take-ownership-folder-windows-10-using-file-explorer Installing X-Plane in the Program Files(x86) folder probably messed up the permissions which persisted when you moved it "somewhere else". Re-claiming ownership and _possibly_ granting write permissions would've been enough. Forcing something to run as Administrator out of frustration is almost always a mistake and a good way to get system-wide extremely persistent malware.

Please post again and attach a copy of Log.txt from the X-Plane folder.

I'm exploring the issue at the moment. Waiting for X-Plane to load while I post this. My apologies for the inconvenience. Hopefully a few more hours and I'll have this resolved.

You have a different problem. You have not provided any Log.txt file.

X-Plane is installed in the Program Files(x86) folder which is protected by Windows. Move it somewhere else.

It's probably looking for x-plane.exe ... which doesn't appear in your screenshot.

Install a clean demo copy of X-Plane. Install only the IXEG product into that new copy. Test. Add your extra plugins one by one. Test.

Are these custom scenery airports or just stock x-plane stuff?

This issue has been noted in the bug tracker. Please report what kind of VR headset you're using and your 2D monitor resolution choices for completeness. It seems the size of the 2D windows in VR is related to the resolution of X-Plane when it's in 2D.... need to collect more data. I don't have a 4k screen here and only have an unloved HTC Vive to test with so I might not be able to reproduce this at all.

Have you tried switching the default windows sound output to your VR headset before starting X-Plane? ( Click volume in task bar, select VR headset from drop down list of choices that appears above volume slider...) I'll look at making Gizmo better behaved with regards to sound output device in future builds but please understand that it's a very low priority issue. ~6.5% of all x-plane users have ever tried VR. You are the third person this year to report sound issues related to VR. The other two reported that they could start the Winodws Mixed Reality app/service before X-Plane to resolve the issue. I'm guessing that you've got a Vive... again from your Log.txt... when I used mine years ago it didn't need any WMR stuff so I'm not sure what's going on for you. ( Please don't make devs guess. Include as much information as you can upfront. The fact that you're using VR, the type of headset that you've got that will let me google something useful. The rest of the details abotu your system that I'm likely to ask for at some point. It saves both of us time and frustration.)

Probably VR related. (There are traces of VR in your Log but you didn't bother to make it clear so I have to guess.) Does it work if you use it in 2D mode?

Please attach a copy of X-Plane/Log.txt to your next reply.

Something has already been changed in the Saab to make it require 11.50+ It is very unlikely that a special version will be made where this is different.

Please reply with a copy of X-Plane/Log.txt attached.

In the third screen you see where you do not understand you need to click on the item for (21 Feb 2021). When you have selected this click the DeAuthorize button. Another window will appear where you need to type "FREEZE" in the box that appears.

Looks like X-Plane is getting stuck in some kind of Vulkan-related loop. Option 1: Update your GPU drivers, test again. Option 2: Use X-Plane in OpenGL mode. Option 3: Try removing "X:\X-Plane 11/Resources/plugins/SAM/" temporarily. Hope that helps..

Thanks for the email Greg. I received your Log.txt file and read it. The new version of Gizmo that the saab has installed isn't working for you because you're running an older version of macOS. You have the following choices.. 1. Upgrade your macOS version.. 2. Wait for an update to Gizmo that hopefully works on your older version of macOS. (It might not, I don't have an older mac to test with..) 3. Delete the new version of Gizmo64.plugin from your plugins folder. Rename "Gizmo64 2.plugin" in your plugins folder to Gizmo64.plugin so that it can work correctly. If you use option 3 you will be able to continue using any other products that rely on Gizmo64 being installed. Thanks for your patience.

Please attach log.txt from your xplane folder.

You seem to have an old version of Gizmo installed. Please stop messing around, let the Saab installer do it's job. Do not swap the plugins around when it's finished. If you need further help post a complete copy of Log.txt from your X-Plane folder. Screenshots and small slices of the Log.txt are not useful.

Please try installing this: https://go.microsoft.com/fwlink/?LinkId=746572