I like the feature of FSX's moving gates (or airways or whatever)But when they start to connect they always end up too far to the left or something....Anyone know if i can edit the aircraft.cfg or anything to fix it. also, anyone knows how to make them work with 3rd party aircraft?(I imported PSS airbus and it works like a charm, all i need is airgates!)ThanksTruls

>I like the feature of FSX's moving gates (or airways or>whatever)>>But when they start to connect they always end up too far to>the left or something....>Anyone know if i can edit the aircraft.cfg or anything to fix>it. also, anyone knows how to make them work with 3rd party>aircraft?>>(I imported PSS airbus and it works like a charm, all i need>is airgates!)>>Thanks>>TrulsHere's the applicable section of the aircraft.cfg file for thedefault B737-800 that allows the various "features" to work...jetways,baggage loader ):[exits]number_of_exits = 2exit.0 = 0.4, 36.6, -5.0, 3.0, 0 //openclose rate percent per second, longitudinal, lateral, vertical positions from datum (feet), type (0=Main 1=Cargo 2=Emergency)exit.1 = 0.4, -38.5, 4.5, -3.0, 1 //openclose rate percent per second, longitudinal, lateral, vertical positions from datum (feet), type (0=Main 1=Cargo 2=Emergency)exit.2 = 0.4, 33.5, 3.5, -4.0, 2 //openclose rate percent per second, longitudinal, lateral, vertical positions from datum (feet), type (0=Main 1=Cargo 2=Emergency)You need to add a similar section to your addon aircrafts cfg fileand change the co-ordinates accordingly.Knowing just WHAT those co-ordinates are could pose a challenge.One rather tedious method might be to temporarily change the "eyepoint" until you are at the location of the doors and notethose settings for this section. Other than that, you could just "guesstimate" using the pilotsevepoint position as a reference or the gear ( contact point list ) or the engine locations as a starting point.On similar models you can then just copy the approriate sections,assuming they use the same "datum". ( compare the contact pointlists as to gear location to see if they are similar )Perhaps some of the modelers here have a better method of determiningthe exit locations. Paul

Here's a method I have just been using to correctlyspecify the exits on some of my aircraft.I simply involves adding a "test light", or lights,to the aircraft.cfg and using SPOT view.Look at the light you added and adjust it's postion using an extimate. I generally look at one of the exitdoors and assume it to be about 3' wide for purposesof scaling.If you use 2 test lights, 1 white, 1 res, then you can zero in on the correct location a bit faster :)When you make a change to the cfg file just go tothe menu bar and select "Select Aircraft"...clickon the same aircraft and "OK". This will reload theaircraft.cfg file with your new settings. Once you have the test light located at the exit,just transfer those coordinates directly to the[Exits] specification.Here's a section of one of my cfg's with the test light added:[LIGHTS]light.0 = 3, -52.22,-103.52, 11.38, fx_navredh ,light.1 = 3, -52.22, 103.52, 11.38, fx_navgreh ,light.2 = 3, -54.34,-103.64, 11.38, fx_navwhih ,light.3 = 3, -54.34, 103.64, 11.38, fx_navwhih ,light.4 = 3,-139.00, 0.00, 8.42, fx_navwhih ,light.5 = 2, -51.00,-103.40, 11.38, fx_strobeh ,light.6 = 2, -51.00, 103.40, 11.38, fx_strobeh ,light.7 = 1, -5.00, 0.00, -6.25, fx_beaconb ,light.8 = 1, 22.00, 0.00, 18.30, fx_beaconh ,light.9 = 4, 93.21, 0.00, 8.75, fx_vclighth ,light.10 = 5, 18, 20.0, -2.0, RNLE2,light.11 = 5, 18, -20.0, -2.0, RNLE2,light.12 = 6, 80.0, 0.00, -11.00, RNLE2,light.13 = 2, 69.30, -10.5, 7.88 , fx_strobeh , // test lights to locate exitslight.14 = 3, 52.22, -12.52, 0.0, fx_navredh , [exits] // 777-300number_of_exits = 2exit.0 = 0.4, 69.30, -10.5, 7.88,0 exit.1 = 0.4, -69.0, 11.0, 0.5, 1 //openclose rate %/sec, longitudinal, lateral, vertical positions from datum (feet),type(0=Main 1=Cargo 2=Emergency)The red light above would show too far aft and too low and justoutside the fuselage. The white light is in the correct position.And here's the applicable contact point section that I useto get an initial estimate of the location of the main exit.The first entry is the nose gear position. It's 87.42' forward ofthe datum, on the centerline and 17.70 feet below the datum.[contact_points]point.0=1, 87.42, 0.00, -17.70, 1181.1, 0, 4.521, 90.0, 1.00, 2.5, 0.7235, 4.0, 4.0, 0, 270.0, 270.0point.1=1, -19.50, -12.00, -18.50, 1574.8, 1, 4.521, 0.0, 1.91, 2.5, 0.7470, 6.9, 6.9, 2, 270.0, 270.0point.2=1, -19.50, 12.00, -18.50, 1574.8, 2, 4.521, 0.0, 1.91, 2.5, 0.7470, 7.1, 7.1, 3, 270.0, 270.0Of course, remove the test lights once you find the exit positions.For AI aircraft in FSX, you'll need to just add, temporarily,any panel folder so that you can select that aircraft to "fly".Then just go to spot view and proceeed as with a flyable aircraft.Hope this is clear...and helps... Paul

Umm......Isn't there any "easy" ways like in aerosoft's AES it is a program to tell it where the exits are... you can just move it with the arrow keys until it is in the correct position....

>Umm......>>>Isn't there any "easy" ways like in aerosoft's AES it is a>program to tell it where the exits are... you can just move it>with the arrow keys until it is in the correct position....Actually, IF you have the Deluxe Edition and IF you install the SDK......THEN you will have access to the marvelous, new tool known as the FX Tool.Using the FX Tool, it is a simple matter to display a "crosshair" which indicates the x,y,z coordinates. You can then load up any .fx file (such as a red, white or green nav light) and have it displayed wherever the "crosshair" is located.Using the x,y,z coordinate boxes or spinners, you can quickly "move" the crosshair-light to wherever it needs to be while in spot view, without having to "reload the aircraft" at all... ;)

-SNIP->...THEN you will have access to the marvelous, new tool>known as the FX Tool.>>Using the FX Tool, it is a simple matter to display a>"crosshair" which indicates the x,y,z coordinates. You can>then load up any .fx file (such as a red, white or green nav>light) and have it displayed wherever the "crosshair" is>located.>>Using the x,y,z coordinate boxes or spinners, you can quickly>"move" the crosshair-light to wherever it needs to be while>in spot view, without having to "reload the aircraft" at>all... ;) Thanks Fr. Bill. I thought you might pop into this thread. I've not tried playing around with that new tool as yet but I certainly will now! My question, as it relates to the placing of the exits referenced to the datum, does the FX tool place the moved effect data into the aircraft.cfg file? If so, this will certainly save me LOADS of time creating those -Exits- additions for my myriad AI aircaft! Paul - will be busy tweaking today, methinks! :)

> My question, as it relates to the placing of the exits > referenced to the datum, does the FX tool place the moved> effect data into the aircraft.cfg file? If so, this will> certainly save me LOADS of time creating those -Exits-> additions for my myriad AI aircaft!>> Paul - will be busy tweaking today, methinks! :)Hi Paul! I have a few minutes before Midnight Mass, so I'll take a moment to answer your question...Nope, the FX Tool will not write any data to file (except for the new or edited .fx file of course)...However, since it works "real time" in the sim, it makes locating coordinates quick and painless. It's not that difficult to cut-n-paste coordinates from the FX Tool's data windows to the aircraft.cfg file though... ;)Here's a screenshot of an "engine fire" that I used the FX Tool to place an .fx file and "pose" the shot:http://img139.imageshack.us/img139/1112/cj...ginefireql6.jpg

-snip->Hi Paul! I have a few minutes before Midnight Mass, so I'll>take a moment to answer your question...>>Nope, the FX Tool will not write any data to file (except for>the new or edited .fx file of course)...>>However, since it works "real time" in the sim, it makes>locating coordinates quick and painless. It's not that>difficult to cut-n-paste coordinates from the FX Tool's data>windows to the aircraft.cfg file though... ;)>>Here's a screenshot of an "engine fire" that I used the FX>Tool to place an .fx file and "pose" the shot:-SNIP- hehehe...I saw that shot when you posted it somewhere else here in our virtual world. Merry Christmas, Fr. Bill! I did try using the effects tool yesterday to find the coordinates of exits. It took a bit of practice to move the axis values to get the effect at the correct point. That done, however, I find that the x,y,z values did not seem to represent the actual distances from the datum. They didn't scale either, although they appeared to be about 1/2 to 1/3 of the true values. Am I missing something as to those readouts? As it was, I abandoned that effor for the time being and went back to my "three light" method. I was able to "locate" all 14 exits on the B747-400, for no other reason than "they were there" :)B747-400(exits)number_of_exits = 14exit.0 = 0.4, -30.30, -9.5, 0.88, 0 exit.1 = 0.4, -60.30, -10.5, 0.88, 0 exit.2 = 0.4, -146.0, 8.0, -6.0, 1 exit.3 = 0.4, -42.30, 9.0, -5.5, 1 exit.4 = 0.4, -29.70, 10.5, 0.88, 2 exit.5 = 0.4, -48.70, -10.5, 10.88, 2 exit.6 = 0.4, -48.70, 10.5, 10.88, 2exit.7 = 0.4, -60.30, 10.5, 0.88, 2 exit.8 = 0.4, -99.00, -10.5, 0.88, 2 exit.9 = 0.4, -99.00, 10.5, 0.88, 2 exit.10 = 0.4, -132.00,-10.5, 0.88, 2exit.11 = 0.4, -132.00, 10.5, 0.88, 2exit.12 = 0.4, -179.00, -7.0, 0.88, 2exit.13 = 0.4, -179.00, 7.0, 0.88, 2And here are the "test lights" I used for three other aircraft. I have CTL+' assigned to reloadthe user aircraft so moving things about goes fairlyquickly.light.14 = 1, 28.50, -9.0, 7.0, fx_beaconh , //A330-200light.15 = 1, 47.0, 8.0, 1.0, fx_beaconh ,light.16 = 1, -49.0, 8.0,1.0, fx_beaconh ,light.14 = 1, 28.50, -9.0, 7.0, fx_beaconh , //A330-300light.15 = 1, 56.0, 8.0, 1.0, fx_beaconh ,light.16 = 1, -54.0, 8.0,1.0, fx_beaconh ,light.14 = 1, 45.50, -6.0, 7.0, fx_beaconh , //A321light.15 = 1, -33.50, 5.85, 1.0, fx_beaconh ,light.16 = 1, 34.50, 6.0, 1.0, fx_beaconh , Paul ( the above are within a foot or so of the center of the exits )