Think I'm gonna stick with 4.4 as it works absolutely fine for me , tried the 4.5 and had issues and so went back to 4.4 . Reading the varied responses from users here I'm gonna wait until new win 10 update,  add on updates , rex orbx etc and the P3d v5. Thanks for all the feedback , it's been useful 

And what's the betting, that P3D v5 (which will no doubt cost), will inherit all these issues ?

I get the feeling P3D is going the same way as Windows 10 ... fix one thing, break two others.

Hmmm.... time will tell.

9 minutes ago, asustech said:

Think I'm gonna stick with 4.4 as it works absolutely fine for me , tried the 4.5 and had issues and so went back to 4.4 . Reading the varied responses from users here I'm gonna wait until new win 10 update,  add on updates , rex orbx etc and the P3d v5. Thanks for all the feedback , it's been useful 

Heh, V5 will probably have you waiting months for some addons to become compatible, rather than hours and days.

2 hours ago, simbol said:

Correct, this will only appear if you rebuild your prepar3.cfg file after the HF or on a brand new installation (no P3D before)

I will have a double check because after upgrading the Client (only) and deleting the Prepar3D.cfg before the first launch I didn't find the UIHardwareAcceleration=false.

2 hours ago, JJJackson said:

Try this.

My new fix crashed my P3D 4.5 at startup, but this fix solved my problem.

______________________

I found the problem of P3D not starting after the hotfix. The WX Advantage Radar is the reason. Removed the MV_WXM.dll from the Modules folder and problem solved. I guess it needs to be updated.

--------------------------------------

 

Jack

the Swede in Spain

Thanks JJJackson. It was me who found the solution :DD

Edited May 14, 20197 yr by Daedalus

Thanks for that Daedalus, guess you made a lot of people very happy!  Keep up the good work. 😄

Jack

32 minutes ago, vbazillio said:

I will have a double check because after upgrading the Client (only) and deleting the Prepar3D.cfg before the first launch I didn't find the UIHardwareAcceleration=false.

You can add it yourself and change it to True, as you want max performance .....

Edited May 14, 20197 yr by GSalden

1 minute ago, GSalden said:

You can add it yourself and change it to True, as you want max performance .....

Yes will test ! Despite, I'm not expecting anything magic (too old in the sim. business) 😉

So far a (very) quick test showed good performance so far. I'm currently enthousiastic at Flytampa Las Vegas and raised some autogen sliders to push my performance enveloppe. So far so good and my favorite addons are compatible (F1 GTN, Active Sky).

Hello everybody!  

The option you are commenting on: UIHardwareAcceleration ... In which part of the Prepard3d.cfg is it placed?  [DISPLAY], [MAIN] ... ??  

Thanks and best regards!

2 minutes ago, Joetsa said:

Hello everybody!  

The option you are commenting on: UIHardwareAcceleration ... In which part of the Prepard3d.cfg is it placed?  [DISPLAY], [MAIN] ... ??  

Thanks and best regards!

Under [USERINTERFACE]

1 hour ago, vbazillio said:

I will have a double check because after upgrading the Client (only) and deleting the Prepar3D.cfg before the first launch I didn't find the UIHardwareAcceleration=false.

That is not what I said on my earlier posts, my current understanding is that this setting will be default is enabled even if the setting is not configured at all (missing) and therefore UIHardwareAcceleration=false should not be there as this would disabled the hardware acceleration.

However there are reports of some user performing a full fresh install where the entry UIHardwareAcceleration=True is present.

As I said I will ask later today to Rob McCarthy (Lockheed Martin Engineer) confirmation about what is the expected behaviour for this new setting inside the prepar3d.cfg file in relation to:

A) What happens if the entry is not present at all.
B) Why some users have the entry set to  UIHardwareAcceleration=True when they perform full installs and missing when performing just client updates.

However, it is important to clarify one more time, that if you have disabled hardware acceleration via registry keys, it will remain DISABLED for P3D regardless of the setting you configure via UIHardwareAcceleration inside P3D.CfG, so it is very important to remove any registry key that disables HW acceleration if you have it.

Regards,
S.

 

Edited May 14, 20197 yr by simbol

Just now, simbol said:

However there are reports of some user performing a full fresh install where the entry UIHardwareAcceleration=True is present.

Can confirm, on a fresh installation of Windows that has never seen P3D and a full install of HF1, I have UIHardwareAcceleration=True present in the .cfg per default.

2 minutes ago, simbol said:

That is not what I said on my earlier posts, my current understanding is that this setting will be default is enabled even if the setting is not configured at all (missing) and therefore UIHardwareAcceleration=false should not be there as this would disabled the hardware acceleration.

However there are reports of some user performing a full fresh install where the entry UIHardwareAcceleration=True is present.

As I said I will ask later today to Rob McCarthy (Lockheed Martin Engineer) confirmation about what is the expected behaviour for this new setting inside the prepar3d.cfg file in relation to:

A) What happens if the entry is not present at all.
B) Why some users have the entry set to  UIHardwareAcceleration=True when they perform full installs and missing when performing just client updates.

Regards,
S.

 

Hi S,

Just to let you know I did have that line added under User Interface when doing a Client Only update, deleting the .cfg and shaders.  It did indeed add UIHardwareAcceleration=True to the .cfg with Client Only

-P

3 minutes ago, Sethos1988 said:

Can confirm, on a fresh installation of Windows that has never seen P3D and a full install of HF1, I have UIHardwareAcceleration=True present in the .cfg per default.

 

1 minute ago, psolk said:

Hi S,

Just to let you know I did have that line added under User Interface when doing a Client Only update, deleting the .cfg and shaders.  It did indeed add UIHardwareAcceleration=True to the .cfg

-P

Thanks guys, in that case @vbazillio, you might want to confirm you really installed the latest hotfix and actually deleted you P3D config file.

S.

47 minutes ago, simbol said:

 

Thanks guys, in that case @vbazillio, you might want to confirm you really installed the latest hotfix and actually deleted you P3D config file.

S.

I saved my old CFG  checked no UIHardwareAcceleration=True in that CFG then deleted the CFG copy  back my old start P3D then close it and there we have UIHardwareAcceleration=True in the old CFG must be added automatic.

Edited May 14, 20197 yr by westman