Hi Gerard, you've got 6 cores so your addons have got a whole dual core to go at. You're using 340 which gives a little bit more headroom to the rest of the show than 1360. You can extend the addons over some of the the sim cores, but I doubt you need to.

Thing is, Gerard, that with the four core, it's more of a balancing act because the apps are all going to coincide. But at least we can keep their main activity away from the main sim core. If we really need to we can push the sim onto three cores. But you've got two free cores. With the 6 core HT enabled, and AM=340, your addons hit core zero, and core five will still be relatively free for activity like Rob reported which is emanating from utilising system resources.

Steve,

 

P3Dv3 is at AM 340.

All other programs at 0,1,10 and 11 ( Process Lasso ) :

 

- Prosim 737

- Prosim MCP

- Prosim Panel

- Opus FSI Server ( only buttkicker )

- SIOC 

 

I have one issue : SIOC ( Opencockpits hardware program ) stops responding after 30-60 minutes...

 

So I was thinking of setting the other addon programs to core 0,1 and 10.

And SIOC to 10 and 11.

 

Can you advice on this ?

 

Thanks, 

Hi Gerard, some programs, just don't like being moved. Any odd behaviour, better to just let them run as normal and the jobscheduler will take care of it.

That might be it as before Process Lasso I never had this issue with SIOC.

4 core HT enabled, 4 LPs one per core configuration

AM=85=(01,01,01,01)=0,2,4,6 P3D

F8=248=(11,11,10,00)=3,4,5,6,7 Addons

 

 

Using 4 core with HT, AM 85... Most times using GTN 750 I would get non-reaponding click spots on GTN.

 

GTN setup program has a place to specify which core to run on. I set the GTN 750 to core 5 and no longer have the problems.

Thanks.

If a program has it's own way of setting affinity then you must use that.

 

Using 4 core with HT, AM 85... Most times using GTN 750 I would get non-reaponding click spots on GTN.

 

GTN setup program has a place to specify which core to run on. I set the GTN 750 to core 5 and no longer have the problems.

Thanks.

core 5? Do you mean LP5 on core 2?

 

...yes you do. Interesting though since the GTN wouldn't know the difference which core or LP it's assigned to. LP5 is especially a problem for a dual core.

 

Am I to presume you get the click spot problem if you use process lasso?

...The moral of the story is to always use the affinity setting the app provided in it's own config if it has it, and for other apps, if there is any odd behaviour, don't lasso it. In the case of the GTN, it doesn't matter what LP is allocated, and with AM=85, setting it to 5 is a good choice.

Gerard you still pulling your hair out or flying

Gerard you still pulling your hair out or flying

This afternoon I was able to make a flight from Amsterdam to Schiphol without any issues.

 

I had to do 3 things to solve the SIOC issue and I needed all three of them :

- connected the CDU usb cable to another free port

- first startup Prosim and then SIOC

- SIOC now is allowed to use all cores in Proces Lasso

The GTNs and the SIOCs can be started with the .bat methods I posted if you want to set affinity on them.

The GTNs and the SIOCs can be started with the .bat methods I posted if you want to set affinity on them.

My other addon programs are working fine through Proces Lasso so with SIOC set to all cores I am fully covered ...

 

Thanks,

That's great Gerrard.

 

Folk need not shy away from using the .bat's, since they use the starting method that Windows uses to start apps, and so are completely reliable. They can be assigned a shortcut by right-clicking and dragging, and the shortcut can happily replace the shortcut installed for the app.

Last question regarding finetuning

 

What about the settings for :

 

• Texture_Bandwith_Mult
• TextureMaxLoad
• FFTF
•  

Now we are with P3Dv3, do I need to delete , add olr modify ?

I am using photoscenery only + custom autogen placed on top of it.

 

 

Thanks, 

TBM is difficult to determine without test results.

[Display]

TEXTURE_BANDWIDTH_MULT=180 (Smoother texture handling with medium+ autogen.)

 

I tested that and you're probably in the region of 200 if you've left the cfg TextureMaxLoad defaults.

 

Give more time to background tasks and maybe reduce blurry textures if that's a problem:

[Main]

FIBER_FRAME_TIME_FRACTION=0.40 - 0.50

 

FFTF is not included in the cfg