[P3D 4.5 HF1] Sim reduces the LOD radius by one notch, forcing a reload while flying the PMDG748.

[Martyson]

Here (in 2017) you had PMDG747 Appcrashes with P3Dv4.2.

So this has type of problem P3D CTD) has been with you for a long time.


https://www.prepar3d.com/forum/viewtopi ... 83#p181183

[JohnB]

Here (in 2017) you had PMDG747 Appcrashes with P3Dv4.2.

So this has type of problem P3D CTD) has been with you for a long time.


https://www.prepar3d.com/forum/viewtopi ... 83#p181183

No, this is a completely different problem. Crashes on westbound routes were a known problem
Mine isn't P3D crashing when i close It, which is also a known problem.

It's the drop of LODR for no reason.

[Martyson]

Here (in 2017) you had PMDG747 Appcrashes with P3Dv4.2.

So this has type of problem P3D CTD) has been with you for a long time.


https://www.prepar3d.com/forum/viewtopi ... 83#p181183

No, this is a completely different problem. Crashes on westbound routes were a known problem
Mine isn't P3D crashing when i close It, which is also a known problem.

It's the drop of LODR for no reason.

Would you say your P3D setup and PC (itself) has been error free with PMDG747 until P3Dv4.5 HF1?
I ask because you mentioned your PC has been acting up.

If you reboot your PC after a crash and start P3D again, are your last saved Config setting(s) correct?

Note:
If I had a CTD I would not look back to see if a config item had changed ... like LOD?
In fact I do not know exactly what my last working set of settings is right now without loading a saved set.

[JohnB]

Here (in 2017) you had PMDG747 Appcrashes with P3Dv4.2.

So this has type of problem P3D CTD) has been with you for a long time.


https://www.prepar3d.com/forum/viewtopi ... 83#p181183

No, this is a completely different problem. Crashes on westbound routes were a known problem
Mine isn't P3D crashing when i close It, which is also a known problem.

It's the drop of LODR for no reason.

Would you say your P3D setup and PC (itself) has been error free with PMDG747 until P3Dv4.5 HF1?
I ask because you mentioned your PC has been acting up.

If you reboot your PC after a crash and start P3D again, are your last saved Config setting(s) correct?

Note:
If I had a CTD I would not look back to see if a config item had changed ... like LOD?
In fact I do not know exactly what my last working set of settings is right now without loading a saved set.

I can confirm that it has been error free since flying the 748 and recently updated 787 in 4.5 HF1.
I always verify settings after a crash and they never change. Something is sending a command to change settings, most likely the same thing that sent a command to wipe my axis mappings.

Could I just make the P3D.cfg read only?

[Martyson]

No, this is a completely different problem. Crashes on westbound routes were a known problem
Mine isn't P3D crashing when i close It, which is also a known problem.

It's the drop of LODR for no reason.

Would you say your P3D setup and PC (itself) has been error free with PMDG747 until P3Dv4.5 HF1?
I ask because you mentioned your PC has been acting up.

If you reboot your PC after a crash and start P3D again, are your last saved Config setting(s) correct?

Note:
If I had a CTD I would not look back to see if a config item had changed ... like LOD?
In fact I do not know exactly what my last working set of settings is right now without loading a saved set.

I can confirm that it has been error free since flying the 748 and recently updated 787 in 4.5 HF1.
I always verify settings after a crash and they never change. Something is sending a command to change settings, most likely the same thing that sent a command to wipe my axis mappings.

Could I just make the P3D.cfg read only?

Ok,
How did you get to P3Dv4.5 HF1?
For example:
Did you Uninstall all add-on, uninstall P3D, download full P3D product, install it then your add-ons?

[JohnB]

I used the individual component installers exactly like poppet said so.

This might be not be related, but today it occurred twice and each time it was some time after active sky changed the cloud draw distance.

[Martyson]

I used the individual component installers exactly like poppet said so.

This might be not be related, but today it occurred twice and each time it was some time after active sky changed the cloud draw distance.

Back yo my last question?


Which component installers did you do?

You may have to go back to a default P3D install without add-ons to verify no error.
Then just add the PMDG747.

[JohnB]

https://www.prepar3d.com/forum/viewtopi ... 2&t=120861

This is how I update P3D.

I use all of them, I update fully.

[Martyson]

https://www.prepar3d.com/forum/viewtopi ... 2&t=120861

This is how I update P3D.

I did not read your link.
My question was :
Did you Uninstall all add-on(s), uninstall P3D, download full P3D product, install it then your add-ons?

"I use all of them, I update fully."

Ok,
Looks like your HF1 install/setup has a problem.
Maybe a flawed download.

edit:
Just to verify did you uninstall all add-on(s) first?

[JohnB]

Nope, I don't. It says its unnecessary so I don't do it.

[Martyson]

Nope, I don't. It says its unnecessary so I don't do it.

Ok,
That is true.

Unless the update is not working for you.

So, maybe it is an add-on like you mentioned (activesky?) or other.

In some cases going back to a default P3D and testing for no errors prior to reinstalling any addon(s) is the best way to go.

[JohnB]

Maybe I should try hotfix 2 and see if it fixes this?

[Martyson]

Maybe I should try hotfix 2 and see if it fixes this?

You know your system best.
The Windows error you are getting is a hard one to find a solution for.

I have HF2 (previously HF1 all ok) installed and no problems with PMDG737, 777, 747, 747-expansion.

[downscc]

The kernelbase errors can be linked to a video driver corruption. Use DDU with Windows in safe mode to remove all remnants of driver files, old and new. See: http://www.prepar3d.com/forum/viewtopic ... 5&t=126058

Then install latest NVidia drivers. Hope this helps.

[JorgenSA]

A "kernelbase.dll" error is not a P3D error, it is a Windows error, and unfortunately it can have several causes - and solutions.

You'll need to google that, and apply fixes as necessary for your particular situation.

I had such an error about 6 months ago, googled it, applied the fix I thought best suited to my situation, and the error never returned.

Jorgen