3 hours ago, Bunkie said:

Call me an word not allowed, but I tried a 7th flight.

Set up exactly the same as all the previous ones. Only loaded 20 passengers, and actually got off the ground at the calculated V speeds.

Autopilot engaged... following heading, and VS. Turned to intercept the nav course (I didn't have a SID programmed) and lined it up. Engage LNAV... aircraft does a 360. Entered a Direct-to - as I probably should have. The aircraft now flew about 70 degrees away from the planned course. Then decided that 360's are more fun.

Okay. Back to PMDG and Fenix.

This baby just isn't ready for prime time - at least on my system it isn't.

Thanks for doing the test run for the rest of us.

Man, that's too bad about some of the issues. I was looking forward to getting this since I'm an old JustFlight/Wilco Classic 737 fan (Still have the box and CD) from the FS9/FSX days and I miss those old classic 737's. That sound of the trim wheel from that addon were so unique to that aircraft.

I'll wait a little and hope it matures a bit. But I'll be be watching and following closely.

4 hours ago, Bunkie said:

Engage LNAV... aircraft does a 360. Entered a Direct-to - as I probably should have. The aircraft now flew about 70 degrees away from the planned course. Then decided that 360's are more fun

Someone else on the discord was experiencing this and turns out they had a FFB yoke which was interfering with the systems.

If you have one try disabling the FFB portion of your yoke? Just a guess as it’s the only report I saw of the plane doing 360s

For context I’m not a dev.

4 hours ago, Lucky38i said:

Someone else on the discord was experiencing this and turns out they had a FFB yoke which was interfering with the systems.

If you have one try disabling the FFB portion of your yoke? Just a guess as it’s the only report I saw of the plane doing 360s

For context I’m not a dev.

I wonder how could it interfere because of FFB. FFB merely mimic actual yoke movement in the cockpit

5 hours ago, Lucky38i said:

Someone else on the discord was experiencing this and turns out they had a FFB yoke which was interfering with the systems.

If you have one try disabling the FFB portion of your yoke? Just a guess as it’s the only report I saw of the plane doing 360s

For context I’m not a dev.

Nope, no FFB yoke here, just the Thrustmaster Boeing yoke and Honeycomb Bravo throttle. But thanks for trying to find a solution for me!

Another issue I hadn't mentioned was that the framerate dropped significantly as soon as I hit LNAV; I wasn't able to determine if that was the CSS 737 or SU5 doing it's usual thing.

There's lots to love about the model - hand flying was excellent. Hopefully future updates will tame it.

Any good Qantas 737-400 community-made liveries-there’s of course a a very nice Qantas 737-300 VH-TAH on the CSS Launcher?

With the CSS 737-300/-400/-500 now available individually for $45, going to get them finally!

On 6/6/2026 at 9:29 AM, michap7 said:

Maybe I overlooked something here: Didn´t they also plan to release freighter versions of the 737? Or will they be released later on?

No one?

13 hours ago, Dreamflight767 said:

Thanks for doing the test run for the rest of us.

There's definitely a systems bug here but also a bunch of operator error so I would take it with a grain (perhaps half a cup) of salt.

8 hours ago, sd_flyer said:

I wonder how could it interfere because of FFB. FFB merely mimic actual yoke movement in the cockpit

The same thing occurred with the tristar when V1 was streaming it. Why that happens I haven’t got a clue.

1 hour ago, michap7 said:

No one?

They will be released later on as $10 addons that require ownership of the passenger equivalents. Though I’m not sure if it’ll work like the TFDI model where it’s vice versa

3 hours ago, mspencer said:

There's definitely a systems bug here but also a bunch of operator error so I would take it with a grain (perhaps half a cup) of salt.

Could you elaborate on what his user errors were?

There's not a lot of value in stating he made a bunch of user errors, but then not pointing out what they were; so that users can isolate what the bug elements are.