Ok, try this:Download the Depends utility for x86 here:http://www.dependencywalker.com/Open the QW757.GAU file, and see if it reports errors like missing files. Note that, some of these errors might be misleading, so look the ones at the end of the list, and see if you find anything.Errors reported here, would suggest some system libraries missing from your system.
Quote from: jsbryner on June 08, 2017, 04:21:13 amNotwithstanding, I still have the QW757-2 error since the update of Addon Manager to 4.0.0.0 (it is now 4.0.0.3 at last update). Notwithstanding your experience you evidence above, mine and others unfortunately have not been the same.My reply has been based on what QW told me about the meaning of the error, which means the Gauge couldn't verify the activation but, I can assure you that, if the Addon Manager is reporting the product as "Active" you can be sure it IS reporting it to the Gauge as such, and nothing has ever changed in the Addon Manager.However, it's *possible* they might ALSO call Esellerate directly in the Gauge, and few months ago Esellerate has switched the activation servers, so we now use a different library to access them in the Addon Manager, so we don't include the old Esellerate .dll anymore in the Addon Manager, but this won't be a problem, since it IS included in the full QW757 installer. That's why we always say to install with the full QW757 first, and then the Addon Manager, so both .dll are surely installer.But, just to be sure, do you have this file ?C:\ProgramData\Esellerate\Esellerateengine.dll
Notwithstanding, I still have the QW757-2 error since the update of Addon Manager to 4.0.0.0 (it is now 4.0.0.3 at last update). Notwithstanding your experience you evidence above, mine and others unfortunately have not been the same.
I'm having the same exact QW757 gauge problem. The only solution is choosing the airplane again and then the gauges show up. It wasn't a problem before but it's a pain in the neck especially for something that you've paid for. Isn't there a fix for this?
Same exact thing for me. Have to load the 757. Get the error, end the flight, then restart it again and everything works like normal.
First post here, I just registered to report the same exact problem here. By loading the aircraft twice it goes away for me, too.
It's a pain but the only thing to do until this problem is fixed.