Herman

There isn't one. It's not for P3Dv4. From the system specs page: System requirements: Microsoft Flight Simulator X (with SP1 & SP2, Acceleration Pack), Microsoft Flight Simulator 2004 or Lockheed Martin Prepar3D V1/V2 Windows XP / Vista / 7 / 8 Processor with 3.0 GHz (Dual Core processor recommended) 2 GB RAM (4 GB recommended) 3D graphics card with 512 MB (1024 MB recommended) .net Framework 3.5 or higher (only if you use the Aerosoft-Launcher) Download-Size: 950 MB Installations-Size: 2 GB

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Moved from the 3rd/Settings MCDU threads to the Checklist area.

This is unrelated to the 3rd/Settings MCDU, so I moved it to the "standard" MCDU thread.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

I reposted this link to Secondator's advice several times, but you apparently didn't look at the related threads. Here's how to get to 1.2.2.1:

You could also take a look at this post by Mathijs regarding "hidden" colors at the dark and light end of your monitor's display range. Follow the suggestions, then (and only then) take a look at the graphic file. If you followed instructions, you'll see your dark areas have more detail. All this should be in connection with the other suggestions such as a properly calibrated monitor using Dave's advice. Here's Mathijs' post:

Thanks, Dave. Another way the commercial products help is at least one airport that otherwise might not have been done was done and in detail for a commercial customer. Once the commercial project was complete, it was relatively easy to port it over to a consumer product.

Please take a look at this link if you want/need to roll back (Click on "Herman replied to a topic" and you'll see some warnings and another cut-out of what to do. If you clock on Sabretooth's message, you'll wind up at the start of the full thread): At present this is the only safe way to do a roll-back. The emphasis is on correcting the issues associated with 1.2.2. Coming up with an easier way to roll-back is further down the priority list.

Depends on your point of view. "Good" in that commercial customers are always highly prized in a business like Aerosofts, "bad" in that it might cause a delay in this product because commercial projects frequently/usually have a higher priority than consumer products. That's true of almost any business BTW.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Glad to hear you're now able to fly. Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

There's a dedicated forum section for livery requests, so I moved this there for you. Please look around that section and you might find what you're looking for.

Your issue isn't related to the Options/Settings (aka Third) MCDU so I moved this for you to a better area of the forum. As for your observations, there are several real life and current Airbus drivers on the test team who would disagree with your assessment. Please clarify your personal experience with the Baby Busses and what specifically you think should be different.

A correction on the email address Dave provided. The Zendesk system was replaced and support is now reached at https://helpdesk.aerosoft.com/portal/home. Here's some background if you're interested: Also, I changed the font size used in the lead post so it doesn't look like shouting.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.

I just redid mine using the instructions by Secondator here: First, use only the Windows Control Panel/Programs and Features applet to delete your current version. If it's not there (mine was missing), then simply use the uninstaller in your Airbus folder. Never just delete folders to "uninstall". As you note, the current download from the store is 1.2.1.0. Do bear in mind the store download will almost certainly be a "dot" update or two behind current until we get past SP1. You then use the Updater, after changing the configuration to NOT use experimental updates, to bring your installation up to 1.2.2.1. Here's what it should look like when you're done (I added the yellow markings to call attention to the key elements): With regard to your second question, please post it as an issue in the appropriate section of the forum. The lead question was about Updater version issues, while the fuel state issue you're seeing is unrelated to that.

Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic.