FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: disco79stu on September 07, 2021, 01:32:57 pm
-
I have a huge problem with today's update (2.9.4):
After running LiveUpdate, GSX works as expected, everything looks ok, Logo are there.
But when I run P3D (v5.2) a second time OR I reset my position through the GSX menu, GSX becomes unresponsive (menu won't show).
Restarting Couatl through the Add-Ons menu tab does not solve the problem, restarting the Sim does not work.
Menu entries are still there, but GSX just won't respond.
It's only when I run LiveUpdate again, GSX will work again, but only for one time.
Please advise.
Thanks,
Stu
-
But when I run P3D (v5.2) a second time OR I reset my position through the GSX menu, GSX becomes unresponsive (menu won't show).
I can't reproduce the problem. Tried several restarts, works every time. Tried both by exiting and restarting the sim, and using the "Restart Couatl" as well.
Restarting Couatl through the Add-Ons menu tab does not solve the problem, restarting the Sim does not work. Menu entries are still there, but GSX just won't respond.
Are you sure you have the latest 5.2 hotfix, and you installed using the FULL installer ( not just the Client ). This seems the very well known problem of the Simconnect menu being stuck freezing the sim. If you update just using the Client, the menu system might not be updated so, you might still running using the bugged Html menu.
And if you haven't installed the hotfix, it's sure the menu will freeze the sim.
It's only when I run LiveUpdate again, GSX will work again, but only for one time.
That might indicate you are running the sim in a wrong Compatibility mode. It's possible Windows has set a wrong compatibility setting in the registry for you, because the previous session crashed. The Live Update fixes that, by resetting all compatibility flags to default, that explains why it seem fixed that way.
-
Same here, after updating GSX crashing... waitting for some more info...
-
Same here, after updating GSX crashing... waitting for some more info...
That doesn't seem to be the "same" problem at all. The OP reported he couldn't start the sim a 2nd time without having the SIM freezing, which was eventually fixed by running the FSDT Live Updater, indicating a problem with the sim itself ( not updated correctly or using the wrong compatibility settings )
You are reporting something that looks very different, a "GSX crash", with no further details like an error message or something like that so, please clarify.
-
Are you sure you have the latest 5.2 hotfix, and you installed using the FULL installer ( not just the Client ).
That might indicate you are running the sim in a wrong Compatibility mode.
I'm running the latest P3D version, no compatibility modes active, sim did not crash.
Everything worked perfectly the previous months, I have never had problems with GXS until today's update.
But I noticed after closing the sim, the process "couatl64_P3D.exe" keeps running. Could that be a hint?
-
The OP reported he couldn't start the sim a 2nd time without having the SIM freezing, which was eventually fixed by running the FSDT Live Updater.
No. The Sim works fine. It did not crash.
1. I ran liveUpdate (new version installed)
2. I opened P3D. GSX works fine (called for catering etc.)
3. I "reset position" withing the GSX menu
4. GSX won't respond anymore.
After I close P3D (normally, no crash) and open P3D again, GSX STILL won't respond.
Only when I run LiveUpdate again, GSX starts working again (but the whole above problem starts again).
-
I'm running the latest P3D version, no compatibility modes active, sim did not crash.
The wrong compatibility settings which are set by Windows are NOT visible, unless you edit the registry.
Everything worked perfectly the previous months, I have never had problems with GXS until today's update. But I noticed after closing the sim, the process "couatl64_P3D.exe" keeps running. Could that be a hint?
Couatl64_P3D.exe closes normally here and, nothing in the latest update could possibly change anything related to that. If the simulator itself crashes for other reasons, it's possible it might have Couatl not closing automatically, because if the Simconnect communication with the sim is interrupted abruptly, that's likely to happen.
First, try to wait a bit if the Couatl64_P3D.exe closes itself automatically, since it DOES have a safety mechanism that should kick in when the sim crashes for other reason and should be able to close itself, perhaps taking a bit longer.
If it really doesn't close, just terminate it with the Task Manager and see if it works on the next restart. That would be another explanation why it was "fixed" by the Live Updater, because another thing the updater does, is to be sure Couatl it's not running when you start the update.
-
Here's a video of the issue:
https://vimeo.com/599500541
-
If it really doesn't close, just terminate it with the Task Manager and see if it works on the next restart.
Just tried, this doesn't work either.
When I terminate the process and run P3D again, GSX ist still unresponsive (no pop up menu etc.).
The process "couatl64_P3D.exe" is starting with P3D though.
-
Here's a video of the issue:
Have you disabled the messages in the top green bar ?
When you reset the position, you should have seen the message "Airport cache loaded successfully", which indicates GSX is ready but now, with the messages disabled, I can't tell if it failed to restart of you just disabled the messages.
-
Same here, after updating GSX crashing... waitting for some more info...
Let me be more detaelied:
After updating , sim loading , GSX menu not shown... when pressing restart couatl , GSX crashing... (no more dispaly at the menu at all)
-
should be able to close itself, perhaps taking a bit longer.
Waited 10min, the process keeps running.
RE-booting the PC also doesn't help, GSX stays unresponsive.
Right now the only way to get it to work again for one session is by running LiveUpdate.
-
After updating , sim loading , GSX menu not shown... when pressing restart couatl , GSX crashing... (no more dispaly at the menu at all)
So yes, your problem is completely different than the OP because, it always had the GSX menu visible. The usual suggestions:
- Be absolutely sure the antivirus is configured to exclude the WHOLE Addon Manager folder.
- Run the FSDT Live Update again.
-
Here's a video of the issue:
Have you disabled the messages in the top green bar ?
When you reset the position, you should have seen the message "Airport cache loaded successfully", which indicates GSX is ready but now, with the messages disabled, I can't tell if it failed to restart of you just disabled the messages.
I have that enabled, yes. I see this message when I open the Sim after LiveUpdate. I've never seen that oon position reset before though, only when "restarting and rebuilding airport cache".
-
Here's a video of the issue:
Have you disabled the messages in the top green bar ?
When you reset the position, you should have seen the message "Airport cache loaded successfully", which indicates GSX is ready but now, with the messages disabled, I can't tell if it failed to restart of you just disabled the messages.
Hi,
I'm having a similar problem, GSX menu not shown when opening the sim, an attempt to restart couatl and rebuild airport cache causing the couatl and gsx entries in the add-on menu to disappear, no messages in the green bar related to the airport cache reset or gsx at all (the green bar is activated, other messages like when loading PMDG aircrafts are working).
I've tried to run the FSDT live updater, no luck with that.
-
I have that enabled, yes
Are you sure ? Then why I can't see the green message saying ( in your case ) "[GSX] Handling by Menzies" and "[GSX] Catering services requested" appearing in sequence in your video ?
I see this message when I open the Sim after LiveUpdate. I've never seen that oon position reset before though, only when "restarting and rebuilding airport cache".
That's a problem indeed but, as I've said, it's strange you don't have the following two messages:
"[GSX] Position Reset" appearing for a very short time as soon as you select "Reset position" ( this might be too brief to be seen, some times )
"Airport cache loaded successfully" when the restart completed. This, coupled with the fact you don't have the "Handling" and "Catering" messages too, seemed to indicate either you have disable all green messages altogether, or there's a problem with those menus.
-
It's getting a little confusing to me.
I get some messages, yes, but not all, so maybe I indeed deactivated them and only get the important ones?
Anyway, I'm a little step further now:
I tested several combinations, and everything worked as usual. Repositioning the aircraft, calling stairs, restarting couatl, everything fine.
UNTIL I call for catering. Then and only then I will have an entry in the pop-up menu to "reset position" (not "reposition aircraft"). When I hit THAT, GSX breaks.
Will keep testing....
-
UNTIL I call for catering. Then and only then I will have an entry in the pop-up menu to "reset position" (not "reposition aircraft"). When I hit THAT, GSX breaks.
That's not normal either. The "Reset position" will appear after you start ANY service, not just Catering. And it won't replace the "Reposition aircraft" at the 0 slot but, instead, will replace the "customize this parking position" at slot 9, because you can't customize a parking while services are running.
-
UNTIL I call for catering. Then and only then I will have an entry in the pop-up menu to "reset position" (not "reposition aircraft"). When I hit THAT, GSX breaks.
That's not normal either. The "Reset position" will appear after you start ANY service, not just Catering. And it won't replace the "Reposition aircraft" at the 0 slot but, instead, will replace the "customize this parking position" at slot 9, because you can't customize a parking while services are running.
Okay, so I guess I should completely de- and re-install then. Maybe this helps.
-
I tried doing something similar to what you did in your video ( calling catering and then "reset position" ), and it works just fine, see the video:
As you can see, I also tried a reset position after calling refueling and even the most tricky one: a reset while SODE jetways were moving, which restarts both SODE and GSX, and that one worked normally as well.
-
I tried doing something similar to what you did in your video ( calling catering and then "reset position" ), and it works just fine, see the video:
As you can see, I also tried a reset position after calling refueling and even the most tricky one: a reset while SODE jetways were moving, which restarts both SODE and GSX, and that one worked normally as well.
Okay, thanks, then it's definitely something messed up on my end.
When I tried to reset with SODE moving, it did not restart SODE.
I'll try a clean re-installation of GSX and SODE.
-
Okay, so I uninstalled GSX and AddonManager and re-installed everything.
Unfortunately, the problem persists.
I believe that after the 1st run (after LiveUpdate, where everything works), GSX apparently won't start properly. I didn't notice this at first but let's forget the catering/resetting etc. for a second.
Here's what happens:
- 1st run, everything's OK. In the top menu bar under "Add-ons" I have "Couatl settings", "Couatl Live Update" and "GSX". All good & working.
- Quit P3D normally.
- 2nd run, GSX now unresponsive, in the top menu I now only have "Couatl settings" and "Coutl Live Update". ... "GSX" is missing (as seen in my video as well).
Nothing I do (reboot, restart etc.) will bring the "GSX" menu entry back from this point on. So "something" is not starting anymore after the 1st run, for whatever reason.
Any ideas?
-
I was fairly sure the problem won't be fixed by reinstalling GSX because, it's most likely not caused by GSX.
I'll ask again: do you see some of the green messages ? Check if you have the GSX Verbosity setting to the maximum value.
-
I was fairly sure the problem won't be fixed by reinstalling GSX because, it's most likely not caused by GSX.
I'll ask again: do you see some of the green messages ? Check if you have the GSX Verbosity setting to the maximum value.
Yes, after setting the messages to "all", I saw every message, green and red. The ground handler was mentioned as well as the airport cache etc. Seemed legit.
But still, it doesn't work anymore after I quit P3D with the above mentioned missing "GSX" menu entry.
-
But still, it doesn't work anymore after I quit P3D with the above mentioned missing "GSX" menu entry.
Which is not what you showed in the video, which was GSX not restarting during a normal session. Now you are saying it's not starting after you quit P3D ( and I assume after you also restart P3D ) so, are you:
- Still getting the problem of the "reset position", as in your previous video ?
- Getting a different problem, which is a failure to start after quitting and restarting the sim ?
- Getting both problems ?
-
It looks like all of my FSDT purchased products are in TRIAL mode after this latest update.
Attempting to re-register them does nothing.
I also am able to see the GSX menu initially, but on subsequent restarts it is no longer visible. The addon manager shows TRIAL mode for GSX and all other FSDT addons I have.
-
It looks like all of my FSDT purchased products are in TRIAL mode after this latest update.
Please don't post in a thread something that doesn't have anything to do with it, especially when another thread with a title exactly like your problem has already opened here, containing several suggestions:
http://www.fsdreamteam.com/forum/index.php/topic,25476.0.html
-
But still, it doesn't work anymore after I quit P3D with the above mentioned missing "GSX" menu entry.
Which is not what you showed in the video, which was GSX not restarting during a normal session. Now you are saying it's not starting after you quit P3D ( and I assume after you also restart P3D ) so, are you:
- Still getting the problem of the "reset position", as in your previous video ?
- Getting a different problem, which is a failure to start after quitting and restarting the sim ?
- Getting both problems ?
Basically both problems. I just wanted to make it as easy as possible. I have the feeling the issues are rooted in the same problem.
- "reset position" will "kill" GSX and it's entry in the menu.
- Quitting P3D will do the same, after opening it again, the GSX menu entry is gone.
- The "Couatl64_P3D.exe" process won't terminate when I quit P3D. This leads to Couatl being missing from P3D all togehter on the next start, unless I terminate the process manually.
- In all cases, GSX will only work again when I run LiveUpdate prior to opening P3D. But only so long until I either quit P3D or "reset position". After that GSX will not work anymore.
What related processes should be running for GSX to work correctly?
-
Hi Umberto,
After playing a bit with my scenery list I was able to open the GSX menu but now I'm facing the same issue as the OP. GSX is working only after running the FSDT live updater, I can see all green bar messages and everything is working until I'm changing aircrafts in the sim or after closing and re-opening. Couatl64_P3D takes a lot of time to close after closing the P3D, even tried to manually shut it down before re opening the sim with no luck.
Thanks
-
Couatl64_P3D takes a lot of time to close after closing the P3D
But it does close automatically ? Taking a long time to close it's not a problem, it might take a while if you have a lot of add-ons installed, so both a lot of RAM is allocated ( meaning Windows must reclaim it all, before it will really close the sim ) but also lots of add-ons are handling the closure.
Also, we have a system that will try to quit in any case, when the connection with the simulator is interrupted for some time, which also explains why it seem to take longer than usual to close automatically. But if it close by itself, it means everything is fine, and it should start normally on the next sim restart.
-
Couatl64_P3D takes a lot of time to close after closing the P3D
But it does close automatically ? Taking a long time to close it's not a problem, it might take a while if you have a lot of add-ons installed, so both a lot of RAM is allocated ( meaning Windows must reclaim it all, before it will really close the sim ) but also lots of add-ons are handling the closure.
Also, we have a system that will try to quit in any case, when the connection with the simulator is interrupted for some time, which also explains why it seem to take longer than usual to close automatically. But if it close by itself, it means everything is fine, and it should start normally on the next sim restart.
It is not closing at all here, no matter how long I wait. And as mentioned, when I close it manually it WILL start with P3D correctly, but this doesn't solve the problem that the GSX menu entry (and the GSX functionality) is gone.
-
It is not closing at all here, no matter how long I wait.
I don't know what to say, it closes here 100% of the times.
The only time it doesn't close, is when there's an unrecoverable error ( which we already fixed ), and you reply Yes to the request to restart Couatl after the error. But, since at least the F-35 error has already being fixed, unless there's another unknown error, this shouldn't happen any
And as mentioned, when I close it manually it WILL start with P3D correctly, but this doesn't solve the problem that the GSX menu entry (and the GSX functionality) is gone.
And it works if you run the FSDT Live Update again, before starting the sim another time ?
-
And it works if you run the FSDT Live Update again, before starting the sim another time ?
Correct. This solves the issue for one session.
After closing P3D something brakes and not even a reboot can bring it back.
-
Correct. This solves the issue for one session.
Check my reply here and see if this might be your case:
http://www.fsdreamteam.com/forum/index.php/topic,25479.msg167492.html#msg167492
-
Correct. This solves the issue for one session.
Check my reply here and see if this might be your case:
http://www.fsdreamteam.com/forum/index.php/topic,25479.msg167492.html#msg167492
Hm....that's not really the case here.
I know GSX' behavior and those instances where it's not responsive until the airport cache is created, and I've been using it for years now without any issues of that kind. I have successfully created own GSX airport profiles, changed SODE jetways, etc. etc.
And even when GSX got stuck or crashed in the past, it was nothing a restart/reboot couldn't fix.
Right now, after one successful sim session, I don't even have the GSX menu entry in P3D. I'm really out of ideas...
-
I know GSX' behavior and those instances where it's not responsive until the airport cache is created, and I've been using it for years now without any issues of that kind. I have successfully created own GSX airport profiles, changed SODE jetways, etc. etc.
Please re-read my post again.
There has always been TWO caches, the airport cache and the object cache but, until today, the object cache was created fairly quickly, so we never add any message about it.
Now, with many more objects due to the new multi-liveries, the object cache creation will take longer and, since there's no specific message telling it's ready, it's possible you might have called the GSX before it was ready. That's why I asked to check on an airport with GSX jetways for their appearance, as the cue GSX is really ready.
And, it's also possible if this happens, the object cache creation might be interrupted, so you need to run the FSDT Live Update which, amongst many other things, clear the whole airport and object cache folder.
-
Okay, so I uninstalled GSX and AddonManager and re-installed everything.
Unfortunately, the problem persists.
I believe that after the 1st run (after LiveUpdate, where everything works), GSX apparently won't start properly. I didn't notice this at first but let's forget the catering/resetting etc. for a second.
Here's what happens:
- 1st run, everything's OK. In the top menu bar under "Add-ons" I have "Couatl settings", "Couatl Live Update" and "GSX". All good & working.
- Quit P3D normally.
- 2nd run, GSX now unresponsive, in the top menu I now only have "Couatl settings" and "Coutl Live Update". ... "GSX" is missing (as seen in my video as well).
Nothing I do (reboot, restart etc.) will bring the "GSX" menu entry back from this point on. So "something" is not starting anymore after the 1st run, for whatever reason.
Any ideas?
Just posting to put my "+1" to this issue. This is exactly the behaviour that I'm seeing also
After doing the initial upgrade, I did see the "Airport Cache" rebuild successfully in the status bar. Subsequent P3D starts, GSX seem to be missing from the Addons menu. It is however present (and activated GSX + L2) in Addon Manager
-
I know GSX' behavior and those instances where it's not responsive until the airport cache is created, and I've been using it for years now without any issues of that kind. I have successfully created own GSX airport profiles, changed SODE jetways, etc. etc.
Please re-read my post again.
There has always been TWO caches, the airport cache and the object cache but, until today, the object cache was created fairly quickly, so we never add any message about it.
Now, with many more objects due to the new multi-liveries, the object cache creation will take longer and, since there's no specific message telling it's ready, it's possible you might have called the GSX before it was ready. That's why I asked to check on an airport with GSX jetways for their appearance, as the cue GSX is really ready.
And, it's also possible if this happens, the object cache creation might be interrupted, so you need to run the FSDT Live Update which, amongst many other things, clear the whole airport and object cache folder.
Okay, I see what you mean.
But that didn't seem to solve it either.
1. I ran LiveUpdate
2. Opened P3D and didn't do anything for at least 5min.
3. I just checked the menu entries under "Add-ons" without even selecting or calling anything. The GSX entry was there:
(https://i.imgur.com/7bAYTNX.png)
4. I quit P3D (couatl64_P3D.exe closed as well this time)
5. I started P3D again and right away the "GSX" entry was gone again from the menu:
(https://i.imgur.com/zGeoKaf.png)
-
Having this exact same problem after installing uninstalling, actually doing a few things for the past couple of hours and getting the same thing. GSX initally starts then a reset or change aircraft/airport stops GSX alltogether. I have tried to resart couatl but that doesn not respond either without a P3D resart, then back to square one. I loose all my fsdreamteam sceneries also just with a reset or move airport. I have waited 10 mins or so after a rebuild airpost cache and nothing appears.
-
Having this exact same problem after installing uninstalling, actually doing a few things for the past couple of hours and getting the same thing.
See the last replies here:
http://www.fsdreamteam.com/forum/index.php/topic,25476.msg167518.html#msg167518
About clearing the airport and object cache before starting.
-
So I've deleted, de-installed, re-installed everything again, but the problem is still there.
I tested at a GSX-jetway airport, let the cache(s) rebuilt, GSX-jetways appeared, everything seemed ok.
Then I did that catering-reset-position-thing again and got a green bar message
[SODE] All active Jetways stopped due to Main Module (exe) Reset/Disconnection! (N-1)
All Jetways disappeared, GSX-menu-entry vanished, GSX didn't recover or started working again, even after resart.
Can you make sense of this?
-
Then I did that catering-reset-position-thing again and got a green bar message
[SODE] All active Jetways stopped due to Main Module (exe) Reset/Disconnection! (N-1)
That's exactly what you are supposed to see when you restart when SODE is doing something, see my previous video:
Which showing the same message, that's perfectly normal ( SODE is telling you GSX asked SODE to restart ), but in my case, you can see it restarts normally after that.
-
I see.
So in my case it just won't restart and it also won't start with P3D any more after the initial session after LiveUpdate.
No matter what I do, everything seems fine and okay (cache rebuilt, jetways appearing, services working) until I start P3D again. GSX will only start once right now.
-
Add me to that list...
I just ran Live Update.
Startet in LOWW (I have GSX Jetways there).
Inital load everything fine.
I changed now the Aircraft and for any reason GSX did a restart:
(https://i.imgur.com/YUvq4Vf.png)
Thats in the Taskmanager but nothing is happening
EDIT:
Got in event viewer now this after closing P3D:
Name der fehlerhaften Anwendung: couatl64_P3D.exe, Version: 4.0.0.4579, Zeitstempel: 0x613104de
Name des fehlerhaften Moduls: couatl64_P3D.exe, Version: 4.0.0.4579, Zeitstempel: 0x613104de
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000054ff4
ID des fehlerhaften Prozesses: 0x3254
Startzeit der fehlerhaften Anwendung: 0x01d7a41b675a2846
Pfad der fehlerhaften Anwendung: E:\Addon Manager\couatl64\couatl64_P3D.exe
Pfad des fehlerhaften Moduls: E:\Addon Manager\couatl64\couatl64_P3D.exe
Berichtskennung: 37e6ac9e-9874-4ab9-8f4b-7b6699bcd409
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
-
Deleted the cache files and restarted at KLAX. All ok (apart from trial mode warning now ) until I change aircraft i.e. NGXu. Then the scenery dissapears and couatl dissapears from Taskmanager but still have couatl64_P3D running if I use Process Explorer. Couatl still in Addon Menu but does not respond to anything i.e rebuild cache etc. The only way to get GSX back is to resart p3d then the loop continues.
-
Okay, I now can also confirm the "solution" from the other thread.
Deleting the Couatl folder in \ProgramData\Virtuali before opening P3D will bring GSX back to life without running LiveUpdate.
The caches rebuild and GSX works. But this is necessary every time I start P3D.
(deleting that folder was only possible after manually terminating the Couatl process in the task manager. No Idea why it just won't shut down automatically)
-
No matter what I do, everything seems fine and okay (cache rebuilt, jetways appearing, services working) until I start P3D again. GSX will only start once right now.
You haven't said if it's solved the way I told you in my last reply, when I said to check another thread, which suggested to remove the C:\ProgramData\Virtuali\Couatl ( that's the cache folder ) manually before each start.
-
No matter what I do, everything seems fine and okay (cache rebuilt, jetways appearing, services working) until I start P3D again. GSX will only start once right now.
You haven't said if it's solved the way I told you in my last reply, when I said to check another thread, which suggested to remove the C:\ProgramData\Virtuali\Couatl ( that's the cache folder ) manually before each start.
sorry, I didn‘t catch that at first and tried to make up for it in my post above. Indeed deleting that cache folder fixes the issue but only for one session (the one where it rebuilds the cache).
-
same problem
-
I already posted a new thread, but I am having the exact issue in P3DV4.5 as well.
Scott
-
I already posted a new thread, but I am having the exact issue in P3DV4.5 as well.
If you have this exact issue, you shouldn't have posted a new thread. I removed it so, unless your issue is different, don't open a new thread when a new one discussing exactly the same issue is already opened and you even posted on it.
As discussed in this thread, we isolated the problem although we haven't been able to replicate it yet, I could only see it on an user's system via remote assistance. For those affected, it results in the inability to make a "normal" Restart IF the airport cache has already been built from a previous session
If the cache is rebuilt, Restart seems to work ( or, at least, it worked with no issues on that user system I had a chance to try ) so, as TEMPORARY fix, we released a small update that for the time being will always trigger a cache rebuild.
This, depending on your system speed and the number of sceneries you have installed, will like result in a slower Restart. To speed it up as best as possible, I suggest adding all folders you have sceneries installed to the Antivirus Exclusions, which will bring down the cache regeneration time quite a bit. Again, this is just a temporary solution that should help you get going while we find what's causing this.
-
a temporary solution that should help you get going while we find what's causing this.
Thanks Umberto!
-
Thanks Umberto!
Scott
-
Similar Problem here - When I delete the cache folder in ProgramData\Virtuali GSX starts as usual. When I restart the P3d v5.2 it don´ts appears. When I try to delete the cache again I get the message "this folder is using by another program". In the task Manager shows couatl-engine is already running, seems not to be closed during Sim-shutdown. When I shut the couatl task, I can delete the cache folder and after restarting the sim, GSX works.
-
For me the update also did not solve the issue.
It's still working directly after a LiveUpdate, but on the next sim start, GSX won't work again (and it won't rebuild the caches).
Deleting the cache folder manually as a workaround however does still make GSX work again.
I also noticed that after the LiveUpdate, couatl64_P3D.exe will properly shut down with P3D (checked task manager), at least for me.
But after the next sim start and sim shutdown it will keep running forever forcing me to terminating it manually in order to delete the Couatl. cache folder.
-
For me the update also did not solve the issue.
It's still working directly after a LiveUpdate, but on the next sim start, GSX won't work again (and it won't rebuild the caches).
Deleting the cache folder manually as a workaround however does still make GSX work again.
That's because the fix never claimed to have fixed a START when the cache is already present. As the release notes say, the fix only fixes RESTARTS, which are all the things triggered by switching the airplane, select "Reset position", choosing "Restart Couatl", which were the most annoying to be affected by this problem.
So yes, while we find a proper solution, for the first start of the sim, removing the C:\ProgramData\Virtuali\Couatl folder is still required. I suggest creating a batch file to start the sim, containing those lines
DEL C:\ProgramData\Virtuali\Couatl /S /Q
PREPAR3D.EXE
This should be named with any name with a .BAT extension ( like START.BAT ), to be placed in the Prepar3d root folder and used to start the sim.
-
I suggest creating a batch file to start the sim, containing those lines
DEL C:\ProgramData\Virtuali\Couatl
PREPAR3D.EXE
This should be named with any name with a .BAT extension ( like START.BAT ), to be placed in the Prepar3d root folder and used to start the sim.
Hm, while this asks me if I want to delete it, it's not doing anything when I agee.
I had to add "/s" to get it to delete everything even in the sub folders (and I added "/q" to skip the prompting). But this way it works for me.
Edit: Here's the bat code I use:
DEL C:\ProgramData\Virtuali\Couatl /s /q
start "" "C:\Program Files\Lockheed Martin\Prepar3D v5\PREPAR3D.exe"
-
I had to add "/s" to get it to delete everything even in the sub folders (and I added "/q" to skip the prompting). But this way it works for me.
Yes, you are right, I forgot the /s, your code it's fine.
-
I suggest creating a batch file to start the sim, containing those lines
DEL C:\ProgramData\Virtuali\Couatl
PREPAR3D.EXE
This should be named with any name with a .BAT extension ( like START.BAT ), to be placed in the Prepar3d root folder and used to start the sim.
Hm, while this asks me if I want to delete it, it's not doing anything when I agee.
I had to add "/s" to get it to delete everything even in the sub folders (and I added "/q" to skip the prompting). But this way it works for me.
Edit: Here's the bat code I use:
DEL C:\ProgramData\Virtuali\Couatl /s /q
start "" "C:\Program Files\Lockheed Martin\Prepar3D v5\PREPAR3D.exe"
This was helpful, thanks
-
Hi Umberto,
It worked fine initially, but then back to no GSX. :'(
Scott
-
It worked fine initially, but then back to no GSX.
Have you got the latest update ?
Are you clearing the cache before every startup, possibly using a batch file as explained above ?
-
I was not clearing the cache. I thought the update was doing that. I will run the batch file and see how that goes. I did run the update.
Scott
-
Hi Umberto, thought you might like some feedback. The patch dated 8th Sept is seemingly not enough to resolve this issue
Applied the 8th Sept update. LiveUpdate killed the %programdata%\virtuali\couatl folder.
Launched sim, spawned at an airport
GSX rebuild the airport database - GSX present in Add-ons menu - GSX works
Closed sim - all related processes closed fine
Re-launched sim, spawned at an airport - %programdata%\virtuali\couatl folder is still present, and GSX is no longer in the Add-ons menu
Closed sim - couatl process hangs and does not close (needs to be forcibly killed)
With the couatl process confirmed closed, launch sim with bat file, GSX operates normally again (and process terminates cleanly after sim is closed)
GSX will work correctly on all subsequent sim restarts using the bat file method
Hope that kind of helps locate what the issue is
-
I'm going to have to try the update because I don't have GSX in my menu anymore. Thanks for bringing back the logos to V5, Umberto!
-
I'm seeing this as well. The Couatl process will not close on an P3DV4.5 restart. If I force it to close and restart, the update with the batch file works as published.
Scott
-
Let's just hope they fix this quickly...
-
I have the same problem as anyone else...
After looking at the sim it seems that when you restart the sim after shutdown, and go to add ons it reverts to trial mode which could be an issue.
Update to the lastest version, works and is active, if you shut down then reload, it reverts to trial mode.
Any suggestions?
-
We had ANOTHER update ( though it hasn't been listed in the release notes yet ) yesterday so, even if you updated the 8th, it doesn't mean you have the latest version so, please, try again.
The difference is this new update will AUTOMATICALLY clear the C:\ProgramData\Virtuali\Couatl folder at each restart, something you HAD to do manually at each start in the first version of the fix ( or using a batch file, as suggested in previous posts )
This means:
- If you tried the first version of the 8th fix, and you didn't clear the folder before each start, it was expected to not work on a 2nd launch because, the first version of the fix only fixed a restart in-game, not the first start, you still had to clear the cache manually.
- If you run the FSDT Live Update again, you will get another updated that will clear the cache for you automatically at each restart, not requiring to do anything or use a batch file anymore so, in theory, this should fix the problem for everyone.
-
We had ANOTHER update ( though it hasn't been listed in the release notes yet ) yesterday so, even if you updated the 8th, it doesn't mean you have the latest version so, please, try again.
The difference is this new update will AUTOMATICALLY clear the C:\ProgramData\Virtuali\Couatl folder at each restart, something you HAD to do manually at each start in the first version of the fix ( or using a batch file, as suggested in previous posts )
This means:
- If you tried the first version of the 8th fix, and you didn't clear the folder before each start, it was expected to not work on a 2nd launch because, the first version of the fix only fixed a restart in-game, not the first start, you still had to clear the cache manually.
- If you run the FSDT Live Update again, you will get another updated that will clear the cache for you automatically at each restart, not requiring to do anything or use a batch file anymore so, in theory, this should fix the problem for everyone.
This does not work for me.
Even with the latest update, the folder won't be cleared. Maybe due to the fact that the couatl64_P3D.exe process isn't closing with P3D.
But even when I terminate the process manually, opening P3D won't clear that folder and GSX will stay inoperable.
Only thing that works for me right now is to a) have the Couatl process terminated (manually) and b) run the batch file to clear the folder.
-
This does not work for me. Even with the latest update, the folder won't be cleared. Maybe due to the fact that the couatl64_P3D.exe process isn't closing with P3D. But even when I terminate the process manually, opening P3D won't clear that folder and GSX will stay inoperable.
Only thing that works for me right now is to a) have the Couatl process terminated (manually) and b) run the batch file to clear the folder.
I don't think you have the last update. Please try again now.
Note that, the updated file that clears the cache is the Addon Manager so, for P3D V5, it's the file named bglmanx65.dll.
You can check with absolute certainty if you have the latest version by checking the timestamp of the Digital Signature, it must be of today. If it's not, run the FSDT Live Update again, and check if you get the latest version. It might just be a matter of waiting until all Cloudflare nodes are replicated with the latest file so, not everyone will get it at exactly the same time.
-
We had ANOTHER update ( though it hasn't been listed in the release notes yet )
Will run this again to rule this out.
For anyone getting stuck couatl processes on sim exit, I've added the following to the bat file (must be run as Administrator)
taskkill /im couatl64_P3D.exe /F
DEL C:\ProgramData\Virtuali\Couatl /s /q
start "" "E:\Lockheed Martin\Prepar3D v5\PREPAR3D.exe"
(change the path to your v5 exe as appropriate)
Seems to more reliably ensure GSX works on sim restart
Will post back after checking LiveUpdate (again)
-
Okay, did another update since there apparently was one an hour ago and now it works!
The process now gets shut down with P3D.
The caches are rebuilt every time the sim starts.
GSX works every sim start now.
Thanks!!
-
for anyone getting stuck couatl processes on sim exit, I've added the following to the bat file (must be run as Administrator)
The batch file is no longer required with the latest update, which always clear the airport cache at each startup. We also updated the release notes to keep track of all fixes.
-
GSX works every sim start now.
Thanks!!
Reassuring to hear :)
-
Note that, the updated file that clears the cache is the Addon Manager so, for P3D V5, it's the file named bglmanx65.dll.
You can check with absolute certainty if you have the latest version by checking the timestamp of the Digital Signature, it must be of today.
I can confirm I now have this file with matching timestamp on the digital signature. Hopefully this is me sorted too. Thanks
-
Umberto I have mine working too, It is however telling me my airport cache failed but if I close P3d and delete the files.bin file it works again just incase anyone has this issue
-
If the cache regeneration failed, it's usually a problem of some .BGL, for example those with corrupted files or files with 0 length. If you have logging enabled, those are indicated in the log.
-
Hi Umberto
I'm not sure what is going wrong with this I have attached the log. Could you help me out.
Thank you
John
-
I'm not sure what is going wrong with this I have attached the log. Could you help me out.
This is your error:
The process cannot access the file because it is being used by another process: "C:\ProgramData\Virtuali/Couatl/prepar3dv5\files.bin"
Are you still using the batch file method to have it removed automatically on each start ? That's no longer needed and, in fact, might cause that problem. That, or another program, like an antivirus.
Also, try after a Windows restart, to be sure you are starting fresh.
-
Installed the Sept 7 FSDT update (P3DV5.1) and had issues similar to those reported in this thread.
Installed the Sept 9 update and now all my FSDT scenery software is running in Trial Mode. The Add-On Manager is present but the Couatl scripting engine is not running, and so the Register Serial function does not work, and of course I cannot update the scenery cache.
Prior to these events, all software worked properly.
-
Hi Umberto
thanks for your reply.
I can confirm I am not using the batch file or the other fixes I have downloaded the latest version.
I have added the exclusion to my anti virus, the folders etc so unsure why this is happening. Normally if I delete the files.bin and restart it works but now its not.
-
Just wanted to confirm that things are fine for me now (following the 9/9/21 update)
-
Installed the Sept 9 update and now all my FSDT scenery software is running in Trial Mode. The Add-On Manager is present but the Couatl scripting engine is not running, and so the Register Serial function does not work, and of course I cannot update the scenery cache.
There has been two updates today so, please be sure you run the updater again, to get the very latest version, which always automatically recreates the cache at each start.
-
I don't know if it has any relevance but after rebooting Windows I loaded up P3D at FSDT Geneva and P3D then offered me a series of messages telling me that Geneva, GSX and GSX were not installed into P3D. I accepted all of the dialogue boxes to install and create back ups of the registration and low and behold LSGG loads fine and GSX and Coulti are back in the menu. They had been previously installed.
-
P3D then offered me a series of messages telling me that Geneva, GSX and GSX were not installed into P3D.
Was the message wording:
"The product xxxx is installed but not active yet on this PC. Do you want to activate now ?". This is a message from the Addon Manager when it sees you have a serial key in the registry, but it's not active for some reason.
or was something different, like the message from P3D itself, saying a scenery is not enabled ?
-
Installed the Sept 9 update and now all my FSDT scenery software is running in Trial Mode. The Add-On Manager is present but the Couatl scripting engine is not running, and so the Register Serial function does not work, and of course I cannot update the scenery cache.
There has been two updates today so, please be sure you run the updater again, to get the very latest version, which always automatically recreates the cache at each start.
I ran FSDT Updater twice and Couatl Settings, Couatl Live Update and the GSX add-on menu items are now available. The are still a number of significant problems.
I have KORD/KJFK/KLAX/GSX2 installed with status installed and active.
None of them work correctly: scenery partially/completely missing, GSX2 just doesn't work, Couatl will not restart/rebuild.
I also get messages saying products are not activated (on P3DV5 startup) when they show as activated within the add-on manager.
I have no idea what to do.
Again, prior to the September updates all were working perfectly.
-
I have KORD/KJFK/KLAX/GSX2 installed with status installed and active.
If they are flagged as Active, it means everything is working from the software side.
None of them work correctly: scenery partially/completely missing, GSX2 just doesn't work, Couatl will not restart/rebuild.
Couatl will always restart and rebuild, if you have the latest update installed.
I also get messages saying products are not activated (on P3DV5 startup) when they show as activated within the add-on manager.
Do they showed as Activated in a PREVIOUS session, but you are getting those messages on another startup of the sim ? This is consistent with the problems which were happening on our *first* release of this update, because Couatl couldn't read an already made airport cache and in that case, it didn't closed correctly, so it didn't work on the next startup of the sim.
Even when we HAD this problem, it was always fixed by removing the airport cache before each start but now, with the current update, is no longer required, since the cache will always be rebuild in any case.
So, again, from your description of the problem, it really seems you don't have the latest update. As I've said in previous posts you can check the timestamp of digital signature of the bglmanx65.dll, to be sure you have the latest version. It must be today, because that's what refresh the cache rebuilding at each start.
-
The problem appears resolved. Two successive starts of P3DV5 with normal FSDT scenery behavior. Puzzling.
1. You were correct when you asked about active on startup and not on the next startup.
2. The timestamp on bglmanx65.dll is Sept 9 on my machine (after 4 FSDT update runs).
3. After a computer restart, the problem is fixed.
Thank you
-
2. The timestamp on bglmanx65.dll is Sept 9 on my machine (after 4 FSDT update [runs).
You mean you tried 3 times, and you were always getting the older version ? That seems to indicate a delay of your local Cloudflare node getting the latest files. There are 260+ nodes so, I guess it might take some time to propagate all changes through all nodes, surely is not immediate.
If that's the problem, getting the latest file was the thing that fixed it, because with the previous version, you had to manually remove the airport cache before each start, which was the temporary fix that was suggested in this thread, before this latest fix.
-
I am now faced with yet another error, this time when trying to amend my aircraft config or by selecting reset position its causing the error message pictured below.
I have attached the log also. Any help would be greatly appreciated I've spent all day trying to fix this doing various restarts and updates but nothing seems to work.
-
I am now faced with yet another error, this time when trying to amend my aircraft config or by selecting reset position its causing the error message pictured below.
The error you posted in your log is clearly happening in the airplane configuration editor so, unless you are having a separate different error, it's not possible THAT error could happen either by editing the airplane OR selecting "reset position" ( if you mean the reset position while services are running ). That specific error can only possibly happen while in the airplane editor.
Of course, as soon as you posted the log, I tried editing a plane by moving some doors randomly, and I can't see any errors so, please, try to describe more precisely the exact operation you did in the editor which caused that error, so I can try to replicate it.
If, instead, you are still getting errors on restart, then please post these other errors ( or describe the issue if you don't have any error ), because it's simply not possible to get that kind of editor error during a restart.
-
P3D then offered me a series of messages telling me that Geneva, GSX and GSX were not installed into P3D.
Was the message wording:
"The product xxxx is installed but not active yet on this PC. Do you want to activate now ?". This is a message from the Addon Manager when it sees you have a serial key in the registry, but it's not active for some reason.
or was something different, like the message from P3D itself, saying a scenery is not enabled ?
Hmmm. I want to say that the series of messages incorporated both types of messages but I’ve been asleep since then. 🙂. Definitely the former messages. I don’t know how they became inactive as I’d been using GSX during the afternoon.
-
chiming in to say.........the most recent update fixed the problem. thanks umberto!
-
I was hoping not to have to add to this already long post, but I am having this issue persist even after running the updater as of 5 min ago.
I own all FSDT NA airports, GSX2
Doing some trouble shooting, this is what's happening:
Start P3d - in the scenario menu:
chose a default plane, select KLAX (any gate)
no weather running or any other external addon
spawn the sim
immediately after KLAX buildings are rendered, I get an error:
The Couatl scripting engine has encountered an unrecoverable error and will be restarted. Please run live update
Here's the log output:
couatl v4.0 (build 4585)
panic log started on Fri Sep 10 20:24:24 2021
problem raised by engine or unspecified addon
{'Airport': 'KLAX', 'User Pos': (33.946942202685406, -118.40502513560536, 39.5962 m, 1.1922 m, 117.99999648425124, -0.06060376763343811, -0.0527089424431324, 0.0, 1.1475720319747926, 1.0)}
I exit from P3d, wait a few min, run Live update (have run it at least 10 times by now)
Then relaunch P3d and chose a non-FSDT airport.
P3d will spawn with no errors - all appears normal. I then try to go back to KLAX (or any other FSDT airport), get the same error. Couatl will not run.
Not sure what to do here. Checking in the Addon manager, all the FSDT addons are registered and active.
Yet I can't spawn from any FSDT airport without this error appearing.
I have not made any changes to the sim other than running Live update with the changes released recently.
Suggestions? Thanks
-
immediately after KLAX buildings are rendered, I get an error:
The Couatl scripting engine has encountered an unrecoverable error and will be restarted. Please run live update Here's the log output:
Even if you haven't posted the log file ( just the error, to get the log file, you must have Logging enabled in the GSX Settings ), I guess the cause of this is the same as already discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,25477.msg167546.html#msg167546
With a more detailed explanation about why it's happening, here:
http://www.fsdreamteam.com/forum/index.php/topic,25477.msg167624.html#msg167624
As already discussed in several other threads, we are working on an automatic fix, which will filter out custom textures found in existing profiles made for P3D V4, so no editing will be required.
-
Ok thanks - yes it looks like it's the custom texture being the culprit.
I'm using the same Cartanya profiles as one of your other posters, which then it all made sense.
Hopefully the pending change you'll introduce to the ini will allow these older profiles to be used.
-
Hopefully the pending change you'll introduce to the ini will allow these older profiles to be used.
Yes but, of course, without custom textures.