Ever since I updated P3D v4.5 to HF3 my FPS have declined by approximately 10, where I used to consistently get 25 to 30 I am now getting 15 to 20.

I have not added or changed anything from HF2 to HF3 or after.  I am flying in the same area with my favorite aircraft the Carenado Beech Baron B58.

I tried uninstalling and re-installing the Client.  I tried deleting the Shaders.

Has anyone else found this to be an issue?

 

If there is no solution to this I am wondering if I can actually go back to HF2 - is that possible?

I notis the same problem with HF3, in HF2 i had aprox 10-15 more fps on the same config

1 hour ago, Dane Watson said:

Ever since I updated P3D v4.5 to HF3 my FPS have declined by approximately 10, where I used to consistently get 25 to 30 I am now getting 15 to 20.

I have not added or changed anything from HF2 to HF3 or after.  I am flying in the same area with my favorite aircraft the Carenado Beech Baron B58.

I tried uninstalling and re-installing the Client.  I tried deleting the Shaders.

Has anyone else found this to be an issue?

 

If there is no solution to this I am wondering if I can actually go back to HF2 - is that possible?

Did you delete the P3D.cfg file and let regenerate?

Can you run Lorby's addon tool and do a check on encoding.  if some required files encoding is not set up right - slow fps can occur (it all depends).  I like to make sure all my files have the right encoding.  

If there are encoding issues - just run Notepad++ - open the file, change encoding to UCS - BOM-LE (something like that) and save viola.  Run the lorby app again - check encoding - it will say no errors found.

See if that brings back some fps.

1 hour ago, Skywolf said:

change encoding to UCS - BOM-LE

But only if it is a .cfg file.

xml files have to be encoded according to their own declaration in the top line header.

21 minutes ago, Farlis said:

But only if it is a .cfg file.

xml files have to be encoded according to their own declaration in the top line header.

I am just giving a suggestion.

@Dane Watson have you check your Nvidia Control panel and to see by accident windows 10 / or nvida driver update put it to Optimal power settings vs Maximum Power.  

Deleting of Prepar3d.cfg usually for most of the times solves the problem.

 

13 minutes ago, Skywolf said:

I am just giving a suggestion.

Then give one that is correct. 😉

6 hours ago, Skywolf said:

Can you run Lorby's addon tool and do a check on encoding.  if some required files encoding is not set up right - slow fps can occur (it all depends).  I like to make sure all my files have the right encoding.  

This would not depend if you're running v4.5 hf2 or hf3. I frequently use the Lorby P4AO with hf2 and have not seeing any adverse impact on the FPS related to encoding.

The OP describes an issue with low FPS when running hf3.

Cheers, Ed

Edited April 25, 20206 yr by edpatino

9 hours ago, Dane Watson said:

Ever since I updated P3D v4.5 to HF3 my FPS have declined by approximately 10, where I used to consistently get 25 to 30 I am now getting 15 to 20.

I have not added or changed anything from HF2 to HF3 or after.  I am flying in the same area with my favorite aircraft the Carenado Beech Baron B58.

I tried uninstalling and re-installing the Client.  I tried deleting the Shaders.

Has anyone else found this to be an issue?

 

If there is no solution to this I am wondering if I can actually go back to HF2 - is that possible?

Did you originally only do the Client update or did you update any other component, like Content?.

If you only did the Client update you can revert back to hf2 at any time by doing the same procedure (inverted, of course). I don't have any experience when reverting back if you also updated the Content/Scenery components.

Cheers, Ed

Edited April 25, 20206 yr by edpatino

Can someone elaborate for me.........is there a specific reason to update from 4.5HF2 to 4.5HF3? Since this is likely to be the last iteration of P3Dv4, I am not convinced that "updating" to HF3 has any merit.

5 minutes ago, Christopher Low said:

Can someone elaborate for me.........is there a specific reason to update from 4.5HF2 to 4.5HF3? Since this is likely to be the last iteration of P3Dv4, I am not convinced that "updating" to HF3 has any merit.

I looked through the change list and saw no compelling need, so I haven't. 

4 minutes ago, Christopher Low said:

Can someone elaborate for me.........is there a specific reason to update from 4.5HF2 to 4.5HF3? Since this is likely to be the last iteration of P3Dv4, I am not convinced that "updating" to HF3 has any merit.

I don't find any valid reason for the update. There were some reports about performance gains after updating to hf3, but maybe it's the usual hype from some users with no really valid arguments to justify the gains.

And now, this thread talking about FPS losses makes me think that's probably better to stay with hf2 before jumping to v5.

Cheers, Ed

I agree that the OP should try to delete their prepar3d.cfg. Usually this has fixed  all sorts of issues for me, and I’m pretty sure that this is a highly recommended step after updating the client.

as for whether to update to 4.5hf3... I haven’t. My sim is running very smoothly generally, so the last thing I want to do is mess it up. I’ll stay with 4.5 the way it is, perhaps installing an airport now and then, but that’s it. No major changes until I move to v5.

I have read and have appreciated all the feedback from everyone - thank you.

Before I roll back to HF2, I will try one thing that I had not done and has come across loud and clear from many of you - I will delete the CFG file and see what happens.

Will let everyone know later today my results.

I also haven't updated to HF3 yet since I can't find any good reason to do so except P3D being on the latest version. There's not a single thing in the changelog that would benefit me in any way (at least to my knowledge). Also posts like this are not very encouraging, although I'm not sure the FPS loss issue has anything to do with HF3. A lot of simmers updated P3D to HF3 yet this is the first post about such issue. I mean, 10-15 FPS is huge. If it would be a genuine bug in the code we'd have HF4 by now. IT would be interesting to hear from others who updated to HF3.