9 hours ago, Quasimodo said:

Hmmm, That's kind of an atypical setup for Flight Sim. When you are reading posts about how silky smooth it is from other users bear in mind that they are probably nearly all using a TV and have there monitor set to 30hz with Vsync. So what they are seeing in there FPS synced to their refresh rate which equals smooth game play. Your Gsync montor will adjust the refresh rate to match your frame rate on the fly. I'm just spit balling here but the Frame rate in P3D can be very erratic which might cause problem for gsync. with that setup can you change you refresh rate in NCP? If so try 60hz. Then in the sim lock your frame rate to 60 and make sure you have the setting low enough to deliver 60fps constantly. If you can with that setup try using Vsync instead of Gsync just to see if you get any improvement.

You do not need to be running a 30Hz monitor for smooth performance in a flight sim.  I run a 105Hz Gsync monitor and every other flight sim I run is very smooth (XP Vulkan beta, DCS, IL2, etc). Earlier P3D versions were at times a stuttery mess, that is true.  But that was the huge problem with P3D that v5 is supposed to solve.

The default installation of v5 for me is very smooth with my monitor, avg fps from 40ish on up to the refresh rate depending on the settings.  In this case it looks like there might be something with these users that is interfering.  I definitely recommend disabling external frame limiters to start if you have a Gsync monitor - if you can stay above 40 the monitor should be able to adjust and the tech should work effectively.  I always turn OFF Vsync in sim for Gsync and have it ON in Nvidia Control Panel ( to prevent tearing at high fps).

19 minutes ago, cwburnett said:

Positive progress.  With 8 cores/16 threads, your affinity of 85 is only using 4 threads, so basically only 2 for scenery rendering.  That might explain the popping. I'd go with 01 01 01 01 01 01 01 01 which is 21845 as a starting point.

So, I change affinity mask=85 to 21845 right? 

10 minutes ago, PurdueKev said:

You do not need to be running a 30Hz monitor for smooth performance in a flight sim.  I run a 105Hz Gsync monitor and every other flight sim I run is very smooth (XP Vulkan beta, DCS, IL2, etc). Earlier P3D versions were at times a stuttery mess, that is true.  But that was the huge problem with P3D that v5 is supposed to solve.

The default installation of v5 for me is very smooth with my monitor, avg fps from 40ish on up to the refresh rate depending on the settings.  In this case it looks like there might be something with these users that is interfering.  I definitely recommend disabling external frame limiters to start if you have a Gsync monitor - if you can stay above 40 the monitor should be able to adjust and the tech should work effectively.  I always turn OFF Vsync in sim for Gsync and have it ON in Nvidia Control Panel ( to prevent tearing at high fps).

I’m g-sync 100hz and I’ve found enabling Vsync and triple buffering in p3d is making mine smooth? Is that the right thing to do? 

4 minutes ago, Ianrivaldosmith said:

So, I change affinity mask=85 to 21845 right? 

Correct.

3 minutes ago, Ianrivaldosmith said:

I’m g-sync 100hz and I’ve found enabling Vsync and triple buffering in p3d is making mine smooth? Is that the right thing to do? 

Defer to PurdueKev, since I don't have a g-sync monitor. My take is that as long as you can keep above the min 36 FPS, G-Sync should do its thing if configured correctly.

17 minutes ago, PurdueKev said:

You do not need to be running a 30Hz monitor for smooth performance in a flight sim

I never said you did!

1 hour ago, cwburnett said:

Correct.

Defer to PurdueKev, since I don't have a g-sync monitor. My take is that as long as you can keep above the min 36 FPS, G-Sync should do its thing if configured correctly.

Hi, tried the 21845 affinity mask, seems like 85 was working better. What does it actually do? How do I calculate it? Why don’t LM include it as an option? Sorry for so many questions! 

14 minutes ago, Ianrivaldosmith said:

Hi, tried the 21845 affinity mask, seems like 85 was working better. What does it actually do? How do I calculate it? Why don’t LM include it as an option? Sorry for so many questions! 

This is a good resource and where I learned what I learned.

http://www.codelegend.com/forums/viewtopic.php?f=2&t=698&p=5762#p5762

Maybe try 1365, that will give you 2 fewer cores.

18 hours ago, Ianrivaldosmith said:

I’m g-sync 100hz and I’ve found enabling Vsync and triple buffering in p3d is making mine smooth? Is that the right thing to do? 

 

18 hours ago, cwburnett said:

Defer to PurdueKev, since I don't have a g-sync monitor. My take is that as long as you can keep above the min 36 FPS, G-Sync should do its thing if configured correctly.

I'm not an expert on the tech, just going off of the various tutorials that are out there (and admittedly some are contradictory).  I am on my second Gsync monitor now (100 Hz wide screen that overclocks to 105; I used to have a 144Hz previously) - the best practice as I understand it is to set any in-game fps target (if it is available) to at or just under your maximum refresh rate, and to turn off any vsync in the sim or game but turn it on in the Nvidia control panel (when Gsync is enabled):

- you don't need vsync on in the application, since the monitor and Nividia drivers will adjust the monitor refresh on the fly; if both are on at the same time, you can get weird conflicts and choppy rendering.  It might work OK depending on how vsync is implemented in the application, but it isn't necessary.  I have seen occasions where P3D get stuttery if I have both on.

- you don't need triple buffering on... triple buffering is used with fixed-refresh vsync to compensate for the fluctuating pace of delivering frames from the application, but variable refresh is already compensating for that and having it on can lead to input lag;

- I have read differing guidance as to whether you need vsync on or off in the Nvidia Control Panel when Gsync is on...  if the application is unconstrained, then you want vsync ON in the video driver to kick in only to prevent screen tearing if your fps exceeds your max refresh rate (100Hz for your monitor).  But since we have an fps target in P3D to limit the output, you probably shouldn't need it - just set the P3D FPS target to at or below your maximum monitor refresh rate and you will never exceed what it can handle.  I usually experiment with each application to see if there is an effect (positive or negative).

Like I said, I am sure someone with knowledge of the programming would correct some of my explanations, that is my experience setting up the two Gsync monitors I have.  I would never go back to fixed refresh, which is why I have been so frustrated that P3D up until now hasn't benefited from the tech in the same way it has in other games and simulations.

cwburnett is correct, as long as you stay above 36fps or something like that (I think the exact lower limit depends on your monitor) then Gsync can operate as designed.

Edited April 18, 20206 yr by PurdueKev

17 hours ago, Ianrivaldosmith said:

Hi, tried the 21845 affinity mask, seems like 85 was working better. What does it actually do? How do I calculate it? Why don’t LM include it as an option? Sorry for so many questions! 

So edit that AM doesn't seem to be working right, at least for me.  My AM is set to force P3D on all 6 of my cores (I have an I5-9600k OC'd to 5ghz).  Yet it is using only cores 1, 3 and 5 aggressively. More research is required here.

Edit: I have posted the question on the prepar3d forum.

Edited April 18, 20206 yr by cwburnett

On 4/17/2020 at 2:44 AM, pilotngb said:

I left P3D a few months ago as I was fed up with the sinusoidal performance of my sim - one flight it looked amazing and then the next flight I suffered from slow loading scenery textures and micro-stutters. Switched to DCS and kept my passion for simming going. Reinstalled v4.5 there last month and accepted it for how it performed. Along comes Xplane vulkan and P3D v5. Great, time for smooth flying finally right? Only one sim is delivering that and its not v5. 

Default aircraft in P3D v5 (tested Cub and coupled with Orbx LC + region. FPS is good (expected with no add-on). Nothing but micro-stutters in external views and scenery textures constantly loading in as I fly around. PC specs should not be an issue. I can run other Direct X 12 applications with zero performance issues. As a test I've turned sliders way down to left hand side and tried HT ON/OFF and still the same issue. v5 should not be scenery popping with sliders almost full to the left. I keep on top of my hardware and keep applications to a minimum on my PC. v5 should be performing better.I will be trying a fresh installation tonight and failing that it will be a refund for me. But even stating I have to reinstall is not a great start on my relationship with v5. Disappointing. 

Just stick to DCS until things settle out in P3Dv5. Yeah, the regions are lacking but the flight experience in terms of smoothness and higher FPS are superior to anything else right now. Furthermore, everything you learn to do well in DCS (like correct navigation and landing procedures) will reap benefits when you cross back over to P3D or MSFS down the road.

Edited April 18, 20206 yr by Ezra

Reinstalled twice including in a new M.2. Updating graphics driver and deleted Orbx, Scenery still popping out at a horrendous rate.

I'm out for the time being. May re-invest in V5 in the future. Refund sadly requested. 

11 minutes ago, pilotngb said:

Reinstalled twice including in a new M.2. Updating graphics driver and deleted Orbx, Scenery still popping out at a horrendous rate.

I'm out for the time being. May re-invest in V5 in the future. Refund sadly requested. 

Remember, you can only get a refund one time per version.

Reinstalling won't help.  Finding the correct settings will.  Best of luck.

Hook

1 minute ago, LHookins said:

Reinstalling won't help.  Finding the correct settings will.  Best of luck.

Sadly with sliders low the scenery still constantly loads textures. At one point, buildings were literally rising from the ground as I flew around. Something is wrong. It shouldn't be my hardware. I don't think settings will help. I'll take my money back and look at reinvesting if MSFS2020 doesn't come out this year. I'll also go back to 4.5 which was flyable. Wish I never deleted it now!!

3 minutes ago, pilotngb said:

Wish I never deleted it now!!

This is why you never delete an old version of a program until the new version is working as expected. 🙂 If nothing else you'd still have access to anything you'd installed or changed in the old version.

Hook

On 4/17/2020 at 5:13 PM, Ianrivaldosmith said:

I’m g-sync 100hz and I’ve found enabling Vsync and triple buffering in p3d is making mine smooth? Is that the right thing to do? 

You know what Ian?  I have to apologize - I gave you some ill-informed advice... or at least incomplete.  I did some testing in v4.5, and in fact you are correct that enabling Vsync in the P3D menu DOES in fact make for smoother flight when Gsync is enabled.  I think the key though is having the fps target set in P3D at Unlimited - that way, the sim will output the best frame rate it can, your monitor will adjust to match, and (at least it appears) that with the Vsync box checked in the sim the P3D engine will try to match the timing of frames to where your monitor is already running.  There are some developers on here who know how the engine works much better who can confirm, but it seems the Vsync option inside P3D is not the same as Vsync for our monitors.

Setting an fps target in the Options menu might cause the sim to try to generate extra frames to match whatever the target is set for rather than what Gsync is adjusting to for a refresh rate, which can lead to mis-timing, stutters and reduced fps.  See this post and associated discussion:

Locking Frame Rate

You still don't want Triple Buffering set (either in the game or in the Nvidia settings), as you don't need it since your Gsync is already compensating and you don't want to add input lag.  And I set Vsync to On in Nvidia Control Panel just in case the frame rates exceed my maximum refresh rate which would lead to tearing - it likely won't kick in anyway since P3D is never getting to 100fps LOL.

Just wanted to correct the record since you were on the right track, and I learned something new!