Jump to content
The simFlight Network Forums

pete_agreatguy

Members
  • Posts

    527
  • Joined

  • Days Won

    23

Posts posted by pete_agreatguy

  1. 1 hour ago, ATControl -- Joe said:

    A.  I'm not going to waste my time 'waiting' for the forum to tell me how to write my schedules.   Nor will I conduct straw polls to figure out who wants what. 

    I suggested you ask forum members. i.e. Be democratic. However, that said I understand your point of view and do appreciate your hard work that you do. My apologies if I came across strong and "selfish" - I was just frustrated and annoyed that what I was expecting from this compared to others was different lol.

    A good controller does not need to see any "color" on an airplane to control an airplane.

    It's called Tower3D for a reason ;)

    Unfortunately it takes an act of God to get Nyerges to commit to new liveries unless it's new DLC.  I asked for an LAX update over 3 months ago, was told it was in the works and never got done.  So -- if you want more liveries, complain to Nyerges and maybe things will change.

    I doubt they will listen. They never do. Look at all the bugs that aren't being fixed.

     

  2. I'd agree with subforums but a layout such as below would be recommended from me:

    Main forum = ATC Sims
    Sub forums (with other sub-forums):
    - Tower3d / 3d  Pro
    ------ Custom schedules
    ------ Feedback
    ------ Support


    - Tracon
    ------ Custom schedules
    ------ Feedback
    ------ Support


    - others ... etc
     

  3. 50 minutes ago, winsaudi said:

    ... he has written before that his schedules are a closer match to real world than the RT version from ND, and if that results in albino traffic so be it...

    No real colours for those who purchased the RC packs. Real logic there! Should implement real colours into the schedule or at least ask the forum members what they would like in a strawpoll or something.

    Fixed the 772 Korean Air. But now I got no livery for SAS940. So need to edit that one too.

     

    EDIT: For those who want to see the SAS ... Change :

    line 630 from "ARN, LAX, 333, SK, 939, 11:54, 12:00, 1, SK" to "ARN, LAX, 343, SK, 939, 11:54, 12:00, 1, SK".

    ... and ...

    line 1390 from "LAX, ARN, 333, SK, 940, 12:00, 14:48, 1, SK" to "LAX, ARN, 343, SK, 940, 12:00, 14:48, 1, SK".

    1710636033_tower3d2018-08-0420-48-42-52.thumb.jpg.52413563fc0176d0b781b7ba1766c727.jpg1610088524_tower3d2018-08-0420-44-35-91.thumb.jpg.7989b3e49aa3c3b1ea24acc2b3a15220.jpg

    • Like 1
  4. 1 minute ago, winsaudi said:

    Pete,

    I have just tested the RT default schedule and the KAL 772 is nicely in Korean blue. 

    BTW, the KAL schedule line you quote above is for the inbound flight but your screenshot shows data for the outbound flight so the relevant schedule line should be:

    LAX, ICN, 77L, KE, 274, 12:00, 15:05, 1, KE

    Wayne

    Well noticed.

    Just tested the default schedule and the livery appears fine in there ???? So what gives? Why doesn't it appear in @ATControl -- Joe 's schedule?

    562887411_tower3d2018-08-0420-25-53-27.thumb.jpg.913d61f002526f199957bed73540a9f6.jpg

  5. 23 minutes ago, ATControl -- Joe said:

    What you have quoted here are not MY issues.  

    1.  A livery missing is Nygeres issue.  You should contact them about it.

    2.  Your system not being able to recognize something you say is not my schedule issue.  

    Right for starters, every other schedule from @crbascott and others all work fine with the ALASKA callsign. That one specific one above was not working, yet other VRD and ASA Alaska callsigns were in your schedule, so it is not my system ;)

    I'll get someone else to test this because I doubt it is my system that is the issue.

    I've attached my log file so you can see for yourself. output_log.txt

  6. Hi,

    Had a few issues since the new update. This was a multiplayer session using an excellent custom schedule (Friday) from crbascott . I have included my local log file, the host log can be provided if required but it is 39MB odd. My log file is attached. If you need the host one I can upload it to cloud storage for download upon request.

    1) Aircraft landing on runway 1R taxi onto S fine but should really stop prior to G. After providing taxi to terminal commands, aircraft taxi via S > D to get to G.

    204052381_tower3d2018-07-1215-47-01-17.thumb.jpg.38118f24fe5b153e848d32a6114fcb45.jpg

    2) Pushback issues with AAY472. He was doing donuts for about 5 minutes lol:

    1911676954_tower3d2018-07-1217-09-24-22.thumb.jpg.07b52d54b0d59b3f1aae0345c0734fea.jpg

    3) Aircraft (NKS562 in this example) not holding short of runway 8L on taxiway A8 even though instructed to - note: we were using 8R for departures. We found a temp solution of getting them to hold short of taxiway A8 on taxiway B instead. @crbascott suggested this is linked with issue 5 on this thread  as mentioned by @Pdubya

    671719482_tower3d2018-07-1217-09-52-61.thumb.jpg.b747e6f3081d4a11ed29a2bdccc6d7ce.jpg

    Log file attached. HOST log file.

     

    my_output_log.txt

  7. Hi,

    Found an issue at KLGA with arrivals on runway 4 taxiing to terminal via A M. They seem to want to taxi onto taxiway B which is not what we as humans want to happen :D (DAL2665)

    The way round it at the moment is to only give taxi instructions via A (DAL886) but even this isn't enough as sometimes you want to route departures out onto B.

    Screenshots below and log attached :) Please fix.

    2002447293_tower3d2018-07-1113-31-50-33.thumb.jpg.5daeb36c7b2c3a9df96fe3387a9aa779.jpg

    45281667_tower3d2018-07-1113-32-28-11.thumb.jpg.cdf9d8c647ddb5300332b2e71a11736c.jpg

    output_log.txt

×
×
  • Create New...

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.