Herman

Bradley, I edited your post to remove the comment about the developer. As this is a commercial forum hosted by Aerosoft, please avoid opinion on other developers. Thanks in advance for understanding our interest in respect for others in the business.

Lost comm procedures for airspace under US FAA jurisdiction: https://www.faa.gov/air_traffic/publications/atpubs/aim_html/chap6_section_4.html Lost nav is best avoided by carrying the right mix of redundant nav systems so the loss of a single system still leaves alternative methods, including radar vectors, to visual meteorological conditions. Properly equipped, loss of all nav is extremely rare in today's environment. This said, along with the comments from other contributors, probably doesn't really get to your first question. At some point, the probability of total total failure as you described would require the crew to use available resources as seen in such "non-survivable" incidents as the "Miracle on the Hudson", United Flight 232 (here) or DHL A300 OO-DLL. Granted, these were different factually from your scenario, but all illustrate that crew resource management, using all available resources, offers the best outcome to any emergency. With regard to your question 2, dead reckoning (DR) from a last known position would be my last resort. Too many variables in winds/weather and too many non-variable rocks. A DR letdown in full non-visual conditions isn't an option at all, considering the people on the ground you're putting at risk, plus whoever's on board. Backup comm resources used to get me to a safe alternate with a radar approach would be a better choice.

It's completely normal, and a good cabin crew keeps it coming. If turbulence is expected, you drink fast. If it's unexpected, you have an embarrassing stain in your lap at the end of the flight. Just like everyone in the back. Unlike "Fate is the Hunter," the contents aren't going to short out the electronics and cause you to crash.

The Airbus Professional series, as well as the earlier Aerosoft Airbus products, all specifically focus on the flight deck operations and not the cabin. This has been explained numerous times over the course of development. Thanks for your interest, but your request is outside the scope of the product line and simply won't be an option.

Moved as requested by OP

Nice to see another budding painter.

Duplicate post. Please reply or add additional comments only to your earlier one. Thanks!

Robin, this does seem perplexing. Thank you for your detailed responses and the accompanying screen shots. That makes things quite clear. I don't see anything wrong with your axis assignments (although the aileron and elevator null zones seem a bit large, they're not out of bounds). I'm not seeing any multiple axis assignments, and your brakes are both correctly reversed. So all those look good. The only other question mark I have in your replies is that I see you don't have the FSX folder excluded from your anti-virus scan. I've never heard that could cause this kind of issue, but it's the only item I can think of that I'd like you to try applying to see if it fixes this. Along with that, I should have asked which AV you're using. Some (e.g., Norton) do odd things that result in unusual events. Probably the easiest thing to do for testing is simply disabling it, give the controls a full test, and reply back. Something I forgot to ask earlier: are you using FSUIPC? If so, try temporarily moving the FSUIPC.ini out of your modules folder (park it somewhere safe outside your sim folder structure and test again. A long-shot question that occurred to me after my last post, though obvious, I need to confirm anyway: are the hydraulics on during your control check? Please complete the entire cold and dark pre-flight to line-up using the tutorial and reply back on whether or not the controls work. Finally, to check my understanding of the issue, is it that none of the controllers result in the expected control movements (as seen externally and in the (lower center) ECAM display) with electrical and hydraulics on?

Clearer now. Thank you. With the controls working in default aircraft, they have to work with the Airbus. Please confirm if you checked all the items in my initial troubleshooting steps: Are each of them showing up in the Devices and Printers applet in Windows Control Panel? Are they all calibrated through the individual item in the applet? When you test the controllers in the calibration applet, do the axes move smoothly or is there spiking? What dead zone do you have set? Do each work correctly with the default aircraft in the sim? In the sim, under the controller assignments, are the relevant axis assignments correct and is there only one controller assigned to each axis? It's very common for the sim to assign pitch and roll for example to both your yoke and rudder pedals. Other considerations: Please reply with where your FSX and Airbus are installed (complete path). If in the default, it's likely the User Account Control (UAC) is interfering, even though you report the controllers working with a default aircraft. Are you using FSUIPC? Did you unzip the downloaded Airbus file before installation? If you unzipped it, did you use a quality unzip app like 7-zip (link here) instead of the built in Windows one? 7-zip is free and one of the very best file unpacking apps out there. Did you have the anti-virus off during installation? Does your anti-virus exclude your FSX folder (it should)? Did you install with Administrator rights and are you running FSX with Administrator rights? Was FSX off during installation (should be obvious, but we just saw another report of a partially functioning add-on caused by installing while the sim was running)? If the answer to all of this is a dedicated drive (first point), "No" to the second point and "Yes" to everything else, uninstall the Airbus using the Windows Control Panel applet (if you can see the Airbus there) or with the uninstaller in the Airbus root folder. Never by simply deleting files. Reboot the computer, turn antivirus off, install the Airbus with Administrator rights, reboot, turn on anti-vurus, check the controllers for proper function in the Windows Control Panel Devices and Printers applet, then try the Airbus in the sim.

So that sounds like the 32bit Airbus (this link in the store). I'll move this to that support forum. I should have also asked which sim you're using: FSX, FSX:SE, P3Dv3. What isn't quite clear from your reply is what the controllers are or are not doing. For example, pitch and roll are fine, rudders don't work, thrust levers (throttles) are fine, brakes won't release. Please clarify that part for us.

Kiwi pilot, a belated welcome to the Aerosoft support forum. Please note you posted in the "General Discussion (no support)" section of the forum, so if you'll respond with which version of the Airbus you have, I'll move this for you to the appropriate specific support section. Also, please describe a bit more clearly what is or is not happening with your inputs. The controllers you noted are typically used, so it shouldn't be hard to get them working for you. Initial troubleshooting steps include: Are each of them showing up in the Devices and Printers applet in Windows Control Panel? Are they all calibrated through the individual item in the applet? When you test the controllers in the calibration applet, do the axes move smoothly or is there spiking? What dead zone do you have set? Do each work correctly with the default aircraft in the sim? In the sim, under the controller assignments, are the relevant axis assignments correct and is there only one controller assigned to each axis? It's very common for the sim to assign pitch and roll for example to both your yoke and rudder pedals. Looking forward to your reply so this can be moved to the right forum section and we can get you flying.

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.

Steve, it's great news to hear you found the issue and the problem is gone. Thank you for this great example of collaboration between a customer and Aerosoft support. Your error reports were concise and helpful, you documented troubleshooting you'd done, and most important of all, you kept a positive attitude throughout. Thanks also for calling out Oliver's extra efforts to make this work. Also, thanks so much for sharing what you learned on the FSPXAI Facebook site. I for one appreciate you pasting the text into your message, since some (including me) choose not to have a Facebook account and members don't always think to allow access to non-members.

Welcome to the Aerosoft forums, Julius. It's not possible to estimate an availability date. The cost has not been established and won't be until very close to release. When the date and cost are known, you will see it announced here, so no need to ask later on.

Read here (last Q&A). It's not been decided.

Moved to the German language forum from the English language one.

The airport comes with it's own appropriate AFCAD, so that may well be your issue. I can't think of a reason why you'd want to disable it (unless you were troubleshooting) since it's designed for this add-on. Your description sounds like there's another AFCAD conflicting with it. I suggest disabling (by adding ".off" without the quotes after the filename or alternatively, putting them in a separate folder from the "Scenery" one they're in). Also, do a search for AFCADS with LEBL in the filename and disable them too. Then use only the AFCAD included with the Mega Barcelona airport and report back with your findings.

This thread will remain open for an additional 30 days, pending further information or troubleshooting results from the original poster (OP). To date, it seems to be a problem specific to that installation and of course a genuine issue to the OP.

Six months ago, I did a cleanup of this thread to delete the repetitive wing flex/release date/32 bit version/OT/livery and so forth questions. I see it's time for another one. On January 1, I noted about 70% of the posts (based on pages reduced during that clean-up) were of the noted "clutter." Going forward, and in alignment with Mathijs' statement about strict(er) moderation following the temporary closure for comments on this thread, I've again pruned such clutter as well as questions that have been overcome by events. Doing so should make it easier for regular as well as new readers to more quickly learn about earlier design and strategic decisions along with updates without using the search tool or paging back. Aerosoft staff and moderators work hard to keep all the Aerosoft forum topics open and friendly. The community in the vast majority of cases offer questions and comments that sustain that. While we all appreciate the positive comments that accompany information updates (like a recent video of the beta), such comments have less relevance over time and so I've hidden those as well. Please take that as not a mark of disrespect or lack of appreciation. Each one means a lot to the person you're thanking. For that reason, we typically leave them up for about a month so their glow can continue for a while. Staff and moderators deeply appreciate the support the community has shown in the A330. One simple measure of that is we can see there are 43 pages total of comments in this thread, mostly helpful and few not. That you see less simply means there are that fewer pages worth of really lasting value and useful contribution. Thank you for your overall support and excitement about this aircraft.

I'll have to take the time to count how many technical errors are in this. It's hilarious. This guy blows it with his first sentence about the "McDonald Boeing A390" and goes downhill from there. I really enjoyed the "ancient art of hand-flying" and the sex partners at Coachella comparison. What a hoot!

English in English language forums, please. Also, there is no support where you posted (as stated in the title of this section), so this will have to be moved. Do you want to use a software translation tool and keep it in the English section or do you want it moved to the corresponding French language section? If the latter, support is likely to be slower, as most of our tech support experts use English or German. Merci!

In-game screenshots are simple, just hit the "V" key, then look in your pictures folder for them. Do check to ensure the format is .jpg, as that's the most compact and easiest for others to see. Here's the menu item:

Here's a link to the Orbx Compatibility forum in case you have other add-ons with conflicts.

Asked and answered by Mathijs (2x), so until Aerosoft has anything more to say formally, speculation here on the commercial support forum serves no useful purpose. I also edited the title to make it a question and so it doesn't look like a factual statement. 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.

The red x's at the gates like that are a sure sign there are issues with your SODE setup. If you haven't already, please closely read the SODE User Guide available here or in your SODE folder in the Start Menu to ensure you've installed and activated it correctly. Remember to open the Platform Manager to check if SODE is properly registered. Also, you should have two root folders with "12bpilot" files in them. One is in the always visible Program Files (x86) folder and the other is in the usually hidden ProgramData folder. OR, you could use the Windows Control Panel applet to uninstall it, reboot, and reinstall SODE 1.6.4, being very careful to carefully follow all the steps.