Throttle issues appear to have been rectified with this 5th patch today!
But… appears to default to Mach number for FLC will have to look at it closer later.
And the livery still flickers….
1 Like
Are the lights fixed? Specifically landing or taxiights.
I didn’t check… will do in a sec and report back!
Just checked - taxi / landing lights - appears fixed pointing forward and lighting the runway appropriately!
And on the Mach thing, disregard, appears to have been user error! 
After a good check up, it appears the CJ4 is behaved as it did in 2020 - with the exception of the livery flicker.
Also, it would be great if the checklist in the MFD were back, if not the safety announcement also!
2 Likes
After reading about the updates, I gave it a shot with a short flight from KGRB to KMKE.
Flight performance was acceptable, but there were issues.
There was one waypoint (ADELE) on the route to get me into a straight in approach to RWY 19R. The CJ4 failed to turn and flew straight past the waypoint. I had to go back into heading mode and work my way back to the waypoint, where NAV mode finally picked it up and flew me in properly.
The PFD and MFD maximum brightness seems low and was hard to read from the default viewing position in broad daylight. I had to zoom in to them to get the eye adaptation to stop and brighten the view. I’ve had a disdain for the eye adaptation feature even on FS20, and it seems worse now unless the FD’s are really that much dimmer.
The taxi and landing lights, I don’t know how true to life they are now, but would prefer them brighter. This is just a personal preference across all aircraft, really.
I couldn’t load passengers at departure because the ATC function wasn’t available. When I parked at the destination, it was available and I tried to request boarding. When the bus magically appeared and people started walking into the side of the nose, my frame rate turned into a slide show. I was 60 fps nearly the full flight until then. I expected some frame rate reduction, but that much is excessive and I don’t get that in career mode with loading passengers into other aircraft.
Oh, and of course the flickering livery textures, including bad texturing on the engine fan blades when running.
I’m still unable to work this plane and I don’t know if it’s just me or what. No one else seems to be posting these issues, but I don’t know what I could possibly be doing wrong. That said, the checklist in the EFB only has like 4 items so maybe I’m missing something?
As soon as I start an engine it goes straight to 100% and doesn’t respond to any movement of the throttle, either directly moving the lever in the cockpit or my peripherals. Every other plane works correctly so I don’t see how this can possibly be a binding issue. Moving my hardware throttle correctly moves the throttle in the cockpit. With the levers at 0% both hardware and cockpit, the engines are still stuck at 100%. Once the second engine is lit and goes to 100% the brakes no longer hold and the airplane just runs away and crashes.
Is there some step I’m supposed to be doing that isn’t in the incredibly sparse checklist on the EFB?
Hmm just saw this. I’m not doing landing challenges, just basic free flight. HOWEVER the two times I’ve tried this I was in VR, got the bug where you can’t click Start Flight, then had to exit VR and click the button. So tl;dr it took me a minute or so before I did click it and I wonder if it might be similar. I will try to remember to try again tomorrow but be in 2d mode when starting the flight and see if that “fixes” the engines.
Just tested this again in 2d mode, clicking Ready to Fly right away, removed the important bits then jumped in and started up all within a very short time.
Same issue, engine goes right to 100% power after startup and the throttle has no effect.
Sounds like a binding problem somewhere…
I am no longer having any throttle issues since the last update.
As I stated above, I’m 99.99% sure it isn’t a binding issue. It makes zero sense for that to be the issue when 1) My binds are correct for every other aircraft in the sim and 2) My binds correctly move the throttles in the cockpit and 3) Moving the throttles in the cockpit by the mouse also has no effect
Further more I can see now in 2d mode something I missed in VR which is there is a blue bug at 100% throttle implying something like an autothrottle setting that 100%. I can’t find a AT button anywhere though?
Als I’m now getting a new issue which is as soon as I get in the aircraft before I even apply power, there is a constant chime from the master caution like once a second that never stops.
There’s no AT on The CJ4.
Can you post a screenshot of what you’re seeing?
Airspeed is only used for FLC…
The blue bugs have always been there, but should not have any effect.
Are you referring to the blue marker on the MFD on the power gauge (not sure the specific term)? From my understanding, that is supposed to be an indicator of where to set the throttle for optional fuel economy at different phases of flight. I don’t think that is accurately modeled in the sim and it just leaves it pegged at 100%. The CJ4 itself does not have an auto-throttle, so those bugs are meant to be used as a guide for manual throttle setting.
For what it’s worth, I’m not experiencing the full power issue, but I’m using an Xbox controller with throttle increase and decrease custom set to Y and B respectively (blame FSX for getting me use to that binding).
Here are a couple screenshots. The first I grabbed fast as it was spooling up, you can see the blue bug that appeared and the thrust goes right to that as you can see in the second screenshot. The third is just zoomed out to show the throttle levers are in idle position.
Also apparently the annoying master caution is from the parking brake. It keeps dinging comnstantly until I release the brake. Can’t even clear it 
So this is at start up?
If so there is going to be a run up of the engines as they spool up under FADEC control.
Do they not stabilize to idle after start up?
The blue bugs are as per the post above…
May try a complete reinstall, I did it once already, took 15 minutes.
Already done a complete reinstall. I see no value in doing a second one. Yes this is at startup and they are still there at 100%.
Are you on xbox or pc? I’m on PC. Seen some planes already that work fine on Xbox but not on PC.
Yeah, that is really odd.
I have nothing…
I think this is to alert of the conflict of parking brake and what it perceives as full throttle, so I would expect that issue to resolve itself when the throttle is figured out.
I also noticed you have avionics set to dispatch mode. What happens if you turn that switch to the on position to activate everything before you fire up the engines? I never bother with the dispatch mode.
Nope, no change. I also disconnected ALL peripherals so it most certainly isn’t a binding issue.
To hit 100%, unplug all of your HW peripherals, then load into the plane and see if you’re still getting the engine 2 issue.
There have been so many weird controller interactions posted here over the years, you never know if there’s one lurking.
LOL, never mind then!
Can you describe your exact startup procedure, step by step, including how you are interacting at each step (i.e. mouse or hot key)? A video along with the description would help too.
Also, what happens if you CTRL+E short cut the process?
Actually I think you were right. Disconnecting everything didn’t change anything. But then on a whim I restarted MSFS and it did. Now I don’t have the issue.
So it’s almost like some binding that is only resetting when the sim is restarted. So I need to go through one by one restarting each time to track it down
Still seems incredibly odd that no other plane has any issues but I’ll know more once I track it down.
2 Likes