Jump to content

Airbus Fan

Members
  • Posts

    62
  • Joined

  • Last visited

About Airbus Fan

Recent Profile Visitors

1951 profile views

Airbus Fan's Achievements

Newbie

Newbie (1/14)

16

Reputation

  1. During approach I recognized that managed speed returned in some way during descend - not as it should be, but it wanted to fly M.69/230KIAS (not 110...) during the complete descend. When I was on final approach and APP phase activated, it wanted to fly the chosen final appoach speed, regardless of the flaps setting. Maybe these findings can help you a bit.
  2. Same here on two flights, from and to KJFK. A333 v1.0.4.2. P3D v4. System: i7 10700K, RTX2080, 32GB RAM. Addons in use: GSX, ORBX packages, dozens of airport sceneries, ActiveSky. Some facts about the incedent: It happened out of nowhere and managed speed dropped from M.82 to 116 KIAS. I have not klicked a button for minutes before it happaned. I have not changed any runway during the flight up to this stage. Only fix was to fly the rest of the flight in selected mode. Loading SEC F-PLN does not help. For short times managed speed returned when conducting a step climb, but it was lost again when reaching the new CRZ level. The correct managed Mach number was always displayed on the PERF CRZ page. Of course INIT A, INIT B, PERF, even the winds were programmed for some waypoints. Here is a screenshot from the MCDU FUEL PRED page after it happaned. Maybe this includes a hint where it could come from? Not sure. ZFW and FOB seem to be correct. Step climbs did not change FUEL PRED page - not even for a moment. Hope you can somehow figure out where this problem comes from...
  3. Any updates on this? Today I experienced the mentioned problem on a turnaround flight without restarting the sim.
  4. Great to hear that, thank you! System is: P3D V4, A330 V1.0.2.0, Windows 10. PS: If you do this correctly, the nosewheel steering should not work whenever the lower ECAM indicates N/W STRG in orange (e.g. when all Hydraulic systems are shut down). Besides the status page, the ECAM indications are all implemented, but currently they have no consequences for the actual plane.
  5. What I should add: In the test with the brake accumulator down to zero I turned off all hydraulic systems. The indicator indicated no braking at all, but in fact the brakes worked perfectly fine.
  6. Hello, I recently found that the nose-wheel-steering/anti-skid selector turned to off has no meaning to the actual nose-wheel steering. It is displayed in the lower ECAM, but still everything including the nose-wheel steering works perfectly fine. The same holds for the braking system. It is simulated impressively (normal/alternate braking, accumulator) in the brake pressure indication right of the lower ECAM, but even if the brake accumulator is down to zero, the actual braking still works perfectly fine. I somehow felt "tricked" when I found this out, especially because the indication seems to work very well. Maybe you can add consequences for these two states? I don't really care too much about the specific handling of the braking (especially with the poor ground-handling simulation of the simulator), but without any pressure on the system and with the accumulator down to zero, in my opinion braking should not be possible. And if the nose-wheel steering is turned off, I should not be able to steer the nose wheel, either.
  7. Is this still recommended? Or has it been solved in one of the last updates?
  8. Hello Aerosoft, for a while now I am happily using your A333 - it brings me all over the world without issues (Airbus long-haul - have been waiting for it a long time!). Thank you for that!!! There are just three things I would like to request for future versions: 1. I would love to see OPT FL (PROG Page) working after having saved a flight and reload it. Also the timers do not continue where they stopped after a saved flight. 2. I would like to use VHF2 on the captain's side, too. At the moment I must use the FO's radio panel to tune in ATIS frequencies etc. - it is a workaround, but it feels strange to have the function, but the key on the captain's side is not operational. Maybe you can add that and make more keys functioning on the radio panel? 3. Lowest priority for me, but the weather radar seems not to be operational on the FO's side. I would be very happy to see these functions added in the near future. Thanks a lot! I do know that you are working on some other fixes, so I am looking forward to see your next update!
  9. The controller asked my whether I am on STD, I sayed yes - tested around a bit and realized the problem. But great that you are already working on it! Waiting for a little hotfix. Btw. other than that I do enjoy your A330. Cross The Pond to JFK - no issues, really like it!
  10. Hello, when I am using the altimeter pressure in in Hg and set it to STD during climb after passing 18000ft, the display shows STD, but the displayed altitude does not change. If I do this using the hPa mode, the displayed altitude changes as it is supposed to be. Maybe you can investigate this? I it happens with any pressure (obviously not with 29.92/1013 as no change in the displayed altitude should happen here). For me it looks like something is wrong with the in Hg mode of the altimeter. The problem accurs in cruise, too - if I change it just for testing purposes. So it does not depend on my flight phase. At the moment I solve this by switching the altimeter setting first to hPa and then to STD. Thanks a lot! PS: Aircraft is your A330 (latest version) in P3DV4.5.
  11. This post deals with P3d v2. I really like all the new addons (produced or published by Aerosoft) working fine with P3d v2. But as you probably know older products have some problems with the new P3d versions. Especially the lights at night are not working the way they should do. In most sceneries this is the only thing that causes problems. I see that there are planned new versions for many of those airports (e.g. Frankfurt), but on the other hand many older airports such as "German Airports 2012" will stay incompatible to P3d v2 for years. And this is the point. I like your products, and I know the patches of simmershome. I use them, too. However many of these patches are quite poor and have unwanted side-effects. I do not know how much work it is to include P3d v2 lights in your FSX-sceneries and I only ask for the airports no update is planned for in the near future. I only ask for compatible lighting (I think you know how to do that because your new sceneries are fully compatible to P3d v2) and maybe for a new installer. For example you could develop a product including patches for all Aerosoft-airports. I am pretty sure many people would pay for example 30€ for that. Please, set up a team which patches the old FSX-sceneries to make night-landings a joy again. I would very very much appreciate it! Thank you for reading this.
×
×
  • Create New...