Ben Russell

Signed up for ProjectFly myself to investigate further. Hopefully the issue will occur for me on my dev machine and I can figure out more about what's going on. Thanks for your patience.

It could also be the projectfly plugin. D:\X-Plane 11/Resources/plugins/projectFLY/ I'm starting to see bug reports where this is installed. Still collecting info... Not sure what's going on yet. This thread has been added to the bug tracker thread.

Thanks for the help. Appreciate the effort to add more test data.

Thanks for the log files. I've never seen this error before. Will take a while to figure out what's going on...

Here are the relevent text's from the DRM GUI. For selecting the machine to freeze: "Select ONE machine to de-authorize forever:" For confirming YOUR action: "De-auth and freeze this machine forever:" Additionally, to ensure that you actually read the text above, you are required to read this sentence: "Please type FREEZE to agree.." .. You clearly read the words on screen. You ignored the consequence. This is not in the fine print of a EULA you scrolled past - like every other major service -. Please explain how the process could be clearer. You chose to ignore the information presented.

The message earlier in the thread is a reply. It may not be the reply you like or wanted. Earlier iterations of the DRM were utterly plagued by large numbers of users sharing our products in any way they could. This loophole has been eliminated. The wording throughout the DRM FREEZE process is fairly clear and blunt. If you believe it can be made easier to understand please post feedback about where wording is unclear or how it failed you. "Assuming it was like Apple" was your failure to properly read and understand the process.

Always post Log.txt file form X-Plane folder.

You should be able to run it after you've copied the X-Plane folder to the new machine. If there are any issues with Gizmo not working install this: https://www.microsoft.com/en-au/download/details.aspx?id=48145

You have an old version of Gizmo installed. Download and install a new one from the link below or re-run your product installer.

That's a new one.... Will have to investigate. Standby.

xEnviro team have identified the issue as their own and the fix will have to come from their side. https://forums.x-plane.org/index.php?/forums/topic/149092-xe-and-gizmo/&tab=comments#comment-1428322

Documentation for the OpenAL function that consumes the audio data after it's extracted from the WAV file container. There is no mention of padding requirements. There is a mention of data interleaving requirements for stereo files. Perhaps (and this is pure guess work) the warning message being thrown is for stereo-format files where the interleave data is missing a trailing byte. (Say: 30 samples for left data and 29 for right...) If OP wants to chime in and provide more facts about what's actually wrong, what tool they were using or how to interpret the cropped screenshot they provided I could make more meaningful progress. Bottom line: there are no errors logged against this for thousands of customers and varied hardware running it.

I have my doubts that OP even understands the warning message he's interpreting. I re-read the WAV file specs. It could be as simple as a single byte missing from a number of different chunk types. <WAVE-form> → RIFF('WAVE' <fmt-ck> // Format [<fact-ck>] // Fact chunk [<cue-ck>] // Cue points [<playlist-ck>] // Playlist [<assoc-data-list>] // Associated data list <wave-data> ) // Wave data https://en.wikipedia.org/wiki/WAV#Specification RIFF files consist entirely of "chunks". The overall format is identical to IFF, except for the endianness as previously stated, and the different meaning of the chunk names. All chunks have the following format: 4 bytes: an ASCII identifier for this chunk (examples are "fmt " and "data"; note the space in "fmt "). 4 bytes: an unsigned, little-endian 32-bit integer with the length of this chunk (except this field itself and the chunk identifier). variable-sized field: the chunk data itself, of the size given in the previous field. a pad byte, if the chunk's length is not even. https://en.wikipedia.org/wiki/Resource_Interchange_File_Format Given that we have no bug reports on this issue in so long I'm going to error on the side of mundane and meaningless. Had the OP named the chunk-type that was throwing the warning message it would add more weight to the post. Had the OP named the tool he used to generate the warning scan it would've made investigations easier. @parsec Thanks for the notes regarding data-format matching and mixer overheads. Note worthy info that's easy to overlook. In the grand scheme of things with 8 core machines and everything from crap on board sound to dedicated gaming sound chips it probably doesn't make a huge difference. I'm honestly not sure if the OpenAL calls we use run in the game thread or their own. I suspect on Apple hardware at least it runs in a seperate thread. (My brain is ringing bells from reading crash dumps where OpenAL is in a thread of its own...)

Like what? I have no open bugs against this issue. Genuinely curious. Share your wisdom.

So: 1. Andrey has already put a warning label on his software stating that his plugin might not work with some addons. 2. Andrey has admitted that the problem with the Saab/IXEG/Gizmo is his/x-plane's problem and that he is working on a fix. 3. We should put a warning label on our products just to make you happy? Go find something else to do.

The. Author. Of. xEnviro. Has. Traced. This. Bug. It. Is.. A. Problem.With. xEnviro. This is not up for debate. The technical work has been done. We assisted where possible. The cause has been found. It's. not. my. problem. Factual reality. Please join it.

Or you could argue that you donate to xEnviro because the bug is their problem. There is literally not a single thing I can do about it. They have admitted they're on track to a fix and have discovered that it is their problem. What would you have me do? Ask them for source code to their product? Your attitude is laughable.

By their own admission, this is not my problem. https://forums.x-plane.org/index.php?/forums/topic/149092-xe-and-gizmo/&amp;tab=comments#comment-1428322

While your i5 might be "working fine" it's also working at almost half the speed of a modern i7. https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-2500K+%40+3.30GHz&amp;id=804

FYI: The authors of xEnviro are aware of the problem and are working on a solution.

Should be fine. Just don't change the author or description data which is used to locate the product in your purchase history and license data.

Quote your ticket number here. Be patient. Sending multiple emails will reset your position in the ticket queue. Quoted delay is 3 days. If it's been two days and you send another email out of frustration you'll end up waiting upto five days. From the contact page: "Please do not send multiple e-mails or this will delay our response to you!"

Try some flights in a different location.