DaveCT2003

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.

Jammin, I'm going to answer most of your Private Message to me here in the forums, so that others will benefit from the questions and answers. People new to flight simulation aren't aware, but flight sim has been around for over 37 years and we've had an online community for most of that time. So lots of questions have been asked and answered online, and a simple Google Search can provide you immediate answers as aposed to posting a question in a forum and having to go through a lot of explanation and wait several days for the answer you're looking for. This is because nobody knows your system and how you have it configured better than you do, but all that info has to be provided in order to get an answer that is helpful to you. That said, I am not trying to discourage you from posting questions or seeking help, you are always most welcome to do that. I wrote the above to help you get at least some answers immediately. Case in point, you're new to P3D and asked me how to reset your P3D shaders, and a Google search would have provided you the answer immediately. I'm also very happy to answer the question for you. There are two Shaders folders in P3D, one is located in your Main P3D folder and this one you never, ever want to touch. The other is located in your C:\Users\[YOUR USERNAME]\AppData\Local\Lockheed Martin\Prepar3D v4 folder and is named "Shaders". To reset your shaders, simply delete this folder and it will be rebuilt the next time you start P3D. This should be done anytime you install or update Graphics Card drivers or an aircraft that uses RealLight and/or TrueGlass (such as the Airbus Pro, Leonardo MaddogX or TFDI B717, etc.). The AppData folder and sub-folders are hidden by default in Windows, so you will have to make Hidden Folder/Files visible in Windows before you will see them. Regarding your question about Monitor Calibration, you simply have to Google "Monitor Calibration" and you'll find both payware and freeware software, and even some hardware, to help to calibrate your monitor(s). For freeware, I recommend Calibrize. Note however that you may not need to do this after resetting your shaders as that may resolve the issue for you while the aircraft is on the ground. My very best wishes.

To accomplish this, you can place your mouse on the bottom of the PFD. Also, I'm pretty sure you know this but for the benefit of anyone who might read this thread in the future, you have to undock the 2D window in P3D before you can move it to another display. Best wishes!

I can say that I've never experienced this, and I don't recall anyone ever reporting it. Are you using an added sound card on your system? When this occurs, try pressing the "Q" key twice (it's an old issue with FSX and P3D on some systems) and see if that brings back the sound. I would also update your sound drivers to see if that resolves this. Best wishes!

Sorry Hanse! I didn't realize it had been updated my friend, I thought it was still being worked on.

We are indeed aware of this, there should be a few posts around here about it. The Checklist is a bit out of order with the sequence of events because of the changes we've made since release.... you can usually work around them, but it will be back in sync with one of the coming updates. Please keep in mind that our CoPilot / Checklist feature is designed as a way to familiarize non-Airbus experienced sim pilots with how to operate the Airbus and after than to not use it. In other words, it's not a full up CoPilot like some third party addons offer. Thanks for writing in! My very best wishes!

Thats a good question. It will have two different MCDUs and a third for settings. As far as your specific question, software wise it has one FCU which feeds all MCDUs, but since nobody ever sees the FCU it really doesn't matter. Best wishes!

Hello Eric! If you haven't already, use the AS Updater to update to the most recent version. The Airbus Pro has a few more things which have to be entered that were not present on the FSX version. To check for these, please see the Step by Step Guide in the documentation. A combination of the above should help you resolve your problem my friend! Best wishes!

It's likely a P3D setting that forces that.

For those having this issue (likely everyone)... LM has said to "time_constant=0" under the [SOUND] section of Prepar3d.cfg" and see if that resolves the issue. We will still look at the sound file on our end. Best wishes.

Have you updated to the latest version? If so, then I think we have to use at pre-flight and/or operational related matters as I can tell you that the aircraft doesn't normally do this. Have you run through the tutorial flight? This is an excellent place to start, especially for Boeing experienced sim pilots as the Airbus is radically different from Boeing (this is merely a guess on my part... trying to give you enough to go on to solve the issue you're experiencing). Looking foward to hearing back from you!

Hey Paul, We've been providing experimental updates via the ASUpdater, and the team has been working on the next such update as well as on SP1. Unfortunately I can't give you a date because of the complexities and different prioritized work items. Mathijs has been doing an excellent job of keeping everyone updated, and I'm sure he'll let the community know as soon as the next update is ready. Thanks so much for your question! Best wishes my friend.

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.

Most welcome! Sorry that we could not directly intervene, but I'm confident the update was sent to them. Best wishes!

Thanks for letting us know! What version of the aircraft are you currently using?

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.

If we were to do a TSS Sound Pack ourselves, it would drive the price up higher, and we focus on quality at a reasonable price. Honestly, that does nothing to help confirm anything that I asked about. I'll try and find some time in the schedule to test this myself. Thanks guys.

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.

Thanks guys, I'll put this into our Bug Database and also contact Navigraph. Thanks again for letting us know!

Unfortunately not. I would write to them (directly or in their forums where they also provide support) and ask them for a timeline for the update. This is how it has to happen as they are the ones who sold you the product. Best wishes!

Do you load a default aircraft first on every flight? If not, then that is what I'm asking you to test. You say that you normally don't have to load a default aircraft and "it works", but my reply is how would/do you know unless an error causes a visual issue or CTD? Many times an issue isn't seen or experienced, but it's still there. Anyway, when we troubleshoot, we test and look at specific things to help rule them out my friend. Many thanks!

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.

Okay, entered into our Bug Database. Thanks again for writing to us about this!

I suspect the difference you saw is likely because of the time difference it takes to update weather servers. We see this all the time comparing VATSIM weather to real world weather, and ActiveSky to Real World. One won't always see it, but it happens regularly enough. We'll take a look at the ATIS Printout. We've already made some changes there and I believe it's already been resolved - but I'll check. Thanks for writing to tell us about this! Best wishes.

I experienced this one time during RTO testing, but never on a normal landing. Of note is that I almost always boot into a default P3D aircraft first (the F-22 is not truly a default, I use one of the Mooney aircraft), but I didn't do this for my RTO testing and I did do it for normal flights. Can you please try booting into a default aircraft, and see if you still have the issue? I will do the same (tomorrow). This will help us track it down. Many thanks for writing in about this!