Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'phoenix'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Product Support Forums
    • FSUIPC Support Pete Dowson Modules
    • MyTraffic Support Forum
    • FeelThere Support Forums
    • FS Commander Support Forum
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • Intrasystems Support Forum
    • FScene Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • FS MAGAZIN (DE)
  • simRussia
  • FSUIPC Client DLL for .NET

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. pete_agreatguy

    T3D KPHX Phoenix issues

    Had a multiplayer session a few days ago on Phoenix; and came across the following issues: Notes: Used @crbascott's custom schedule found here; however these are occuring with the default RT one as well. 1) Gate Pushback issues (aircraft pushing back incorrectly): DAL136 pushbacked in a unconventional way. Couldn't get a good screenshot myself as I was doing tower. AAL2189 appeared to pushback from the wrong gate causing issues on pushback: SWA3037 had major pushback issues, including blocking taxiways. 2) Serious issues with aircraft not exiting onto taxiway B7 when landing on runway 8. It's not a taxiway connection issue. This issue seems to be linked to landing distances of some aircraft (mainly CRJ's): ASH5954 (CR9) did not exit at B7 but again left onto A7. B8 would have been preferred if not B7: AAL1169 (B738) managed to exit at B7. Around time index 14:07:15. DAL947 (B717) managed to exit onto B7. Around time index 14:12:42. ASH5957 (CR9) did not exit at B7 but again left onto A7. B8 would have been preferred if not B7 AAL2342 (B738) managed to exit onto B7 at around 14:30:00. NOTE: I tried using both the commands "[callsign] exit at taxiway bravo 7" and "[callsign] vacate runway right onto taxiway bravo 7" with the same results. See log file below for more details: output_log.txt
  2. pete_agreatguy

    T3D KPHX Taxiway B7 not connected!

    Hi, Another bug to report at Phoenix. Taxiway B7 is not connected to the runway nor taxiway B. Evidence: Aircraft landing do not taxi onto taxiway B7. In the log file I instruct AAL634 to exit via B7 .. yet it taxi's off of the runway onto taxiway A6. output_log.txt
  3. pete_agreatguy

    T3D more KPHX Phoenix bugs

    Did a session last night with 8 and 7L active. A few bugs to report again .... LOG file attached :) 1) AAL1597 gets stuck after pushback and will not taxi to runway 8 whatever command is issued (inc. continue taxi) 2) FDX3711 will not taxi to ramp via the following route after landing ... Now taxi's via this route ... 3) FDX556 will NOT taxi to 7L via the following route output_log.txt
  4. pete_agreatguy

    T3d More issues at KPHX (Phoenix)

    Hi, More issues to report for KPHX (Phoenix)! Some maybe similar to this post. Log is attached as per usual. 1) Inbound American landed fine and began the taxi to the assigned gate. For some reason, no idea why. he got stuck and I had to delete him... 2) American outbound did a unexpected taxi across the airport terminal and gates towards no mans land ... 3) Outbound ASH5896 got stuck after pushing back. Tried several commands to get him going without luck. Had to delete him ... 4) Outbound southwest SWA3812 did a 360 twirl after line up and wait command prior to takeoff command ...
×

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.