Ben Russell

If you want something released "on time" go buy Cyberpunk 2077, that worked out great.

I suggest you install a fresh demo copy of X-Plane and try flying in that. You have a large number of additional third party plugins installed, any of which could be the root cause of the problem despite what it says in the log files. X-Plane has a shared memory area for all plugins to use. The same as Win3.11 or MacOS Classic used back in the early 90s. Any plugin can overwrite the memory of any other plugin resulting in a crash.

Please provide your Log.txt file from the X-Plane folder.

I left Gizmo running for about 6 hours yesterday with the IXEG 737 sitting on the tarmac. There was no collapse of FPS or memory leak. This does not invalidate your findings. It shows that code changes since the last public beta release may have resolved the issue if there was one.

And yet some people manage to litter the forums with threads about how mean we are because we locked their machines forever... Sigh.

Assuming you're using Windows this is likely caused by a Windows Update and is no reason for such panic. Freeze the oldest item in the list.

1.25% now...

In your X-Plane folder you will find a file called Log.txt. Please attach a copy to this thread to help us diagnose your issue.

This is not a support site for the xPilot client. They chose their product name very poorly.

What was the purpose of your post beyond internet points? -yawn- This thread is dead, let it sleep.

If you haven't re-installed your OS the machine ID should remain the same.. Will be interesting to see what happens. Please report either way.

If only threading bugs were so clear cut. Just recently I spent three days debugging a threading bug where an entire copy of a plugin image was being copied into the Lua reserved RAM pool. The RAM pool that X-Plane reserves with the Operating System _BEFORE_ it loads any plugins. What should be entirely impossible was happening. Do not underestimate the damage and difficulty that wrong use of threads can achieve.

My guess is that some OpenGL friendly plugin is changing the "working folder" and not restoring it properly which leads to Terramax writing its pref file to a folder its not expecting. The test is of course to remove all your plugins and then test only Terramax in OpenGL in isolation and see if the problem persist with just terramax or if it's actually triggered by something else that only shows up in OGL mode.

Do you have any unusual USB peripherals plugged in? Looks like X-Plane is crashing just as it's starting to list/scan the USB HID devices... Try unplugging any non essential USB items and see if X-Plane will start up..

Your attitude and behavior and attempts to ignore and bypass the standard support waiting times is what's unacceptable. In a shopping mall you'd be having a long attitude re-adjustment chat with the security team. Here, I'll just tell you plainly where you can go.

Thanks for the abuse. Quality customer. Pleasure to serve you. F off.

There are other customers that need their queries answered to, your insistence that you be served instantly and not read anything presented to you is laughable. Do you skip to the head of the queue when you're shopping to or does your common decency come into play because you're more accountable in real life?

From your post history I'm going to guess that you want help with a locked machine ID. Locks are permanent. I replied to you on sept 23rd.

No log files. Can't offer any help.

Processor upgrades have no effect on machine ID. Something else caused the issue and you decided to ignore it while being required to type FREEZE to move forward. I'm tired of this thread.

You are permitted to use your software on upto 3 machines at the same time. Due to software and hardware upgrades occasionally your machine ID may change. When it changes you are given the choice of which of your machines you wish to lock. You cannot lock the machine that you are currently using. This is to avoid accidental locks. You cannot unlock a machine because this would allow you to share software with your friends. Machine locks are permanent. No amount of forum posts on any site will change this policy. There are far more possible machine ID's than there are people on the planet. The mathematically probability of two machines sharing an ID is so low that it's practically impossible.

That's not how it works. Machines are locked from the customer's machine. Ip address does not affect or change your machine ID. Lying will not help you.

There's nothing to reply to. You either ignored the warnings and locked your own machine or you shared your login details and products with a friend and they locked your machine for you. In either case, the result is permanent. Your machine is frozen. This is a hard rule to combat product sharing.

This is a not a gizmo error. The sr_systems plugin isn't loading at all.

Might wanna find a different VPN provider, nord don't give a shit about your privacy. (they knew for a few months before disclosure) https://www.theverge.com/2019/10/21/20925065/nordvpn-server-breach-vpn-traffic-exposed-encryption