PMDG 777 Door too high @ ImagineSim KATL

Home Forums Support PMDG 777 Door too high @ ImagineSim KATL

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #776
    wde12
    Participant

    Hi there,

    First off – congratulations and well done 12bpilot for SODE jetways. This is a great development and shows incredible promise. Well done!

    I am having a small problem and hope you can help. I have ImagineSim’s KATL. It is updated to the newest version. I also have downloaded SODE (latest version) and GSX. I have downloaded the GSX update and the SODE updates – specifically, the ones that allow the two engines to be compatible together (Couatl, etc.)

    I have no connection problems with SODE (when tested, everything is okay). The SODE jetways work for the PMDG 737 at every gate.

    BUT – only a handful of jetways work for the PMDG 777 @ KATL. This was typically gates F1, F2, and F5 (if I remember correctly). ALmost every other gate, including the “heavy” gates, give me a message that the 777 door is too high. I have tried reconfiguring the door parameters (through 12bpilot’s pin thread, as well as the values given in this thread: http://www.avsim.com/topic/471587-exit-1l-data/page-2

    I tried all the options in that last avsim thread. As you will see, one poster suggested the problem is ImagineSim’s bgl files. I posted this question to ImagineSim and oooooh boy, they got super defensive, offended, and pissy: https://www.facebook.com/795499297198912/photos/a.795502433865265.1073741828.795499297198912/1063783100370529/?type=3&theater

    Can anyone here PLEASE help. What seems to be the problem? Have you heard of this issue – because I know I am not alone.

    This ONLY happens at KATL.

    Thanks in advance,
    William

    #777
    12bPilot
    Keymaster

    Hi William,

    Coincidentally, I created the jetways for KATL 😉
    On some positions, the jetways are at their geometrical limits, so weren’t able to reach the door mostly due to the door being too high.
    I have now revisited the source files and tried to give the jetway legs more reach. I have compiled a new jetway package now and would be happy if you could test it with the 777.
    The zip with the files is here: http://sode.12bpilot.ch/temp/ImagineSimKATL/SODE_Jetways_KATL_03AUG16.zip

    Installation is straight-forward: Unzip the contents to C:\ProgramData\12bPilot. It might be a good idea to remove the old KATL simbojects from C:\ProgramData\12bPilot\SODE\SimObjects\ImagineSim_KATL. Just to be sure…

    Also, as of SODE version 1.3.1, SODE comes with its own (small) database of door positions and the PMDG777 are included there. And if you are using GSX, there’s also no need to fiddle around with the aircraft.cfg files anymore.

    -Jeffrey

    • This reply was modified 7 years, 9 months ago by 12bPilot.
    • This reply was modified 7 years, 9 months ago by 12bPilot.
    #781
    wde12
    Participant

    Jeffrey – outstanding news great to hear from you. I am just getting to work now (here in ATL it’s 9am). So it will be some time before I can install the package. In the meantime, THANK YOU for your prompt reply and efforts. I will keep you posted as soon as I can install. – William

    #783
    wde12
    Participant

    Jeffrey,

    Good news, the jetways appear to be working. I think I got confused as to the unzip and which folders to replace completely, as there are double jetways and on one occasion, the jetway disappeared after I activated GSX. I completely removed GSX, cleared registry, and reinstalled. The two now seem to be working together normally. I will have to go back and figure out what exactly I need to remove before (re)installing your zip.

    In the meantime, just wanted to say that when it comes to the geometric limits and your efforts to fix them as much as possible – this appears to be a success. THANK YOU.

    William

    #784
    12bPilot
    Keymaster

    Thanks for the feedback. I will then forward the files to imaginesim.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.