I flew a long flight yesterday with the CJ4.  No problems (Flying south down the east coast.).  Today using the CJ4 at Denver at takeoff CTD.  Reloaded and tried again, CTD.  Restarted windows and turned off REX Weather, at takeoff CTD.  I changed aircraft to the TBM 900, same runway with REX Weather on, no problem.

    I will try again later but for now I'm flying.  😎

Bill

8 minutes ago, cwburnett said:

There is no consensus. All I know for certain is that the CJ4 mod by itself does not directly cause a CTD. I know this because a large majority of people using the mod do not experience CTDs, myself included.

However, people on various threads on various forums and on our discord have said the following things stopped their CTDs:

-Rolling back NVidia Driver

-Not using FP Sync

-Removing Navigraph Data

-Removing Navigraph Simlink

-Removing 3rd party scenery

-Not using the world map other than to specify departure point

-Not using simbrief import and instead using LNM to import to the world map

-Not using LNM import to world map and instead using simbrief to import to the world map

-Not using either LNM or Simbrief on the world map, but instead using the simbrief FMC import

-Disabling processor overclock

-Disabling GPU overclock

-Disabling live weather

-Disabling Rex

-Disabling live traffic

-Disabling AI traffic

-Disabling rolling cache

-Removing FSUIPC

-Removing mod XYZ from their community folder

We have provided Asobo with many crash dumps and they report that in each dump we've provided, including a number from people in this thread, none of them point to anything related to the plane causing the CTD, but rather a failure of some drawing of something - at an airport or scenery related - I don't have the exact specifics.

At least one person has reported each of these solutions to us - that by doing one or more of the things above they now don't get CTDs in the CJ4 anymore. I think the conclusion we're coming to is that there is no pattern and no specific thing we can do to eliminate the crashes, which is unfortunate, but reality as of today. Clearly some of the "solutions" are contradictory. How one person can say "I don't get CTD if I use the world map for LNM import" and then someone else comes along and says the opposite is what is causing their problem...

We will continue to look at and review CTD reports, we will continue sharing info with Asobo in hopes of finding a smoking gun, but in the meantime we will continue adding features and capabilities for the majority of users that aren't experiencing CTDs.

We continue to advise not using the FP Sync feature since it does try to sync nav data back to the sim that is more detailed in our FMC than in the game flight plan, but at the same time, people do use it and aren't getting CTDs...

I wish I had something more definitive to say, but I do not.

Interesting! I'm pretty sure we eventually find out what causing it. Here are some points on my side:

1. I have never had any CTD with stable version before!

2. I fly the same routes with different aircraft and don't have CTD. That to to illuminate possibility of scenery conflict or nav MSFS stock data bug (I don't use navigraph)

3. As I do not use any extra overclock with my i9-10900 and RTX3900 respectfully, and I don't have CTD with aircraft almost 99%. Neither I have CTD with any working title mods like G1000/3000  in another aircraft 

4. I'm trying to figure out a possibility of conflict with another 3rd party mod. I wonder for example if FBW320 could be a cause because I use FBW unstable build ?

My personal educated guess that is some kind parsing error specific to a flight or conflict with another mod that causing CTD. Because every CTD I have with CJ4 precedes fps freezes. 

21 minutes ago, cwburnett said:

However, people on various threads on various forums and on our discord have said the following things stopped their CTDs:

Lists like this must be the kind of stuff that make developers bang their heads off the wall...kudos to sticking in there and trying to find the source!

I do feel like there has been a general increase in instability for me since the last patch globally, not just when using the CJ4.  It also seems like just when I think I’ve figured out what is causing it, I get a few flights in successfully, then another CTD pops up.  It’s like whack a mole.  

24 minutes ago, bendead said:

Working great, thanks 😉

Also, Is it possible to change the zoom level without going inside the PFD menu?

The far right knob that says "RANGE" will adjust the range for the MFD and PFD together as in the real aircraft.

The plane spawns without interior for me. Anyone know what could be causing the problem?

 

EDIT: Problem solved itself.

Edited December 28, 20205 yr by FlyerNYC

1 minute ago, cwburnett said:

The far right knob that says "RANGE" will adjust the range for the MFD and PFD together as in the real aircraft.

Cheers, I really need to stop working that much. I thought it was the control for the weather radar dish.

1 hour ago, sd_flyer said:

Interesting! I'm pretty sure we eventually find out what causing it. Here are some points on my side:

1. I have never had any CTD with stable version before!

2. I fly the same routes with different aircraft and don't have CTD. That to to illuminate possibility of scenery conflict or nav MSFS stock data bug (I don't use navigraph)

3. As I do not use any extra overclock with my i9-10900 and RTX3900 respectfully, and I don't have CTD with aircraft almost 99%. Neither I have CTD with any working title mods like G1000/3000  in another aircraft 

4. I'm trying to figure out a possibility of conflict with another 3rd party mod. I wonder for example if FBW320 could be a cause because I use FBW unstable build ?

My personal educated guess that is some kind parsing error specific to a flight or conflict with another mod that causing CTD. Because every CTD I have with CJ4 precedes fps freezes. 

The FPS freezes are interesting - just did a couple flights with the recent storm and got major freezes on both Approaches (1 RNAV 1 ILS) with an older system far inferior to your specs FWIW

Just now, Flyfaster_MTN002 said:

The FPS freezes are interesting - just did a couple flights with the recent storm and got major freezes on both Approaches (1 RNAV 1 ILS) with an older system far inferior to your specs FWIW

I had similar freezes in custom FMC in XP11 especially in IXEG. Most of the time they would just go away. I had fair share of CTD with IXEG followed freezes.

 

Any way I will try to remove FBW320 and G3000 mod and see what gives

19 hours ago, cwburnett said:

On the FMC go to IDX -> Page 2 and select MOD SET to get into mod settings menu. Enter your correct pilot id and press the button next to the simbrief id. You can also delete or by hitting clr/del and then clicking the select button next to the ID.

Ok - thank You again. I got this working now as I did it a correct way. I tryed change the ID number into Route Page before and not into MOD SET settings menu.

These guys continue to amaze me...looks like the next update might add hold functionality!

I've had a chance to use ver 8.3 and I'm happy to report the oscillations are gone.  I still get CTD right after takeoff every few flights. Usually clears when I open MSFS and try again.  Still has some wonky flight characteristic in Turbulence with high tail winds.  It reminds of a model airplane hanging from one string on the ceiling and the way it moves when bumped.  But overall a great improvement.  Issues and questions...

1.  Whenever I load a flightplan from simbrief or route page on the FMC the route loads perfect, but the airport frequencies on the Frequency page are usually wrong or 000.00.  Only way I can avoid this is to load the entire flight plan manually.

2.  Can Vnav/Approach mode be used on visual approaches created in FMC or is it just for lateral reference? If so is there a way to calculate the gp intercept altitude for the waypoint thats created at whatever distance you choose?

3.  I still get the sudden altitude changes whenever the baro changes above FL180

All in all great job, can't wait to see what you guys have in store next!!! 

10 minutes ago, Novej757 said:

I've had a chance to use ver 8.3 and I'm happy to report the oscillations are gone.  I still get CTD right after takeoff every few flights. Usually clears when I open MSFS and try again.  Still has some wonky flight characteristic in Turbulence with high tail winds.  It reminds of a model airplane hanging from one string on the ceiling and the way it moves when bumped.  But overall a great improvement.  Issues and questions...

1.  Whenever I load a flightplan from simbrief or route page on the FMC the route loads perfect, but the airport frequencies on the Frequency page are usually wrong or 000.00.  Only way I can avoid this is to load the entire flight plan manually.

2.  Can Vnav/Approach mode be used on visual approaches created in FMC or is it just for lateral reference? If so is there a way to calculate the gp intercept altitude for the waypoint thats created at whatever distance you choose?

3.  I still get the sudden altitude changes whenever the baro changes above FL180

All in all great job, can't wait to see what you guys have in store next!!! 

Do you have the latest hotfix? It took care of these issues.

For anyone experiencing regular CTDs with the Working Title CJ4 v0.8.3, there is a new channel dedicated to CTDs on our discord. We have posted there a beta test build that we're inviting people that do have CTDs to test. If you're having regular CTDs, I'd encourage you to go there and get the latest build and provide your feedback via discord in the #cj4-ctd-temp-channel.

 

58 minutes ago, Flyfaster_MTN002 said:

Do you have the latest hotfix? It took care of these issues.

Is the test version on the discord temp channel the hotfix for version 8.3?  Or is there a separate version 8.3 hotfix somewhere?

3 minutes ago, Novej757 said:

Is the test version on the discord temp channel the hotfix for version 8.3?  Or is there a separate version 8.3 hotfix somewhere?

The latest official version is v0.8.3 available via our github here: https://github.com/Working-Title-MSFS-Mods/fspackages/releases/tag/cj4-v0.8.3

The discord temp build, which is v0.8.3b-beta1 is the CTD test build and should ONLY be used by people actively testing CTD behavior.

Edited December 29, 20205 yr by cwburnett