CJ4 Community Mod by Working Title Released

I installed v0.5.1 and tried it out for two flights. In one case, flying an instrument approach with ceiling below 1,000 ft, the autopilot was wandering above and below the ILS glideslope in approach mode. It seemed to be trying to follow the glideslope, but I wonder if either the Asobo modifications in the recent patch or the PID changes in the mod have tried to slow down the oscillations to such an extent that it wanders up and down a lot before correcting. Is anyone else seeing this behavior?

i just did a flight at EHAM with the CJ4, 27knt wind with gusts to 39, and it followed the glideslope perfectly (untill windshear happened). so no, not here

There are no autopilot PID changes in the mod

1 Like

Not sure if this belongs to here - as I expect this is a general problem, hoewever most obvious to me in CRJ4 with this great mod;
my problem: the FMS does not show any departure nor destination. It also does not show any legs, even the FP is loaded in the background.

  1. for me it’s not possible to enter the departure airport into the FMS… it “accepts” it i.e. the ICAO letters disappear (no error msg) but the FMS itself does not show the “origin”… same with destination.
  2. if I plan the route before start, the FMS is also empty…however it somehow seems to be loaded in the background as I can select FMS as source and the AP follows the legs with “NAV”… but the MFD is empty (no route showing) as well as the FMS itself.

Any help would be appreciated.
Hint (I hope it’s not the case); I installed the sim on another drive than C:\ and on another drive than my usual steam software…

Never heard of that yet. Are you on the latest 0.6.0 version?
This thread here is very old, of the first version.

Found bug on descent PFD freeze and drop speed to zero, then after 20-30 sec it back and show huge overspeed.

Try getting the latest version v0.6.0 if you don’t have it already.

Thanks @dga711 and @DabullAir - affirm, I am on 0.6.0 - and I have this problem since the first version; my MFD never showed anything and I never could enter my ORIGIN nor DESTINATION in the FMS… in the earlier version I even had an error message.
I also get an error message when I try to enter a waypoint; “Doubles Found”.
However, this is not only in the CRJ4 - this happens in all planes…

It was exactly with 0.6.0, never saw it with 0.5.1

It was my bad, I didn’t switch on pitot heat and it was simply iced that time.

I’m having a hard time keeping up speed in the aircraft. I’m currently on my way from Rotterdam (RTM) to Vienna (VIE) at FL360, and the aircraft is struggling to maintain speed.

My ZFW is 11160lbs, and I took 3300lbs of fuel with me. Payload is 800lbs.
I’m currently cruising at FL350, and have a tailwind of roughly 28-29 knots.

My IAS is now 205, with an N1 of around 86-87%. From what I can see that’s even slightly beyond the climb detent. Whenever I move the throttles back to the cruise detent, I immediately lose speed to even a situation in which the aircraft stalls.
By the way, I use Simbrief in concert with K20017’s A/C profile to dispatch my flight.

I’m not sure whether this is caused by an inaccuracy in the sim or by my own fault.
Does anyone have any pointers? Thanks!

Ignore the detents, until we implement FADEC they will not be of any help. You will need throttle full forward for climb above 30k and cruise at whatever power setting gets you to your desired cruise speed. You can’t hurt the engine, it won’t exceed 100% N1 right now.

4 Likes

Check, thanks for clarifying!

hey,
i´m having a problem with the version 0.6.1.
The engine run stop buttons will always stay on “RUN”.
It is not possible to start the engines.

Have anyone an idea what is causing this problem?

Above FL260 use Mach number instead of IAS.

I updated the CJ4 from Profile page to ASOBO version 0.1.46. Now when I try to load the program it crashes before opening. If I remove CJ4 0.6.1 from community program loads OK. Tried putting CJ4 back in community, same problem. Any ideas?

I am on 0.6.1 and my run stop button was working until this evening. I am now experiencing the same issue. When I turn on the battery, the run stop button is already lit, even from a cold start.

Afaik this is usually caused by an (usb) controller that has an axis tied to Mixer/Fuel things.

Try to disconnect your controllers and it should work. So you have to check your input settings and unbind that.

Somehow Asobo connected Jet engine things to that setting too.

Hi all,

Head over to the latest thread to find our new version, 0.7.0!

2 Likes

Closed as new Development thread released.