If anyone wants to help resolving the issue, please check if Q400 has generated a fresh CMJC84BaseErr.log file in the Prepar3D v5 client root folder. If it is there, we kindly ask you to email it to support@majesticsoftware.com
If this helps any, I did a fresh install into V5. My hydraulics are not showing the errors as depicted above and everything seems to be working fine. I am not a Q400 expert so take that as you wish. There are no errors on the warning panel either. My windows has not updated to 2004 yet so that may be an indicator. Just trying to provide an additional data point
I only have 1 regedit key. The correct one. I got the same issue with the gauge jumping up and down. There is no error log generated in the P3D V5 root folders.
Anyone using EZ Dok software? I was getting CTDs after installing/re-installing multiple times. I received some key errors from EZCA but once I fixed these, I was able to get the plane to load. Now I have the same error sounds, hyd issues and gauge flickering as others have posted. May try the registry trick.
So just tried deleting the registry entries and re-installing with admin rights. No joy. getting immediate CTD when trying to load the Dash 8. This thread shows [RESOLVED] it does not appear to be solved??
@adl320 said:
This thread shows [RESOLVED] it does not appear to be solved??
You should have also noticed that this was for a thread started back in 2018 where the issues were resolved. These issues are driven from a new installer driven by different reasons.
@adl320 said:
This thread shows [RESOLVED] it does not appear to be solved??
You should have also noticed that this was for a tread started back in 2018 the issues were resolved. These issues are driven from a new installer driven by different reasons.
Round 2. Edited the Registry as suggested. Reinstalled the Dash 8. No change. Uninstalled the Dash 8 and deleted the Majestic Software folder (main key). Reinstalled the Dash 8 and started up P3D v5 with Dash 8 selected as load aircraft. P3D crashed. Started P3D with default aircraft. P3D loaded correctly. Selected Dash from dropdown menu and it appeared to successfully load BUT the doughnut of death was circling and within a minute P3D crashed. Loaded P3D with addon PMDG 737 and loaded correctly. I'll wait for further advice on this.
Same problem (Instruments popping & markers for hydraulic systems jumping up and down) here with P3DV5HF2 and Win10 2004. Previous version for V4 deinstalled completely before. No error log present.
Thanks in advance!
@chumley said:
Round 2. Edited the Registry as suggested. Reinstalled the Dash 8. No change. Uninstalled the Dash 8 and deleted the Majestic Software folder (main key). Reinstalled the Dash 8 and started up P3D v5 with Dash 8 selected as load aircraft. P3D crashed. Started P3D with default aircraft. P3D loaded correctly. Selected Dash from dropdown menu and it appeared to successfully load BUT the doughnut of death was circling and within a minute P3D crashed. Loaded P3D with addon PMDG 737 and loaded correctly. I'll wait for further advice on this.
Thanks for the additional information. We knew that users who would have installed to Win 2004 would have had some issues, and we addressed most of the issues that we suspected had a direct impact on the add-on. Of course there may be others affected by this who have not reported, but it seems to be a small group of users thus far.
@chumley said:
Round 2. Edited the Registry as suggested. Reinstalled the Dash 8. No change. Uninstalled the Dash 8 and deleted the Majestic Software folder (main key). Reinstalled the Dash 8 and started up P3D v5 with Dash 8 selected as load aircraft. P3D crashed. Started P3D with default aircraft. P3D loaded correctly. Selected Dash from dropdown menu and it appeared to successfully load BUT the doughnut of death was circling and within a minute P3D crashed. Loaded P3D with addon PMDG 737 and loaded correctly. I'll wait for further advice on this.
Thanks for the additional information. We knew that users who would have installed to Win 2004 would have had some issues, and we addressed most of the issues that we suspected had a direct impact on the add-on. Of course there may be others affected by this who have not reported, but it seems to be a small group of users thus far.
Small group of users, eh?
Same problem here. Try and not delete my post again just because I voice criticism.
We don't have a problem with critism and I delete what ever post I deem necessary based on your tone.
It's a piece of software prone to many unknowns regardless of the Test team.
Cheers
@nguindon@fogboundturtle@mifuc thanks for this additional information. Apart from the win 2004 update windows 1909 also pushed an update 2 days before we pushed the new installers and we did observed some issues forcing us to make some last minute changes. The addon worked without issues prior to this.
So it's going to require some trouble shooting to get a handle on it.
@kroswynd said: @nguindon@fogboundturtle@mifuc thanks for this additional information. Apart from the win 2004 update windows 1909 also pushed an update 2 days before we pushed the new installers and we did observed some issues forcing us to make some last minute changes. The addon worked without issues prior to this.
So it's going to require some trouble shooting to get a handle on it.
To help you find the fix, as additional information, i am on 1909 but have the updates paused since June 10, 2020 so I wouldn't have the update you are referring to above.
@kroswynd said: @nguindon@fogboundturtle@mifuc thanks for this additional information. Apart from the win 2004 update windows 1909 also pushed an update 2 days before we pushed the new installers and we did observed some issues forcing us to make some last minute changes. The addon worked without issues prior to this.
So it's going to require some trouble shooting to get a handle on it.
To help you find the fix, as additional information, i am on 1909 but have the updates paused since June 10, 2020 so I wouldn't have the update you are referring to above.
My last updates were installed on June 10th before I paused it as I control when I want the updates installed.
I also have the issues, usually a crash to desk top. but if I do get it to load the jumping gauges then after a few minutes a crash to desk top.
This is n P3Dv5 with HF2 and win 10 2004 update.
Best wishes
Bob
Comments
Crash on startup of P3D v5 HF2 with 1.021 here
@korundar for the reset, please contact support@majesticsoftware.com with your order number
If anyone wants to help resolving the issue, please check if Q400 has generated a fresh CMJC84BaseErr.log file in the Prepar3D v5 client root folder. If it is there, we kindly ask you to email it to support@majesticsoftware.com
If this helps any, I did a fresh install into V5. My hydraulics are not showing the errors as depicted above and everything seems to be working fine. I am not a Q400 expert so take that as you wish. There are no errors on the warning panel either. My windows has not updated to 2004 yet so that may be an indicator. Just trying to provide an additional data point
I only have 1 regedit key. The correct one. I got the same issue with the gauge jumping up and down. There is no error log generated in the P3D V5 root folders.
Anyone using EZ Dok software? I was getting CTDs after installing/re-installing multiple times. I received some key errors from EZCA but once I fixed these, I was able to get the plane to load. Now I have the same error sounds, hyd issues and gauge flickering as others have posted. May try the registry trick.
So just tried deleting the registry entries and re-installing with admin rights. No joy. getting immediate CTD when trying to load the Dash 8. This thread shows [RESOLVED] it does not appear to be solved??
You should have also noticed that this was for a thread started back in 2018 where the issues were resolved. These issues are driven from a new installer driven by different reasons.
Thanks..missed that detail.
I found loading a default aircraft first then switching to the Dash 8 stopped the crashes.
where do I find how many installs I have left ?
I've installed and deleted a few times on both p3dv4 and 5 while trying to get this to work
Round 2. Edited the Registry as suggested. Reinstalled the Dash 8. No change. Uninstalled the Dash 8 and deleted the Majestic Software folder (main key). Reinstalled the Dash 8 and started up P3D v5 with Dash 8 selected as load aircraft. P3D crashed. Started P3D with default aircraft. P3D loaded correctly. Selected Dash from dropdown menu and it appeared to successfully load BUT the doughnut of death was circling and within a minute P3D crashed. Loaded P3D with addon PMDG 737 and loaded correctly. I'll wait for further advice on this.
Thanks in advance!
Thanks for the additional information. We knew that users who would have installed to Win 2004 would have had some issues, and we addressed most of the issues that we suspected had a direct impact on the add-on. Of course there may be others affected by this who have not reported, but it seems to be a small group of users thus far.
It seems that the Problem is not limited to 2004 users. I do not have it yet and the Trouble is the same.
FYI I am not on Win 10 2004. Same issue
I’m not on win 10 2004 and have the same issue. Tried multiple reinstalls without any success.
Small group of users, eh?
Same problem here. Try and not delete my post again just because I voice criticism.
We don't have a problem with critism and I delete what ever post I deem necessary based on your tone.
It's a piece of software prone to many unknowns regardless of the Test team.
Cheers
@nguindon @fogboundturtle @mifuc thanks for this additional information. Apart from the win 2004 update windows 1909 also pushed an update 2 days before we pushed the new installers and we did observed some issues forcing us to make some last minute changes. The addon worked without issues prior to this.
So it's going to require some trouble shooting to get a handle on it.
Thanks, so a little Patience is needed in this case
To help you find the fix, as additional information, i am on 1909 but have the updates paused since June 10, 2020 so I wouldn't have the update you are referring to above.
My last updates were installed on June 10th before I paused it as I control when I want the updates installed.
let us know what you need
I also have the issues, usually a crash to desk top. but if I do get it to load the jumping gauges then after a few minutes a crash to desk top.
This is n P3Dv5 with HF2 and win 10 2004 update.
Best wishes
Bob
Attention folks.... Just a quick question for everyone who is experiencing the CTD /protection issue.
Which version of the Q400 are you using please?
@kroswynd mjc8-400-Pilot-1_021_x64.
Same
http://majesticsoftware.com/forums/discussion/817/temporary-fix-for-prepar3d-v4-5-v5-ctds/p1?new=1
how do I get th is dll. I bought from PC Aviator