Ben Russell

It would be nice if you'd included more than a verbal description of your bug. Instead you've just filed a rant.

From the xplane menu; Plugins / Gizmo64 / Windows / X-aviation Licensing..

I'm sorry. You're going to need to wait for an official reply from the support@x-aviation.com ticketing system. No one on the forums has access to the X-Aviation customer records of any kind. I recommend that you do not send any more emails for at least three business days. This is a standing X-Aviation policy and is published here: https://www.x-aviation.com/catalog/contact_us.php Please understand that there are many customers already in the queue.

What kind of response are you hoping for if you don't need me to verify your account and purchase history?

Hostname is only for your reference and makes no real difference to the DRM system. All other details are restricted to the X-Aviation support system. No one on the forum can verify your purchases or inspect lock out reasons. Sending multiple emails to the support ticket can slow down any response.

Removing DataRefTool will make your logs significantly easier to read and more useful. It is spamming them full of (sometimes corrupted) entries from a background thread* that mixes its (mostly useless) info with the entries from everything else. Here's an example: * Logging is the only known "thread safe" part of the X-Plane SDK.

Does the folder X:\Steam Games\steamapps\common\X-Plane 11\X-Aviation exist? It should've been created during product install but maybe you removed it, just making sure..

iMac's don't have screws. They're glued. It's a massive headache to deal with and even Linus Tech Tips fried their monitor doing it. Just pay the tax and keep the warranty.

Good to see you resolve this. Thanks for taking the time to report your success and solution to the forum.

https://forums.x-pilot.com/forums/topic/16091-ixeg-733-development-status/

Make a copy of this folder: X-Plane / Output / preferences / There are several files inside. Read through the names and delete the ones you'd like to reset.

http://www.xprealistic.com/

Windows update will typically trigger a new machine ID 2-3 times a year. I consider this an acceptable trade-off in the "giant waste of time" that is DRM technology and code. On the other hand, Gizmo pays almost no attention at all to the hardware your machine has in it.

Probably reshade or some other weird special effects plugin causing weird side effects.

Something(a plugin) is causing a strange memory corruption in your sim session. Your log is filled with the following string: "AIRCRAFT/X-AVIATION/SAAB 340A/PASSENGER VARIANT/LIVERIES/LDJ-WAGGA WAGGA VH-SBA/" This eventually builds up into a log clogging repeating mess that is probably overwriting various bits of memory in the sim that will eventually lead to a weird behaviour or a crash. I don't know for sure what's causing this but because the string has been converted to ALL CAPS I can say that it's not Gizmo. Gizmo does not perform a caps transformation on the data, there's no need to do so at any point, it only makes life harder if you support all three OS in your source code and design. (Linux specifically is case sensitive..) You can see Gizmo logs the same data here: 0:02:26.124 G64: core: Livery Changed: Name:(liveries) Folder:(Aircraft/X-Aviation/Saab 340A/Passenger Variant/liveries/LDJ-Wagga Wagga VH-SBA/) My advice is to try disabling FlyWithLua.... fly a session, inspect your Log.txt for any ALL CAPS data about the livery selection. I base this on the fact that it's running unknown scripts and shares close memory alignment with Gizmo because of the use of Lua. It also shows some activity in the Log file between the time when Gizmo logs the livery data (cleanly) and the first signs of the glitch appear in the Log. The other plugins showing activity during this window are GroundTraffic, AOS (doing a weather update) and X-RAAS and they seem unlikely to be inspecting the livery data. If disabling FWL doesn't work I'd try disabling: X-Plane 11/Resources/plugins/SAM/ X-Plane 11/Resources/plugins/SkunkCraftsUpdater/ Hope that helps.. Ben

I've just had a read through the log and it's very strange. It could take me a while to figure this one out so I've posted this quick reply to keep you informed.

Looks like it's probably this /Users/eduardo/Desktop/X-Plane 11/Resources/plugins/AVS/64/mac.xpl (1-sim AVS).

Please attach a copy of Log.txt from inside the X-Plane folder.

VR headset tracking is likely overruling the shaking effects.

The tbm uses your graphics card and os drivers in complicated and unusual ways "compared to other aircraft" so what the other products do is irrelevant because their systems do not compare.

This is normal. The old-style GUI windows were created before X-Planes upported HD Scaling.

No response on Slack yet. Give it a few more days and I'll send him an email.

I've just sent Torsten a DM on the laminar research slack chat. Thanks for the name drop.

If you had posted the complete Log.txt file I could probably give you a working response here. The part you decided to copy tells me almost nothing. If you're on Windows, try this: https://aka.ms/vs/16/release/vc_redist.x64.exe If that doesn't help, post a complete copy of Log.txt as an attachment to your reply.

You found a bug. You seem to think shadex causes it. Don't use shadex?