FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: airbadger on September 07, 2021, 02:24:18 pm
-
I'm encountering the following issues after today's update to GSX.
GSX will run once after running Live Update, then if I close P3D V5 and restart, GSX won't start again.
All FSDT products are in Trial Mode.
-
First, the usual suggestions:
- Be absolutely sure the antivirus is configured to exclude the WHOLE Addon Manager folder.
- Run the FSDT Live Update again.
But, from your report it seems the programs are not really running in Trial, plain and simple.
It only happens when you restart the sim ? That might be caused by not having waited enough time before the next restart, so Couatl .exe didn't had a chance to close itself. In this case, wait a bit more between restarts and, if it doesn't really close, try to close it manually with the Task manager and see if the 2nd restart works.
-
First, the usual suggestions:
- Be absolutely sure the antivirus is configured to exclude the WHOLE Addon Manager folder.
- Run the FSDT Live Update again.
But, from your report it seems the programs are not really running in Trial, plain and simple.
It only happens when you restart the sim ? That might be caused by not having waited enough time before the next restart, so Couatl .exe didn't had a chance to close itself. In this case, wait a bit more between restarts and, if it doesn't really close, try to close it manually with the Task manager and see if the 2nd restart works.
Addon Manager folder is definitely excluded.
This is still happening after running Live Updater a 2nd time.
Addon Manager in P3D says, "Product Installed, in TRIAL mode" for all FSDT products. If I spawn in at a FSDT airport like KLAX, the airport is missing like when trial mode expires.
-
Addon Manager in P3D says, "Product Installed, in TRIAL mode" for all FSDT products. If I spawn in at a FSDT airport like KLAX, the airport is missing like when trial mode expires.
Don't be mislead by the Addon Manager saying a product is in Trial. The Addon Manager doesn't know anything if a product is in Trial or not, it need to ask Couatl so, if Couatl.exe is not running for any reason, it will always say "Trial"
When a scenery is REALLY in Trial, it will work for 5 minutes and *then* it will expire. If it's GSX, it will work normally, but only at the FSDT airports or the 3 Trial airports. That's Trial. Yours is not really "trial" but is "Couatl not started"
As I've said, that might be caused by not having waited enough time before the next restart, so Couatl .exe didn't had a chance to close itself from the last session. In this case, wait a bit more between restarts and see if it closes and if it doesn't, close it manually with the Task manager and see if the 2nd restart works.
-
Addon Manager in P3D says, "Product Installed, in TRIAL mode" for all FSDT products. If I spawn in at a FSDT airport like KLAX, the airport is missing like when trial mode expires.
Don't be mislead by the Addon Manager saying a product is in Trial. The Addon Manager doesn't know anything if a product is in Trial or not, it need to ask Couatl so, if Couatl.exe is not running for any reason, it will always say "Trial"
When a scenery is REALLY in Trial, it will work for 5 minutes and *then* it will expire. If it's GSX, it will work normally, but only at the FSDT airports or the 3 Trial airports. That's Trial. Yours is not really "trial" but is "Couatl not started"
As I've said, that might be caused by not having waited enough time before the next restart, so Couatl .exe didn't had a chance to close itself from the last session. In this case, wait a bit more between restarts and see if it closes and if it doesn't, close it manually with the Task manager and see if the 2nd restart works.
I ran Live Update again. Now I'm getting an error when starting a flight in P3D: the addon <unknown> is causing the couatl scripting... etc. etc. Log attached.
-
I ran Live Update again. Now I'm getting an error when starting a flight in P3D: the addon <unknown> is causing the couatl scripting... etc. etc. Log attached.
Ok, I can see the issue, there's a problem if you use an airplane that has no GSX configuration at all ( the F-35 doesn't have one by default ). Try to use a support airplane while we fix the problem.
-
I ran Live Update again. Now I'm getting an error when starting a flight in P3D: the addon <unknown> is causing the couatl scripting... etc. etc. Log attached.
Ok, I can see the issue, there's a problem if you use an airplane that has no GSX configuration at all ( the F-35 doesn't have one by default ). Try to use a support airplane while we fix the problem.
Ok, using the NGXu, the pop-up error is gone but GSX is still not running.
-
I ran Live Update again. Now I'm getting an error when starting a flight in P3D: the addon <unknown> is causing the couatl scripting... etc. etc. Log attached.
Ok, I can see the issue, there's a problem if you use an airplane that has no GSX configuration at all ( the F-35 doesn't have one by default ). Try to use a support airplane while we fix the problem.
Ok, using the NGXu, the pop-up error is gone but GSX is still not running.
Also, 5 minutes after closing P3D, Couatl Scripting Engine is still running in Processes and using 20-22% CPU
-
Ok, using the NGXu, the pop-up error is gone but GSX is still not running.
Because it's probably still running from the previous session, so you must terminate it manually. When you get an error, choose NO when asked to Restart Couatl after you read the error log, otherwise it will not close properly.
-
Ok, using the NGXu, the pop-up error is gone but GSX is still not running.
Because it's probably still running from the previous session, so you must terminate it manually. When you get an error, choose NO when asked to Restart Couatl after you read the error log, otherwise it will not close properly.
In this case, it's still running after I ran the NGXu and stopped getting the pop-up error from using the F35. I just tried it again and confirmed it's still running long after I close P3D.
-
In this case, it's still running after I ran the NGXu and stopped getting the pop-up error from using the F35. I just tried it again and confirmed it's still running long after I close P3D.
What's happening here is:
- it doesn't close automatically when you had an error ( like the one related F-35 ) AND you replied Yes to restart Couatl when asked. This will require closing couatl .exe manually from the Task Manager, we'll investigate this, which is not a normal situation anyway, since the errors are not supposed to happen to begin with.
- it does close automatically when the sim quits, if there are no errors.
And, we already fixed the error with the F-35 so, unless you have another error, this shouldn't happen anymore, after you run the FSDT Live Update again, to get the F-35 error fix.
-
My issue not resolved. I ran the latest update, and yes, that fixed the separate F35 issue. However, I'm still having the problem where GSX will not start. I was sure to check that all Couatl processes were ended.
If the F-35 issue is fixed, it means Couatl now starts correctly so, the problem is:
- it doesn't restart or doesn't load after a sim restart
OR
- you don't have any error with the F-35, just because it's not starting at all, so there's nothing that could generate the error ?
-
same problem for me... GSX doesnt work at all after last update. Fslabs A321 and prepar3d 4.5
-
same problem for me... GSX doesnt work at all after last update. Fslabs A321 and prepar3d 4.5
This thread has several suggestions to try if GSX doesn't start.
-
same problem for me... GSX doesnt work at all after last update. Fslabs A321 and prepar3d 4.5
This thread has several suggestions to try if GSX doesn't start.
What's the next step after we've run through all of the suggestions so far and still can't get GSX to start?
-
What's the next step after we've run through all of the suggestions so far and still can't get GSX to start?
You might try running the FSDT Live Update after a Windows restart.
-
same problem for me... GSX doesnt work at all after last update. Fslabs A321 and prepar3d 4.5
This thread has several suggestions to try if GSX doesn't start.
None of them are working..
Maybe problem is on your side, something wrong with an updater or something likr this?
-
Maybe problem is on your side, something wrong with an updater or something likr this?
There aren't any problems on our side and, as I already showed in a video, it works perfectly fine here. When we release an update, this usually happens:
- some antivirus might block the updated program (just because it's new), so the antivirus must be properly configured to exclude the Addon Manager folder.
- the day of release, not all Cloudflare nodes will get the same file at exactly the same time, it's impossible this could happen, because there are 260+ of them, which means it's possible that some users downloading from different places might not get all the updated files, and a mix-up of version will likely cause problems but, eventually, everybody should get all the proper files.
-
What's the next step after we've run through all of the suggestions so far and still can't get GSX to start?
You might try running the FSDT Live Update after a Windows restart.
Ok, done. Restarted my computer and immediately ran FSDT Live Updater, in admin mode.
Result is the same. GSX starts fine and rebuilds cache the first time starting P3D. Then, I close P3D. I wait and check to make sure no leftover couatl processes are running. I restart P3D. GSX is now missing. All I see in Add-ons is Addon Manager, Couatl settings, and Couatl Live Update.
-
I wait and check to make sure no leftover couatl processes are running. I restart P3D. GSX is now missing. All I see in Add-ons is Addon Manager, Couatl settings, and Couatl Live Update.
Assuming you are sure there are not couatl .exe processes still running when you restart the sim and still doesn't start, what if you run the FSDT Live Update again, before restarting the sim ?
-
I wait and check to make sure no leftover couatl processes are running. I restart P3D. GSX is now missing. All I see in Add-ons is Addon Manager, Couatl settings, and Couatl Live Update.
Assuming you are sure there are not couatl .exe processes still running when you restart the sim and still doesn't start, what if you run the FSDT Live Update again, before restarting the sim ?
If I run Live Update before starting the sim, GSX starts every time.
If I then CLOSE P3D and DO NOT run Live Update, GSX will NOT run the next time I start P3D.
When GSX does NOT successfuly run and I then CLOSE P3D, couatl64_p3d.exe continues running in the background and does not close itself.
Even if I END the Couatl background process, GSX does NOT start successfully the next time I run P3D.
-
If I run Live Update before starting the sim, GSX starts every time.
Check my reply here and see if this might be your case:
http://www.fsdreamteam.com/forum/index.php/topic,25479.msg167492.html#msg167492
-
If I run Live Update before starting the sim, GSX starts every time.
Check my reply here and see if this might be your case:
http://www.fsdreamteam.com/forum/index.php/topic,25479.msg167492.html#msg167492
I tried warping to an airport (JFK) with a GSX profile with LVL2 gates. I went to the menu and tried both Restart Couatl and Restart/rebuild airport cache, with no response. I have in-sim messages turned on so I can definitely see whenever it rebuilds the cache.
-
I have in-sim messages turned on so I can definitely see whenever it rebuilds the cache.
Please re-read my post again, especially the part which explains there are two caches ( airport and objects ), and there's no message telling you the object cache is ready and, if you try to start GSX before it is, it might not work.
That's why I asked, on an airport with GSX jetways, to wait for the jetways to appear, before starting GSX. Do this after starting clean, meaning after an FSDT Live Update.
Instead of running the Live Update, try to just remove this folder:
C:\ProgramData\Virtuali\Couatl
If you notice the effect is the same as running the Live Update ( fixing the start for one session ), at least we know IT IS something related to the creation of the two caches so, be sure you try to wait a bit for the jetways, so we would know if the problem is in fact trying to start GSX when the object cache is still rebuilding ( which, again, doesn't have a prompt, we are planning to add it )
-
I have in-sim messages turned on so I can definitely see whenever it rebuilds the cache.
Please re-read my post again, especially the part which explains there are two caches ( airport and objects ), and there's no message telling you the object cache is ready and, if you try to start GSX before it is, it might not work.
That's why I asked, on an airport with GSX jetways, to wait for the jetways to appear, before starting GSX. Do this after starting clean, meaning after an FSDT Live Update.
Instead of running the Live Update, try to just remove this folder:
C:\ProgramData\Virtuali\Couatl
If you notice the effect is the same as running the Live Update ( fixing the start for one session ), at least we know IT IS something related to the creation of the two caches so, be sure you try to wait a bit for the jetways, so we would know if the problem is in fact trying to start GSX when the object cache is still rebuilding ( which, again, doesn't have a prompt, we are planning to add it )
I ran the live update. Spawned in at an airport with GSX jetways. They appeared immediately - no waiting at all. I was able to open GSX menus and interact, etc.
I then closed P3D. Checked that couatl processes were definitely not running. Then I deleted C:\ProgramData\Virtuali\Couatl. I started P3D, and GSX showed up as normal. As before, the jetways were immediately available.
I then ran P3D again WITHOUT deleting C:\ProgramData\Virtuali\Couatl. This time, GSX didn't show up in the menu. I waited ~10 minutes for jetways to appear and they never did. Upon closing P3D, couatl continued to run as a background process until I manually stopped it.
Edit: I deleted the couatl folder again and GSX started fine/rebuilt the cache/etc. so the issue is definitely with whatever is going on with that folder.
-
Edit: I deleted the couatl folder again and GSX started fine/rebuilt the cache/etc. so the issue is definitely with whatever is going on with that folder
Ok, even if I cannot replicate it, at least I have some data to look into it.
-
Just noting that I have exactly the same issue as airbender.
-
Just noting that I have exactly the same issue as airbender.
Meaning it's fixed if you clear the cache manually before starting ?
-
Just noting that I have exactly the same issue as airbender.
Meaning it's fixed if you clear the cache manually before starting ?
Affirmative.
-
Affirmative.
That's good to know so, as I've said, even if I cannot replicate it, at least I have some data to look into it and guess something.
-
i have exactly the same problems!
nothing works since the update
-
nothing works since the update
Saying "nothing works" is probably the least useful comment one could offer, especially at the end of a long thread which has so many discussions and suggestions and, if you read the latest posts, it seems that, for those affected, removing the airport cache folder:
C:\ProgramData\Virtuali\Couatl
Before starting the sim, seems to solve the problem.
Please make subsequent posts on this thread ONLY if the above (TEMPORARY, until we find a fix!!) solution doesn't work.
-
Same problem here. Even if I delete the Couatl folder before start, as soon as I change aircrafts, GSX disppears from the menu and is not usable anymore.
-
Same problem here. Even if I delete the Coatl folder before start, as soon as I change aircrafts, GSX disppears from the menu and is not usable anymore.
This is known, every "normal" restart, which is any one that doesn't rebuild the cache, seems to not work ( for all affected users of course, I still cannot replicate it ) so, more than a problem of restarting, it seems a problem of loading the airport cache if it exists. I think if you start a session correctly, you can choose "Restart and rebuild cache" as many times you want, it will always work.
I still cannot replicate it but, I've seen it on an user system in a remote session. Assuming we cannot find the real reason, we might release a temporary fix ( tomorrow, since it's 00:55 here now ), that would always rebuild the cache, regardless of the restart, which would at least work as a temporary solution until we find the cause.
-
I still cannot replicate it but, I've seen it on an user system in a remote session. Assuming we cannot find the real reason, we might release a temporary fix ( tomorrow, since it's 00:55 here now ), that would always rebuild the cache, regardless of the restart, which would at least work as a temporary solution until we find the cause.
Thanks for your efforts, Umberto!
Rich
-
Same issue on my side. All prducts went into Trial Mode and GSX only shows up under Add-Ons, if I delete the cache before starting the sim.
-
Same issue on my side. All prducts went into Trial Mode and GSX only shows up under Add-Ons, if I delete the cache before starting the sim.
Already discussed and answered here:
http://www.fsdreamteam.com/forum/index.php/topic,25475.msg167604.html#msg167604
-
Hi Umberto,
I assume the changes to always refresh the cache in the FSDT Live Update have been pushed.
I did the update but I'm still having the same issue.
My /program data/virtuali folder is not regenerated when starting a new session.
I'm happy to continue with the workaround of deleting the folder with a BAT file, but I just wanted to let you know that I continue to have the same issue even after running FSDT Live Update.
-
My /program data/virtuali folder is not regenerated when starting a new session.
Have you read the linked thread I've posted just before your post ? It explains why the fix ( as indicated in the release notes as well ), only fixes RE-STARTS, which are all those cases in which you have a restart during a session. It doesn't fix the normal startup of the sim, for that you still need to clear the cache manually before each startup, and the linked thread suggest an automatic solution using a batch file.
Yes, I know it's not an ideal solution, but we wanted to fix the most annoying issues first ( airplane change, mainly ) as soon as possible, while we investigate the proper fix ( remember: I'm still unable to reproduce the problem ) and give you something usable, while we look into it.
-
Thanks - I did read that but evidently did not understand the explanation.