dc10boy

Hi, I noticed both engine oil pressure warning lights beneath the engine indicators illuminate when annunciator lights in test, but fail to illuminate on engine shutdown.

I'd like to second this comment. All the push switch and annunciator lights on full bright look more like the dim position in the actual aircraft. in daylight conditions the lights are pretty hard to see.

Hi All, I did a few flights in both the GE and P&W variants and am not hearing an altitude alert tone either when approaching and capturing an altitude selected in the FCP, or deviating from the altitude selected in the FCP.

After a re install where I deleted the work folder (I think this was the key) Iflew the ORD MIA leg without any problems. FMC loading worked without any WASM issues at all. It was a great experience. IRL I worked COs A300B4-203s and as an AA mechanic worked our -605Rs at ORD from '90 until their retirement. you guys really hit this one out of the park! I felt right at home being back in the "Bus" Thank you. Stan

After a re install where I deleted the work folder (I think this was the key) Iflew the ORD MIA leg without any problems. FMC loading worked without any WASM issues at all. It was a great experience. IRL I worked COs A300B4-203s and as an AA mechanic worked our -605Rs at ORD from '90 until their retirement. you guys really hit this one out of the park! I felt right at home being back in the "Bus" Thank you. Stan

I've managed only 2 flights without WASM crashes in SU 14, and they were just local circuits around DEN and MIA. Since SU 15, none. Sim is updated to SU 15 and otherwise normal, no CTDs or weird behavior. Today I reinstalled the aircraft, and attempted to fly ORD-MIA KORD/09R N0461F350 DCT CMSKY DCT CARYN DCT CYBIL DCT PXV DCT HITMN DCT ACORI FROGZ4 KMIA/08R planned on Simbrief. I tried about a dozen times, each attempt ending in an aircraft freeze/WASM crash before I could leave the gate. I tried with the latest Navigraph database and default. I tried manually loading the aircraft, and importing from Simbrief. I tried manually building the OFP in the FMC and importing from Simbrief.The result is always the same. I found if I added the route first, and waited to do the init page 2 data, I could add the departure runway, arrival STAR and approach without a crash. EVERY time I entered the CG from the EFB, it would WASM crash. If I enter the init page 2 data first, EVERY time I added the arrival STAR and approach, it would WASM crash. I tried entering this data both during IRS alignment, and after. I tried during fueling, and after. I literally tried every possible sequence programming the FMC. All result in this crash. I'm at a loss, could SU 15 have borked the WASM code? No other aircraft I fly have had this issue, including the Flythemaddog MD-80 or TFDI MD-11. Any ideas?

Guys, this is SO bad. The aircraft is unflyable, I can't even get off the gate, as the cockpit freezes just by accomplishing basic FMC functions, such as adding a departure runway, or a STAR or arrival runway. I've made 7 different attempts, and the result is the same. Sim continues to function, all aircraft functions freeze. What worse is there has been no response to these reports. Why is nobody from INI on this forum responding to these issues?

FWIW, that same KMKE circuit flew normally using other aircraft.

Nope, Even the GE model WASM crashes when I try to fly out of MKE. Maybe something in the navdata? WASM crash occurs repeatably when clearing the discon between the T/O runway and the final approach fix. EFB shows fueling still happening . it's counting fuel added, but entire aircraft and all displays frozen.

I've noticed that the automatic slide arming/disarming setting is not working. it has to be done manual. In the airline industry we have this mantra..."If you blow the slide you have to take the ride" Wheee go down the slide!

FWIW, I just flew a KMIA circuit using the same procedures in the GE bird with no faults.

Sorry, I should have also added that I'm running SU14, not any SU15 Betas.

I bought the A300 last week and got a couple of flights in using the GE version. The aircraft is updated to the latest version. I'm quite well versed in the operation of the aircraft. I've made 7 attempts for a simple KMKE/KMKE circuit ( with the beautiful new Ini Scenery) departing on RW 19R and returning to the ILS 19R. every single time a WASM crash stopped the aircraft from responding to any inputs, while the sim continues to function. many simple actions seem to trigger the crash such as starting the APU, (hung, would not start or restart.) loading weights from EFB, programming FMC, clearing route discons, etc. all result in CDU and FCP going blank and aircraft no longer responding to inputs. I will re test the GE version, and see if it's any better, but this 40$ aircraft is pretty much un flyable. I'm running W11 with an I7 14700K a 4070TI super and 64GB Corsair Veangence RAM. This runs any other aircraft and scenery combination with great performance.