DaveCT2003

Here is a video showing the issue. 2019-01-23 18-32-12.mp4

Guys, I just installed, and I have the same exact problem. It's not my system or settings, it's the scenery.

I've looked into this, and I don't know what caused the error. I would head over to Navigraph and see what they say.

Well, nobody can say you're not consistent my friend.

Here is a definition of the Ground Temp entry: Ground temperature is normally entered during preflight. In flight the ground temperature defaults to a blank display (3 dash lines). But (and it's a HUGE "But"), neither FMGS type for the Airbus's are perfect, especially when it comes to temps and cruise levels. Though in a strange way, I actually have some direct experience with just these sort of calculations. Basically, the calculations for temps, economic speeds and cruise levels and Tropopause are not only extremely complex, but the FMGS calculations can also be wrong with certain "correct" inputs. For this reason, Airbus has recommended NOT changing the internally calculated Ground Temp or Tropopause figures. CAVEAT: If you Google this, you'll find a slew of sites/PDF/training documents that say for GND Temp you should enter the Ground Temp as it will be at Takeoff. But again, Airbus engineers said NOT to do this and that appears to be the latest information on this. Put another way, the values that auto-populate exist to mitigate the inaccuracies in the calculations. So, we recommend that you leave both the above entries alone. If you decide to change them (hey, it's your aircraft!) then please don't report any bugs seen during flights where this info was changed. I hope this answers your question! Best wishes.

Please take a look at the system requirements for the Product in our store (link below). Note in particular that Video RAM requirement... which is the same for P3DV4. Will it work? Maybe, maybe not, it's your graphics card that is the weak link. I recommend going to a 1070 (minimum), 1080 or one of the latest cards so long as it has 8GB of VRAM. Best wishes! https://www.aerosoft.com/en/flight-simulation/prepar3d-v4/aircraft/2437/a320-family-professional-bundle

The best place to start is with Monitor Calibration. I recommend a freeware tool called Calibrize. After you are sure that your monitor is correctly calibrated most darkness related issues will be resolved.

and... if I may, it also helps Aerosoft to keep consumer products at a lower price than otherwise might not be possible.

I agree. If you're not familiar with manually adding scenery to FSX then I would just use the built in Scenery Manager and point it to where the scenery is installed and you should be good to go. Best wishes!

Sorry, but we are no longer dealing with Version 1.2.2.2. The forums are full of the reasons why my friend!

I'm going to let one of the guys working on the IAE address this for you.

Which version of the Airbus do you have installed? Also, which specific Aircraft and Engine type) are you reporting on?

Those waypoints are almost certainly runway (approach) waypoints as I don't show them on worldwide VFR, Jetway or Victor airways charts. I believe the errors indicate that the waypoints are also not in the NAVDATA being used. The correct points for NOR05 are 5.29714444 by -74.29844722 which I pulled up in the 1901 cycle of Navigraph data. Maybe you're current NAVDATA revision doesn't have that and the other waypoint? If not, you can always enter it manually into your NavData (not for beginners) or you can always enter a manual waypoint in the FMGS.

Did you search manually or did you use a tool to search, and if a tool then which one?

Thanks for the feedback! Believe me, the team feels the same way. What happened with 1.2.2.2. was bad and completely caught us off guard as well. I think you guys will really like the update, which isn't far off.