avusm575

Steve: In P3D v4 there's a search window in Axis assignements. If I insert "throttle", all choices for throttle axis shows up. If I select "Throttle axis" and thereafter calibrate the axis, I then got one throttle for both single engine and multi engine aircrafts. I had a look at a youtube video from P3D V5 and "Throttle axis" was a choice in the list, so in theory you should be able to find it. Nowadays I've got the Airbus Thrustmaster dual engine throttles, so I don't use the assignment "Throttle axis" for that, but instead "Engine 1 throttle axis" and "Engine 2 throttle axis" for the two throttle axis. I hope you'll figure it out. Tor

To me it looks like St. Elmo's fire. It's strange if the effect is activated for no reason. If you look in the folder ...Aerosoft A320-A321 Professional - Aerosoft A320-A321 Professional Base - Tex_FB_VC, you'll find a dds-file named AS_AIRBUS_STELMO_C that's similar to the image in the link. You can read more about St. Elmo's fire on page 33 in the pdf "The Airbus X in FSX" which you can find in the folder ...Aerosoft - Aerosoft A320-A321 Professional - Documents

Then I'm out of ideas. I hope you'll figure it out.

I've seen something similar like your scenery glitch before and I solved it by verifying the files for the airport/scenery in ORBX Central, and then verifying the ORBX Libraries. I have EGPB up and running in P3Dv4 without EU Scotland or TrueEarth Great Britain.

Hello SnoBrit! I'll try to help you with your issue. I'm on P3D v4.5, but I guess it's the same in P3D v5. The gaps in the Scenery.cfg numbering are supposed to be there because sceneries added with the xml method are using the missing numbers. Then both methods normally ends up in ascending order in Scenery Library like this: Scenery.cfg + Addon.xml = Scenery Library Here's an example from my scenery.cfg where number 237 is missing: [Area.236] Title=LGZA Zakynthos Local=D:\Addons\LGZA Zakynthos Layer=236 Active=TRUE Required=FALSE [Area.238] Title=Mega Airport Rome Local=Ecosystem\aerosoft\Rome2015 Layer=238 Active=TRUE Required=FALSE Number 237 was in my case the airport Rhodes which was added with the xml-method. Back to your case. I had a look at your scenery.cfg and maybe you can restore it (if you don't have a backup). Here's the last scenery in your Scenery.cfg: [Area.436] Title=New Orleans_KMSY Local=C:\P3Dv5\KMSY14 Active=TRUE Required=FALSE Layer=632 As you see, the Area number and the Layer number is different, but they shold be the same. I recommend to take your time and go through the whole Scenery.cfg and change every Area number back to the same as Layer number. As an example your last scenery should be [Area.632] (and not 436) like this: [Area.632] Title=New Orleans_KMSY Local=C:\P3Dv5\KMSY14 Active=TRUE Required=FALSE Layer=632 Then save your Scenery.cfg and start P3D and see if it works. Later you can move on to scenery layering. I use two ORBX insertion points and Lorby Addon Orgainzer to layer my sceneries. I'm not familiar with "Lorby Scenery Export utility" as you mentioned, but I hope that it has not messed things up as well.

Hi yvessamuel, To me it sounds like the AI-airplanes are confused because of a missing file or something wrong within the AI-aircraft folders. Try to click on the troublesome planes in AI-Aircraft Editor and see if the AC Folder and AC Status boxes are displayed in green (OK) or red (not OK).

That's the trick I've used for years. My preferred zoom is 0.7. To get it to work in VC, I have created a shortcut / key assignment in P3D for "View (set to default -1x). After P3D starts up in VC, I press the key and I immediately get zoom 0.7. Then it stays like that until I restart P3D and I have to press the key again.