4.5 hot fix is out

[Sethos 4,298]

"Added configuration option to toggle UI hardware acceleration mode (UIHardwareAcceleration)"

I assume that's the "DisableHWAcceleration" registry edit that was suggested when ReShade was acting up in 4.4, which has now become a user option?

[simbol 5,811]

Dear All,

Anyone still having issues with performance after the hotfix, please rebuild your shaders and be sure to check if you have this registry key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration

If you do, please delete it, restart your PC and launch P3D again..

There is a new setting under Ptepra3d.cfg called UIHardwareAcceleration, it is important to have this setting set to True.

The setting works as follow:

UIHardwareAcceleration=False - Disables Hardware Acceleration for P3D.

UIHardwareAcceleration=True - Enables Hardware Acceleration for P3D.

People using Reshade might need to disable it, however please try your performance first with HW acceleration enabled.

Regards,
Simbol

Edited May 13, 2019 by simbol

[simbol 5,811]

4 minutes ago, Sethos1988 said:

"Added configuration option to toggle UI hardware acceleration mode (UIHardwareAcceleration)"

I assume that's the "DisableHWAcceleration" registry edit that was suggested when ReShade was acting up in 4.4, which has now become a user option?

Correct, please delete your registry key.. and use the setting instead, however be advised performance might be affected with this disabled on certain systems.

S.

Edited May 13, 2019 by simbol

[Skywolf 992]

@simbol - Awesome Posts...Thank you for the work!

It is great you get to beta test P3D  

I wish I had the time to Beta test these days unfortunately I do not.

[AnkH 2,233]

14 minutes ago, simbol said:

Dear All,

Anyone still having issues with performance after the hotfix, please rebuild your shaders and be sure to check if you have this registry key:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration

[...]

Thanks Simbol, but honestly, a little bit to much to ask users to modify their registry for a "hotfix", no? Obviosuly the problem is not solved by the hotfix? Can you elaborate a little bit further on this registry entry? I have it in my registry, but as I did not observe any FPS issues already without the hotfix, I wonder what the registry entry stands for? Reason I ask: I might simply not have seen the FPS drop due to my FPS limit at 30. But if this registry entry might be the reason for reduced FPS, I also want to get rid of it...

[simbol 5,811]

6 minutes ago, AnkH said:

Thanks Simbol, but honestly, a little bit to much to ask users to modify their registry for a "hotfix", no? Obviosuly the problem is not solved by the hotfix? Can you elaborate a little bit further on this registry entry? I have it in my registry, but as I did not observe any FPS issues already without the hotfix, I wonder what the registry entry stands for? Reason I ask: I might simply not have seen the FPS drop due to my FPS limit at 30. But if this registry entry might be the reason for reduced FPS, I also want to get rid of it...

This registry setting disables hardware acceleration for all applications on your PC, you want this enabled to get the best performance out of your system.

P3D 4.4 enabled hardware acceleration hardcoded inside the source code, but some people complained about this change since Reshade and other overlaying /recording software were not working correctly with P3D 4.4. and as a result LM gave the registry setting for a work around for user experiencing this problem.

P3D 4.5 disabled hardware acceleration via internal code, to correct the issues stated above as people were complaining about issues, etc.

P3D 4.5 HotFix has re-enabled Hardware Acceleration by default, and included a setting via Prepard3.cfg to override it if necesary: UIHardwareAcceleration=false. NOTE: It was determined via beta tests that the change in hardware acceleration via internal code caused the performance drops in comparison with P3D 4.4 under certain systems.

So you need to delete this registry setting if you have it in your system.

Regards,
Simbol

 

 

[fluffyflops 1,845]

1 hour ago, SunDevil56 said:

Pete, you can do the full installer, or just the client, which apparently addresses the quote, "performance issues seen on some systems and configurations" according to the hotfix page at LM. 

Thank you very much 

[fluffyflops 1,845]

14 minutes ago, simbol said:

This registry setting disables hardware acceleration for all applications on your PC, you want this enabled to get the best performance out of your system.

P3D 4.4 enabled hardware acceleration hardcoded inside the source code, but some people complained about this change since Reshade and other overlaying /recording software were not working correctly with P3D 4.4. and as a result LM gave the registry setting for a work around for user experiencing this problem.

P3D 4.5 disabled hardware acceleration via internal code, to correct the issues stated above as people were complaining about issues, etc.

P3D 4.5 HotFix has re-enabled Hardware Acceleration by default, and included a setting via Prepard3.cfg to override it if necesary: UIHardwareAcceleration=false. NOTE: It was determined via beta tests that the change in hardware acceleration via internal code caused the performance drops in comparison with P3D 4.4 under certain systems.

So you need to delete this registry setting if you have it in your system.

 

 

 

Was that related to cpu affinty issues? By any chance? 

Very interesting. 

Edited May 13, 2019 by tooting

[Sethos 4,298]

19 minutes ago, simbol said:

This registry setting disables hardware acceleration for all applications on your PC, you want this enabled to get the best performance out of your system.

P3D 4.4 enabled hardware acceleration hardcoded inside the source code, but some people complained about this change since Reshade and other overlaying /recording software were not working correctly with P3D 4.4. and as a result LM gave the registry setting for a work around for user experiencing this problem.

P3D 4.5 disabled hardware acceleration via internal code, to correct the issues stated above as people were complaining about issues, etc.

P3D 4.5 HotFix has re-enabled Hardware Acceleration by default, and included a setting via Prepard3.cfg to override it if necesary: UIHardwareAcceleration=false. NOTE: It was determined via beta tests that the change in hardware acceleration via internal code caused the performance drops in comparison with P3D 4.4 under certain systems.

So you need to delete this registry setting if you have it in your system.

Regards,
Simbol

 

 

So essentially, we've now reached a point where for some users, they might be 'forced' to take the 4.5 performance decrease if they need to use ReShade and disable HWA?

[cyyzrwy24 118]

12 minutes ago, tooting said:

with P3D 4.4 under certain systems.

......looks like KEY word to me. 

[Navigator43 25]

2 hours ago, Christopher Low said:

......smug 4.4 user enters stage left with popcorn in hand

I haven’t got popcorn I got a beer lol

[simbol 5,811]

3 minutes ago, Sethos1988 said:

So essentially, we've now reached a point where for some users, they might be 'forced' to take the 4.5 performance decrease if they need to use ReShade and disable HWA?

Not necessarily.

I use Reshade with 4.5 on my main simulation PC and I don't have any performance issues with 4.5, as I said, no all systems are affected so you will need to TEST on your own computer.

S.

 

[Navigator43 25]

2 hours ago, Christopher Low said:

......smug 4.4 user enters stage left with popcorn in hand

I haven’t got popcorn I got beer lol

[fluffyflops 1,845]

5 minutes ago, Sethos1988 said:

So essentially, we've now reached a point where for some users, they might be 'forced' to take the 4.5 performance decrease if they need to use ReShade and disable HWA?

You beat me too it 

[ComSimPilot 623]

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.