[MSFS2024] Cessna Citation CJ4

While I haven’t flown the CJ4, I did look at it in the flight setup screen and the livery texture flickered on it there.

3 Likes

I am experiencing the textures flickering problem too.

1 Like

There is some sort of flooding lights in the cabin that cannot be turned off (or at least I didn’t manage to find a way to turn it off).
This is particularly annoying during night:

In this screen every possible light that I know was turned off except for avionics screen and integer lights.
CDU birghtness control is not working and right CDU is stuck at max brightness.

4 Likes

Issues noted:

  1. Exterior livery flickers and looks washed out as in pastel colors.

  2. No engine indications while in dispatch mode at engine start.

  3. Flaps fully extend or fully retract when using a controller binding, instead of extending and retracting in increments.

3 Likes


My alt indicator only showed a black box till about 10000 feet then it started to look like the picture. At about 23000 it was the full number but it was 10000 feet off from the standby.

Can not give any useful feedback as using this aircraft results in me getting the well documented VRAM bug and my FPS plummets to almost single figures, rendering it unflyable.

Not selectable for any career VIP mission, despite costing over 7mil credits.

3 Likes

I noticed the same thing on the Baron…

Unable to select the middle flaps position using any controllers flaps up/down - always goes full scale full down or full up.

Throttle issues - lots of twitching. Unable to find any conflicts. Achieves around 30% TQ with full throttle. Does not happen with same controller settings on other aircraft.

Livery Flickering on external view

2 Likes

I had to modify my Bravo throttle quadrant for the flaps and disable the paddle and enable the axis on the far right. Check out the Working Title Discord channel, Discord
:grinning:

Yes, as a workaround I also managed to use an axis on the Bravo for Flaps.

The CJ4 Flaps issue is fixed in the 1.2.7.0 patch. The jittery throttle issue is not, so the aircraft is not controllable.

Have tracked down the Jittery Throttle issue:

It is tied to the Autopilot and FLC setting.

Setting a higher FLC speed will cause the jittering throttles to increase, reducing the FLC speed will reduce the jittering throttles. No controls are set to Auto Throttle.

The CJ4 AP is not supposed to be able to change throttle settings.

EDIT: This dependency on the FLC setting applie event if the AP is disabled.

The flickering on external views is still present for me after the latest patch.

2 Likes

Same here. IT’s flickering on all default liveries.

2 Likes

I’m disappointed too at the lackluster updates in the Dec 10 release. This plane is not flyable for me either. hmmm, back to Condor 3 in the gliders for a while I guess

I went to the Flysimware Learjet 35 for now until the CJ4 is updated fully.

Flysimware updated it for 2024 sometime last week I believe and it works flawlessly…

Does this plane actually WORK for anyone?

I tried it today. Started according to the EFB checklist, and after both engines were started I was suddenly zooming along the ground, despite the parking brake being set, my toes firmly down on the brakes, and the throttles at idle, confirmed with the visual throttles in the cockpit.

After crashing and being put “back on track” a bit above the ground, suddenly I didn’t have ENOUGH thrust even with the throttles at FULL power.

It’s like the throttle doesn’t even work and just does what it wants.

I am not having it run a way, but brakes seem less effective in a short hop l just did…

Also, the throttle binding is off somehow, I was able to set for take off, but once airborne bringing the throttles back reduced the in cockpit throttles to idle and would not move forward with the throttle binding only with in the cockpit with the mouse.

I tried moving them both with the mouse in cockpit and with my hardware. In both cases the throttles in the cockpit MOVE but have no actual effect on the output of the engines.

Yeah, now that you mention it.,.

This was not an issue before the latest patch!

Aargh….:grin: