FSDreamTeam forum
Products Support => Charlotte KCLT Support FSX/P3D => Topic started by: beechcaptain on June 11, 2017, 02:50:43 pm
-
I get an Error Occurred message each time when I exit P3Dv3.3.5 (Windows 10 Home Ed. 64bit), when I am at either KCLT or KMEM. I have run Live Update but still get the error. I have the latest SODE v1.5.2, and it works well. I also do not get the error when I exit from P3D while at ImagineSim KATL with SODE update, so I can confirm it is not a SODE issue, and Jeffrey (12bpilot) can not find any issues with my various SODE and P3D config, exe and dll files.
I can still fly my flights with KCLT and KMEM active, I just have to live with the Error Encountered message upon exiting P3D. I hope there is a solution to this, though.
Thanks.
-
I suggest to update to P3D 3.4 first.
-
Why? v3.3.5 has been extremely stable and I have not had a need to pursue v3.4 and deal with updating all my addons again. Also, the listed requirements from the product page for KCLT are: "FSX+SP2 minimum, FSX+Acceleration Pack, FSX:Steam Edition, or Lockheed Martin Prepar3D 1.4 or later, including V4".
-
Why? v3.3.5 has been extremely stable
It doesn't seem so stable, according to your own report.
and I have not had a need to pursue v3.4 and deal with updating all my addons again.
Why you think you must update all your addons ? This must be some kind of urban legend, but it's entirely untrue. I did the update personally, on a user's system, and it was done exactly this way:
- Uninstall the Prepar3d client (ONLY)
- Download and install the latest 3.4 Client (ONLY)
Done. No addons ever needed to be updated, and the bugfix and crash fixes from 3.3 to 3.4 is very long. A 3.3 bug was quite bad, and resulted in fake exceptions in all Simconnect clients, and it was fixed only with the latest 3.4 Hotfix 3.
-
I do not believe my P3Dv3.3.5 setup is unstable, and what I've indicated does not reflect it being unstable when everything runs fine except KMEM and KCLT. However, we are entitled to our own opinions.
That being said, I will definitely try installing the client only for 3.4 as you suggest. Thanks for that tip.
-
I uninstalled P3Dv3.3.5 client and installed v3.4. When I am at KCLT and exit P3D, this is the error message I receive, now:
"Prepar3D exe has stopped working
A problem caused the program to stop working correctly. Please close the program."
Again, it does not do this at KMEM or IS's KATL, for example. I do get a message at KMEM that SODE has quit working when I exit the sim.
Any ideas as to finding these causes?
Thanks.
-
Again, it does not do this at KMEM or IS's KATL, for example. I do get a message at KMEM that SODE has quit working when I exit the sim.
It seems something related to SODE. Are you using the latest 1.5.2 version ?
-
Yes, v1.5.2.
Also, for the first time, I just encountered this with KMEM:
"Prepar3D exe has stopped working
A problem caused the program to stop working correctly. Please close the program."
Again, it is only upon exiting P3Dv3.4. Everything functions fine during the pre flight, flight and post flight.
I am in correspondence with Jeffrey (12bPilot) about possible SODE issue causing the error. However, at this point, cause is uncertain.
Virtuali, I can pm you my dll.xml, exe.xml, cfg files if you would like to review them. Just let me know which files you would need.
Thanks.
-
Virtuali, I can pm you my dll.xml, exe.xml, cfg files if you would like to review them. Just let me know which files you would need.
Under P3D 3.4 we don't use the DLL/EXE.XML files anymore. Maybe you *edited* them, because you assumed our lines were missing, so you are now loading the executable twice, since they are already loaded by the add-on.xml.
-
Why do you assume I edited any files, when I did not mention this in any way, shape or form? I have not touched any of the critical files in P3Dv3.4 since installing KCLT.
I am merely offering my pertinent files for your review so you can determine if there is an issue or not. Nothing more, nothing less.
-
Why do you assume I edited any files, when I did not mention this in any way, shape or form? I have not touched any of the critical files in P3Dv3.4 since installing KCLT.
I haven't assumed anything: I said MAYBE, because you said yourself you wanted to have your xml files checked and, since we do not use them anymore (from 3.4 onward), they cannot possibly be related to the crash on exit so, either you edited them (which might explain the crash), or the crash is caused by something else.
-
re: MAYBE - fair enough, my misunderstanding.
I also offered to provide my cfg files for review, in addition to the xml files. All I was doing was offering everything file wise I could think of for you to be able to take a look to see if there was an issue. I understand about the XML files, but I did also offer cfg files which are pertinent, aren't they?
-
Try to disable every other 3rd party addon module from both the DLL.XML and the EXE.XML. Do it for BOTH set of files, the ones under %PROGRAMDATA% and the ones under %APPDATA%
To disable a module, set <Disabled>True</Disabled> on its section. Then, with all modules disabled, see if you still have the error on exit.
-
Try to disable every other 3rd party addon module from both the DLL.XML and the EXE.XML. Do it for BOTH set of files, the ones under %PROGRAMDATA% and the ones under %APPDATA%
To disable a module, set <Disabled>True</Disabled> on its section. Then, with all modules disabled, see if you still have the error on exit.
Will do. If the error on exit does not occur once the above has been completed, I assume I should then enable one at a time to see if I can isolate a specific entry/addon?
Thanks.
-
I assume I should then enable one at a time to see if I can isolate a specific entry/addon?
That's exactly what we usually do, to troubleshoot something like this.
-
After trial by elimination (disabling addons in exe.xml and dll.xml and then enabling one at a time) it turns out that the Addon Manager entry in the dll.xml which loads the bglmanx.dll is linked to the "P3d Error encountered when Exiting" issue. When this entry is disabled, and I am at KCLT (whats left of it) I get no error upon exiting P3D. As soon as I enable the Addon Manager entry and exit P3D while at KCLT, the error on exiting P3D occurs.
-
it turns out that the Addon Manager entry in the dll.xml which loads the bglmanx.dll is linked to the "P3d Error encountered when Exiting" issue.
Which confirms what I already said about you introducing the problem, when you edited the XML files, because the Addon Manager is NOT supposed to be there!
You said you use P3D 3.4 and, under 3.4, our installer DOES NOT place anything in the DLL/EXE.XML files anymore.
It ONLY uses the add-on.xml file to call the executables so, if you add the lines manually to it, maybe because you didn't know about the add-on.xml method, so you assumed the lines were "missing", you are causing the sim to load two copies of it, and this will surely cause a problem.
-
Once again, you are accusing me of doing something I did not do! I have never said nor indicated I have ever edited the xml files. The only files within P3D I have ever edited have been P3D.cfg and Scenery.cfg, and these were limited to minor tweak in P3D.cfg and turning off scenery in the Scenery.cfg.
Also, if you recall, based on your recommendation, I upgraded my P3Dv3.3.5 to v3.4. My P3D v3 install originated at v3, and has been upgraded from there.
I have had the following FSDT products for P3D beginning in 2014 and as the newer have been introduced (GSX, KORD, KDFW, KJFK, KLAS, PHNL, KFLL, KLAX, KIAH, KMEM and latest KCLT. Would any of these in the past have added the entry? There is a back up copy from 2016 that is named dll_xml_Before_Addon_Manager.xml, there is also the exe_xml_Before_Addon_Manager.xml, so I am assuming at some point when I installed an FSDT product or the Stand Alone Manager it made these changes and most likely put the entry in the dll.xml file.
This is why I offered to send you the files to review to determine if there was an errant entry issue or something causing the problem. Nevertheless, should I remove the Addon Manager entry from the dll.xml file and should the exact same entry go into the addon.xml?
Edited to add question.
-
I have never edited the xml files. The only files within P3D I have ever edited have been P3D.cfg and Scenery.cfg.
Then you must have installed something using an outdated installer AFTER you used a new installer.
I have had the following FSDT products for P3D beginning in 2014 (GSX, KORD, KDFW, KJFK, KLAS, PHNL, KFLL, KLAX, KIAH, KMEM and latest KCLT. Would any of these in the past have added the entry?
Yes, the old installers did. But, as soon as you run a new installer, the new installer will migrate all the existing installed sceneries to their new installation folder and will *REMOVE* both their entires from the scenery.cfg AND will *REMOVE* the software from the DLL/EXE.XML file.
Of course, if you ran an old installer after running one of the new ones, it will place the lines back so, you must re-run any updated installer to redo the migration and clean up files.
It's best if you just get rid of any outdated installers you might still have.
-
The only installers I have run in past 6 months have been GSX, KMEM and KCLT and the Stand Alone Manager.
At this point, which installer should I run to resolve this?
-
The only installers I have run in past 6 months have been GSX, KMEM and KCLT and the Stand Alone Manager.
It doesn't tell which version you used to install. If you installed either GSX or KMEM using outdated installers AFTER KCLT, this is what caused the problem, because the installation reverted to the old system.
At this point, which installer should I run to resolve this?
As I've said, any NEW installer will migrate all the other products installed with the old installer.
-
Ran the current GSX installer. The dll.xml, exe.xml and add-on.xml files are all neat and properly arranged now, and no Addon Manager entry in the dll.xml any longer.
However, this did not resolve the error upon exiting P3Dv3.4. If I am at KCLT and exit, the error still occurs. What next to look at to troubleshoot?
-
However, this did not resolve the error upon exiting P3Dv3.4. If I am at KCLT and exit, the error still occurs. What next to look at to troubleshoot?
Have you checked both set of XML files, the ones under %APPDATA% and the ones under %PROGRAMDATA% ? Our installer surely cleans up both but, it might not succeed if there's an error in one of them.
-
I checked both set of XML files, the ones under %APPDATA% and the ones under %PROGRAMDATA%, they are nice, neat and clear of duplications.
I just finished a flight in PMDG B738 NGX from Flight Beam's KSFO to FSDT's KDFW, using Active Sky 2016, Pro-ATC/X and Ultimate Traffic 2 with Tooting's Super Duper UT2 AI updates, and had zero issues. P3D exited normally without any errors.
Any ideas at this point?
-
Please allow me to add something about additions to the dll.xml: I've only installed P3Dv4 products following your quick release of said products. I remember seeing the bglman.dll in one of the files but it seems to have been removed by installing KMEM again. Please check your P3Dv4 installers for KCLT, KFLL, LSGG, LSZH and KLAS - one of those might be adding the dll.xml entry, I didn't add it!
I'm in the same boat now, still getting the crash on exit at KCLT and KMEM with clean exe.xml and dll.xml (in both locations).
-
Please check your P3Dv4 installers for KCLT, KFLL, LSGG, LSZH and KLAS - one of those might be adding the dll.xml entry, I didn't add it!
The installers are all compiled automatically from the same source code so, it's impossible that one of them would have added the lines to the XML file and others didn't.
If you are sure you never added manually, then the only possible explanation is that, at some time, one your XML files was corrupted, so the installed failed to *remove* the existing line, because it won't touch a corrupted XML file.
-
I see that I am not alone in experiencing the error encountered when exiting P3D at KCLT and KMEM. I hope you have not given up on us, Umberto. We are patiently standing by.
-
I see that I am not alone in experiencing the error encountered when exiting P3D at KCLT and KMEM. I hope you have not given up on us, Umberto. We are patiently standing by.
That's just two users out thousands that bought these sceneries so, it's clearly some conflict with some other software installed that hasn't been identified yet. Until I could reproduce it, there's no way we can even start working on a fix, assuming a fix on our side is required or even possible.