Ben Russell

No one on the forums can help you with this issue. Only X-Aviation support can verify your purchase records and merge your accounts if applicable. Your machine registration cannot be reset from your end. You should've contacted support before making your second purchase as you were already aware that you had lost access to an old X-A account.

Try removing XJet from your active plugins list. You can also try using the Gizmo beta...

It may take some time to resolve this. It's an unusual bug in some code going through some big changes. My advice is the same as Camerons for now. Use Gizmo Stable. Hopefully with the next release of Gizmo beta your problem will be resolved. I have no current time plan for when that will be released.

Checking for changed hardware is a lot harder than checking what time Windows was installed. It's also more likely to lead to clashing machine ID's. Would you really want a DRM that went off every time you fiddled with your RAM load out? Or would you rather deal with an occasional bump in the road every 3 months when MS did an Update that's internationally well known in timing.

I already explained what win 10 is doing.

https://daycalc.appspot.com/09/22/2013 Product was released Sunday 6 years 10 months and 19 days from today... if you want to play that game.

This log file shows you were trying to fly the Zibo mod 737-800. Besides that, it looks normal. Gizmo is installed and loading. Can't give any advice about the IXEG 737 Classic experience though as there's nothing in the log related to it. Thanks.

Please post a copy of log.txt from your xplane folder.

Upgrades to Win10 will occasionally reset the Windows install date. This date stamp, measured down to the second, is part of the data used to identify each machine uniquely and ensures that it is extremely unlikely that your machine ID matches with a random stranger's. As above: Use the machine naming feature to give your systems meaningful names. Retire the oldest item in the list. If you are still unsure of how to proceed please file a support ticket with x-aviation so that your records can be reviewed before you freeze.

Hopefully you've entered useful names for each machine that help you remember which each one is. Choose the oldest item for the machine that you want to re-register and freeze that one. If you have multiple machines and chose not to name any of them for the DRM system your choice is going to be harder. Choosing the oldest item is still generally going to be the safest.

The log file you posted shows you are not using the gizmo beta. Post a new log file so that we can get useful error data and provide meaningful advice.

Try using the Gizmo beta option.

Try using a fresh demo copy of X-Plane, or.... remove all your other third party plugins. I don't really have much else to offer. Both Gizmo versions work fine for thousands of other people all over the world. The problem is something on your end.

This forum has nothing to do with the xPilot online flying client. They chose their name very poorly.

Please delete this folder: F:\X-Plane 11/Resources/plugins/XP11Gizmo64.plugin It's one of several messy things in your Log.

Moderators do not have access to X-Aviation purchase and activation records or the help desk ticketing system. The sites are closely affiliated but still separate entities. Sorry, but no one on the forum can help.

The number of possible machine ID's with 128 bits is 2 raised to the power of 128, or 3.4x1038, or 340 undecillion. The chance that you have a legitimate collision is .... very very very (35 more verys) small.

https://www.x-aviation.com/catalog/contact_us.php "We will reply as soon as we are able and will endeavor to reply within 3 days, but usually quicker.Please do not send multiple e-mails or this will delay our response to you!"

No one on the forum can help.

Some of these things will likely go away with the next Gizmo release.

Roughly where in the world are you located? The error message you're receiving is probably caused by a network timeout.

Xplane has a cmd line flag to start up in simulated vr mode... Might help without needing actual hardware. (mines in a box, used very rarely)

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

The TBM systems coding is extremely complex and advanced and makes much more usage of your additional CPU cores and other system resources than any other product I know of. I suggest turning down some of X-Plane graphics and quality details to free up some system resources for the TBM to share. If the problem clears up or improves than the cause is a basic overload of hardware resources. Please also attach a copy of X-Plane / Log.txt to your next post so that we can have some idea of what your X-Plane install looks like including scenery in use and plugins installed.

Because the question was already answered and your options to resolve it have already been provided before me. You're asking if we've made any progress fixing something we have no control over fixing. In short, your post was a waste of time.