FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: McMogwai on November 16, 2019, 11:06:39 am
-
Hello!
After I started the FSDT Live Update yesterday, my P3D does not start anymore. Only displayed in Task Manager.
Once I uninstall GSX2 everything works wonderfully again.
Once I completly reinstall GSX2 the problem is back.
Does anyone have an idea what the problem is?
Thank2 you in advance!
Michael
P. S. Used Version: Prepared3D_Academic_4.5.12.30293
-
here the same. maybe because of the last windows 10 updates? I use p3dv4
regards joerg
-
Good note, thanks Jörg. I also had a Windows Update just before i updated GSX2. I did not consider that as a problem until you mentioned the Windows Update.
-
Same problem here. When i disable FsDreamTeam Addon Manager in Scenery, everything works as normal. But then there is no GSX and Couatl. Using p3dv4.5
-
Same here!!
Hope it will be fixed soon!
-
I started the thread before this one (http://www.fsdreamteam.com/forum/index.php/topic,22417.0.html). But the idea with the Windows update could make sense also at me.
Update: I uninstalled the last Windows update and P3D still don't run with the Addon Manager.
-
Same here - did not updated Win10, but ran the FSDT live Updater. If I disable the addon-maanger the P3d starts (V4.5 HF2).
-
Oh dear, think ill hold off on the latest update for now...
-
Unfortunately the problem persists. Is there any solution or is it being worked on? A short feedback from fsdreamteam would be very nice. Thanks :-)
-
I'm sorry, but I cannot reproduce the problem. Tried the Live Update right now, it works normally, and of course the simulator starts with no issues whatsoever. The usual suggestions:
- Be sure you don't have a firewall program which might block the updater, not downloading alll files.
- Be sure you don't have an antivirus program which might block the updater or, even worse, block some files and let others to be installed, because a mixup of outdated and updated files would likely cause issues. Configure the antivirus to exclude the whole Addon Manager folder and run the FSDT Live Update again.
-
I'm sorry, but I had to delete lots of posts, because there were entirely DIFFERENT issues reported, that didn't had anything to do with this thread ( one was a question about customizing liveries...), and it made impossible to follow it.
The title of this thread is the latest Update is making the sim not to start. We'll discuss about this, and this only. Of course, I cannot reproduce it but, as usual, I'm always open to get into a Teamviewer session, to understand what might be different in your systems.
If you are affected, PLEASE contact me by email or Private Message, so we can arrange a remote assistance session to check for THIS and THIS problem only.
Many removed post here, were referring to an entirely different problem, which caused a GSX error log, which has been already discussed in another thread, with a solution, of course:
http://www.fsdreamteam.com/forum/index.php/topic,22447.msg151597.html#msg151597
-
Sorry, but the problem with p3d not starting, when addon-manager is active still exists !!??
I have followed every single advice here in the forum, unfortunately still doesn't work !?
I see the process "prepar3D.exe" running in the background, but unfortunately nothing happens...
I have to kill prepar3D.exe manually !
Without the addon-manager everything runs without a problem !?
any ideas ?
-
Same here, the problem isn't solved! I also tried everything mentioned in the forum.
Thanks in advance
-
Several users confirmed they fixed the problem, which in their case was outdated VC++ libraries in their system, like in this thread:
http://www.fsdreamteam.com/forum/index.php/topic,22451.msg151705.html#msg151705
-
Thanks for your answer. I also tried that, but the problem is still there.
-
Updating the VC++ runtimes ( do it for both, x86 and x64 ) might require a Windows restart before the update is really finished.
-
I noticed something: while some users that had this problem fixed it by updating the VC++ runtimes, it seems that most of you that posted in this thread and couldn't fix it this way, all have email addresses that looks german. So, it's likely your problem is an entirely different one, even if the final result (p3D not starting) looks similar.
Is your user name folder containing non-ASCII characters, like Umlauts/Eszett perhaps ? If yes, maybe I understand what the problem might be.
-
That could be the problem. My Name is Jürgen. The "Ü" is in some folder names.
Thanks again.
-
GOOD NEWS ;D
After hours of testing, I found the culprit:
It was her LSZH-Aerosoft Scenery !!!
I provided this scenery with an inibuild gsx-profile, and that was the problem!
Obviously the new GSX version doesn't work with the existing inibuild gsx profiles!
Oh man, that was really hard to find this bug now - I hope I helped some of you with it !
Maybe you also have some extern gsx profiles which cause problems !
greetings
ggerolamo
-
My name is Bjørn, and the user name folder contains the letter "ø" (Norwegian letter)
-
I noticed something: while some users that had this problem fixed it by updating the VC++ runtimes, it seems that most of you that posted in this thread and couldn't fix it this way, all have email addresses that looks german. So, it's likely your problem is an entirely different one, even if the final result (p3D not starting) looks similar.
Is your user name folder containing non-ASCII characters, like Umlauts/Eszett perhaps ? If yes, maybe I understand what the problem might be.
Yes, thats possible, mine is Joël
-
Yes, thats possible, mine is Joël
I tried here, creating both a new "Joël" user name, and a "Bjørn" and, in both cases, I cannot reproduce the problem, but perhaps it must be tested on a non-English Windows as well. I made some changes "in the blind" that might result in some difference, let me know how it goes with this file:
http://betaupdate.fsdreamteam.com/bglmanx64.dll
Place it in the root of the Addon Manager folder, replacing the one which should be already there.
-
Unfortunately, it didn’t help as well. :-[
-
Try this:
http://update.fsdreamteam.com/LOG/bglmanx64.dll
This is a debug version with logging. When the sim appear to be locked up, exit or force exit, and check this folder:
%APPDATA%\Virtuali\bglmanx.log
ZIP that file and send it to me by email (use the address on the "Contact Us" page of this site, or the small email icon under by avatar logo ). Maybe, it will tell me *where* the program is crashing.
If you don't have that file, it will still be useful to know, because if you don't have it, it means the program haven't even got a chance to start, so this will tell for sure the problem is with your system, like missing libraries, antivirus, etc.
-
Thank you so much for helping. I tried the debug Version, but can't find the file. I checked the antivirus several times, but no problem there.
-
hmm in C:\Users\Joël\AppData and C:\Users\Joël\AppData\Roaming\Virtuali i can't find this file.
I have to close P3D via Task Manager if this is not a Problem.
Possibly this is another point:
I have uninstalled your Geneva addon to try the new one from Aerosoft. Then I have seen some old objects from your scenery in the one from Aerosoft on false places (I think they are from your scenery but they could also be P3D standard ones). After that I controlled the ranking in the scenery.cfg of AS GVA with “Lorby-SI AddonOrganizer_P3D_V4”. I received an “duplicate” error and I let correct it from this program. Now I restarted P3D and it didn’t run anymore.
In the same time, I started FSDT Live Update, but I don’t know anymore if it was before I started the P3D the first time or in the same time as I correct the Scenery.cfg with “Lorby-SI AddonOrganizer_P3D_V4”.
I deleted the scenery.cfg and Prepar3D.cfg and this didn’t help. Later I have seen, that there are a lot of other Peoples reports some problem and so I think its not the problem with the GVA scenery.
-
I tried the debug Version, but can't find the file.
This seems to confirm what I was suspecting all along: there's nothing wrong IN the Addon Manager, because if you don't even have a Log created with the debug version, it means the program was blocked by the OS, the antivirus, or it simply couldn't start because some kind of system library is either missing/outdated/corrupted in your system.
I think the only option left here, is to contact me in private to have a Teamviewer session, so I can see what's wrong with your system.
-
Hi Umberto,
thank you very much for your efforts.
I have updated all necessary programs/libarys again.
Then i tried your debug Version of bglmanx64.dll. I didnt find a log file and of course the prepared prevents to start.
Then I simply deactivated the dll (renamed) without touching the rest of the installation. And Prepared starts again normally (without gsx in the menu). The file re-enabled and Prepared does not start as i expected.
Of course I checked bitdefender (antivirus) again but i could not find any strange.
However, i find interesting that obiously the dll prevent prepared to start. Maybe that helps to narrow down the problem?
I really do not want to miss GSX in my simulation - but I do not know what to do anymore.
Thx, Michael
P. S. I would make myself available by teamviewer.
-
I changed my account name on Windows 10 and removed the german umlaut ö from my name. My Name is "Michael S......" I reboot my System and tried to start prepared with gsx. No chance. Unfortunately that did not help ...
-
Please be patient, I already had a TM session with Joggu a few hours ago, and tried everything, but still couldn't find the reason. However, he and I had limited time this evening, so we'll have another try tomorrow, so I would have several other things to try.
My theory so far, is that it must be something related to VC++ runtimes, because even in his case, the program doesn't even execute a single line of code (the first thing it does is to open the log file so, even with a single line, some log file *should* appear), so only something in the OS can block a program like that, most likely a missing .DLL or something like that.
But I have several tools to try, so I'm sure we'll find the cause.
-
Hi Umberto,
after installation of the update 2.8 I got this message see attached and P3dv4.5 not starting.
Any idea?
-
Hi Umberto,
after installation of the update 2.8 I got this message see attached and P3dv4.5 not starting.
Any idea?
I get this message whenever I accidentally start the P3D twice.
-
That problem accurs after updating GSX 2 to v2.8 -> is not so easy to answer. The p3dv4 is trying to start again and again because of that this messages accuring again and again ... >:(
BTW after updating I expect updated software without investigating why the P3d is not working ....
-
I believe the problem has been found, thanks to the help from Joggu, which I had two separate sessions with.
After trying everything, we found that, on his system, the add-on.xml path for a scenery from FSDG resulted in a crash when being read. It was related to the fact his user name contained non-ASCII characters, but the strange thing was, ALL the other sceneries installed ( even others from FSDG ), had their add-on.xml in the same folder, since his user name it's always the same.
But for some reason, this particular add-on.xml couldn't be opened. The file itself was fine, it was just the problem of being in a path with a non-ASCII username, but the thing that puzzles me is all the other add-on.xml were in the same path.
This triggered some kind of bug in an open-source library we use to parse xml file, which made the Addon Manager crash, and the sim with it ( a .DLL that crashes will crash the sim, unfortunately ).
I still not fully understand what only *that* file couldn't be opened without crashing, but I managed to add a workaround to prevent this case. It's on the Live Update now, waiting to hear your feedback.
-
I just run the Live Updater and added the FSDG files again. P3D is opening correctly and runs fine! Thank you so much for your efforts!
Do you just remember which scenery triggered the error?
-
Do you just remember which scenery triggered the error?
It was the Documents\Prepar3D V4 Add-on\FSDG\add-on.xml
But the xml file itself was fine, because if I placed in my system, it worked normally. In order to replicate your crash, I had to create an alias named "Joël" on my system, and edit the path in the add-on.cfg to point *there* and THEN I could make my system crash as well.
Which as I've said, it's really strange, because ALL your other add-on.xml files were in the same C:\Users\Joël path, but if you remember the session we had, it was enough to skip THIS single add-on, to have your P3D starting.
-
It works! ;D
Thank you very much for your support.
Greeting
Jürgen
-
Thank God - or in this case: Thank Umberto, it works again & great!
I hope I did not get annoyed too much. But I was close to despair because I tried everything to get GSX back to work.
Thank you for not giving up to find and fix the bug.
So now I have to fly. A lot of flights have been canceled for more than a week. I have to catch it up :-)
Again, thank you very very much!
Best greetings, Michael
-
Sorry just for my understanding. Just run the live update or do I have to move the FSDG\add-on.xml also ?
-
Sorry, after the live update for me it does not solve the problem P3d still not starting ....
-
Sorry just for my understanding. Just run the live update or do I have to move the FSDG\add-on.xml also ?
No, the latest update is able to deal with it.
-
I got the latest update one hour ago, but does not solve - sorry. Where can I find the log file in order to send it to you?
-
I got the latest update one hour ago, but does not solve - sorry. Where can I find the log file in order to send it to you?
The update surely fixed the problem which was caused by non-ASCII user names. Have you noticed if it has downloaded an updated bglmanx64.dll ?
If not, or are not sure, please check the date of the Digital Signature of this file:
Addon Manager\bglmanx64.dll
The date of the digital signature, not the date of the file.
-
It worked for me. Thank you so much Umberto, and you 2 Joggu :D If you ever com to Oslo, i'll have a cold beer waiting for U
-
I have also a non-ASCII user name (with "ä"). See the attached picture
-
I have also a non-ASCII user name (with "ä"). See the attached picture
As you can see, the problem was fixed by everybody else with a non-ASCII user name, except you. That's why I asked to check the date of the digital signature of the file, because I'm not sure you got the updated one.
-
Hi Umberto,
did you checked the attached pic in my last message? It was from yesterday evening ....?
See attached update.
The only thing I was trying was installing Visual C++ 2019 both x86 and x64 . https://support.microsoft.com/.../the-latest-supported... nothing else
In the task manager still there.
Please for me is not solved!
-
did you checked the attached pic in my last message? It was from yesterday evening ....?
Of course, that's precisely why for "the date of the digital signature, not the date of the file", because the date of the file only tells when *you* downloaded it, doesn't say for sure if it IS the last version, because you might have got and outdated version from the server (we use 190 servers, they are not all in sync immediately), which some times could happen, in the first few hours after an update.
But from the digital signature date, it seems you got the latest version, the one that everybody else in this thread has confirmed to be working so, perhaps your problem was different.
Try this logging version, which also has additional checks in case your username has non-ASCII characters:
http://update.fsdreamteam.com/LOG/bglmanx64.dll
Even if the sim doesn't start, see if there's a log file here after the exit:
%APPDATA%\virtuali\bglmanx.log
If you have it, ZIP it, attach it to a post, and send him BY EMAIL the email address is on the small email icon under my fsdt logo avatar here.
-
Ok, thank you. Will be back with the log files soon!
-
Hi Umberto,
-> the logging version from you of the bglmanx64.dll does not help the P3dv4 was not starting, only still in the backround I have to finish him via the task manager
-> when I delete the bglmanx64.dll - P3dv4 starts normal , but without GSX of course
-> no bglmanx.log file found under ... virtuali ...
The troublemaker seems to be the bglmanx64.dll ???
Any idea?
-
The troublemaker seems to be the bglmanx64.dll ???
On your system only, because this version has been fixed the problem for everybody else that ever posted in this thread. I'm afraid we'll have to schedule a Teamviewer session tomorrow, maybe your issue is the same as all the others.
Send me a PM to arrange this.
-
I have send you a PM, hopefully has arrived you