Announcement

Collapse

PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

Fine tuning parking spot

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Fine tuning parking spot

    When I load the 700 or 800 at a gate, usually at KMCO, it's always 2 or 3 feet off the lead in line. Is there a way to fine tune this??

    The only way I am aware of is with the slew function. But this jumps WAY to fast and far laterally. I just need to fine tune to the line so that the jetway doesn't go half way into the fuselage. 😕
    Brian Murphy FSX- 747-400 / MD-11 / MSFS DC-6/ 737-700


    #2
    This is not a PMDG issue, but either Asobo (default airports) or the developer of the airport in question. It's all about the scenery
    Mark "Crabby" Crabtree AAL311 | PHL
    I7-9700KF | 2070 Super | Honeycomb Alpha/Bravo | MFG Crosswind

    Comment


    • Murf7413
      Murf7413 commented
      Editing a comment
      Yeah... I know it is an Asobo thing, and not PMDG. In FSX it was pretty simple to make minor adjustments. But either MSFS doesn't, or I just don't know how to do minute minor adjustments. A few inches to a foot at a time, instead of several feet at a time.

    #3
    Like Mark said it's a scenery issue. There is a solution if you are using GSX though since you can define the parking position precisely in their editor. If you do that then the next time you load into the parking spot, open the GSX menu and get it to warp you to that parking spot (since it would have spawned you at the default location), this will put you at your accurately defined spot.

    Most addon airports though are pretty good with their parking spots (except you Orbx YBBN ).

    Comment


    • Murf7413
      Murf7413 commented
      Editing a comment
      The only 3rd party airport I have is Renton. There is no 3rd party add-on for KMCO (Orlando, Fl.)... actually the busiest airport in Florida and the highest tourist attraction count in Florida and among the highest in the U.S., but not important enough apparently for an airport builder such as Orbx, Fly Tampa... ect... to do a good add-on. Flightsim.to has one add- on for KMCO. but only of the B-52 park, and unfortunately that's not entirely accurate either... though the B-52 looks good. In fact our brand new Terminal C opened for business yesterday. Air Lingus and GOL were the first one to arrive and depart from the new terminal.

      I digress... anyway... I do have the GSX Ground Services PRO, but I haven't figured out how to use it to adjust anything yet. Still trying to figure out how to use the fuel truck with PMDG... LOL :-D

    #4
    I agree, most parking at stock airports is dismal, and I often have to provide a little nudge in slew to operate the jetway. I have found that by assigning a few slew axis to my Warthog joystick (translation and rotation) that then the response in slew is not as aggressive as with key commands. Another instance where I often use the slew is when starting on the runway, Asobo seems to think we start our takeoff from the touchdown zone rather than back close to the threshold or the numbers.

    For a few airports I care about, like my own KCRP, I have created a customization of the stock airport with careful attention to location of parking and jetways and this is available in flightsim.to. I am also working on Houston Hobby KHOU but that's not ready for flightsim.to yet, every single parking spot in that stock airport was numbered wrong and mislocated as well as getting the ramp taxi lines totally hosed up. Problem is, this kind of fix-up takes more hours than I'm generally in the mood to spend.
    Dan Downs KCRP
    i7-10700K 32GB 3600MHz 3080Ti

    Comment


    • Murf7413
      Murf7413 commented
      Editing a comment
      Thanks Dan!! Wish I had your knowledge to be able to do airports... just not something in my skill tool box. lol

    #5
    Originally posted by DDowns View Post
    I agree, most parking at stock airports is dismal, and I often have to provide a little nudge in slew to operate the jetway. I have found that by assigning a few slew axis to my Warthog joystick (translation and rotation) that then the response in slew is not as aggressive as with key commands. Another instance where I often use the slew is when starting on the runway, Asobo seems to think we start our takeoff from the touchdown zone rather than back close to the threshold or the numbers.

    For a few airports I care about, like my own KCRP, I have created a customization of the stock airport with careful attention to location of parking and jetways and this is available in flightsim.to. I am also working on Houston Hobby KHOU but that's not ready for flightsim.to yet, every single parking spot in that stock airport was numbered wrong and mislocated as well as getting the ramp taxi lines totally hosed up. Problem is, this kind of fix-up takes more hours than I'm generally in the mood to spend.
    Nice. I really would like to see HOU worked on.. Im interested in that. That's my WN hub!
    Jason Saucier

    Comment


      #6
      Originally posted by DDowns View Post
      I agree, most parking at stock airports is dismal, and I often have to provide a little nudge in slew to operate the jetway. I have found that by assigning a few slew axis to my Warthog joystick (translation and rotation) that then the response in slew is not as aggressive as with key commands. Another instance where I often use the slew is when starting on the runway, Asobo seems to think we start our takeoff from the touchdown zone rather than back close to the threshold or the numbers.

      For a few airports I care about, like my own KCRP, I have created a customization of the stock airport with careful attention to location of parking and jetways and this is available in flightsim.to. I am also working on Houston Hobby KHOU but that's not ready for flightsim.to yet, every single parking spot in that stock airport was numbered wrong and mislocated as well as getting the ramp taxi lines totally hosed up. Problem is, this kind of fix-up takes more hours than I'm generally in the mood to spend.
      Dan, sorry to deviate the post. I imagine you modify the parking positions using msfs SDK right?, or do u use ADE?. I tried to modify a payware airport with both and had issues with both. msfs sdk corrects everything i change (eg. remove REIL lights that most developers don't even bother to delete with airports that don't use this) but it removes some textures from apron and from runway. When tried with ADE, the modifications are not showing. Is this happening to you?.
      Sergio Naiberg

      Comment


        #7
        Originally posted by 737NG4EVER View Post

        Dan, sorry to deviate the post. I imagine you modify the parking positions using msfs SDK right?, or do u use ADE?. I tried to modify a payware airport with both and had issues with both. msfs sdk corrects everything i change (eg. remove REIL lights that most developers don't even bother to delete with airports that don't use this) but it removes some textures from apron and from runway. When tried with ADE, the modifications are not showing. Is this happening to you?.
        I'm using ADE Alpha Build 21. I literally hate the DEV mode in MSFS and only use it in duress. I'd rather manually edit the xml than go through that anguish.
        Dan Downs KCRP
        i7-10700K 32GB 3600MHz 3080Ti

        Comment


          #8
          Originally posted by DDowns View Post

          I'm using ADE Alpha Build 21. I literally hate the DEV mode in MSFS and only use it in duress. I'd rather manually edit the xml than go through that anguish.
          Yeah, using same ADE with HF5, but you didn't loose textures, for example apron ground texture numbers for gates?. Also hate msfs sdk, always CTD's
          Sergio Naiberg

          Comment


            #9
            Originally posted by 737NG4EVER View Post

            Yeah, using same ADE with HF5, but you didn't loose textures, for example apron ground texture numbers for gates?. Also hate msfs sdk, always CTD's
            You have to be sure to use the Grid option for displaying an object's properties. There is a specific xml property for displaying the gate number. I've never had a problem with it not working.
            Dan Downs KCRP
            i7-10700K 32GB 3600MHz 3080Ti

            Comment


              #10
              If it’s any comfort, in real life they can be off by a few feet at a time.

              It’s no biggie; they’re usually designed for wingspan clearance and access to ground services, as well as making sure the tail has adequate clearance to the servicelanes behind the aircraft, but there’s quite a decent amount of safety margin.

              Largest deviation I’ve ever seen was a full 3 feet off, and that was a CRJ rushing into the gate for a quick turnaround after a 3-day pairing, and the crew were eager to go home. It was a non-issue, ground crew didn’t care at all.
              Amr Diab

              - My love, the light of the eye

              Comment


                #11
                Yeah... it's not a big deal... would just like to be able to line it a bit more.
                Brian Murphy FSX- 747-400 / MD-11 / MSFS DC-6/ 737-700

                Comment


                  #12
                  Originally posted by DDowns View Post

                  You have to be sure to use the Grid option for displaying an object's properties. There is a specific xml property for displaying the gate number. I've never had a problem with it not working.
                  It is checked, some textures will not get saved to the bgl. Thanks anyway. Sorry for the post derail.
                  Sergio Naiberg

                  Comment


                    #13
                    Originally posted by Murf7413 View Post
                    When I load the 700 or 800 at a gate, usually at KMCO, it's always 2 or 3 feet off the lead in line. Is there a way to fine tune this??

                    The only way I am aware of is with the slew function. But this jumps WAY to fast and far laterally. I just need to fine tune to the line so that the jetway doesn't go half way into the fuselage. 😕
                    This app solves the problem. It's called MDAdjustAircraft. I've been using it since forever. You can adjust your aircraft perfectly (i.e.: forward, backward, rotate left and right, shift left/right, very small (finetune) movements; normal movements and huge movements), then save the position (you can save several or all gates and ramps, and perfect runway positions (the default one is rubbish if you want to start on the rwy lol)), and next time, all you have to do is open the app, load a saved position, and close the app. Here it is:

                    https://flightsim.to/file/4877/adjus...eading-lat-lon
                    Last edited by DiBarkis; 25Sep2022, 05:43.
                    Chidiebere Anyahara
                    i9-9900k; ROG Maximus XI Extreme; Kraken X62; 64GB TridentZ RGB Royal Gold; RTX 2080Ti FTW3

                    Comment


                    • Murf7413
                      Murf7413 commented
                      Editing a comment
                      Very cool... Thanks!!!

                      I have been playing in GSX this weekend... actually rather enjoying it. :-)
                  Working...
                  X