FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: racekarts2 on August 20, 2022, 09:15:42 pm
-
After running the latest update GSX has stopped working with KDEN (Flightbeam). When I attempt to activate it I receive the message screen asking me to "select parking facility". I scroll past the runways to available parking places and I am offered one at concourse B gate 16. I tried selecting that gate and warp me there and try to activate it again. I then get the audio message "This parking is isolated" followed by "no ground services available".
I have tried uninstalling GSX and KDEN and reloading them both and continue to have the same issue.
I have loaded several other Add On airports both FSDT & Flightbeam and GSX is working correctly.
It is the same for me with both P3d V4 & V5.
Can you please help me out?
Thank you.
-
Try this installer, it's not MSFS-specific, it's just an offline copy of the files you were *supposed* to get from the servers:
http://www.fsdreamteam.com/forum/index.php/topic,26480.msg175191.html#msg175191
Before we can look into possible issues, we need to be sure you get the right files.
-
Hello Umberto, thank you for responding. I downloaded and ran the Addon-Manager that you provided the link for.
I loaded up P3d v5 and then loaded up KDEN.
There was no change it is still not working with KDEN.
What would you like me to do next or what information can I provide you to help assist?
-
+1 KDEN is not working, GSX does not recognise the gates, only 1 is available.
Any help would be appreciated.
-
For Flightbeam KDEN, as with KSFO and KIAD, you have to remove the kxxx-flightbeam Config file from the scenery folder for each airport.
-
Thank you very much that seemed to do the trick and everything seems to be working now.
-
Hey guys.
I have tried the above fix in P3D V4 and it seems to work with KSFO, but does not work with my KDEN and KIAD sceneries. I deleted the .ini out of the respective FlightBeam folders.
The only way to even get the Control menu to appear in my sim for those two sceneries, I have to delete the other airport .ini in the Virtuali GSX folder under Users/Program Data. Otherwise, it just says my parking is isloated just like when the .ini was in the FlightBeam folder.
Doing so, gives me the option to select GSX services and as soon as I request a jetway or any other service, it just locks out the Control Menu. It doesn't even get to the point of asking which airline I would like to use.
I've worked several hours to try and remedy the situation. Any help would be great. I have also attached my Couatl File to see if that will help.
Thank you all and I appreciate anyone's help/advice.
-
For Flightbeam KDEN, as with KSFO and KIAD, you have to remove the kxxx-flightbeam Config file from the scenery folder for each airport.
You are kidding me. How do I remove the config file from the scenery folder for KDEN for flight beam?
Is this now how this product is being supported? the users have to go out and fix applications and files on their SIM?
Disappointed long time customer.
Joe
-
Is this now how this product is being supported? the users have to go out and fix applications and files on their SIM?
And why, a suggestion from another user, has anything to do with "product support" ?
Nobody from FSDT has suggested you are supposed to that, we are obviously looking at the real causes of the problem and we'll fix that but, if another user suggested you a TEMPORARY WORKAROUND, it's up to you to use it or not, without this would have anything to do with the "level of support".
-
Is this now how this product is being supported? the users have to go out and fix applications and files on their SIM?
And why, a suggestion from another user, has anything to do with "product support" ?
Nobody from FSDT has suggested you are supposed to that, we are obviously looking at the real causes of the problem and we'll fix that but, if another user suggested you a TEMPORARY WORKAROUND, it's up to you to use it or not, without this would have anything to do with the "level of support".
Thank you, point taken. I’m just curious how long we will have to wait for a fix to some Payware airports like flightbeam’s KDEN. I have always flown with your product since the day it came out. I’m just frustrated at the moment. I really do appreciate you reaching out to us.
Joe
-
This is beyond acceptable, I want my prior working product back. This update has done nothing but put my system on its knees. This has been over a week now. After years with your product you really s&^&*%d with the pooch. It is not reading the KDEN.ini with GSX PERIOD . .. more that frustrated. Sorry but this mistake has taken days and it is not fixed.
-
This is beyond acceptable, I want my prior working product back. This update has done nothing but put my system on its knees. This has been over a week now. After years with your product you really s&^&*%d with the pooch. It is not reading the KDEN.ini with GSX PERIOD . .. more that frustrated. Sorry but this mistake has taken days and it is not fixed.
I said multiple times there are surely issues with airport customization and we are aware of them so, what is the point to remark it AGAIN ? Do you think posting another message and forcing me to reply would SPEED UP in any want the problem eventual resolution ?
-
I said multiple times there are surely issues with airport customization and we are aware of them so, what is the point to remark it AGAIN ? Do you think posting another message and forcing me to reply would SPEED UP in any want the problem eventual resolution ?
@virtuali, Umberto, I may have come across something that may help here but I want to address this specifically to you.
On my machine I noticed that the character encoding of the add-on.cfg files in
C:\ProgramData\Lockheed Martin\Prepar3D v5
C:\Users\USERID\AppData\Roaming\Lockheed Martin\Prepar3D v5
are incorrectly set in UTF-8 instead of UCS-2 LE BOM as they should be. Changing this fixed KDEN, KIAD and might work for other sceneries as well.
-
I have the same problem on P3D v4,5 with KSFO, KDEN and KIAD. Question: will FSDT post a solution for that problem? Everything was working fine for me before the last update.
-
I Have the exact same issue at the same airports. I Have used GSX a long time, and it has worked well. This issue is frustrating. I would appreciate a fix as soon as possible, This latest update really seemed to make things worse.
Thank You
-
Hello,
At KDEN and KSFO there is only 1 available spot for parking. All the jetways are there and GSX sees all the runways but there is only have one spot available.
-
Please ZIP the .INI file here and Attach it to a post:
S:\Lockheed Martin\Prepar3D v5\Flightbeam\Flightbeam - KDEN\scenery\kden-flightbeam.ini
-
Sure thing
Thanks,
-
If someone could help. I landed at KIAD today. There was only one stand available to park. Literally no others listed. The jet ways are all still visible but no options for parking with GSX. I’m fairly certain it’s something I’ve done. If anyone can help. I tried uninstalling and reinstalling the airport. No joy.
P3D 4.5
Thanks in advance
Ryan
-
Please run the FSDT Live Update now, because we found an issue that resulted in an airport custom profile not being loaded.
-
I am using P3dv5.3 and Flightbeam KDEN. Today I updated my GSX (as mentioned in P3d) and now I have issues. I am unable to park in C (only A and B. When parked in A & B, i receive the message the space is too small and services are not available.
-
Getting the exact same thing with Flightbeam KIAD. This sas after FSDT prompted me to do a live update today.
-
Please run the FSDT Live Update now, because we found an issue that resulted in an airport custom profile not being loaded.
-
Still getting the same after running live update.
-
Still getting the same after running live update.
Your log doesn't indicate a problem of not having loaded the correct .INI file, so this update won't change anything, since it fixed just that.
Please clarify exactly which problem you have, because I don't see any errors in your log.
-
Still getting the same after running live update.
Your log doesn't indicate a problem of not having loaded the correct .INI file, so this update won't change anything, since it fixed just that.
Please clarify exactly which problem you have, because I don't see any errors in your log.
Still only getting one parking spot available at both flightbeams's KSFO and KDEN. Please let me know what I can attach to help.
-
Still only getting one parking spot available at both flightbeams's KSFO and KDEN. Please let me know what I can attach to help.
- your Couatl.log starting up at that airport
- the GSX .INI file for that airport.
-
- your Couatl.log starting up at that airport
- the GSX .INI file for that airport.
Here you go
-
Ah so it’s not me lol. Phew. No worries. As long as you guys are aware. I’ll await a fix. Thank you. Let me know if you need to see any of my logs etc
-
Yes, I can reproduce the problem, is surely caused by something the .INI, we are looking at it.
-
Thank you
-
Im not sure what the update did. I now have no GSX options. Once p3d is loaded there are no options available now other than Disable in the GSX menu. Even that does not work. I am baffled
-
Check if this applies to you:
https://www.fsdreamteam.com/forum/index.php/topic,27475.msg179924.html#msg179924
Running the updater will always clear the model cache and, for a reason still unknown, is taking longer than normal on P3D 4, causing a timeout that stops the program, try the solutions explained there
-
I am experiencing the same issue and I tried the solution from the provided link with no luck. The contents of the log file is included below for reference. I am running GSX in Prepar3D v4.5, Windows 11 Home.
Also tried running the offline installer followed by the Live Update, several times (last tried 1730 GMT), prior to running the steps indicated. No change - the error still occurs and no GSX menu options are functional.
Just to confirm - by "default airport", does this mean an airport for which custom scenery hasn't been installed? I tried KMIA and KPHL, using default Prepar3D scenery, but saw no jetways present. Are there certain airports which would work best for the workaround indicated in the link?
Thanks for any further advice/suggestions! Contents of log file below.
- Bob
couatl v3.2 (build 4792)
panic log started on Tue Sep 6 14:02:44 2022
problem raised by addon <unknown>
Traceback (most recent call last):
File ".\common\modelCustomization.py", line 949, in setJetwayAirlineCode
File ".\common\modelCustomization.py", line 993, in getModelForCouatlType
File ".\common\modelCustomization.py", line 962, in getModelsForCouatlType
File ".\common\criticalsection.py", line 23, in _synchronized
File ".\common\modelCustomization.py", line 763, in _cache
File ".\common\modelCustomization.py", line 832, in _loadCacheFromPath
File ".\common\modelCustomization.py", line 927, in _loadLiveriesForModel
RuntimeError: this tasklet is taking too much time to execute
{'Airport': 'KMIA', 'User Pos': (25.797924034401852, -80.2744657536788, 5.40335 m, 2.96535 m, 131.4299909503431, 0.01497578527778387, -0.001745329238474369, 0.0, 2.621280116271973, 1.0)}
View changed to Spot
View changed to Locked Spot
View changed to FlyBy
View changed to Top-Down
Connection with Prepar3D v4 lost (has it crashed?)
disconnected from SimConnect.
-
Umberto, will give it a go. Fingers crossed
Thank you
-
Buddy, I tried the fixes as suggested multiple times with no success. It appears that GSX and Courtl resets are not working.
I need a few days away from the sim anyway. Hopefully there will be a fix in the next few days.
I know you guys are working hard to find a fix and am certain you will.
From reading a few of these posts it would appear that some others need to take a break too 😬.
Will keep a look out.
Ryan
-
RuntimeError: this tasklet is taking too much time to execute
Yes, you have the problem I discussed in my previous post:
Your problem is caused by a timing error, the creation of the model cache is taking too long, we don't understand what's causing this, because P3D4 should have the smallest model cache of all, since it has far less model variations due to having Render to Texture available.
The problem seems to happen randomly, the only solution I found for the time being, is selecting "Restart Rebuild the airport cache" again, until it works.
Go to a default airport where GSX has replaced the default jetways and choose "Restart Rebuild the airport cache", and pay attention when the jetways come up. They might take even 20-30 seconds or even more, if they don't show up, it's likely you got that error again, so you need to try that option again, until it works.
-
Umberto, having run Live Update this morning I positioned to KDEN and have the same problem. Only one parking position available - Concourse B Gate 16 and when I position there I hear a warning about no facilities available.
I have renamed my custom ini in appdata\virtuali\GSX and reloaded Couatl with index build. The AFCAD in use is KDEN.BGL. Opening that with ADE and running Find Faults lists multiple issues including duplicate parking positions and altitude issues. I know this is a FlightBeam airport, not FSDT but having located to KORD the isolated parking problemhas been resolved.
Using the Flightbeam utility it shows my version is the latest. If you have this airport you should be able to replicate the problem. I'm running P3Dv5.3 HF2.
-
I already replied in several threads: there's still a problem with some .INI files which I can replicate, but I still can't understand why it's happening.
This is unrelated to my previous reply, which I added because the user posted a log with a completely different issues that happens only on P3D4 so, even if he posted in the wrong thread, I wanted to help anyway.
-
I already replied in several threads: there's still a problem with some .INI files which I can replicate, but I still can't understand why it's happening.
This is unrelated to my previous reply, which I added because the user posted a log with a completely different issues that happens only on P3D4 so, even if he posted in the wrong thread, I wanted to help anyway.
Understood. I'm checking my other FB airports to see if there's any problem with those. More later...
-
I have the following Flightbeam airports... KIAD, KMSP, KPHX, KSFO, LFBO, NZAA and NZWN.
KIAD and KSFO have the same problem as KDEN - only one parking position available. The rest are fine.
Looking at the AFCAD for KIAD and KSFO they're not clean by any means but they did not have this one parking position issue on earlier builds. Not much more I can add really. Good luck trying to find the problem.
-
I already replied in several threads: there's still a problem with some .INI files which I can replicate, but I still can't understand why it's happening.
Looks like it has something to do with the missing "parkingsystem = xx" entries in the ini file.
Flightbeam KDEN:
- In the default ini none of the entries has the "parkingsystem = xx" entries.
- When loading KDEN without having a custom ini in '%APPDATA\virtuali", Gate 16 is the only available parking.
- I then customized that parking position (actually not changing anything, but activating/deacticvating a checkbox, to 'activate' the apply button, and let GSX save the custom ini file in in '%APPDATA\virtuali". => The custom ini file contains now the "parkingsystem = " entry for gate 16.
- Quit P3D, and restart P3D at KDEN, now with the custom ini file available.
- Now, not only Gate 16 is available, but also gate 18.
I assume that adding the "parkingsystem = " entry to gate 18 as well, will make another gate available.
It's like with FSDT LSGG => adding the 'parkingsystem = xx' entry, resolves the 'parking is isolated' issue.
-
We found the problem with .INI files, and it's fixed with the current Live Update.
-
We found the problem with .INI files, and it's fixed with the current Live Update.
Well done. What was it please?
-
Well done. What was it please?
It was related to parking systems.
We realized having parking systems in the .INI as numbers wasn't a very good idea, because it restricted the ability to add new types in an ordered manner, so we switched to storing their names instead.
Obviously, we thought about not breaking existing profiles so, if an old .INI file with numbers is found, it will be translated to the new names system automatically so, in this case, the translation routine didn't work if there were *no* parking systems in the .INI file but, since we try to manage all possible errors, the problem was hidden by the error handling, so you didn't see any errors, but it resulted in the parking being ignored.
-
Amazing! Thank you. Still looks like a few grumpy people on here need to have a few days off of their computers lol
-
Amazing! Thank you. Still looks like a few grumpy people on here need to have a few days off of there computers lol
The worse is hearing people complaining about "we don't care about P3D users anymore", when we put so much work trying to have a (mostly) common code that runs with both simulators, which is the ONLY thing that would allow us to continue to release updates for P3D for the foreseeable future.
It we really wanted to drop P3D, we would just "frozen" the code in March, release one last full update, and that's it, future updates, MSFS only.
-
It was related to parking systems.
We realized having parking systems in the .INI as numbers wasn't a very good idea, because it restricted the ability to add new types in an ordered manner, so we switched to storing their names instead.
Obviously, we thought about not breaking existing profiles so, if an old .INI file with numbers is found, it will be translated to the new names system automatically so, in this case, the translation routine didn't work if there were *no* parking systems in the .INI file but, since we try to manage all possible errors, the problem was hidden by the error handling, so you didn't see any errors, but it resulted in the parking being ignored.
Thanks. I’m guessing this doesn’t impact on user’s custom ini files in roaming\virtuali\GSX since I was able to select from many gates where that file was used. The Flightbeam airports must have been different for KSFO, KIAD and KDEN.
It’s good it’s fixed and a huge relief for you and your team. I’m relieved you haven’t drawn a line on P3D because it’s still used by many of us. :)
-
We found the problem with .INI files, and it's fixed with the current Live Update.
Great! Thanks a lot, Umberto!
-
Amazing! Thank you. Still looks like a few grumpy people on here need to have a few days off of there computers lol
The worse is hearing people complaining about "we don't care about P3D users anymore", when we put so much work trying to have a (mostly) common code that runs with both simulators, which is the ONLY thing that would allow us to continue to release updates for P3D for the foreseeable future.
It we really wanted to drop P3D, we would just "frozen" the code in March, release one last full update, and that's it, future updates, MSFS only.
Agreed and sorry you get people like that. It’s a complex business. As far as I’m aware this has been the first major issue with GSX and you had it solved within 48 hours. I also don’t remember you ever asking for further payments for all your regular updates and I’ve been using GSX since nearly the beginning. Thank you for this product and the hard work bud.
-
I also have a problem now with Flightbeam KDEN and GSX Level 2. Last week I had to do a complete reinstall of P3d v4.5 and everything associated with it. I started everything from scratch with a fresh new simulator.
I have the latest GSX L2 version and SODE v 1.7.1 installed.
When I activate jetway services, for example gate B86, the simulator changes to external camera view and then the simulator resets to my default start up airport. When I uninstalled KDEN the default jetways work and everything is normal.
I never had a problem with Flightbeam and GSX before my reinstall of P3dD.
Any help is appreciated.
Jeff