We have at this moment problems with e-mails coming to us via Microsoft servers (Outlook, Hotmail, Live, etc). We are in contact with Microsoft to solve this issue.

Jump to content

tgcbraun

Members
  • Content Count

    60
  • Joined

  • Last visited

Community Reputation

2 Neutral

1 Follower

About tgcbraun

  • Rank
    Flight Student - Airwork

Recent Profile Visitors

1048 profile views
  1. So, I have purchased this airport via the MS Store and cannot complete a flight to it. Second attempt that resulted with a Crash about 2-5 miles out of the aiport with my default C152. Generally my sim is pretty stable and I have not experienced crashes recently even though I am actively using it. Some information from the Eventlog: Crash #1 Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f5b8327 Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f5b8327 Exception code: 0xc0000005 Fault offset: 0x00000000012a9988 Faulting process id: 0x48a8 Faulting application start time: 0x01d694ba3379a777 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: 943233bc-4c99-4142-8451-52996b571618 Faulting package full name: Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Crash#2 Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f5b8327 Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f5b8327 Exception code: 0xc0000005 Fault offset: 0x00000000012a9988 Faulting process id: 0xd2c Faulting application start time: 0x01d694b0bd637752 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: a19a6fb3-6700-42ba-9a19-aa62c21a25bc Faulting package full name: Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Not sure what kind of additional evidence I can provide. The crash does not seem to be reproducible when I start from the Airport.
  2. I do understand, thanks for the sensible comment. The scenario itself should not be that complicated to re-create, as it involves basically the aircraft not bleeding its energy off during approach. I will conduct additional flights in the next days and try to record a video if the issue happens again.
  3. So, reporting issues is worthless now... I have actually stopped using the A330 until it improved, as I am not keen on having such issues after a long-haul flight. I am also not a paid tester, but rather a consumer who has bought a product that clearly has issues. A screenshot has been shared on the first post showcasing my winds and throttle configuration and also a pretty clear description of the situation. This same problem has been now confirmed to be reproducible by multiple costumers. I think the ball is now with Aerosoft to try to reproduce this. If someone else can offer that video, great!
  4. I am not saying that the A330 behaves normally like that. I am saying that happened in one of my approaches (and apparently reproduced by others as well). It has nothing to do with how the real behavior of the aircraft as represented in the simulator...I repeat: 10kt headwind, speedbrake, gear down, flaps full, one engine off and the IAS would not bleed off. If you find one real A330 pilot that says that is normal, I"ll shut up. Unfortunately this over-defensive position, basically looking down on long-time costumers and dismissing them as some sort of incompetent user is not really what I would have expected here...
  5. Hey Mathijs, I am aware that you guys have been receiving multiple reports from people that you may not know the background, but I am what you would consider a hardcore simmer with pretty much every study-level aircraft available, including the PMDGs, FSLabs and others. The behavior that I experienced with the A330 was clearly something else. I repeat: the aircraft had the engines off, speedbrakes, full flaps and gear down and even then it would not reduce the speed considerably when descending. I am sure this is not being caused by Activesky...
  6. As seen in the screenshot, I was having partial headwind of 10 knots using Activesky. For me it is clear that this is a bug.
  7. Yes, I might have had some turbulence on the approach. The engine sound did not increase at all on my side.
  8. No, there is not. As mentioned, the IAS did not bleed off even when I turned 1 engine off and was descending with full flaps, speedbrake up and gear down.
  9. Auto throttle is off and throttle is on idle position. If there is thrust, this seems to be a problem, no?
  10. Just experienced a very weird issue during approach. As seen on the attached screenshot, my plane was leveled at 7.000 feet, ATHR was off (with throttle levers on idle) and the IAS kept raising... This situation continued until landing and even with the two engines off, full flaps and speedbrakes on, I could not reduce the speed while on the glide-path.
  11. I am experiencing a similar issue with my Thrustmaster Warthog. I use it with the FSLabs Airbus and the FFA320 and the input in the A330 is definetely laggier.
×
×
  • Create New...