KConlon

I think they are in the AerosoftAxx-Axx Pro V5/Data folder. If not here is what I have and use to configure SPAD. I have 9 Go Flight panels including the EFIS configured using SPAD A31X_32X_LVars.cfg

To edit my post.... I have the TCA support set in the EFB

Is there any special configuration needed to get the thrust reversers working with the TCA-Quadrant? Using P3d's axis control I cannot get it nor have I been able to set using SPAD.

I ended up deleting prepar3d.cfg and installed 5.1HF1 and I am no longer having the DXGI_ERROR_DEVICE. Still running Trueglass and seeing the memory max out on my 2080TI around 4.5GB at FSDT KCLT and UTLive getting a solid 28-30fps internal and external (using GeForce Experience fps counter)

Mathijs, totally agree that the hardware linking is a function of the sim. What I don't understand is why all of my other 3rd party developer aircraft function fine - including the Aerosoft CRJ. I did a full uninstall of the 318/19/20/21 and 330 along with a complete reinstall and all seems to work now.

I recently purchased the TCS FO pack. Configured P3d (5.1HF1) per the Vol1 documentation. Throttle works great! The stick no so much - no control surface movement. When I look at the ECAM I see no deflections in F/CTL and the rudder shows left hard over but the on the PFD the white cross moves correspondingly along with the stick animation. Both engines are on (as is the APU) and HYD looks good. I am seeing similar results using the 318/19, 320/21 (1.4.1.2) and the 330 (1.0.3.2) . Other aircraft seem to work fine including the AS CRJ , PMDG 737,747,777 Capt Sim 757-67 and default airc

Recently (I mean very recently) I started getting DXGI_ERROR_DEVICE-HUNG errors with - and ONLY WITH the CRJ. I am using version 2.2.0.2 on P3dV5 HF2 . I can run AS's Airbus Professional with out any issues. After the first few CTD's I updated my nVidia drivers to 457.09 but still have the error yet the 319 still runs fine. Could it be FS2Crew for the CRJ causing this? I use FS2Crew for the Airbus Pro but who knows. I'm baffled. Any ideas?

View File US Airways A319 IAE N828AW 2.1 Update to a livery created by Nathan H for the Airbus X to make compatible with AS A319 Pro using the latest livery installer. Submitter KConlon Submitted 07/24/20 Category Aerosoft A318/A319 professional liveries  

Contacted and was given the OK to repost.

I made some modifications to make an AS AB Pro compatible variation of US Airways A319 IAE N828AW 2.0 . I have messaged the OP but their activity shows they have not visited the forums since 2016. Any issues reposting with credit to the OP for the livery. Kevin

FS2Crew has a beta update for P3dv5. https://www.avsim.com/forums/topic/575656-aerosoft-airbus-pro-for-p3d-v5-public-test/ Download from your order history Kevin

I was having some issues with A2A's 172 - where the font's were not displaying properly on some of the gauges. I guess it is a know issues in v5. You should be able to resolve the issue by manually editing the Prepar3D.cfg as described in the post I linked above. (i.e find the line "COCKPIT_HIGH_LOD=0" which is the "[GRAPHICS]" section and change it to ""COCKPIT_HIGH_LOD=1") The Prepar3D.cfg can be found in C:\Users\[UserName]\AppData\Roaming\Lockheed Martin\Prepar3D v5 Credit to the OP on the A2A forums https://a2asimulations.com/forum/viewtopic.php?f=108&t=70238#p534103

I am having similar problems, on the ND the arc seems too big for the display. Also, MCDU II (where all sim settings are) seems to mirror MCDU I. When I bring up the popup for MCDU II al I get is a black screen in the MCDU window. I am using v5 and understand that the 'bus is not supported. I copied the contents of Documents\Prepar3D v4 Add-ons to Documents\Prepar3D v5 Add-ons mot just the add-on.xml files In v4.5.13.32097 the ND appears wnl but MCDU II when popped out is still black (screen shot attached - with both MCDU's displayed.

Just installed the latest version for the A318/19/20/21 (Thanks for adding in the EFB!), and notice that when selecting the EFF tab when I am in the 319, the Take off data is for the A330. Is there a configuration step I missed? +