FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: N76055 on November 21, 2022, 08:15:15 pm
-
Couatl/GSX Loads properly, but as soon as jetways begin to move, it crashes and immediately restarts the couatl service.
This happens over and over again, eventually I get a very generic error. Disabling AI traffic fixes the issue, but previous version worked fine with AI.
couatl v4.8 (build 5086)
panic log started on Mon Nov 21 12:52:14 2022
problem raised by addon <no traceback available>
IndexError: tuple index out of range
{}
-
I have the same issue. Until FSDT finds a cure for this issue I found, for me, that disabling AI detection in the SODE Manager Platform resolves the couatl issue and allows you to run your AI aircraft. The jetways, however, will only work for your aircraft. I hope this works for you.
GRouner
-
This happens over and over again, eventually I get a very generic error. Disabling AI traffic fixes the issue, but previous version worked fine with AI.
Please enable logging and post the complete error log ( ZIPPED and Attached to a post ), because the panic log doesn't contain enough data for us to understand the problem.
-
My reports are attached.
-
My reports are attached.
Your log don't show anything wrong, other than as soon you loaded the scenery, you exited the sim. Or it really crashed ( the whole sim ) ?
-
No, P3Dv4 does not crash but cache keeps reloading every time the SODE gates begin to operate for the AI aircraft.
-
I am attaching the SODE log to see if this can explain anything...
-
Seeing similar behavior at KORD in P3dv5, couatl restarts repeatedly on it's own. This started after updating with fsdt installer 11/24.
-
Any idea why the sode AI setting would trigger the constant restarts and ultimate sim CTD? Started after the update on the 24th.
-
Open item still.
-
Umberto, can you please look into this? It's very frustrating.
GRouner
-
Are you all using P3D V4 ? I just checked with V5, and no problems even when jetways dock to AI
-
Thanks for looking at this. I did run the installer/updater today to make sure all files are current. It did require two times before no additional files were being downloaded.
Just to confirm... This is with the SODE settings AI detection set to TRUE in the SODE manager. In P3Dv5 when I load any aircraft at KORD couatl goes into a loop of resetting followed by a sim ctd after a number of couatl involuntary restarts. The objects that are triggered to reset like some term structures, jetways etc disappear and reappear like I selected the rebuild function. This continues with no change to the couatl log. It simply asks if the sim crashed no matter how many times couatl loops.
With the SODE AI detect set to false the sim works as it should, but of course there is no jetway connection to any AI aircrafts at any airport equipped with SODE jetways. I've used this feature without issue for a long time, and enjoy the extra immersion. This issue started after I updated the GSX on 11/24.
-
I have P3Dv4.
-
If I fly into KORD the airport loads, except for the jetways, and will not start looping. However if I select any services the loop begins.
-
After the most recent update, disabling the AI jetways in SODE no longer stops the cache loop at KORD. Even with all AI traffic stopped, the loop continues. The airport is no longer useable. Please help!
GRouner
-
I am also getting a constant restart and I don't know how to fix it! I have something similar to the other people in this post!
-
With the SODE AI detect set to false the sim works as it should, but of course there is no jetway connection to any AI aircrafts at any airport equipped with SODE jetways. I've used this feature without issue for a long time, and enjoy the extra immersion. This issue started after I updated the GSX on 11/24.
In my video, I show jetways that docked with AI so, clearly, I also had the SODE AI detection enabled, otherwise they wouldn't work.
-
Didn't watch the video. Your system working is irrelevant to me obviously.
For those that are facing this issue I've been able to find an alternative that is reproducible and makes my system functional.
When I load at Kord I let the loop do it's thing for the first cycle. I then select customize airport position from the GSX menu, that menu window will close by itself within 4-5 seconds of it being opened, I then select it again immediately and it will stay open. I keep it open for 15-20 seconds to be sure the loop is dead. At this point I can close the menu and all services have worked completely for me for that departure. The jetways for the AI will also function as they should. Hope this works for you until we can find a real resolution. Good luck!
I have not tried flying into Kord, but will when I have some extra time.
Don't waste your time deactivating/uninstalling/reinstall etc... It did not change anything for my system even though I removed all fsdt products and their associated folders and so forth.
-
Didn't watch the video. Your system working is irrelevant to me obviously.
It's obviously relevant to at least made you suspect you might have another problem, and that GSX in itself doesn't do that. That's the whole point of testing: NOT to say "I don't believe you", but to HELP YOU trying to find other reasons for the problem, possibly a conflict with something else.
You said yourself you used P3D V5, that's why I spent some time testing KORD in P3D V5, following your report so yes, the vide WAS relevant to you, even if you decided looking at it wasn't worth your time.
Don't waste your time deactivating/uninstalling/reinstall etc... It did not change anything for my system even though I removed all fsdt products and their associated folders and so forth
That alone would indicate the problem must be somewhere else, like an unknown conflict with another addon, or some setting.
-
What about my issue with this problem. I updated this morning with the most recent (12/5) update and the problem still exists, cache keeps looping when AI SODE attempts to dock with plane. However, now, with all AI turned off and SODE set to false on AI detection, KORD still loops cache. I have P3Dv4. I can't use this airport now because of this. Before the 12/3 update, I could at least turn off SODE for AI jetways and the looping stopped and AI planes were active. I am attaching the most recent SODE log so you can see the looping.
GRouner
-
HELP YOU
"Help" would have been you responding to why opening the airport customization window creates the predictable responses. Why might the window close on it's own the first time, and then stay open and disrupt the loop the second time restoring stability... Did you look at the sode log submitted by the other customer? Did it provide clues about some interaction? If you did, great! What can you surmise from your new understanding? Could it be simconnect/sode/couatl/fsuipc? What are the possibilities?
-
From Papacoach's suggestion (thank you!), I was able to open the "Customize airport positions" and see, for some reason, all the parking spots had been assigned jetways. Not sure why but I will have to take the blame for this. I corrected the issue and rebuilt the cache. KORD then seemed to work fine. I came back later today and went to KORD. I received a message that KORD was in trial mode. Not sure why as it showed registered. Then everything involving FSDT KORD disappeared. I looked under Add-ons and there was no couatl settings, couatl Live Update, or GSX. I shut down the program then did a ctrl/alt/del. The task manager showed couatl was running. I shut it down then restarted P3d. Same thing happened. I shut down P3d and checked the task manager again. Showed couatl was running. I shut it down then did another FSDT update. Started P3D, went to KORD, and the looping started again. I was able to get the "Customize airport positions" window open. Everything then began to work properly. I shut down P3D, waited a few minutes then checked the Task Manager. Couatl script engine was still running. I shut it down again then restarted P3D and went to KORD. The cache reloaded 5 times. I was able to open the "Customize airport positions" then closed it. Airport started functioning normally.
It seems what Papacoach reported is exactly the same that I am experiencing.
-
I shut down P3D, waited a few minutes then checked the Task Manager. Couatl script engine was still running. I shut it down again then restarted P3D and went to KORD.
Then this is the only real issue, which of course is not normal. First, just to be sure, you mean Couatl64_P3D.EXE, right ? Just to be sure you are not loading the 32 version for some reason, which might start, but it's no longer tested or supported.
If you are running the correct version, the possible reasons why Couatl wouldn't close automatically are:
- It couldn't receive the standard Simconnect "Quit" command, either because Simconnect was too busy because too many add-ons sending too many commands at the same time, or simply because the sim crashed, even silently, before it was able to send it.
- The antivirus might interfering
The cache reloaded 5 times. I was able to open the "Customize airport positions" then closed it. Airport started functioning normally.
No, the cache hasn't reloaded 5 times, you probably have seen the message being refreshed 5 times, but I assure you it loaded only once.
-
Just started up P3D at KORD this morning. Everything appears to be working. Wish I (we) knew what happened but thankful it is working now.
-
Curious about this: MsgWaitForMultipleObjects Failed with error 87
When Monitored AI is over 80ish couatl restarts itself repeatedly and records error 87 in the log. It lists AI Monitored and WaitObjects size. If the AI are less than 80 things seem to work fine. However, this is only at KORD. At kmia, katl, or similar AI Monitored can exceed 150 with no ill GSX issues.
I've changed nothing in my AIG traffic volume or models. The trouble began when I updated GSX on 11/24 with no change in subsequent updates. Maybe something in resource handling has changed in combination to recent GSX updates...
-
Curious about this: MsgWaitForMultipleObjects Failed with error 87
This is basically a catastrophic Windows error, which has nothing to do with GSX and, it's usually caused by Simconnect being so overwhelmed by too many add-ons spamming too many commands in a very short amount of time, that GSX is never called enough time to flush its queue of commands.
We haven't changed anything in the way this method works, surely not in years.
-
Hello to all, I am also having the same issues after downloading this recent update. Attached is my log. I am utilizing P3D v4.5. Thanks!
-
Hello to all, I am also having the same issues after downloading this recent update. Attached is my log. I am utilizing P3D v4.5. Thanks!
There's nothing in your log that shows any problems. Please describe exactly what is happening
-
Hello Virtuali, I am having the same issues as the other posters. With the gates reloading constantly. The only fix I have found so far is to utilize the customize airport positions and GSX will work as normal. Any insights?
-
With the gates reloading constantly.
Please clarify what do you mean with "gates reloading constantly"
-
I would load the simulator and while at the stand, the gates would initially load, then a couple of seconds later the ads would turn black, the gates would turn in weird directions, and disappear including the visual docking system. If I try to hit crtl+F12 the menu would also disappear at the same time if the gates and VDS are recycling. I only notice this when using DD KJFK. As stated before the cycling stops when I clicked on customize airport positions from the GSX menu. If I can help with a video, I’ll do so shortly.
-
gates and VDS are recycling. I only notice this when using DD KJFK.
Please clarify: have you replaced the SODE jetways that comes with the scenery with GSX ones, which can only be made by removing the XML/SDX file from the SODE folder ?
Because if you haven't, and you are using the SODE jetways that comes with the scenery, nothing of what you are reporting has anything to do with GSX, since when a scenery comes with its own SODE jetways, they are not created ( or in this case, re-created ) by GSX.
-
Virtuali, I am happy to report that I am no longer having issues with jetways recycling. I'm not sure what happened or if I did anything. Everything loads the way it's supposed to at the beginning. Thanks for the support!!
-
I am encountering the same issue as well but at LAX. It's weird when I am only approach everything is fine but when I touch down it starts to reset every 10 seconds.
Peter
-
Hi guys,
Suddenly same issue here. After change my setup everything was working as expected.
Have been flying in europe with no issues, apart ones that seems recent bugs as I posted before in another thread.
Today, after loading at KBOS, this loop of constantly reloads is happening.
Then tried to load before an european airport and was ok. Changed in the same session to KBOS, and again the loop begun.
Doing as teje724 said, editing park position (enter and exiting) and returned to normal.
Will continue to test, reporting the airports that's happening.
Prepar3d V5.3
Happy new year.
-
Hello , i am having the same type problem. I get mine during replay. I use qw,pmdg, active sky , p3dv4.5 (lastest version),GSX,GSX 2,REX WX RADAR, happens with any aircraft and any settings.Re-installed many times no change. Win 10,lastest fsuipc.navi-graph,flightbeam ksfo. When replay runs freeze's about every 30 seconds. Alan sims
-
Has anybody received an answer from FSDT Team yet about this ,frustrating !
-
Same issue here. I have it at KORD and KLAX (P3d v4.5) so far and let's hope it doesn't spread elsewhere.
-
I am having these issues again at KORD. I upgraded from P3Dv4 to P3Dv5, installing all the addons again but for V5 version. I am using the stock jetways FSDT included with the KORD program. I ran the updater for FSDT as of today, using the installer and live update. SO, again, I am disabling the SODE for AI aircraft and the cache stops refreshing and I am able to use the airport.
GRouner
-
On another topic this was said,
"In a recent update, we added a feature that will constantly check if the Simconnect connection is not replying for more than 30 seconds and in this case, it will automatically restart the Couatl engine, which sometimes fixes issues of the program being stuck because of this."
I request this "feature" become a user's choice.
-
HI all!
I have the same problem on all FSDT-airports, no other. Im running P3d 4.5
-
Had the same problem arriving at YBCG, no jetways at all but as soon as i tried to open GSX menu to select parking space i started getting the loop..
-
This has been going on since November. Please help us with this issue. I am attaching logs. My specific is KORD. The cache refreshes every time SODE attempts to dock with AI aircraft. If I disable SODE AI detection, the refreshing stops. I had the same issue with P3Dv4 at KORD. P3D does not crash, just keeps refreshing.
-
This has been going on since November. Please help us with this issue. I am attaching logs. My specific is KORD. The cache refreshes every time SODE attempts to dock with AI aircraft. If I disable SODE AI detection, the refreshing stops. I had the same issue with P3Dv4 at KORD. P3D does not crash, just keeps refreshing.
Your log shows what is happening, which is something completely abnormal: a Simconnect timeout, that is the sim stopped talking with GSX for more than 30 seconds, which is clearly a problem, since they are supposed to be in constant communication at least every second.
This will trigger an automatic restart of the Couatl program, in the hope the communication might be "unstuck" but, it should be JUST a restart, not a cache refresh, assuming with "refreshing" you really mean a cache refresh ( the "regenerating airport cache" percentage running ), and not the message "Airport cache loaded successfully", which indicates a normal restart.
If you are really seeing a cache refresh instead, it might indicate the previous cache regeneration failed, so it will try to do it again so, you need to let it complete at least once. Of course, if you are constantly changing things in the Scenery library, like enabling/disabling sceneries each flight (not really useful in P3D), you are not helping, since you are basically forcing a cache regeneration at every flight.
-
I don't enable/disable anything. I just start the sim and go. This morning I started at KORD and the cache refreshed/restarted 12 times before I gave up. Is it possible the simconnect needs to be updated? If so, where would I find this?
-
The screen does read "Airport cache loaded successfully" every time it refreshes/restarts.
-
Started up at KORD again and let it run. I believe it's on the 25th run of airport cache loaded successfully.
-
when I disable AI detection in SODE, the scenery stops cache reloading.
-
I did download Prepar3D_v5_SDK_Setup_5.3.17.28160, selected repair, but still have the same issue.
-
Well i see the problem is not fixed yet. grouner you must be frustrated.i am too . Come on GSX , get it done.. i guess it is all about MSFS now. Alan sims
-
I did download Prepar3D_v5_SDK_Setup_5.3.17.28160, selected repair, but still have the same issue
Reinstalling the P3D SDK cannot possibly have any effect on this, since the SDK only contains various documentation, code samples and 3dx max plugins, nothing to do with how the simulator works.
-
I did not know. I am trying anything to get this scenery to work properly. What do you suggest?
-
i wish i knew how to make a video of it,that is above my pay grade. i think it might would help maybe if somebody who knows how can do it.maybe that would help. i get it on replay every time i run it after my flight,it does not matter when,where,or how long my flight was. if i hit one of my key board keys as soon as i see the message come on screen (top left corner of screen),it will not pause just display the message and keep playing the replay. About every thirty 30 sec. or so after it gets close to landing on runway.I am sorry for complaining but it is just very frustrating. hope it can be fixed soon. there is something your test is not picking up. i have re-installed 4 or five times ,re-installed my O.S (WIN 10) 2 times.
Alan sims
-
There's no need to do a video. You just need to try to make some effort to be more precise in your reports.
I keep saying the term cache "refresh" or "restart" used liberally, when in fact there are two very different things so, I'll try to make it clear:
- A cache "refresh" is when you see a percentage progress, in red, saying the cache is being regenerated. This is supposed to happen ONLY after something changed in the Scenery Library OR if the previous cache regeneration failed. If the cache regeneration completes successfully, you''ll see a white message saying "Airport cache loaded successfully", which indicates GSX is ready.
- During a restart of the Couat engine, you are only supposed to see the "Airport cache loaded successfully" message, nothing else. This, of course, assuming the previous cache regeneration didn't end up with an error. If there was a problem with it, it will be ( or, at least, the program it will try to ) *regenerated* again, like in the fist point.
Now, there's the OTHER, completely different issue, of the supposed constant restart. In the current version of GSX, we are trying to detect the loss of Simconnect connection from the sim and, if there's no connection for more than 30 seconds in a row ( completely abnormal situation ), the Couatl engine will Restart automatically.
Now, what will happen during that Restart, again, depends on the airport cache status: if the last time it was completed successfully, it will be just reloaded with the "Airport cache loaded successfully", otherwise it will be regenerated.
So, do you realize there are two completely different issues here, which is why I need to know *exactly* what you are getting:
- The fact you are triggering an automatic Restart. This shouldn't normally happen under any circumstances, because it tells something very wrong with the sim is going on.
- The fact you are getting a cache regeneration ( do you ? ) during a restart, which seems to indicate another completely different problem, that is the failure to regenerate the last one.
-
You have made it perfectly clear and thank you. The only message I receive is "Airport cache loaded successfully", no percentage. So, it is a constant restart of the Couatl.
-
i get ("airport cache loaded successfully"). i can pause the replay,still get the mess.("airport cache loaded successfully") while paused,every 15 to 25,30 seconds. P3d v4.5,active sky p3d,asca,fsuipc,flightbeam ksfo,pmdg 777x are my add-ons. will happen with any aircraft.any place,any where,day or night.
-
while paused,every 15 to 25,30 seconds.
It cannot be 15 or 25 seconds. It's either 30 seconds or it's nothing because, the automatic restart can only happens if GSX loses communication with the sim for MORE than 30 seconds.
So, the real question is, why your sim stopped talking with GSX for more than 30 seconds, that I really can't understand.
-
while paused,every 15 to 25,30 seconds.
It cannot be 15 or 25 seconds. It's either 30 seconds or it's nothing because, the automatic restart can only happens if GSX loses communication with the sim for MORE than 30 seconds.
So, the real question is, why your sim stopped talking with GSX for more than 30 seconds, that I really can't understand.
because you can not see it with your tools does not mean it is not happening. On my replay the times were 85 secs. mark,62secs. 51 , 39 . as you can see these were not 30 apart. you got a problem with your code somewhere. deal with that instead of saying were not seeing what we are seeing. 2000+ people have viewed this topic , its a problem. i do not like being called a liar sir. Open your eyes. Good day . i am done with this. Great customer service. Good day.
-
because you can not see it with your tools does not mean it is not happening. On my replay the times were 85 secs. mark,62secs. 51 , 39 . as you can see these were not 30 apart. you got a problem with your code somewhere. deal with that instead of saying were not seeing what we are seeing. 2000+ people have viewed this topic , its a problem. i do not like being called a liar sir. Open your eyes. Good day . i am done with this. Great customer service. Good day.
Fact it can either happen every 30 seconds or it won't, it's not open to negotiation or discussion because, opposite of you, who cannot possibly know anything about the code, I DO know what it's causing it, which I think I already explained it several times so, again, it's 30 seconds.
Two things that might have altered your perception are:
- time acceleration in the sim. This because those 30 seconds are not real time, but sim time so, they will follow the sim time acceleration.
- the message ( which is the only thing you see ) might have not appeared when it was supposed to, because the sim message text has a queue, so even if the the restart happened exactly after 30 seconds, which is the only way it could appear, you might have been mislead thinking the restart didn't happen after regular interval.
- if you used an instant reply, it is possible it might have affected this interval, since instant reply does strange things to simconnect calls, which is what "clocks" our code.
- if you paused the sim.
When the sim is paused, we don't get any callbacks from simconnect either so, for the same above reason, our internal clock doesn't move forward so, for example, if you paused the sim for 15 seconds, and noticed a restart after 45 seconds, it's because for our code, only 30 seconds passed, since nothing was moving in our code during that time, that's of course is what allow all GSX vehicles to stop automatically when in Pause, otherwise they would still move if our time was running independently from the sim.
But that's besides the point. The point is your attitude: NOBODY ever called you "a liar", this is just wrong.
-
I have been doing some experimenting to figure out why the Couatl keeps restarting. First, I went thru KORD, adding jetways from GSX, adjusting vehicles at each parking spot, aligning all the aircraft on the parking spots, and aligning all taxi and paths so the AI aircraft are following on the centerlines, using ADE. When I initially started I had all AI aircraft on and at 50%. When in "customize airport position" in GSX, I noticed that when I selected "Y" to bring the GSX menu customization menu back up, it was very slow to respond then the Coualt keep restarting. So, I turned all the AI aircraft off. GSX performed perfectly and quickly. Once I had completed all the updating, I selected "restart Couatl and rebuild airport cache". Again, everything went fine. I then added back the AI aircraft at 50%. Couatl began it's issue of restarting. I then turned off the AI aircraft and the scenery was fine. I then started adding aircraft at 25%. Program worked fine, I then moved to 35%. Again, everything worked fine. I moved to 40%, then 45% then finally to 50%. All was working properly. I shut down P3Dv5 and restarted it at 50% traffic. It is still working properly! I have no idea why. I am curious, since there are 212 gates (I think) and it takes more than a few seconds for all the gates to load, could the program being timing out because the jetways are taking a long time to load (10 to 15 seconds) and this is causing the Couatl to react the way it was?
What I know about this kind of stuff you can put on the back of a postage stamp in 3/4 inch letters. I am just trying...
-
That's possible. For the next update, we raised the timeout to 60 seconds and, have added a couple of checks to be sure the restart is not triggered while you have the menu opened after pressing ESC, or you are in the settings, but those are things we can check.
We have no much control over the sim is just "slow" to respond, other than just raising the timeout further.
-
Thanks Umberto!
-
This is happening for me at KORD. Every 20 secs the rebuild starts. Hopefully a fix is imminent.
-
This is happening for me at KORD. Every 20 secs the rebuild starts. Hopefully a fix is imminent.
And again, what "rebuild" means ? I'll copy the part of my previous reply with a plead of trying to be accurate in your reports:
You just need to try to make some effort to be more precise in your reports.
I keep saying the term cache "refresh" or "restart" used liberally, when in fact there are two very different things so, I'll try to make it clear:
So, in your case, what is a "rebuild" ?
-
And again, what "rebuild" means ? I'll copy the part of my previous reply with a plead of trying to be accurate in your reports:
You just need to try to make some effort to be more precise in your reports.
I keep saying the term cache "refresh" or "restart" used liberally, when in fact there are two very different things so, I'll try to make it clear:
So, in your case, what is a "rebuild" ?
I think you’re being a little pedantic. It is the automated action reported by the OP which is occurring every 20 seconds. If I am in the middle of choosing a different parking position the menu disappears and a message appears in a green banner top left of the screen. It’s only visible for a few seconds so reading it is not easy.
Is that clear enough?
-
Ray,
I am not sure if what I did will help you with your issue but maybe it's worth a shot.
From my post above:
"I have been doing some experimenting to figure out why the Couatl keeps restarting. First, I went thru KORD, adding jetways from GSX, adjusting vehicles at each parking spot, aligning all the aircraft on the parking spots, and aligning all taxi and paths so the AI aircraft are following on the centerlines, using ADE. When I initially started I had all AI aircraft on and at 50%. When in "customize airport position" in GSX, I noticed that when I selected "Y" to bring the GSX menu customization menu back up, it was very slow to respond then the Couatl keep restarting. So, I turned all the AI aircraft off. GSX performed perfectly and quickly. Once I had completed all the updating, I selected "restart Couatl and rebuild airport cache". Again, everything went fine. I then added back the AI aircraft at 50%. Couatl began it's issue of restarting. I then turned off the AI aircraft and the scenery was fine. I then started adding aircraft at 25%. Program worked fine, I then moved to 35%. Again, everything worked fine. I moved to 40%, then 45% then finally to 50%. All was working properly. I shut down P3Dv5 and restarted it at 50% traffic. It is still working properly! I have no idea why."
I had suggested that due to so many jetways at KORD, the Couatl may be timing out, causing this restart, not reload, of Couatl. Umberto replied that it might be and on the next update they will extend the time limit. Until this happens, you can try what I did as far as starting with no AI present, then gradually increasing. I am attaching my AFCAD file and 3 GSX ini files for you to try. So you know, I am running P3dv5. If you are running something different I can't say if this will work. When installing these files ensure you make backups of your current in the event mine do not work. The ini files on my system are located at: C:\Users\User name\AppData\Roaming\Virtuali\GSX. The KORD file is located on my system at: C:\Program Files (x86)\Addon Manager\FsDreamTeam\KORDV2\scenery. I hope this helps!
GRouner
-
The new update out so I would try it first.
-
@grouner, thanks for your suggestion. Today was the first time in a couple of months I flew out of KORD. It might be another month or two before I do it again.
I’ll update and see what has changed. This is the first time I’ve had this problem at KORD so hopefully the update will revert to the original settings.
P3Dv5.3HF2.
-
I used to be getting the same message every 30s and now with the update pushed today it's still happening but at 60s intervals.
-
I used to be getting the same message every 30s and now with the update pushed today it's still happening but at 60s intervals.
Well, at least we know you got the latest update...however, it's not normal ( doesn't obviously happen here ), why your simulator stops responding.
Before the update, it was possible to trigger a restart if you press the ESC key and just stayed there for more than 30 seconds, but now this condition is detected as well so, the restart doesn't happen until the simulator is really running.
Checking the code again, it seems it might happen if the model cache couldn't be created, or it took longer than 60 seconds to be created, which seems to suggest a VERY slow PC with a VERY slow hard disk, or possibly antivirus interference that would make that process abnormally slow.
However, without a model cache, nothing will work basically so, I guess if this was the case, the restart wouldn't be the biggest problem, more like no objects from GSX even showing up, because if the model cache is really taking longer than 60 seconds ( shouldn't be more than 2-3 seconds ), if a restart happens in the meantime, it won't ever complete, so nothing will really work.
As usual, it's ALWAYS best to clearly indicate which simulator you use, because this is very different between FSX, P3D 4 and P3D 5.
-
Yeah, which makes it weird. I never had a problem with GSX until I updated Jan 4th and again yesterday after not running the update since July 2022. Currently have a pretty fast rig pushing 5.2 all core 9700k and an overclocked 12gb 3060 with all M.2 storage and nothing's changed on the PC since 2021ish. Running P3D v4.5 with the latest FSLABs. This did occur once with the PMDG and the Leo Md88 but haven't tried it since. Last night the restarts were about one every 3 -4 mins. If the cache didn't load properly and failed it did it repeatedly but when it did load right after a PC restart it was on the longer side of the spectrum. There's no crash log even though it's being asked.
There's no antivirus or anything that could interfere. I'm slow to update things since work.... but the only variable that's changed in the equation is the update of GSX in the last few weeks.
-
Umberto,
Sorry to resurrect an old topic but it covers my current situation with a new fast PC. Details in my sig.
P3D v5.3HF2, SimWings EGLL and FSL Concorde.
I'm running a frame rate test. To do this I have all engines running and slew up to 500ft AGL. I then press 3 on the NumPad to start a longtitudial rotation through 360 degrees. This is a test I learned from Pete Dowson many years ago as a good test of performance.
Bearing in mind I'm not positioned at any gate. I'm above the 27R entry point. I keep getting "Airport Cache Successfully Reloaded" message in the green banner around every 20 seconds.
Just prior to this there is a brief stutter when fps drops below 30. I have a 30Hz monitor with VSync enabled.
If I disable GSX from the menu the message doesn't appear and the sim retains 30fps throughout the 360 rotation.
GSX keeps loading the airport cache but I don't know why. Is it responding to Ai on the ground? I have AIG Ai at have set Ai traffic density to 100%. Without GSX enabled that can be maintained even at 100% Ai.
The stutters appear to be down to GSX rather than my P3D settings.
I appreciate this is not how you fly in P3D but it's a useful way of getting settings to a realistic level.
-
Umberto, an update. I tried the same test at 3rd party LFPG, FSDT KJFK and FSDT LAX. All very busy airports with lots of Ai. 100+ at each.
I didn't get this repeated restart issue at any of them. How strange. The fps was a constant 30 during the 360 rotation.
So I went back to Heathrow and did it again. The restart message appeared for a minute or two but then everything settled down and I get a constant 30 with 120+ Ai.
Can you offer any reason why it only happens at Heathrow but then settles down after a couple of minutes?
-
I'm reasonably sure I've found the 'culprit'.
Two settings in SODE v1.7.1 - Enable Aircraft State Triggered Auto-Docking and Enable Ai Traffic Detection were both enabled.
I've set them both to disabled and the repetition of restarts has ceased.
-
I'm reasonably sure I've found the 'culprit'.
Two settings in SODE v1.7.1 - Enable Aircraft State Triggered Auto-Docking and Enable Ai Traffic Detection were both enabled.
I've set them both to disabled and the repetition of restarts has ceased.
Yes, this worked for me as well. I do not accept this as a proper solution though, as having AI dock themselves is hugely immersive. This is a very frustration problem that so many people have and I wish the developer was more interested in solving.