The Aerosoft a330 for P3d v5 is out.

Finally I can get my airbus fix for v5. But hopefully FSLabs follows in the next few days 😄

1 hour ago, Theras said:

The Aerosoft a330 for P3d v5 is out.

Aerosoft updater  is silent 🤨

2 minutes ago, BMW969 said:

Aerosoft updater  is silent 🤨

You have to download the installer from your shop account before it appears in the updater! 

What have you guys been doing in the options with the Force ECAM rendering check box?  Check or uncheck. Notice it's on by default.  

18 minutes ago, micstatic said:

What have you guys been doing in the options with the Force ECAM rendering check box?  Check or uncheck. Notice it's on by default.  

With a GTX 1080Ti I am leaving it checked. I am running v5 with 4K screen resolution, 2K textures, 2x SSAA. The GPU is tapped almost at 100% so I won't put more load onto it.

thanks.  I am doing all the same things as you list with a 1080ti also

One thing I noticed at night anyway is that the landing lights were a pretty big hit on performance.  

Quick flight, and all seems well so far.   Decent performance too, although my 1070 is really getting hammered at 99% and 78c. And thats with conservative settings. 

Finally I got back an FMS...

I've been waiting for the release of the Bus day and night and now I have been able to continue an IVAO Tour.

OK, I ran into some trouble, but got it fixed within 1 hour in the Aerosoft forum.

The digits of the Speed/Heading/Altitude... Display have been much too big. We found out, the installer didn't install some Windows Fonts (Aerosoft/Airbus Fonts) on my system. Some others had the same issue. Aerosoft provided the fonts in a separate package in the forum.

Some others had some kind of zoomed-in ND. They had to verify the Prepar3d.cfg (...appdata/roaming...) for COCKPIT_HIGH_LOD=1. They had it set to "0" and that caused the zoom.
Some may remember, A2A also had some issues with the release for P3Dv5 and this setting was required for the A2A Planes as well.

Due to the experience with the P3Dv5 Version of "Lukla" (VNLK) I already had to switch texture from 4096 to 2048. Following the ORBX recommendations in several of their documents, I had the Level of Detail Radius reduced to HIGH, as well as a Mesh Resulution of 5m. Using these settings (and a few disabled shadows) I had a nice flight in the A333 from LPLA to EHGG this morning. Mostly 2.5-3.3GB VRAM in use (out of 6,7GByte available ). Variable Frames between 20 and 50.

Only one time I had an issue over London, when the Bus veered off the RNAV route. That moment 5 of my 8 CPU cores have been at 100% and all 8 Hyperthreading cores as well 100%. Strange... Never seen this before. I had to cancel ASP3D to continue.

Ralf

Screenshot showing the VRAM in use:

 

Screenshot showing CPU-Use:

Edited May 21, 20206 yr by skystar

Unfortunately, I am getting more than the usual volume of CTD's in v5 with this aircraft (only 2 out of 6 flights finished successfully), despite quite conservative settings.  I am not sure if it is the ECAM hardware rendering, the beta TrueGlass or something else, since my VRAM numbers never get close to my limit and I have quite conservative settings.  This probably goes back in the hangar until at least the next v5 hotfix or update - I just don't have time to go chasing where the issue might be.  Focusing on my more stable aircraft for now.

Edited May 23, 20206 yr by PurdueKev

Yep, I gave it a try, hoping for a miracle.
I had numerous issues like crazy vertical climb, sudden dives, excessive speed etc... with the 330 using P3D4.5.
But actually I love their VC so much, graphics are so immersive and superb, that I wanted to try it again with the V5 until the FSLabs Buses are updated.

Same thing, same bugs.
+ tons of CTDs.

 

I must say the VC looks amazing, probably the best I've seen, even better than PMDG. One thing that annoys me is the default cameras. There's conflict when using Chaseplane. Even though I have disable the entire default Aerosoft A330 view system, I notice that when doing the built in checklists that whenever it switches to different cam views and then you go to switch back to one of your chaseplane views, it messes up and you have to manually go to the chaseplane view.

2 hours ago, captain420 said:

I must say the VC looks amazing, probably the best I've seen, even better than PMDG. One thing that annoys me is the default cameras. There's conflict when using Chaseplane. Even though I have disable the entire default Aerosoft A330 view system, I notice that when doing the built in checklists that whenever it switches to different cam views and then you go to switch back to one of your chaseplane views, it messes up and you have to manually go to the chaseplane view.

You can disable the checklist feature where it changes views for the checklist item, which I don't think works well with CP. I think this can be found under the checklist options in the third MCDU.  I found that then I can follow the checklist process and use your CP views to move around as normal.

43 minutes ago, cwburnett said:

You can disable the checklist feature where it changes views for the checklist item, which I don't think works well with CP. I think this can be found under the checklist options in the third MCDU.  I found that then I can follow the checklist process and use your CP views to move around as normal.

Thanks, I haven't had much time to explore the plane yet.