4 hours ago, onurair said:

Could you resolve your stutters? I have a similar setup except (6700k) and have also stutters since updating to 4.3. No idea what happened there since 4.2 was smooth and the frames were solid.
I also get fps fluctuations with 4.3. 

Stupid question, but did you let v4.3 rebuild your prepar3d.cfg? I realized that by updating the Client only, the prepar3d.cfg was not renewed. I now manually deleted the prepar3d.cfg of Version 4.2 and let 4.3 build a new one. I do not know if this could be the culprit or not. Might be worth a shot, no?

Something completely different: it seems that some autogen definitions were adjusted. Can somebody who installed also the content update check if autogen still loads in patches when using anything higher than "medium" for the autogen drawing distance?

19 minutes ago, AnkH said:

Stupid question, but did you let v4.3 rebuild your prepar3d.cfg? I realized that by updating the Client only, the prepar3d.cfg was not renewed. I now manually deleted the prepar3d.cfg of Version 4.2 and let 4.3 build a new one. I do not know if this could be the culprit or not. Might be worth a shot, no?

Yup, I updated the client, content and scenery. However without deleting anything in the p3d main folder. So my orbx and other stuff was still there. I also didn't touch the xml files, to keep my addons. And yes I deleted the cfg and the shadders. Maybe a wrong setting or a missing texture addon which gave me more stable fps with 4.2

20 hours ago, onurair said:

Could you resolve your stutters? I have a similar setup except (6700k) and have also stutters since updating to 4.3. No idea what happened there since 4.2 was smooth and the frames were solid.
I also get fps fluctuations with 4.3. 

Howdy:

I have to do more testing but I just may have.  

I'm afraid to admit (especially since I consider myself to be a very neat/clean person), but I believe my issues were due to poor housekeeping.  

I took my computer outside yesterday used a computer cleaning brush to remove dust; I was very embarrassed.  I did a test flight today EGLL (UK2000)-KJFK (Drzewiecki-Design) in the 777 and it was pretty smooth sailing.

I wish I could offer you a magic formula to help - I know how frustrating it can be.

 

You MUST let p3d rebuild its cfg after updating...this is a must...then adjust your sliders as you had it

 

I did some more tests yesterday with the FSL320. I can keep 30fps at the ground with pretty high settings. What gives me stutters and dropping/fluctuating fps however is AI traffic.

I had it set to 100% (CUSTOM AI) and let FSUIPC handle it with a limit of 100 and target FPS at 32.
This was giving me good results and solid fps in 4.2

Things are different in 4.3 with the exact same settings. I have to dig deeper. Something is not working correctly. I suspect my FSUIPC installation...

1 hour ago, onurair said:

I had it set to 100% (CUSTOM AI) and let FSUIPC handle it with a limit of 100 and target FPS at 32.
This was giving me good results and solid fps in 4.2

Things are different in 4.3 with the exact same settings.

If you did a content update as well as client, then the default traffic would have been re-enabled as well as your custom AI.  With the slider at 100% it is then possible for there to be a huge amount of traffic beings added for FSUIPC's limiter to delete (the FSUIPC log records the numbers of deletions). That can certainly cause stutters.

This happened to me on a previous P3D4 update (4.0 to 4.1 I think. These days I usually only do client updates.

Check the scenery\world folder to check if there are default traffic BGLs.

Pete

 

7 minutes ago, Pete Dowson said:

If you did a content update as well as client, then the default traffic would have been re-enabled as well as your custom AI.  With the slider at 100% it is then possible for there to be a huge amount of traffic beings added for FSUIPC's limiter to delete (the FSUIPC log records the numbers of deletions). That can certainly cause stutters.

This happened to me on a previous P3D4 update (4.0 to 4.1 I think. These days I usually only do client updates.

Check the scenery\world folder to check if there are default traffic BGLs.

Pete

 

I can remember that I had a second default traffic BGL file after the install of client, content and scenery. I then deleted one of them and added the .bak suffix at the end of the other file.

I have to check that again, once I get home from work. Thank you anyway for the tipp. 

5 hours ago, aamontoy83 said:

You MUST let p3d rebuild its cfg after updating...this is a must...then adjust your sliders as you had it

 

I’ve never deleted my cfg after a client only update.  Have never had an issue

On 7/2/2018 at 2:48 PM, AnkH said:

Something completely different: it seems that some autogen definitions were adjusted. Can somebody who installed also the content update check if autogen still loads in patches when using anything higher than "medium" for the autogen drawing distance?

I made the client + contents update. I also deleted prepar3d.cfg +  the shaders in advance ... as always on upgrades.

The first test flight using 4.3 was to an area where I always had autogen loading in patches (Take off from KSFO heading South to KSJC in a C172). Unfortunately, autogen still loads in patches as soon as I set the distance slider higher than medium. 

Can others verify/valsify this?

Kind regards, Michael

Ok, what a bummer. I also observed this, although a little bit faster in v4.3 now. Seems not to be related to those updates, as I only updated the client. I wonder if this is ever fixed before v5...

9 hours ago, pmb said:

I made the client + contents update. I also deleted prepar3d.cfg +  the shaders in advance ... as always on upgrades.

The first test flight using 4.3 was to an area where I always had autogen loading in patches (Take off from KSFO heading South to KSJC in a C172). Unfortunately, autogen still loads in patches as soon as I set the distance slider higher than medium. 

Can others verify/valsify this?

Kind regards, Michael

Same here.

The only noticable improvement for me is the DL performance. But I am quiet happy with that.

If they fix the autogen popping now I am a happy simmer 🙂

I followed Poppet's  instructions to update to 4.3 Client (only) and receive this error:  Hacklib::Contact Points Offset() Unsupported P3D version.  Content, Scenery and Professional are 4.1.7.22841.  Professional Client is 4.3.29.25520.  Click through the error message and program appears to load normal but does not show up (nor is minimized either.)  Under Task Manager, program show in processes but not in applications if that means anything.Would appreciate any guidance or questions-not sure what more detail is needed.  Thanks.

 

Mark

No ground steering on A2a Comanche or Spitfire-2  since 4.3 upgrade.  

Ezdok is not installed.

No problems with any other aircraft 

Help 😎

29 minutes ago, raybans said:

No ground steering on A2a Comanche or Spitfire-2  since 4.3 upgrade.  

Ezdok is not installed.

No problems with any other aircraft 

Help 😎

You updated from 4.2? A2A airplanes needed an updated when 4.2 was released to fix the problem you are describing.

I suspect you jumped from 4.1 to 4.3, if this is the case you need to update your A2A Airplanes.

S.