Fenric

I won't say that a lack of external control for the Hdg Bug Setter needs a fix, but with my hands and fingers subject to Repetitive Stress Injury, I don't use aircraft that don't have external controller support.I like what I see with the CS 732s but I can't use aircraft that require lots of precise mouse clicking.

John,I've never had a "parking spot size problem" with GSX. I make a dispatch release before each flight and I know which spots my aircraft can fit into according to the BGL data. (And I generally don't fly heavies so I have more options than other users.) And GSX always lets me have the spots I opt for. But I have read where others describe arrving at a spot with clearly enough room, but because of some design reason - maybe the developer builds for FS9 and ports to FSX or maybe they use Andy's tiny-parking-radius trick to always have a space free, or whatever - GSX plays by the rules and says, "you can't go there."I've made a few GSX parking files for some of my airports that have "static" jetways, ill-defined pushbacks, and buildings placed too close to the park spot. So I'm glad FSDT has given us the chance to define elements of "our" parking for GSX, because GSX is "our" ground services... not services for AI. AI can follow the BGL-written rules, but our eyes allow us to (literally, duh) see things differently.You know, I've never gotten a good parking grade from GSX either - and I know I've parked dead-center of the circle well within a degree of the heading. Oh well, more practice needed. :(

John,My line of thinking attempted to parallel what I took to be FSDT's intent to include the ability to have its own data for pushback direction and to manage the placement of the marshaller and vehicles around the aircraft. Perhaps I came to my conclusion in haste and did not consider all aspects of the situation as you suggest.Following what I believe to be your line of reasoning, certainly users could move scenery objects - buildings and jetways - to give vehicles the correct amount of room that a scenery-defined parking space would call for (etc.) without recourse to the GSX parking editor. I'll concur that's undeniably correct.Then again I had also thought that sharing a user-generated text file that would accommodate multiple aspects of GSX's "parking spot" structure with - for instance a commercial airport scenery - should be far less problematic than sharing an actual user-modified commercial scenery file itself. Maybe not though?

Thanks to you both Howard and Andy for the clarifications!Perhaps FSDT will consider adding a "GSX Parking Radius" parameter to a future update so this issue can be managed without having to edit an AFCAD.

Isn't there an option in the GSX parking editor to set a radius? Or am I thinking of a setting that placed the trucks a distance from the aircraft?If it's the latter, then what if GSX modified their parking editor so users could specify a GSX-effective parking radius to avoid having to edit the AFCADs (possibly editing commercial AFCADs)?

D'oh! That's 10 AES credits that I didn't need to have spent. :(

double-post, sorry.

http://www.simforums...onment-x-series

Sounds like me a year ago. :( Then I picked up their MD902 - the speed and range sold me.I can't say I'm a great helicopter pilot a year onward, but it's a very nice machine and I can get to where I want to go without injuring the air too much.Plus its nice for exploring a well done scenery area - Bornholm Island, pretty much any interesting ORBX area, etc.Yes I did spend some time one day hovering around KCVG, playing "WKRP traffic reporter."

Well there is more hot air in the vicinity of this airport than any other airport in the world.

Yes.

Here's a new wrinkle in the latest version:Tell your MCE FO what your "Missed Approach Altitude" (or "Go-Around Altitude") is during the flight, then shortly before you hit your minimums the FO will annouce she's dialing in that altitude setting. Nice!

I'd suggest, as with anything, running a demo/trial first....

"Please, point a gun at me if it helps you relax.... You're only human." --The Doctor

You can run Pete Dowson's MakeRwys utilty (under Useful Additional Files) and it will output several files... the runways.txt and the runways.xml files (they're both pretty big) will contain this data.Examples... <ICAO id="00AL"><ICAOName>Epps Airpark</ICAOName><Country>United States</Country><State>Alabama</State><City>Harvest</City><Longitude>-86.770279</Longitude><Latitude>34.864811</Latitude><Altitude>820</Altitude><MagVar>0.000</MagVar><Runway id="01"><Len>2300</Len><Hdg>10.000</Hdg><Def>Grass</Def><ILSFreq></ILSFreq><ILSHdg></ILSHdg><Lat>34.861698</Lat><Lon>-86.770950</Lon></Runway><Runway id="19"><Len>2300</Len><Hdg>190.000</Hdg><Def>Grass</Def><ILSFreq></ILSFreq><ILSHdg></ILSHdg><Lat>34.867908</Lat><Lon>-86.769608</Lon></Runway></ICAO> Airport 00AL :N34:51:53.2932 W086:46:12.9985 820ft Country Name="United States" State Name="Alabama" City Name="Harvest" Airport Name="Epps Airpark" in file: Scenery\0302\scenery\APX24190.bgl Runway 1 /19 centre: N34:51:53.2932 W086:46:12.9985 820ft Start 1 : N34:51:42.4734 W086:46:15.3193 820ft Hdg: 10.0T, Length 2300ft Computed start 1 : Lat 34.861698 Long -86.770947 Start 19 : N34:52:04.1129 W086:46:10.6778 820ft Hdg: 190.0T, Length 2300ft Computed start 19 : Lat 34.867908 Long -86.769611 Hdg: 10.000 true (MagVar 0.000), Grass, 2300 x 200 ft *** Runway *** 00AL0010 Lat 34.861698 Long -86.770950 Alt 820 Hdg 10 Len 2300 Wid 200 *** Runway *** 00AL0190 Lat 34.867908 Long -86.769608 Alt 820 Hdg 190 Len 2300 Wid 200 FSM A/P 00AL, lat=34.864811, long=-86.770279, alt=820