CJ4 v0.8.x: CTD Reports #608
Comments
cwburnett
added
bug
|
CLIMB |
|
CLIMB First CTD 2-3 seconds after rotation on takeoff. Second CTD in Climb after about 4 minutes in flight. |
|
PHASE OF FLIGHT: Departure/Climb |
|
PHASE OF FLIGHT:climb |
|
@sdflyer001 @BostonJeremy77 @WinstonCh @odourboy |
It was flight plan generated by MSFS->high altitude |
|
My plans were generated by MSFS flight planner. Low altitude (11,000 feet cruise planned). I did go and reconnect discontinuities directly in FMS. |
|
So there could be a common theme in all the CTDs as in that the flight plans came from the world map. COULD be a pointer in the right direction. |
|
Airport names were automagically transferred from the world map for me as
well. I added the departure runway (only) via the FMS.
…On Wed, Dec 16, 2020, 9:04 PM DG, ***@***.***> wrote:
So there could be a common theme in all the CTDs as in that the flight
plans came from the world map. COULD be a pointer in the right direction.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKJOKDCZXR47ZBJZ2BDHVPTSVFRMTANCNFSM4U6IVRVQ>
.
|
|
Attempted @odourboy 's repo instructions as well as my own. Flew both departures to FL250 without CTD. |
|
Well hell! What can I say? Lol
I'll try again tomorrow from cold and dark. See off that changes anything.
…On Wed, Dec 16, 2020, 10:43 PM Sean Connolly, ***@***.***> wrote:
Attempted @odourboy <https://github.com/odourboy> 's repo instructions as
well as my own. Flew both departures to FL250 without CTD.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#608 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKJOKDHXHSNVELZ6ZI5QNSDSVF45ZANCNFSM4U6IVRVQ>
.
|
|
No worries. We see there must be something to it and we are working hard on reproducing it. Its just not easy ;) Every report is very welcome. |
|
PHASE OF FLIGHT: Approach |
|
dga711: I entered the flightplan on the FMS and spawned onto a ramp, without adding any plans from the MSFS main window |
|
PHASE OF FLIGHT: Departure SID from TAPA airport |
|
Not a stunningly detailed test, but following on from above about flight planning. I'll keep playing! |
If your FADEC isn't working, you have a livery conflict. Remove the livery or delete the panel.cfg file in it. The panel.cfg is overwriting our FADEC code execution. |
Is there any way to pinpoint the livery in conflict? Although i think that i havent installed any liveries between working and not-working flights..... |
|
The fastest way would be to remove half your liveries, test, then keep removing half until you can find which half "chunk" the conflict resides. But any livery that has a panel.cfg is going to be in conflict. |
|
PHASE OF FLIGHT: Climb |
|
I had my second CTD and it was shortly after coming from external view to VC during SID. I can swap external and internal views at later stages of flight with no CTD. |
|
PHASE OF FLIGHT: After departure I can confirm that it happened 3 times using MS flight planning. After reading the above comments, I was able to fly without crashes using manual FMS flightplan and even with Simbrief imported flightplan. It's not related to the crash but the sim does not "see" the flightplan put together in the FMS so there is no ATC with IFR plan. In a way it's better so it does not bugging me about altitudes :D |
|
PHASE OF FLIGHT: Departure during SID |
|
INITIAL CLIMB (FMS SID) Always around the same exact altitude !! |
////SEEMS TO BE FIXED//// I reinjected via SIMBRIEF the FPL without SID/STAR (start with DCT, ends with DCT) ........ no more CTD !! |
|
CRUISE LEVEL (FL400) After 10' of perfect flight (V0.8.1) ...... CTD !!! It's really disapointed because works well for 5 flights |
@e4rthdog any livery that contains a panel.cfg that doesn't carry over our changes to panel.cfg will kill FADEC |
|
VERSION MOD CJ4 0.8.1 G1000 3.2 |
|
Got another CTD, this time I was better prepared to gather input PHASE OF FLIGHT: Climb, shortly after departure These are taken right before the CTD: |
|
PHASE OF FLIGHT: INITIAL CLIMB |
|
Fresh one .... PHASE OF FLIGHT: INITIAL CLIMB |
|
PHASE OF FLIGHT: Climb |
|
PHASE OF FLIGHT: Climb |
|
PHASE OF FLIGHT: Initial climb Crash dump: https://gofile.io/d/HJu683
|
|
PHASE OF FLIGHT: Initial Climb Crash dump: https://gofile.io/d/iEN5Ou |
|
PHASE OF FLIGHT: CLIMB - passing FL300 (→FL400) Crash dump: https://gofile.io/d/bgoU5N |
|
PHASE OF FLIGHT: Climb Full crash dump (22GB): https://gofile.io/d/pq1N7o |
|
Some new findings on my end: TrackIR seems to be causing my CTDs with the CJ4 v0.8.x. I've now tried multiple times:
Edit: I suspect it's not necessarily TrackIR per se, but some conflict with my USB devices. Sometimes the pedals get disconnected and I have to re-plug them a couple of times for Windows to recognise them, but this only happens if TrackIR is active. However, with other planes these struggles don't result in a CTD. Edit2: I've now crashed without TrackIR, but I moved around devices to different USB ports (to see if there was a compatibility issue). PHASE OF FLIGHT: Climb Other mods installed: wt g3000, portHH1.1 Full crash dump: https://gofile.io/d/efwFwE |
|
Been using my TIR for all my 8.x flights. No issues on my end, but I’ve had
a pretty stable experience since launch even with my OC’d CPU. RTX2080 is
at stock.
…On Fri, Dec 25, 2020 at 11:57 AM Javi Martínez ***@***.***> wrote:
Some new findings on my end: TrackIR seems to be causing my CTDs with the
CJ4 v0.8.x. I've now tried multiple times:
- With TrackIR app open -> CTD happens always, usually during initial
climb
- With TrackIR app closed -> no CTD
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#608 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACRRDXDRO6ABUCARKADFDTSWS77NANCNFSM4U6IVRVQ>
.
|
|
Not sure if it's the same case of you but I have detected interactions between MSFS/TrackIR/Mouse clic when I turn on left or right my head during a moment. I have 3 screens, left for Skyvector/Windy/...., right for OnAir, central for MSFS. Right have MSFS external popup windows as Comm or Navigation. |
|
PHASE OF FLIGHT: Departure |
|
PHASE OF FLIGHT: Climb |
|
PHASE OF FLIGHT: Climb |
|
forgot to mention i used FLC for climb |
|
2 CTDs today, both departing KBMI enroute to KTEB |
|
PHASE OF FLIGHT: Approach Crash dump (full): link |
|
PHASE OF FLIGHT: Cruise |
|
PHASE OF FLIGHT: Takeoff |
|
PHASE OF FLIGHT: Initial Climb crash dump: https://gofile.io/d/dw2f2H |
|
PHASE OF FLIGHT: Initial climb Full crash dump: link |
|
Since the latest release and the updated G3000 I no longer have any CTDs |
|
CTD with 8.3b-beta3 Wrong link initially... updated: |
|
TL/DR: I hope I have a repro. Confirmed with a friend who has a clean installation of the sim with no mods other than this one. I have experienced CTDs pretty consistently when flying IFR from various places. It looks like some sort of a conflict between FMS plan and the plan in the sim. At least I have never had CTDs flying VFR (in sim) with a flight plan (in FMS), or vice-versa (IFR in sim with no flight plan in FMS). It does not seem to really matter whether I import the plan from the sim, or set it up manually in FMS. Although it feels like if I import the plan from the sim it is less likely to crash, it's more a gut feeling, than properly collected statistics. All crashes occur early in the flight, before reaching the cruising altitude. Autopilot does not seem to matter. I have once flown the whole climb manually without touching any AP settings and still crashed. Matching the plan that the sim has does not seem to matter, although if the plan in FMS is for a completely different route between another two airports it does not seem to crash (I only tried a couple times, so it may also be pure luck) Although I have tried and crashed many times in other conditions, here's an apparent repro, which I confirmed with a friend, who had a CTD even before he retracted the gear:
Not uploading any crash dumps as I have by now forgotten which one is from what situation. But I can generate more, if needed. Fields for a formal report: PHASE OF FLIGHT: Initial Climb |
|
@nARN thanks for the detailed report please try this version https://drive.google.com/file/d/1WNBQ1SECP4wqau-_RiMDGV72IyoIvTV5 if it helps your case |
|
Thanks, @dga711. I tried and flew most of the routes I had regular crashes with, including a few times the one I described above. There have been no crashes at all with this version. |
|
@nARN Sounds great. The coming update will have these and more changes to stuff we think could induce more regular CTDs. We'll see how that goes ;) |
and others
We will use this issue to track CTD reports from users.
PLEASE INCLUDE
PHASE OF FLIGHT:
AP ON/OFF:
VNAV ON/OFF:
WHAT FMC PAGE:
WHAT AUTOPILOT MODES (FMA):
DO YOU HAVE NAVIGRAPH DATA INSTALLED?:
GPU NVIDIA OR AMD?:
SCENERIES INSTALLED?:
DESCRIPTION OF THE EVENT - WHAT WERE YOU DOING/WHAT WAS THE PLANE DOING WHEN IT OCCURED:
Crash dumps
ℹ️ So everyone who gets regular CTD. Could you please do this https://helgeklein.com/blog/2018/10/creating-an-application-crash-dump/ , upload the file to something like https://gofile.io/uploadFiles and link it in your CTD report? Could be helpful in the future to diagnose it.
The text was updated successfully, but these errors were encountered: