12 minutes ago, DylanC said:

David, are you using NVI to force AA into P3D in conjunction with P3D's internal AA setting?

used both, 4xsgss enhancing 4xmsaa and with it off. 20fps in cities with any setting

9 hours ago, DylanC said:

David, are you using NVI to force AA into P3D in conjunction with P3D's internal AA setting?

I believe I have it set to application controlled

Ground traffic hits my frames as well on my 6700k with a 1080TI.

I'm running 4k, most sliders to the right, no AI or ground traffic. AS16 + PMDG 744 + FSDT KJFKv2 (no ORBX yet) = fps on mid-high 20s.

Can't wait to add ORBX FTX Global, LCs and Vector ... I'm sure it'll drop my fps to low 20s to high teens.

Guess we're slowly getting our performance-reality dose one add-on at a time ;-)

12 minutes ago, evaamo said:

Ground traffic hits my frames as well on my 6700k with a 1080TI.

I'm running 4k, most sliders to the right, no AI or ground traffic. AS16 + PMDG 744 + FSDT KJFKv2 (no ORBX yet) = fps on mid-high 20s.

Can't wait to add ORBX FTX Global, LCs and Vector ... I'm sure it'll drop my fps to low 20s to high teens.

Guess we're slowly getting our performance-reality dose one add-on at a time ;-)

I added Global/OpenLC America/socal and my fps are 10-20 in a big city like LA with ground traffic at 10%. slight increase in fps about 5 if ground traffic disabled. At least no out of memory errors...

Guys, there's no way out. You need to untick high resolution terrain and speedtrees. AA setting also plays a big part. And dynamic lighting. I guess we wanted the GPU to take over. Seems LM delivered. But at a cost. 

15 minutes ago, flytrumpet767 said:

Guys, there's no way out. You need to untick high resolution terrain and speedtrees. AA setting also plays a big part. And dynamic lighting. I guess we wanted the GPU to take over. Seems LM delivered. But at a cost. 

I have unticked " high resolution " and speedtrees. Also running at 4xMSAA. Dynamic lightning is off. In my case, the CPU seems to be the bottleneck, not the GPU.

Must say even at low 20s, the sim fluidity is wonderful.

36 minutes ago, 777200lrf said:

I added Global/OpenLC America/socal and my fps are 10-20 in a big city like LA with ground traffic at 10%. slight increase in fps about 5 if ground traffic disabled. At least no out of memory errors...

Indeed... checking the VAS counter like crazy or the paranoia of opening a 2nd window, calling gsx or going to outside view after landing due to OOMs (if you made it to the airport, that is) is something I'm definitely NOT going to miss, ever. Even if that means saying goodbye to a few lovely add-ons, such as the Simcheck A300.

Very happy with v4 so far!

cheers

-E

On 5/31/2017 at 9:25 AM, Christopher Low said:

Why would having Hyperthreading switched off make such a huge difference to framerates? If that was the case, anyone with a CPU that does not have hyperthreading would be getting a raw deal

With all incarnations of P3D I've tested with HP on and HP off, I have never seen any difference whatsoever. If I have seen a difference, it was with HP on, when it was a nats less smooth, but that's all.

22 hours ago, Rockliffe said:

With all incarnations of P3D I've tested with HP on and HP off, I have never seen any difference whatsoever. If I have seen a difference, it was with HP on, when it was a nats less smooth, but that's all.

Sorry, I meant to say... If I have seen a difference, it was with HP off, when it was a nats less smooth,

JFYI : yesterday my sim was stuttering. Framerate up/down from 37 to 4 and up. I only installed some extra scenery. New p3d.cfg file did not solve it.

Than I saw that my P3Dv4 SSD was more than 85% full. It had only 11% left.  The moment I placed the new scenery to another drive and I had 16% empty space it was running smooth again. 

The performance of a SSD goes down very rapidly if it has less than 15% empty space... 

13 minutes ago, GSalden said:

JFYI : yesterday my sim was stuttering. Framerate up/down from 37 to 4 and up. I only installed some extra scenery. New p3d.cfg file did not solve it.

Than I saw that my P3Dv4 SSD was more than 85% full. It had only 11% left.  The moment I placed the new scenery to another drive and I had 16% empty space it was running smooth again. 

The performance of a SSD goes down very rapidly if it has less than 15% empty space... 

My SSD Samsung 1TB EVO 850 has an software that "steels for performance" if accepted , about 10% for none allocated space.

Is this  included in your 15% or is is just a reformatted drive at 100% ?

My 1TB is actually max at 838GB when using my method above by Samsung Magian

 

Thanks

Michael Moe

 

 

 

30 minutes ago, Michael Moe said:

My SSD Samsung 1TB EVO 850 has an software that "steels for performance" if accepted , about 10% for none allocated space.

Is this  included in your 15% or is is just a reformatted drive at 100% ?

My 1TB is actually max at 838GB when using my method above by Samsung Magian

 

Thanks

Michael Moe

 

 

 

I just look at how many is available at My PC . If it is 15%+ then I am at the safe side.

 

According to Samsung, having a certain percentage of free space available at all times will improve the performance of data relocation operations, which the drive carries out internally. For this reason, the drive has an option to reserve some amount of space (hide from the system) for such purposes. This is what is called "overprovisioning".

As long as the drive has sufficient amount of free space, there's no need to reserve anything. The drive will use the regular free space to perform its internal operations. Overprovisioning is only needed to prevent the situations when the free space becomes limited.

It is certainly not required. The drive always have some (relatively small) amount of space unconditionally set aside to use as intermediate buffer for data moving operations. I.e. it comes slightly overprovisioned from the factory. However, that buffer is typically much smaller than the optimum value, meaning that the performance will drop as the drive gets close to full. How much it will drop depends on the implementation. For example, it obviously depends on the size of that unconditional minimal internal buffer

 

 

 

wrong post.