Jump to content
The simFlight Network Forums
VenturaGuy101

Issues with KPHX (#NyergesDesign)

Recommended Posts

I'm not sure if I've seen this issue at any or the airports or not.

When you click on an arriving plane you can see their terminal highlighted. However at KPHX, after issuing a TAXI TO RAMP command some planes are actually end up going to a different terminal. I've attached a couple of screenshots. 

KPHX_Terminal_Highlight.thumb.JPG.d9d749f226734c4379f93e1ae25b3b74.JPGKPHX_Terminal_Highlight2.thumb.JPG.c09109a52e110ba4afdf0fc5a0cc3317.JPG

Share this post


Link to post
Share on other sites

Makes more sense that it is a sim engine issue and not a specific airport issue. Thanks for sharing. 

I'll create a new thread directed to FeelThere and point them to our posts.

Share this post


Link to post
Share on other sites

I found another issue with KPHX. (Might be an issue with calculating the taxi path.)

I had FDX1262 (M11/H) ready for push, so I assigned it to expect runway 7L. It returned "Unable to takeoff from this runway. The runway is too short."
So I assigned it to expect runway 8, and FDX1262 repeated the command. But nothing happened. It stood at it's parking spot closest to H forever without moving and effectively blocking another UPS857, that spawned a few minutes later. It seems like it took too long for the FDX to calculate the waypoints to runway 8, since this would have been H H4 G4 F F6 E6 T C C1 B1.
I had to delete the FDX to get the UPS moving - which then, after pushback, took a wild ride through the nothingness parallel to H directing 250°, starting at the FDX1262 gate (!), until I told it to hold and repeated the order ("UPS857 RUNWAY 7L TAXI VIA H H3 G3 F F3").

(I'd provide the logs, but the forum won't let me, since I'm a newbie, as it seems, who can only attach 20-kB files (the image alone is 1,633 kB, plus 756 kB game.log, plus 523 kB output_log.txt. It was around 19:50.)

Addition (2017/12/24 23:36 UTC):
A minor issue is aircraft landing on runway 8 that are already successfully landed behind B6 always exit at B8; none of them ever exits at B7 (which sometimes leads to a go-around for an approaching aircraft, when the two are separated 5 miles only). Or does that have a specific reason?

Edited by DeltaVII
Just an addition

Share this post


Link to post
Share on other sites
On 12/19/2017 at 4:42 PM, winsaudi said:

Craig,

I have just seen this this twice in a one hour session at KPHL.

kphl 1.jpg

kphl 2.jpg

Hi Craig,

 

Was it happened on a second screen (did you pop the radar out and moved to another screen) or it was in a single screen?

 

Thank you

 

Vic

 

Share this post


Link to post
Share on other sites
1 hour ago, FeelThere said:

Hi Craig,

 

Was it happened on a second screen (did you pop the radar out and moved to another screen) or it was in a single screen?

 

Thank you

 

Vic

 

Vic, I always have my ADIRS on a second monitor so I'm not sure if this happens on a single screen or not.

Thanks, Craig

Share this post


Link to post
Share on other sites

Vic,
I can confirm that the above issue is a multi-monitor issue only. It worked fine when using a single screen. 

Just for grins, I tried it with the ADIRS inside the main window and an ADIRS on a second screen. The ADIRS within the main screen worked fine, the ADIRS on the second screen had issues.

Thanks, Craig

    

Share this post


Link to post
Share on other sites

Thank you Craig, we verified it, unfortunately a bug. We are working on an SP now, it will be part of the fixes.

 

Vic

 

Share this post


Link to post
Share on other sites

Relating to my post from December 23, the improved wayfinding in 3.1d did the trick getting the MD-11 to runway 8 (despite only accepting the "runway 8" instruction without taxi instructions, which leads to it taking the route "sc6, south_cargo, H, H7, G7, F, F13, E13, R, B, B2" - this means it enters the runway at B2 turning left to the beginning of the runway and making a 180 - or "runway 8 via C C1 B1" leading to the route "south_cargo, H, H7, G7, F, F13, E13, R, C, C1, B1", going all around the airfield).

There are three other issues, however:

1) AAL1061 (05:27:00) requested push and start at T_e9 and said it was ready to taxi without actually being pushed and still sitting at the gate.

20180209_2337_KPHX_AAL1061-ready-without-push.png.f03a28262e2f3a2928159af5e352160f.png

2) FDX1403 (06:07:33) landed on runway 7L exiting at F9 and then didn't move an inch (with a lot of ArgumentOutOfRangeExceptions with seemingly the following aircraft in the log at 06:14:31 that span until I deleted the plane). However, from the beginning it had no-free-terminal messages in the log, if that's important. The same happened later with FDX1748 after it exited runway 7L at F8 at 07:14:22.

20180209_2337_KPHX_FDX1403-not-moving.png.2f03157ac7df9e96983b0a36a736562f.png

3) FDX428 (06:16:00) spawned at sc2, was instructed to taxi to runway 7L via H H3 G3 F F3 and then just went parallel to taxiway H in the wild starting at the first gate of that cargo area. When it went into the gravel behind the end of H, I stopped it, issued another taxi instruction at 06:20:32 via H H3 G3 F F3 and it calculated the route 25L, H1, H, H3, G3, F, F3.
I want to point out that I am in no way responsible for what the route looks like !

20180209_2337_KPHX_FDX428-running-wild1.thumb.png.bc0b995406d1aa6b924bf95d05336ac9.png

20180209_2337_KPHX_FDX428-running-wild3.thumb.png.6aadbef3234fa347c06dd36fdfcc74de.png

20180209_2337_KPHX_FDX428-running-wild4.png.a8c086a5ab6da87661854727d973fb71.png

(Again, I had to shorten the log for size restriction, including repetitive Exception messages, since the already shortened log file with all messages inside would have been 9.5 MB. But if you need it, I still have the full log file and I could email it to you, if you provide me an address.)

20180209_2337_KPHX_aal-fdx_shortened_game.log

Share this post


Link to post
Share on other sites
13 hours ago, DeltaVII said:

(Again, I had to shorten the log for size restriction, including repetitive Exception messages, since the already shortened log file with all messages inside would have been 9.5 MB. But if you need it, I still have the full log file and I could email it to you, if you provide me an address.)

If you have a zip utility, you can zip the log file and it will create a much smaller file. I recreated your session and my log file was over 5 MB. My zip file was only 74 KB.

Share this post


Link to post
Share on other sites
On 1/12/2018 at 1:31 AM, FeelThere said:

Thank you Craig, we verified it, unfortunately a bug. We are working on an SP now, it will be part of the fixes.

 

Vic

 

Please don't forget about the red center light problem for the SP.

Share this post


Link to post
Share on other sites
34 minutes ago, Sky King said:

Please don't forget about the red center light problem for the SP.

Vic was replying to a different issue - ADIRS highlighting using a second monitor. 

The red lights are an "airport issue"  which belongs to Nyerges. 

Share this post


Link to post
Share on other sites
On 10.2.2018 at 5:55 PM, crbascott said:

If you have a zip utility, you can zip the log file and it will create a much smaller file. I recreated your session and my log file was over 5 MB. My zip file was only 74 KB.

I know. But I don't like to distribute zip files, just as much as I don't like opening zip files from sources I don't know. They have been abused for malware way too often, and I don't want to encourage people to open zip files from a source they don't know (which is me)...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.