FSDreamTeam forum
General Category => General Discussion => Topic started by: Airshinx_13 on June 06, 2017, 10:27:45 pm
-
Hello, i am posting this message because other simmers and myself have been having issues with the Quality Wings 757 gauges. Ever since the new update in FSDT products the gauges of the plane don't load up and display a "startup error" problem in blue font. I know that the COUATL engine always checks and downloads the gauges for this product, but we have tried to uninstall and reinstall the plane countless times. Can anyone provide for a fix to this issue? Thanks!
Sincerely,
Reynaldo Rodriguez
-
I am another one with the QW757 that gives the Unable to Start QW757-2 error message. It started with the update of the FSDT Addon Manager for P3D V4. I had both P3D V3 and V4 installed and fully operational. However, after the Addon Manager update, I had no access to any FSDT or Flightbeam scenery in P3D V3. The QW 757 also began displaying the Unable to Start QW757-2 error. All scenery worked in P3D V4, however. The only resort was uninstall all things FSDT, including Addon Manager and GSX, Flightbeam scenery and the QW 757. Reinstalled everything starting with the new standalone addon manager, then the FSDT and Flightbeam scenery, then the QW 757. Everything works in P3D V3 and V4. However, I still have the QW757-2 error. To be more specific, I am only using the QW757 in P3D V3.4.
Looking for some help in this forum as the qw757.gau is installed/updated via the FSDT AddonManager.
Jeffrey S. Bryner
-
However, after the Addon Manager update, I had no access to any FSDT or Flightbeam scenery in P3D V3
This was probably caused by not having installed P3D 3.4, which is the only version that supports the new installation system completely. We had an update of the installer in the meantime, which wouldn't use the new system unless you have 3.4 installed.
Reinstalled everything starting with the new standalone addon manager, then the FSDT and Flightbeam scenery, then the QW 757.
This is the problem: as always suggested here, and in the QW forum, you should always install the Stand-Alone Addon Manager LAST.
-
This is the problem: as always suggested here, and in the QW forum, you should always install the Stand-Alone Addon Manager LAST.
Actually we have tried that and its not working and or downloading now 757 gauge files. I am also using V3, and before the major update from FSDT products, everything was working fine.
-
However, after the Addon Manager update, I had no access to any FSDT or Flightbeam scenery in P3D V3
This was probably caused by not having installed P3D 3.4, which is the only version that supports the new installation system completely. We had an update of the installer in the meantime, which wouldn't use the new system unless you have 3.4 installed.
Reinstalled everything starting with the new standalone addon manager, then the FSDT and Flightbeam scenery, then the QW 757.
This is the problem: as always suggested here, and in the QW forum, you should always install the Stand-Alone Addon Manager LAST.
Greetings Umberto,
First of all, thank you for taking the time reply so promptly to this and every post on your company's forum. I understand that running a business is demanding enough, but replying to customers is another level of effort unto itself. Again, thank you.
I did not include some details in my post that may have helped in your response.
- With regard to P3D versions, I have had P3D V3.4 (3.4.22.19868) installed on my machine since Feb 14 2017. I successfully installed P3D V4 (4.0.23.21468) on May 30 2017.
- I purchased FSDT KCLT on June 2, 2017 directly from FSDT/esellrate. This was the product I installed (for P3D V4) which started me down this path. ;)
- I initially installed KCLT in P3D V4. During the install, as I recall, I was prompted to update the StandAlone Installer which I did. It migrated all of my FSDT and FlightBeam products to P3D V4 and during the process prompted for the location for the AddonManager. I took the default. I then launched P3D V4 and was able to see all of the migrated scenery (all FSDT and Flightbeam products). I closed P3D V4 and then launched P3D V3.4 and for the first time got the "Unable to Start QW757-2" error message upon loading the QW 757. Also was unable to see any FSDT and Flightbeam products in P3D V3.4.
So, initially, the last thing I did was install the Addon Manager yet still got the "Unable to Start QW757-2" error message upon loading the QW 757. I could not find any solutions at the time in the forums (FSDT or flight1 QW), so on June 4 2017 I decided to remove everything and start over. To be certain, I downloaded all of the FSDT and Flightbeam products as well as the AddonInstaller Standalone, GSX and the QW757 installer to be sure I had the most current versions of all installed. I reinstalled in the order I mentioned in my post and now everything (FSDT and FlightBeam) works in both Prepar3D V3.4 and V4. However, the QW 757 continues to display the "Unable to Start QW757-2" error message.
As you mention, and as I did initially, the AddonManager was installed last yet I got the Qw757 error message. So, If installing the current/newest StandAlone Addon Manager last is the solution, then all I should need to do is re-run the Stand Alone Addon Manager again (effectively making that the last thing installed) and it should resolve this. Is that correct? Could running the FSDT Live Update take care of this?
Thank you in advance for your attention.
Jeffrey S. Bryner
-
Update to my last post: I just downloaded the Stand Alone installer (Version 4.0.0.1) from the FSDT website, chose update Prepar3D 3.x and 4.x and it ran successfully. I then opened Prepar3D 3.4, loaded the QW757 at (FSDT) KCLT. KCLT loaded just fine but the QW757-2 error still persists. I ran ProcMon and saw requests within the Prepar3D.exe process querying for a QW757.dll within %ProgramFiles(x86)%\Lockheed Martin\Prepar3D V3\ all of which fail. It finds QW757.gau, however. Not sure if this is related and if it is, how it could be resolved. Any help would be certainly appreciated.
Jeffrey S. Bryner
-
The .dll error is not really an error, the sim always tries to find a .dll before a .gau.
As you can see in this thread, the QW757 works fine with the latest Addon Manager. The screenshot shows KCLT, because KCLT works only with the latest Addon Manager and, as I've said in that thread, the only thing I did was to install the QW757 and then the Stand-Alone Addon Manager after it.
QW757-2
According to QW, this error means the gauge is running, it HAS found the Addon Manager, but it cannot find the activation. The new Addon Manager requires Couatl to be running in order to the activation to work.
Couatl is of course installed with the Stand-Alone Addon Manager, but it's possible it hasn't started on your system for some reason so, check if you also have the Couatl menu under the Addons menu.
-
The .dll error is not really an error, the sim always tries to find a .dll before a .gau.
As you can see in this thread, the QW757 works fine with the latest Addon Manager. The screenshot shows KCLT, because KCLT works only with the latest Addon Manager and, as I've said in that thread, the only thing I did was to install the QW757 and then the Stand-Alone Addon Manager after it.
QW757-2
According to QW, this error means the gauge is running, it HAS found the Addon Manager, but it cannot find the activation. The new Addon Manager requires Couatl to be running in order to the activation to work.
Couatl is of course installed with the Stand-Alone Addon Manager, but it's possible it hasn't started on your system for some reason so, check if you also have the Couatl menu under the Addons menu.
Again, many thank you for your prompt and thorough response to my post(s). I do have Couatl installed and operational and see it under the Add-ons menu with its submenus and can access all of the functions of Couatl. You mention that the QW757-2 error is related to activation, however under the Add-ons menu I select Addon Manager... then click on Quality Wings under Publisher, then click on Ultimate 757 Collection under Product and it indicates Product ACTIVE. 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.
Jeffrey S. Bryner
-
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.
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
-
I ran ProcMon and saw requests within the Prepar3D.exe process querying for a QW757.dll within %ProgramFiles(x86)%\Lockheed Martin\Prepar3D V3\ all of which fail. It finds QW757.gau, however. Not sure if this is related and if it is, how it could be resolved. Any help would be certainly appreciated.
Actually, i have tested out possible theories on my own end. I've noticed that inside of my P3DV3.4 gauges folder there is a "Qwings757" folder and inside of that it holds most of the gauges for the QW757. I decided well lets test out by dragging those contents from that folder into the gauges folder. I fired up my sim and most of the gauges started loading except for the PFD and ND displays, and instead displayed "Startup error QW757-2" in blue, but everything else loaded ie. Lower ECAM, MCP, Overhead, ect. Had i not dragged those files from the QW757 folder into the gauges folder then those gauges would not have worked. I think the only thing i am missing is the 757.gau file. Did you happen to find it? At this point we are just doing theories on how to fix this issue...
-
I've noticed that inside of my P3DV3.4 gauges folder there is a "Qwings757" folder and inside of that it holds most of the gauges for the QW757.
No, it contains the *few* gauges which are made in XML. Most of the airplane code is in the QW757.GAU, which is the C++ part.
I think the only thing i am missing is the 757.gau file. Did you happen to find it? At this point we are just doing theories on how to fix this issue...
You mean you don't have it??? If's supposed to be in the main Gauges folder, which is where the QW757 installer places it. I surely have one, it's about 4MB, plus there's a smaller QW757_TCAS.GAU.
You really don't have it ? If yes, maybe the antivirus has removed it, which would explain every problem.
-
I think the only thing i am missing is the 757.gau file. Did you happen to find it? At this point we are just doing theories on how to fix this issue...
You really don't have it ? If yes, maybe the antivirus has removed it, which would explain every problem.
Actually i do have it. I did not look at the file name properly.
-
And you have the Esellerate files in the C:\ProgramData\Esellerate\Esellerateengine.dll ?
-
And you have the Esellerate files in the C:\ProgramData\Esellerate\Esellerateengine.dll ?
Yes, yes i do.
-
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.
-
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.
Okay, I will download and check it out. I will report my findings later, since right now i am doing a flight.
-
So, i ran the program and opened the 757.GAU file and as soon as it processed it detected errors. I am also not sure as to what section to look at for what you asked.
-
Try to look in the bottom window, towards the end. Lots of these errors might be quite misleading, and they are not real errors. But if you find something related to either simconnect.dll or msvcr80.dll or something like that, they might be serious.
-
I see, i ran it and saw none of the mention dll files in the bottom section. Though i did see an UIAutomationcore.dll, but i remember that being attributed to FSX but i have it uninstalled and currently running P3DV3.4.
-
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.
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
I do have that file in that exact location. It's version 3.6.5 dated March 5 2007.
-
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.
OK, Dependency Walker on my QW757.gau did not reveal anything unusual except that the GDIPLUS.dll is being loaded from a Win Side By Side folder. That may be attributed to whether that came from one of the C++ Redistributable installs, but it is dated March 4 2017 and is ver 10.0.14393.953. Otherwise, nothing missing.
Again, thank you for replying.
-
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?
-
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?
Interesting, i tried that and it worked for me. Something is improperly loading.
-
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.
-
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.
For me more precise, i spawn in and then go to "vehicles" and select the same plane again and the black gauges are gone.
-
Hello everyone,
First post here, I just registered to report the same exact problem here. By loading the aircraft twice it goes away for me, too.
Cheers,
Achilleas
-
First post here, I just registered to report the same exact problem here. By loading the aircraft twice it goes away for me, too.
I'm sorry, but I cannot reproduce this. The airplane always loads at the first try here. But it might dependent on what other addons you have, and which Windows libraries (VC++) they load and, possibly, even by their loading order.
-
Their loading order could certainly have something to do with it. I'm going to do some testing when I have some time and I'll report back if anything comes out of it.
Cheers,
Achilleas
-
I still have the same problem and just load the QW 757 twice to get the panel to work. It's a pain but the only thing to do until this problem is fixed.
-
It's a pain but the only thing to do until this problem is fixed.
I'm sorry, but as I've said in my last post, I cannot reproduce this. The airplane always loads at the first try here.
-
It's a pain but the only thing to do until this problem is fixed.
I'm sorry, but as I've said in my last post, I cannot reproduce this. The airplane always loads at the first try here.
Hi virtuali,
Might I ask which OS are you using? Windows 10 Home here.
Cheers,
Achilleas
-
Might I ask which OS are you using? Windows 10 Home here.
Windows 10 Professional.
-
Is the OP trying to install it in v3 or v4? It wont work in v4.
-
Might I ask which OS are you using? Windows 10 Home here.
Windows 10 Professional.
It's probably not an OS issue then... Is P3D installed in Program Files or in another directory? Mine is under C:\P3D
-
It's probably not an OS issue then... Is P3D installed in Program Files or in another directory? Mine is under C:\P3D
Mine is installed into C:\Prepar3d v3
-
It's probably not an OS issue then... Is P3D installed in Program Files or in another directory? Mine is under C:\P3D
Mine is installed into C:\Prepar3d v3
Shouldn't be an issue either then.
Let's try something else, I'm beginning to think it is a load order issue.
DLL.xml (AppData):
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>IvAp</Name>
<Disabled>False</Disabled>
<Path>C:\Users\Achilleas\Documents\Prepar3D v3 Add-ons\IvAp v2\ivap_fsx_bootstrap.dll</Path>
<Commandline/>
</Launch.Addon>
<Launch.Addon>
<Name>FSTramp</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files (x86)\FSTramp\FSTramp.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>
EXE.xml (AppData):
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>AivlaSoft SimpleCam</Name>
<Disabled>false</Disabled>
<Path>C:\Users\Achilleas\Documents\Prepar3D v3 Add-ons\AivlaSoft\SimpleCam\AivlaSoft.SimpleCam.exe</Path>
</Launch.Addon>
</SimBase.Document>
DLL.xml (ProgramData):
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
<Descr>AceXML Document</Descr>
<Filename>dll.xml</Filename>
<Launch.Addon>
<Name>TargetInfo</Name>
<Path>Gauges\TargetInfo.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Fury_1500</Name>
<Path>Gauges\Fury_1500.dll</Path>
<DLLType>PDK</DLLType>
</Launch.Addon>
<Launch.Addon>
<Name>Flight Recorder</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
</Launch.Addon>
</SimBase.Document>
EXE.xml (ProgramData):
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="exe">
<Descr>AceXML Document</Descr>
<Filename>exe.xml</Filename>
</SimBase.Document>
-
Let's try something else, I'm beginning to think it is a load order issue.
Try to disable all the 3rd party modules in the XML files, by setting <Disabled>True</Disabled> first.
-
No joy, even with every third party module off (both EXE.xmls and DLL.xmls) it's still the same, unless I load it twice it gives the all familiar error code.
-
Same issue, waiting on solution. Thank you! No gauges first load, go to menu select same ac and gauges are good. Win 7 here.
-
Same issue, waiting on solution. Thank you! No gauges first load, go to menu select same ac and gauges are good. Win 7 here.
I'm sorry, but as I've said in all my posts, I cannot reproduce this. The airplane always loads at the first try here.
As I've said, I use Windows 10 but, it might be a combination of the OS, the version of the installed VC++ libraries, which is dependent on the OS installed updates and the loading order of the modules.
From your report, what is not loading is the Gauge itself, and we don't have any control in our software over the loading process of it.
-
Hi,
I think there is still no solution for this problem. After the update of the manager I had to do a full reinstallation of all FSDT sceneries, because of the 757 problem, to find out why this happened. Order of installation: All FSDT sceneries first, then 757 and the last installation the latest addonmanager. Same problem exists. Why? If you ask me, there is something wrong with the latest addonmanager. It must be there, so it would be very kind to find out why and have a fix for that. Saying, I cannot reproduce this sounds very poor. Hey, simming is about flying, sceneries are not the first priority. So if you don't care, your sceneries will disappear from my harddisk and I will not buy any in future. You should take this more serious… So come on.
-
Hi everyone!
Yes, the issue still persists however it's not going to stop anyone from flying, all you have to do is reload the 757. Of course I'd like to see it resolved and I'm sure there are things being done to address said issue that we are not aware of but I don't think us complaining is doing much to help. It could, very well, be a QW problem and not an FSDT one and QW have announced they'll be doing some work on the 75 since they cancelled the 737. I guess we'll know soon, in the meantime just reload the plane before you start your preparations and everything will be ok. :)
Cheers,
Achilleas
-
I've had this problem as well. It is that QW reads the old add on manager 3.1.0.1 and not 4.0.0.8. I've emailed and contacted them and had no luck in fixing this problem. I've had two instances where I would install the QW757 as well as other FSDT scenery and having the new and old addon managers installed. The old addon manager would only read the 757 and this would work. But everything requiring the new addon manager would not work. I went and disabled the old addon manager in dll.xm and my FSDT scenery would work. If I disabled the new addon manager the new FSDT scenery would not work but my QW757 would work. Thus proving my point that this is a developer issue. Does this make sense?
QW also said that their own installer automatically downloads the latest addon manager from Virtuali. If this where true it would download 4.0.0.8 and not 3.1.0.1. I've also asked them to fix this in the installer checking and verifying the download link to insure its installing correctly. I don't know how this could be missed. QW needs to fix the gauges files so it reads the activation correctly when it installs the new manager. Thus pointing all figures back to the developer.
-
QW also said that their own installer automatically downloads the latest addon manager from Virtuali. If this where true it would download 4.0.0.8 and not 3.1.0.1
The QW installer hasn't been updated to support our new installation method, which is the add-on.xml in P3D V3.4/4.0 or the DLL/EXE.XML method in FSX or older P3D V1/2/3 versions, with all sim using a single shared folder and running over our new Live Update system.
This means, if you install the QW757 AFTER anything from FSDT that use the new installer, it will ADD a 2nd copy of the OLD Addon Manager, one that puts the bglmanx.dll file in the root folder of the sim, and will always use the DLL/EXE.XML method, meaning this will result in a 2nd copy of the old Addon Manager running alongside the first one.
There's just nothing we can do to fix this, since we cannot retrofit the old installers users might already have.
Which is why, as explained so many times in this forum (and the QW forum too), the solution is always to download and install the latest Stand-Alone Addon Manager, which will FIX everything: it will remove the 2nd copy of the old Addon Manager, both from the sim and from the DLL.XML file, and will change all the setup to run in the new shared folder installation.
This is the same as running ANY recent FSDT installer after the QW757 installation.
Basically, the only thing you shouldn't do, is to install the QW757 AFTER you installed anything using any FSDT installer which was made after June 2017.
By doing this, the QW757 works just fine with the latest Addon Manager, with no issues I can find. We used the QW757F quite a bit while developing KSDF, since it's one of the planes that works at the UPS Cargo cagtes so, if it had any issues, they would have surfaced by now.
-
Thanks for clearing this up! I don't know why they have to work around this just to get their product to work. I will continue to support FSDT!! :) :)
-
My other question was, I have SDF installed now. If I remove it should I remove addon manager when it asks? Then install SDF? Wouldn't SDF come with the lastest version? Or how would I remove the addon manager that installs SDF to install the standalone?
-
There's just nothing we can do to fix this, since we cannot retrofit the old installers users might already have.
Yoh, well. Since FSDT sells sceneries with an addonmanager (which always has been doubtful why) and makes it some kind of incompatible to previous released software, in this case QW, well, I would have my thoughts about the way developers are handling such circumstances.
I know and you know too, this discussion is not new and will never stop if until these situations are treated the right way. Fact is, the QW757 will not load in the first place. For me it doesn‘t make a difference in which order you install everthing. In the end I can be happy to have a functional bird after reloading it. Simple, but that is a bug produced by FSDT. It‘s not about the old installers, no, it‘s about the new installers!
-
Yoh, well. Since FSDT sells sceneries with an addonmanager (which always has been doubtful why) and makes it some kind of incompatible to previous released software
The current version of the Addon Manager is fully compatible with the QW757. See the video below.
I know and you know too, this discussion is not new and will never stop if until these situations are treated the right way.
The situation IS being treated in the right way, which is offering the suggestion that works: never install the QW757 *after* having installed something using the latest FSDT installer. If you do it, reinstall either the Stand-Alone Addon Manager or any other FSDT installer, will fix everything.
Fact is, the QW757 will not load in the first place
It does. See the video below.
For me it doesn‘t make a difference in which order you install everthing.
The installation order makes all the difference. If you install the QW757 last, it's 100% sure it won't work. If you install something from FSDT last, it's 100% sure it will work.
Simple, but that is a bug produced by FSDT. It‘s not about the old installers, no, it‘s about the new installers!
It's no "bug" produced by FSDT. It's ALL about the old installer because they were using a different file structure, but the new installers WILL fix this, if they are run last.
Here's a video I just made, showing the QW757 fully working in both FSX:SE and P3D 3.4, showing gauges working normally, at the first startup of the sim, without having to load the airplane twice.
-
Hi Umberto,
I noticed in your videos a couple of things you and I do in a different way and I wonder if this has something to do with some of us having to load it twice. Firstly, you start a flight with a default aircraft whereas I always load it from the Scenario Screen. Secondly you start with the plane running, my default state is C&D. Would you mind testing it this way and reporting back? I'll, also, test it your way on my system to see if things change.
Cheers,
Achilleas
-
Firstly, you start a flight with a default aircraft whereas I always load it from the Scenario Screen.
This is the big difference. The QW757 works with AddOn Manager 4.x, but only if you load another aircraft first or reload the aircraft. You can start it from the scenario screen with AddOn Manager 3.x.
Cheers!
Luke
-
This is the big difference. The QW757 works with AddOn Manager 4.x, but only if you load another aircraft first or reload the aircraft. You can start it from the scenario screen with AddOn Manager 3.x.
We believe to have found the issue, which is related to timings and the PC speed (so it's not happening in all cases), and it's related to a change we had to do to switch away from the old Esellerate SDK, which wasn't going to be maintained anymore and supported on the newest Windows OS.
The issue is, there's just nothing we can do from our side, it requires a very *small* update of the QW757 Gauge, and we already explained the issue and the required changes to QW, and also offered our assistance to fix it, in case they might be too busy supporting their newer things.
The temporary fix, is to have a startup flight with a default airplane, or load the 757 again when the scenery has loaded.
-
Hi Umberto,
Thanks for getting back to us and for finding the issue. :)
Cheers,
Achilleas
-
I just started having the "Startup Error QW757" error at KLAX. I have not used FSDT KLAX for a few months until now. I use FSX and not knowing what was causing the problem, I reinstalled Full Installer for GSX and reinstalled KLAX, but did not fix the problem. Just by chance what I did is after I opened up FSX, select the QW757 aircraft, select KLAX plus the gate number, and after it opened up with the QW757 at the gate with the gauge error showing, I would select "End Flight" and then open FSX again and the gauges would be working.
Cfoley
-
As I've said in my previous post:
The temporary fix, is to have a startup flight with a default airplane, or load the 757 again when the scenery has loaded.
-
The new problem I noticed even though I end the flight and restart to fix the cockpit error problem, the QW757 looks odd shaped from the outside view. It does not happen all the time when restarting though.