1
Chicago O'Hare V2 for MSFS / Re: Floating lights above runway 9C
« Last post by motleyaces on May 16, 2024, 11:35:37 pm »I still have light poles on 9C that bounces the plane off the runway.
News:
Recent Posts
2
GSX Support MSFS / CTD/freeze continues
« Last post by Gunny on May 16, 2024, 08:03:25 pm »I'm at a loss for words as I have updated the MSFS and GSX continually and still cannot complete a flight with a CTD/freeze of the program. All I am asking for is a solution to the attached event log. Thanks
3
GSX Support MSFS / Re: Pushbak Problem: Parking Brake PROSIM 738
« Last post by Captain Kevin on May 16, 2024, 04:55:03 pm »The last time Umberto was active on the forum was 38 minutes before your initial post. As he is the one who handles support here and hasn't been here, I'm not really sure what to tell you. In any event, you aren't the first person to have an issue with running the ProSim 737 with GSX, and I'm not sure why that is the case. In any event, have a look here and see if this helps:
https://www.fsdreamteam.com/forum/index.php/topic,28548.msg186353.html#msg186353
https://www.fsdreamteam.com/forum/index.php/topic,28548.msg186353.html#msg186353
4
GSX Support MSFS / Re: Pushbak Problem: Parking Brake PROSIM 738
« Last post by Alti on May 16, 2024, 03:08:47 pm »Hello here!
on FSDREAMTEM WEBSPACE I CAN READ:
To obtain support about use of the product, technical issues, report bugs and suggestions, please use the forum
But in this case come NOTHING from the Developer to help in this situation?
Bying GSXpro and the nothing comes back when the purchaser need help?
on FSDREAMTEM WEBSPACE I CAN READ:
To obtain support about use of the product, technical issues, report bugs and suggestions, please use the forum
But in this case come NOTHING from the Developer to help in this situation?
Bying GSXpro and the nothing comes back when the purchaser need help?
5
Chicago O'Hare for FSX/P3D / Re: [p3dv5.3] KORD jetways/buildings disappear and re-appear
« Last post by 19pecker67 on May 16, 2024, 11:13:24 am »Hello Umberto,
I tell you what I do with many purchased airports:
Often the sceneries don't reflect the actual usage of runways, cf. flightradar24, flightaware, etc.
1.
If the runways are parallel, but displaced, e.g. EDDB, ...
-----
T
-----
... take-offs and landings are distributed so, that the taxi time from/to the terminal is minimised.
2.
If there are more parallel runways (e.g. KLAX, KDFW), ...
-----
-----
T
-----
-----
the outer runways will be used rather for landings, the inner runways for take-offs.
3.
In more complex runway setups like KORD or EHAM, the rational described above AND wind sectors decide on which runways are used for T/O and landings.
As said, purchased sceneries often ignore this completely:
A. All parallel runways are 'open' for both; this might be fine for the KLAX example since p3d IMHO chooses the closest runway for an approaching or ready-for-taxi aircraft (AI or my 'own' plane).
B. In the EDDB example the shorter-taxi-time setup improves the flow of taxiing aircraft; the AI aircraft less block themselves waiting the first aircraft to disappear after a given time-out.
C. In more complex runway setups sometimes the 7.9° crosswind method make the runways parallel, but this works only nicely if the wind blows accordingly in the direction of the 'paralleled' runways. If the wind deviates beyond a certain degree (not sure, but I think also the wind velocity seems to play a role --- if very weak winds blow...), AI aircraft might use runways which in real life would never be used simultaneously.
I know, it is only a simulation... 8^)
Back to your question regarding C:\Program Files (x86)\Addon Manager\FsDreamTeam\KORDV2\scenery\KORD 040-090_220-270deg:
If I don't like the purchased scenery runway setup in the AFCAD file, I restrict the used runway directions for take-offs and landings, close them completely for certain wind directions, parallel them if necessary with the 7.9° crosswind runways, sometimes 'paralleling' the smaller sector like a V, sometimes 'paralleling' the obtuse angle \_, create additional folders with sectors of paralleled runway directions in its name, create a subfolder \scenery, put in the edited, compiled AFCAD file, rename the original bgl file to ...bgl.off, bind the new sceneries into the simulation, and have only one of this extra AFCAD file activated, depending on the wind 'today'.
This allows even during a flight to change the AFCAD file, if the wind direction of your destination airport has changed in the meantime
(and only if you are not too close to your destination airport; sometimes the simulation CTDs, if the airport has already been loaded. ).
Back to my original question on dis-/appearing terminals and jetways at KORD:
(a) I found a reference in the kord-V2_fsdt.ini file to the AFCAD containing folder (afcad_path = ...). So I added this reference into copied ini files and put them into my wind dependent scenery folders, and switched the original ini off.
(b) the number created alpha-india AI aircraft seems to be too high to show liveries and the KORD terminals continuously. If I reduce the number of AI aircraft, the flicker stops and all is fine.
So, thank you for your hint, which made me look into your ini file! There I had to 'correct' the afcad_path.
Thx again,
André
tl;nr...
I tell you what I do with many purchased airports:
Often the sceneries don't reflect the actual usage of runways, cf. flightradar24, flightaware, etc.
1.
If the runways are parallel, but displaced, e.g. EDDB, ...
-----
T
-----
... take-offs and landings are distributed so, that the taxi time from/to the terminal is minimised.
2.
If there are more parallel runways (e.g. KLAX, KDFW), ...
-----
-----
T
-----
-----
the outer runways will be used rather for landings, the inner runways for take-offs.
3.
In more complex runway setups like KORD or EHAM, the rational described above AND wind sectors decide on which runways are used for T/O and landings.
As said, purchased sceneries often ignore this completely:
A. All parallel runways are 'open' for both; this might be fine for the KLAX example since p3d IMHO chooses the closest runway for an approaching or ready-for-taxi aircraft (AI or my 'own' plane).
B. In the EDDB example the shorter-taxi-time setup improves the flow of taxiing aircraft; the AI aircraft less block themselves waiting the first aircraft to disappear after a given time-out.
C. In more complex runway setups sometimes the 7.9° crosswind method make the runways parallel, but this works only nicely if the wind blows accordingly in the direction of the 'paralleled' runways. If the wind deviates beyond a certain degree (not sure, but I think also the wind velocity seems to play a role --- if very weak winds blow...), AI aircraft might use runways which in real life would never be used simultaneously.
I know, it is only a simulation... 8^)
Back to your question regarding C:\Program Files (x86)\Addon Manager\FsDreamTeam\KORDV2\scenery\KORD 040-090_220-270deg:
If I don't like the purchased scenery runway setup in the AFCAD file, I restrict the used runway directions for take-offs and landings, close them completely for certain wind directions, parallel them if necessary with the 7.9° crosswind runways, sometimes 'paralleling' the smaller sector like a V, sometimes 'paralleling' the obtuse angle \_, create additional folders with sectors of paralleled runway directions in its name, create a subfolder \scenery, put in the edited, compiled AFCAD file, rename the original bgl file to ...bgl.off, bind the new sceneries into the simulation, and have only one of this extra AFCAD file activated, depending on the wind 'today'.
This allows even during a flight to change the AFCAD file, if the wind direction of your destination airport has changed in the meantime
(and only if you are not too close to your destination airport; sometimes the simulation CTDs, if the airport has already been loaded. ).
Back to my original question on dis-/appearing terminals and jetways at KORD:
(a) I found a reference in the kord-V2_fsdt.ini file to the AFCAD containing folder (afcad_path = ...). So I added this reference into copied ini files and put them into my wind dependent scenery folders, and switched the original ini off.
(b) the number created alpha-india AI aircraft seems to be too high to show liveries and the KORD terminals continuously. If I reduce the number of AI aircraft, the flicker stops and all is fine.
So, thank you for your hint, which made me look into your ini file! There I had to 'correct' the afcad_path.
Thx again,
André
tl;nr...
6
GSX Support FSX/P3D / Re: NOW GSX CRASHES AFTER BOARDING STARTS
« Last post by paullaveault on May 15, 2024, 06:29:15 pm »Found the problem, It turns out it is a airplane problem.
7
GSX Support FSX/P3D / NOW GSX CRASHES AFTER BOARDING STARTS
« Last post by paullaveault on May 15, 2024, 05:47:04 pm »GSX is crashing after boarding starts. Ran live update to no effect.
8
GSX Support MSFS / Re: Disable GSX menu pop-up upon engine shutdown
« Last post by Mr_Moss on May 15, 2024, 10:11:02 am »Understood. If this isn't GSX native behaviour then I shall investigate what's causing it & report back if I find anything for other users experiencing the same thing
Thank you
Thank you
9
GSX Support MSFS / Re: Can we make the GSX window NOT dissapear ?
« Last post by wakevortex on May 15, 2024, 09:06:13 am »Hmm thats interesting..its not popping up for me to select pushback direction..I do see it pop up occasionally other times but then get dismissed by fenix .
Maybe its because Im using the Fenix A320 with Fenix2GSX - (as I prefer it to the fenix own integration) and that is somehow preventing that popping up
Will look at that white toolbar tip you mention ..I actually use Parallel 42 Flow rather than the toolbar to open GSX, so again maybe thats interfering ...
appreciate it !
and by the way I DO see suitcases being handled in outside view..do you not?
Maybe its because Im using the Fenix A320 with Fenix2GSX - (as I prefer it to the fenix own integration) and that is somehow preventing that popping up
Will look at that white toolbar tip you mention ..I actually use Parallel 42 Flow rather than the toolbar to open GSX, so again maybe thats interfering ...
appreciate it !
and by the way I DO see suitcases being handled in outside view..do you not?
10
Chicago O'Hare V2 for P3D4 / Re: KORD is broken. Constant couatl restarts.
« Last post by bhorv67 on May 15, 2024, 06:35:59 am »did anyone ever find a fix for this?
I'm curious if there's some conflict with Drzewiecki's Chicago X - I noticed there's duplicate runway lights at KORD, even though in the DD installer, I deselected installer KORD because I have FSDTs.
The issue is quite annoying. Regardless of AC type, KORD jetways/couatl will restart about every 15 seconds. The only way I've managed to use the airport, is if I'm able to attach the jetways in between restarts (very quickly), the constant restarting stops.
I'm happy to post a video of the behavior if that helps.
Shame this is happening, I really like this airport (and it's my home airport).
I'm curious if there's some conflict with Drzewiecki's Chicago X - I noticed there's duplicate runway lights at KORD, even though in the DD installer, I deselected installer KORD because I have FSDTs.
The issue is quite annoying. Regardless of AC type, KORD jetways/couatl will restart about every 15 seconds. The only way I've managed to use the airport, is if I'm able to attach the jetways in between restarts (very quickly), the constant restarting stops.
I'm happy to post a video of the behavior if that helps.
Shame this is happening, I really like this airport (and it's my home airport).