Ben Russell

@Coop

The Saab is 8 years old and has been upgraded through multiple xplane versions for free.

Copy the scripts folder from one of the other variants into the Airborne folder.

Hitstart products make heavy use of multi threading and graphics driver features that other products do not use. The products you are comparing to do not use these features. Your comparison is only skin deep. Both of your issues are probably fixable by using xplane in opengl mode. You probably aren't willing to do this because of fps drop. The root cause of the issue is the AMD drivers.

Change your Windows display scaling settings to 100%.

What part of "am not going to discuss this further" are you confused about? Rhetorical.

Thank you for the Log file. It appears Gizmo is working correctly and is able to talk to the x-aviation servers. A configuration issue with your PC is blocking it from writing to the license file to save it to disk though, as indicated by these lines in the Log.txt; 0:01:52.741 G64: debug: GK: RX license data from server. 0:01:52.742 G64: debug: Toast Message:(type:error) (X-Aviation Licensing) / (Could not save license data.) Please follow this guide to "take ownership" of your X-Plane folder ensure your file system permissions are correct: https://www.laptopmag.com/au/articles/take-ownership-folder-windows-10-using-file-explorer (You stated that you have "Full Control" but sometimes simply moving a folder out of "Program Files" is not enough...) If you have run a "take ownership" operation on your X-Plane folder in its new location and still cannot get the license data to save correctly we might have a plugin clash. Having looked through the Log provided the only items that stand out to me are: - Loaded: C:\Users/Captain Dudley/X-Plane 11/Resources/plugins/A-Better-Camera/win_x64/A-Better-Camera.xpl (net.llic.brat.abc). - Loaded: Custom Scenery/Sedona UHD/plugins/XCD_Scenery_Technology/64/win.xpl (XCD.ST.SXP-PA.KSEZ). If the "take ownership" operation outlined in the above guide does not resolve the issue: 1. Please try disabling the "a better camera" plugin. This is best done by creating a "disabled" folder inside "X-Plane/resources/plugins/" and moving the entire "X-Plane 11/Resources/plugins/A-Better-Camera/" folder into the new disabled folder. Disabling the plugin from inside X-Plane once it has loaded is not enough. 2. Please try flying in a different location so that the "Sedona UHD" scenery is not loaded and it's plugin is not loaded either. You may need to select a different location in the sim then restart the sim to ensure that the Sedona UHD plugin has never been loaded in sim. All plugins share a global pool of resources and cross contamination is just a fact of x-plane life. It's annoying but we have no control over it. Hope that helps.

Please attach a copy of xplane/log.txt to your next post.

You probably have x-plane installed inside the "c:\program files\" folder. Windows blocks write access to this folder to protect system integrity. This is likely what's preventing your license data being saved to disk. Try moving your x-plane folder to your desktop or some other non-protected location. If you are unable to resolve the issue using the above steps please attach a copy of x-plane/log.txt to your next post so that all available diagnostic data is available to help troubleshoot. Hope that helps..

Please try removing C:\X-Plane 11/Resources/plugins/124thATC64 Then re updating your x-aviation licenses and reloading the sr22.

Gizmo loads as a global plugin before any aircraft. This is why you're seeing it affect the AeroSphere product. The problem is the AMD drivers. If it was Gizmo only the SASL powered JF Archer product would work. It does not. If it was X-Plane none of the products would work in Vulkan mode. As I have stated multiple times, AMD GPU's are known to cause various issues with Vulkan mode. I cannot offer you any further assistance with this until either AMD fixes the issues we've been seeing OR X-Plane 12 comes out at which point we will be reviewing how AMD owners are affected. Good luck.

Your Log.txt appears to have been edited. Please don't do that. It's not constructive. Have you tried starting X-Plane in OpenGL mode?

Why do you need an old version of Gizmo?

Your "no plugins" Log shows me that the Aerosphere Cherokee does not use any plugins, therefore it's not using the OpenGL bridge. You then state that the JF Archer crashes. It's using SASL and features some custom drawing which hits the OpenGL bridge. This reinforces my opinion that it's the AMD graphics drivers at fault. Your options are basically: "Don't use Vulkan" or ... "try older drivers..." I don't have any AMD hardware and because it's so widely glitchy I haven't been tracking which, if any, AMD driver versions are useful. This has been reported to AMD by Laminar but AMD don't seem to care. OpenGL bridge mode is a pretty niche requirement and it would be affecting a very small % of AMD customers. These problems _might_ go away with X-Plane 12 as it has more thoroughly re-worked graphics engine.

Thanks. Here's the thing... X-Plane provides an "OpenGL bridge" to plugins when it's in Vulkan mode. Gizmo and other plugins don't actually do anything different. X-Plane and the GPU driver and doing all the magic behind the scenes to make it work "seamlessly" and provide backward compatibility. Unfortunately in some cases bugs and glitches do happen. I had a look at the products you listed and the JustFlight Archer seems to be the more "GL complicated" of the two... Have you verified that these screens work in Vulkan mode? The plane might load but actually opening these displays and interacting with them is another level of code complexity. They'll be using much of the same "OpenGL bridge" code... not identical, but it helps us narrow things down. Thanks for your help investigating this. I can't offer you any steps to resolve this yet. Gizmo is going to see an update "fairly soon" that has some major internal changes to how things work, the order of ops, etc. There's probably some font-generation code running at the point where Gizmo is locking up for you. I'll review the code and add some additional debug output for those events but I can't give you any sort of release date at this point in time. Sorry I can't resolve your problem at this time.

Without gizmo installed, do you have other third party aircraft with custom avionics that load and draw correctly? If yes, name them. AMD drivers and vulkan cause a wide variety of problems and errors. You are the first that I have seen to report a complete lockup.

This is probably an OpenGL + AMD GPU Driver issue. Do you have any other aircraft with custom-drawn avionics that are working?

Please attach a copy of x-plane/log.txt to your next post.

Gizmo, the plugin that runs the IXEG scripts, starts its sound system very early on in the x-plane life cycle. This is likely the root cause of the problems that come up when switching audio output devices. (It happens with bluetooth headsets and xbox controller audio too...) The future updates for IXEG are going to port the sounds to FMOD which is provided by X-Plane and should be far more capable when it comes to output device selection. Because of this planned port the audio code of Gizmo is not a very high priority for upgrades but I might be able to work something in, in the near future, that might help. The only hint I can give you is to try and set the windows audio output to your reverb headset _before_ starting x-plane. That should let Gizmo attach to it as the audio output device. Thanks for your report. Sorry I can't give you a better solution.

XP12 compatible IXEG update is likely to bring even better fps once FMOD sounds are in place. I've been pouring a bunch of work into Gizmo to enable multi-threaded systems too. Appreciate your kind comments. There are even better things coming in future.

You also have X-Plane installed via Steam inside the "Program Files (x86)" folder. This causes Windows to block saving of the license file to disk to protect the "Program Files (x86)" content from modification. You can use the built-in steam features to move the X-Plane folder somewhere else like your Desktop/Games/X-Plane folder or Documents/Games/X-Plane folder. (You will need to create these folders... choose whatever suits you.) You can also move it to another disk if you have one. The following Steam Guide uses D:\Games\Steam as an example. https://help.steampowered.com/en/faqs/view/4BD4-4528-6B2E-8327#move

Please attach a copy of X-Plane/Log.txt to your next post. This will aid in diagnosis.

Looks like there's a plugin clash 0:08:19.362 G64: core: curl_easy_init() provided by:[G:\X-Plane 11.55r1\Resources\plugins\124thATC64\win_x64\libcurl.dll] Please remove: plugins\124thATC64 temporarily and see if Gizmo is able to activate correctly.

Gizmo is unable to save the license data to disk. Please try this to take ownership of the X-Plane folder: https://www.laptopmag.com/au/articles/take-ownership-folder-windows-10-using-file-explorer If the above instructions do not resolve your issue I suggest moving the X-Plane folder to your Desktop or Documents folder so Windows will know that you should be able to write data into it. Hope that helps. Ben.

Gizmo64 is required to be installed and enabled to validate your licenses. Please check X-Organiser (or similar) has not disabled Gizmo in some way if you're using it. If the above does not help please attach X-Plane/Log.txt to your next post.