pasobconcept.blogg.se

1. #How to make aerosoft airbus x extended respond cuickle full
2. #How to make aerosoft airbus x extended respond cuickle series

I leave here the start of the cfg file from the AXE A320 and, if possible, I'd like to learn what I'm doing wrong. The names listed in the Profile sections can be shortened versions of the real names, or with the "substring" setting (usually defaulted these days), and part of the aircraft names. They don't need to have anything in common with actual aircraft names. Profile names are intended to be chosen to represent a class of aircraft you want treated all the same. Or if PMDG is in there somewhere, the PMDG part? Really you'd have been better off choosing a more snappy name for the Profile. Otherwise each time you load a new aircraft, assign it to the " LSH MD - 82 McDonnell Douglas" profile. If you want all starting with "LSH MD-82" then make the Profile definition say so, i.e.

#How to make aerosoft airbus x extended respond cuickle full

If so, do they all have the name you have definedfor that profile somewhere in their full name? i.e. Is the "ShortAircraftNameOK" parameter in the FSUIPC INI file set to "substring"? Shouldn't the all the MD-80s I have be using the default friction table? What am I missing here? All the other liveries, which also share the "LSH MD.82." are using the DynamicFriction LUA I added LSH MD-82 McDonnell Douglas profile and in this case only that particular one is affected by the ResetFriction LUA. If I'm completely wrong about this believe, please feel free to correct me! It also taxis with idle thrust, which I believe doesn't happen with this type of aircraft. So, after that, it was time to do a test with the LSH "MadDog" MD-80.

#How to make aerosoft airbus x extended respond cuickle series

I created the profile for the B737-800 Ryanair., and all the B737s from 600 to 900 series are using the default friction values. I also read here, that FSUIPC "looks" at the profiles' name and all the others aircraft that share a part of the name are also included in that same profile, automatically removing the hard work of creating one profile for each livery. I just have one doubt about FSUIPC profiles handling.Īs I wrote here, I wanted to use the default friction values with the NGX and created a profile for the NGX with the livery I use more often. So, I did what Pete told me to do and obviously, it works! :)