Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

A300 new build test - AC went haywire on approach

Featured Replies

So, after a hiatus from 2024, I have returned to it a couple of days ago to see if/how things got better. The ATC is still a circus - assigning me initial altitude of 1200 feet when my cruise is FL240 etc... But mainly I wanted to test the new iniBuilds A300 version that came out today before I splurged on their A350. Did a short flight from FAPE to FACT and on approach everything on the flight deck froze - all instruments were stuck in their positions, nothing in the cockpit would click. AC was still responding to manual control input but barely and ended up being uncontrollable. Is this a thing that happens to any of you? Or maybe just with that aircraft? It was a deeply frustrating experience and needless to say, I will be holding off purchasing that A350. I am gonna try again tomorrow and see if I fare any better, but yeah... this was a thing that happened today. Forgot to mention - I am on the SU2 Beta, latest one - 13. 

Edited by BostonJeremy77

I can’t say I’ve had that issue on the A300 but I also haven’t flown with the latest patch yet.  Hopefully they didn’t introduce a new issue, sounds like maybe a WASM issue.  I also haven’t flown it in the SU2 beta.  

The only thing I had happen was a few patches ago when both engines stopped on short final into EBBR…only happened once though.  Rumour has it that wreckage is still sitting in the farmers field I came down in.

Edited by regis9

Dave

Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU

  • Author
2 minutes ago, regis9 said:

I can’t say I’ve had that issue on the A300 but I also haven’t flown with the latest patch yet.  Hopefully they didn’t introduce a new issue, sounds like maybe a WASM issue.  I also haven’t flown it in the SU2 beta.  

The only thing I had happen was a few patches ago when both engines stopped on short final into EBBR…only happened once though.  Rumour has it that wreckage is still sitting in the farmers field I came down in.

It did sound like a WASM crash to me... cause everything basically stopped including the backup instruments. I believe that has happened before on 2020 a couple of times, notably with PMDG 737s, but I haven't seen this in 2024 yet. I am gonna try again tomorrow. Hoping for a better flight. The last 10-15 I have done were OK, though none were with ini buses. 

It happened to me often. Is a WASM crash indeed. A workaround for me is at the first flight when everything is loaded, give a restart of flight and then I hadn’t any crash or freeze. You can try that. This is an issue with inibuilds aircraft, had same freezes with A321 default, so a restart after initial start is working for me.

Edited by David27

  • Author
1 hour ago, David27 said:

It happened to me often. Is a WASM crash indeed. A workaround for me is at the first flight when everything is loaded, give a restart of flight and then I hadn’t any crash or freeze. You can try that. This is an issue with inibuilds aircraft, had same freezes with A321 default, so a restart after initial start is working for me.

So without setting everything up, hit Escape and "Restart Flight"?

27 minutes ago, BostonJeremy77 said:

So without setting everything up, hit Escape and "Restart Flight"?

Exactly, that should work. 

  • Author

Thank you. Will try. It's frustrating cause that's a couple of hours of my time down the drain for it just to stop working on approach without any fault of my own. 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.