5 hours ago, GSalden said:

P3Dv4 Booster Live settings

• Fair weather 80%
• Cloudy - OC 70%
• 　
• Fair weather Frankfurt 50%
• Cloudy - OC Frankfurt 50%
• 　
• Fair weather Nice - Marseille - Barcelona - Milan 70%
• Cloudy - OC Nice - Marseille - Barcelona - Milan 70%
• 　
• Genova 70%
• London 60%
• Paris 60%

How did you come to use Booster Live?

Btw, I also found FPS 20 VSYNC On (Locked in P3D), Monitor refresh @20Hz the best fluid performance, particularly for the unruly FSL A320X.

 

Thanks,

10 minutes ago, GSalden said:

With V4 HT off + AM 62 was slightly better. With V4.1 this results in 100% load on 2 terrain cores

Still trying to dig this. AM 62 leaves out 4 terrain cores not 2 on a 6-core CPU, doesn't it? 

(1 1 1 1 1 0)

Thanks

30 minutes ago, Dirk98 said:

How did you come to use Booster Live?

Btw, I also found FPS 20 VSYNC On (Locked in P3D), Monitor refresh @20Hz the best fluid performance, particularly for the unruly FSL A320X.

 

Thanks,

When I purchased FTX Germany and used it with AS EDDF Pro and heavy weather conditions,  I started seeing some blurries. My FTFF was 0.01, so I needed more time for the terrain to avoid .

But every time I wanted to try a new value I had to re-start the Sim.

Booster Live can change it in realtime and the result can be remarked immediately. I now set it T the beginning according to my tested destination.

I have done several flights and some flights use different FTFF values for the best result ( see my Booster Live list )

As I use a triple view system good  loading loading is very important as that will suffer first before fps going down.

5 minutes ago, GSalden said:

When I purchased FTX Germany and used it with AS EDDF Pro and heavy weather conditions,  I started seeing some blurries. My FTFF was 0.01, so I needed more time for the terrain to avoid .

But every time I wanted to try a new value I had to re-start the Sim.

Booster Live can change it in realtime and the result can be remarked immediately. I now set it T the beginning according to my tested destination.

That sounds like a useful tool, I should get it.

Thanks!

8 hours ago, Dirk98 said:

Still trying to dig this. AM 62 leaves out 4 terrain cores not 2 on a 6-core CPU, doesn't it? 

(1 1 1 1 1 0)

Thanks

2 terrain cores were at 100%

The other 2 not

50 minutes ago, GSalden said:

2 terrain cores were at 100%

The other 2 not

With that AM you should have 3 terrain threads not 4. The thread/core after the main thread is the fiber thread.

4 hours ago, TheBoom said:

With that AM you should have 3 terrain threads not 4. The thread/core after the main thread is the fiber thread.

You are correct. I typed everything to  quickly..

11 hours ago, TheBoom said:

With that AM you should have 3 terrain threads not 4. The thread/core after the main thread is the fiber thread.

What is the fiber thread?

Thanks.

1 hour ago, Dirk98 said:

What is the fiber thread?

Thanks.

Sorry I'm not the person to answer that. Steve has mentioned it a lot of times in many of the AM related threads. It has to do with background tasks assigned by the engine other than scenery rendering, but that's all I know. You can't "remove" or not assign this thread its always there after the main thread.

47 minutes ago, TheBoom said:

It has to do with background tasks assigned by the engine other than scenery rendering, but that's all I know. You can't "remove" or not assign this thread its always there after the main thread.

Actually, that's a pretty good (non-technical) explanation of the fiber thread in P3D.

Thanks for the clarity!

Greg

35 minutes ago, TheBoom said:

Sorry I'm not the person to answer the that. Steve has mentioned it a lot of times over many of the AM related threads. It has to do with background tasks assigned by the engine other than scenery rendering, but that's all I know. You can't "remove" or not assign this thread its always there after then main thread.

Can anybody recall from the discussions how many terrain threads there are in P3Dv4? Are there 4 or 6?

Thanks!

 

57 minutes ago, lownslo said:

Actually, that's a pretty good (non-technical) explanation of the fiber thread in P3D.

Thanks for the clarity!

Greg

No problem glad I could help :).

 

9 minutes ago, Dirk98 said:

Can anybody recall from the discussions how many terrain threads there are in P3Dv4? Are there 4 or 6?

Thanks!

 

That depends on your processor or affinity mask setting.

Example you have a 4 core with HT, that means 8 threads. If you choose not to use an AM or use AM=255 it will use all cores. In this case, the first thread will be the main thread and the second the fiber thread. The rest (6 threads) will all be dedicated to scenery rendering.

If you have a 4 core or use an AM that enables only 4 threads, 4-2 = 2 left for scenery rendering.

If you have a 10 core CPU with HT and don't use an AM or use all threads, 20-2 = 18 cores for scenery rendering.

This is the main reason some people still see blurries with 4.1, by setting an AM that masks off cores, they usually do not have enough resources/threads left for scenery processing. Or settings that are too high for the available amount of resources.

22 hours ago, TheBoom said:

If you have a 10 core CPU with HT and don't use an AM or use all threads, 20-2 = 18 cores for scenery rendering.

Shanan, let me ask you this way -- how many cores do you think should be enough to allocate for terrain threads? 6, or 8 or 16 cores? And I'm asking about general consensus on the subject.

Thanks,

Edited January 3, 20188 yr by Dirk98

31 minutes ago, Dirk98 said:

Shanan, let me ask you this way -- how many cores do you think should be enough to allocate for terrain threads? 6, or 8 or 16 cores? And I'm asking about general consensus on the subject.

Thanks,

What I’ve noticed with my own testing and tweaking is that it is entirely dependent on your autogen settings as well as your core speeds. 

Open up task manager while flying over dense scenery and look at the threads. If they’re being maxed out consistently that means you could do with more cores dedicated to terrain loading. Also if you see any blurries that immediately means lack of terrain loading resources. 

I have an 8 core and use AM=255 (means 6 cores for terrain loading), even then I only use dense for scenery complexity and normal for both vegetation and building autogen. Anything more I see my terrain threads at 100% all the time and get autogen popping in. 

Best play with your settings and find out what’s best for your system. With a 18 core you should be able to do much better with more threads for terrain loading. 

A guestimate would be 8-10 cores at 4.5ghz with the most current CPU architecture for maxed out autogen. 

Although you should note that that would mean more stutters and less fps since you now have more threads drawing calls to the main thread and that is the unfortunate bottleneck of this engine. 

It’s all about the balance. 

On ‎1‎/‎1‎/‎2018 at 3:16 PM, gpf3m said:

I have a 6800K OC @4.3 with a 1080TI, running a 4K monitor.  The AM setting of 1365 and the TEXTURE_SIZE_EXP=9 addition seem to work well on my system, very smooth.  Its important that I run vsync on/ triple buffering with the target frame rate set at 30.

 

Running Prepar3d V4.1

Setting of AM 4093 works very well with my system with sensible settings.