Jump to content

bpcw001

Members
  • Content Count

    263
  • Joined

  • Last visited

Everything posted by bpcw001

  1. Thanks for your replies. So my setup seems to be OK. Good to know. Still: Why have I never seen the master caution light and sound up when the pilots landed and retarded the throttles in the real A320? Does AirbusX deviate from reality here or do I miss some crucial point? Thanks for your clarifications.
  2. Hi, During the "retard" call, im pulling back the throttles from the CLB detent to idle. On my system, I made two observations: 1. when moving the throttles out of the CLB detent back to idle, thrust is not decreased. Engines only spool down as soon as I'm hitting IDLE. 2. When hitting IDLE, the MASTER CAUTION warning comes on and ECAM message is A/FLT A /THR OFF Is that as it is supposed to be? I've watched a couple of A320 cockpit vids on the net but I've never seen the master caution come on when the pilots retarded the throttles.
  3. Then it's about time that this "advanced version" gets tackled. While I understand the initial aerosoft statement that this is supposed to be some "casual" A3xx sim, it's a very good basis and deserves to be extended to also appeal to hardcore simmers. I'd definitely be willing to pay quite some bucks for an advanced version that combines the really beautiful virtual cockpit and model with deeply and accurately simulated systems. The first thing we'd need is an improved MCDU which allows for SIDs, STARs, RWY selections etc.
  4. I did some more flights. Regardless where in the world, when directly overflying one VOR with another one tuned in too, both red flags will show up. Hence, I think that needs to be fixed.
  5. Hi, since 1.21, the MCDU NAV RAD page needs multiple clicks on the respective LSKs until a VOR, ILS, NDB frequency or a course would be accepted by the MCDU. How many clicks are required is totally arbitrary. What happened? Didn't you guys test this thing? It worked perfectly in 1.20.
  6. True. However, the answer of the aerosoft devs better not be to just disable features or cap the instrument refresh rate in order to increase frame rate. I'd like to see the full information on the FO's side displays as well, and I definitely would like to see a smooth update behavior of the instruments. The code needs to be thoroughly optimized.
  7. I will do some more investigation and report back.
  8. In FSX, I don't use: - any of the stock airplanes except when having to load a clean state for an addon aircraft ("C172 cold and dark") - learning center - pilot logbook, award/reward system - missions - FSX's own weather generator - The built-in web browser ("Home") I actually consider FSX more of a platform that hosts my third-party terrain, weather and aircraft addons rather than a one-stop-one-shop package for all my virtual aviation needs.
  9. Be patient. I can feel your pain as I'm turned off by these things too, but they started a very promising Airbus A320 for FSX; the only one that is *native* FSX. It's in an early stage and many things need to get fixed. Everybody will agree on this. I'll start shouting only if we were told that essential things (FBW, FADEC, bugs in the systems simulations) will not get fixed and that there's not going to be an advanced version. Until then, I believe the devs are working hard to resolve the issues that we're reporting in these forums. As for the thing flying like a dog under normal law,
  10. Be patient. I can feel your pain as I'm turned off by these things too, but they started a very promising Airbus A320 for FSX; the only one that is *native* FSX. It's in an early stage and many things need to get fixed. Everybody will agree on this. I'll start shouting only if we were told that essential things (FBW, FADEC, bugs in the systems simulations) will not get fixed and that there's not going to be an advanced version. Until then, I believe the devs are working hard to resolve the issues that we're reporting in these forums.
  11. You don't get the sudden nose down and retrim bouncing when disconnecting the AP on final?
  12. bpcw001

    Airbus X

    It's because the engines don't spool down far enough. Turn off the AT and retard throttles to idle for descent. Kind of defeats the purpose of a FADEC, but well ... so many workarounds needed to fly Airbus X properly. But I still like it. Promising package! They just need to get that sort of stuff fixed soon.
  13. Yeah, I've experienced this as well. The PFD bugs for F and S are screwed up and don't reflect what's in the MCDU. When taking off with flaps 2, according to the PFD F bug I'm expected to retract flaps to 1 when I'm still in the takeoff roll This should be fixed by the devs CG doesn't change depending on the load. That's why we don't have to set stab trim for takeoff either. CG/Stab Trim is probably not modeled.
  14. I agree with most of what you're saying. Yes, there are bugs, yes, there are inconsistencies and inaccuracies, and yes, the FBW sucks to the point where you have to turn it off altogether to properly hand-fly this thing on approach and landings. Still, I think that the Airbus X is a nice package and should provide a solid basis for further work. I only hope that there will be an "advanced" package made available which will give us a more functional MCDU (SID/STAR support, recalculation of TOC, TOD and other parameters when changing route and altitude in flight ...), IRS, a better FBW imp
  15. Yep, I found out. In the aircraft.cfg, there's a "max_throttle_rate" parameter. Increase its value and the AT will be a lot more responsive. Works better for me.
  16. Yo scarebus, great one! Superb work!
  17. Hi, please consider the following scenario: 1. Set valid frequencies for VOR/DME1 and VOR/DME2 in the MCDU 2. RMI needles show bearings to VOR1 and VOR2, and DME1/DME2 are displayed 3. Overfly one VOR (VOR1 or VOR2, doesn't matter) 4. On overflying the VOR, *both* red flags are showing up, and *both* DME displays just show "----" However, this should only happen for the VOR that is actually being overflown. Needle should not disappear, DME should not show "----" and the red flag should not show up for the VOR that is not being overflown. Regards bpcw001
  18. Hm. Never seen the manually set mach number anywhere at or near the speed tape in the PFD, no matter what I did with the speed knob (push, pull, turn, etc). It should work just the same as it does with setting the speed in kts, so I'm wondering what I might be missing here. Will have to check it out again.
  19. Hi all, I'm using the 1.20 version, freshly installed with no previous versions on the PC before. I have three questions concerning autothrottle behaviour: 1. The AT seems to respond very slowly, e. g. when there is a wind change (REX 2.0, wind changes softened by FSUIPC to reasonable rates) from headwind to tailwind, it will almost always result in an overspeed situation because the engines don't spool down fast enough. I would have expected the AT to react dynamically, i. e. when there's a fast change in airspeed, throttles would spool up/down quicker to compensate and adjust to the
  20. Wow, that was fast! I downloaded your fix and the Air Berlin livery is perfect now! Thanks a lot! bpcw001
  21. Recover well! Best wishes bpcw001
  22. Dear Jen Kees Blom, I've downloaded your exquisite Air Berlin livery, together with the fix for the night textures. Great work which I really enjoy a lot. However, there's a small problem with lighting in the cockpit. Please have a look at the following screenshots: AB_night_lights.jpg shows the panel condition when it's night and the panel lights are on. It shows some totally different registration. AB_day_with_lights.jpg shows how the D-ABDU is overlayed by something else when turning on the panel lights. AB_day.jpg shows the respective panel section at day conditions. All fine
  23. Great work! I wanted to post that livery request myself, and I'm quite happy to see that it has already been taken care of! Looks superb! When will it be available for download? Can't wait ... :-)
  24. I didn't know FBW can be turned off in the aircraft.cfg. Good hint, thanks a lot! At least, I found out how to enable the somewhat dead FO displays by replacing them with the versions for the CAPT :-)
  25. Hello all, I purchased and downloaded v1.20 of the Airbus X which appears to be the latest version according to this thread. Here, it says: NOSEDIVE ON MANUAL LANDING SOLVED Disabling AP on final no longer a problem. Now, having had none of the previous Airbus X versions and starting out with a fresh 1.20 install, I regret to have to say that this is exactly the issue I'm experiencing. I usually disconnect the AP about 1000 ft AGL on final to do the rest manually. I also tried to disengage the AP even earlier, always with the same result. The aircraft goes into a nose dive, and re
×
×
  • Create New...