Jump to content

MFD Range dial CTD


JerryJet
 Share

Recommended Posts

Win10-64, P3Dv4.3, CRJ1.2.2.0

 

Seems the MFD Range goes as high as the 40-80 nm scale. If I mistakenly try to go above this limit P3D becomes "Not Responding" followed by a CTD. Repeatable. Sometimes I rotate the mouse wheel in the wrong direction when I want to lower the scale. I wonder if it's possible to trap the error before the CTD?

Link to comment
Share on other sites

Certain locations then as it's happened on more than one different flightplan. But always after TOD when I mistakenly turn the MFD Range dial up past the 40-80nm scale. Most recent flightplan was:

KIAG YULUC BUF ETG BRV HCM KRIC. CRJ700 @ FL310. Crash to desktop happened after TOD, somewhere before HCM on this route.

 

I really doubt this is location specific as the CTD happens immediately after trying to go higher than the 40-80nm scale on the Captain's MFD. Co-pilot's PFD and MFD are turned off via Dave if that matters.

Link to comment
Share on other sites

  • 1 month later...
  • 4 weeks later...
  • 1 month later...
  • 2 weeks later...
  • Developer

I still can't reproduce the issue (10 minutes of rapidly changing ranges with the mouse wheel, mouse buttons and keyboard shortcuts didn't cause a CTD here).

 

However, I looked through the code and found a few places where I could make reinforcements for better multi-threading stability. This change will be available with the next update (around mid January).

Link to comment
Share on other sites

  • 3 weeks later...
  • Developer

I'm really out of ideas regarding this one. I couldn't reproduce this issue even one in more than a year that I've been looking for it. I assumed a multithreading issue, but that's now absolutely failproof. I use the range knob all the time without any problem. May be I'm looking at the wrong place. I really don't know. Sorry.

Link to comment
Share on other sites

  • 3 weeks later...
  • 3 weeks later...

Same here, unfortunately. P3D v4.4, almost fresh Win 10 install

After the latest update to v1.2.3.0, I can at least enter or load the flightplan, but as soon as I change the range of the ND - CTD. I'm using Navigraph data cycle 1813. Still couldn't manage to at least take off without a CTD before.

Happened in Ljubljana on the ground in the -700 after all the other flight preperations have been done (scenery by RFSceneryBuilding, for the case that it matters).

Link to comment
Share on other sites

19 minutes ago, BudSpencer said:

Same here, unfortunately. P3D v4.4, almost fresh Win 10 install

After the latest update to v1.2.3.0, I can at least enter or load the flightplan, but as soon as I change the range of the ND - CTD. I'm using Navigraph data cycle 1813. Still couldn't manage to at least take off without a CTD before.

Happened in Ljubljana on the ground in the -700 after all the other flight preperations have been done (scenery by RFSceneryBuilding, for the case that it matters).

 

I made another flight in the CRJ9 yesterday and didn't have this problem.

 

I don't know if this might cause this issue, but to get the ball rolling let me ask if you've installed any updates for FSX/P3D Global (updating the NavData in the Sim itself rather than NavData for a particular aircraft) such as AeroData, Sors, etc.?

 

The the answer to the paragraph above is negative and you have a Navigraph subscription I would try deleting the CRJ AIRAC data and then reinstalling. The AIRAC data can be found in the C:\Program Files\Lockheed Martin\Prepar3D v4\Ecosystem\aerosoft\Digital Aviation CRJ\NavData folder.

 

Looking forward to hearing back from you!

 

Link to comment
Share on other sites

vor 17 Stunden , DaveCT2003 sagte:

I don't know if this might cause this issue, but to get the ball rolling let me ask if you've installed any updates for FSX/P3D Global (updating the NavData in the Sim itself rather than NavData for a particular aircraft) such as AeroData, Sors, etc.?

 

No, I only updated the Navdata for particular aircraft via Navigraph FMS data manager. I didn't do so since the end of 2018 because their charts always seem to be older than their Nav data and I wanted to "align" them a bit more.

vor 17 Stunden , DaveCT2003 sagte:

The the answer to the paragraph above is negative and you have a Navigraph subscription I would try deleting the CRJ AIRAC data and then reinstalling. The AIRAC data can be found in the C:\Program Files\Lockheed Martin\Prepar3D v4\Ecosystem\aerosoft\Digital Aviation CRJ\NavData folder.

 

Looking forward to hearing back from you! 

 

OK, I'm gonna try that and report back.

Link to comment
Share on other sites

  • Developer
vor 2 Stunden , BudSpencer sagte:

OK, I'm gonna try that and report back.

Don't. It's pointless. There's really zero relation between the navdata and the range CTD. If the navdata was corrupt, then the CRJ would crash on loading the navdata, which happens while the aircraft is loaded. All navdata is validated during that process, so a crash due to wrong or corrupted data can be ruled out.

Link to comment
Share on other sites

1 hour ago, Hans Hartmann said:

Don't. It's pointless. There's really zero relation between the navdata and the range CTD. If the navdata was corrupt, then the CRJ would crash on loading the navdata, which happens while the aircraft is loaded. All navdata is validated during that process, so a crash due to wrong or corrupted data can be ruled out.

 

My thoughts are the data displayed on the NavData, and if the data was corrupt....  but I agree it's a long shot.

 

Link to comment
Share on other sites

vor 6 Stunden , Hans Hartmann sagte:

Don't. It's pointless. There's really zero relation between the navdata and the range CTD. If the navdata was corrupt, then the CRJ would crash on loading the navdata, which happens while the aircraft is loaded. All navdata is validated during that process, so a crash due to wrong or corrupted data can be ruled out.

 

OK, but what else could I try? I've got no idea what direction I should search. Graphic settings maybe? However after the latest similar CTDs all I could do was wait for the next update - which evenetually helped in most cases.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...