I have made a page on my forum that explains:

 

how to make a batch file (.bat) to start apps with affinity

 

Hello !

I tried with TrackIR. I succed, I tried with ASnext, I failed...

I tried AAAA (only the 8 virtualcores)

Hi Steve.

Question, with my Saitek flight controls/rudder pedals and mic would I need to allocate them also to cores 0,1,6,7?

 

cheers

Mike

Interestingly AM=116 gives awful blurries on my system (i3770k @ 4.6ghz with HT on), so I'm back with no AM at all and assigning ASN only to Core 3 (first core after main thread and two fiber threads). I works ok so far. My frames are locked at 60 when flying A2A C172 or RealAir Legacy v2, with FTFF=0.01, never seen such a smooth performance, ever! It is so smooth that I simply still can't believe that could be achieved, especially on my system! When flying NGX or Airbus X, I just lock frames to 30. 

@Pe11e - I run AM=116 on my 3770 and don't have the blurry issue.  BTW, FFTF 0.01 is an invalid entry - valid are 0.10 to 0.99.  IIRC when you have an invalid input it uses the default of 0.33 rathe than the closest valid entry (0.10).

 

Vic

@Pe11e - I run AM=116 on my 3770 and don't have the blurry issue.  BTW, FFTF 0.01 is an invalid entry - valid are 0.10 to 0.99.  IIRC when you have an invalid input it uses the default of 0.33 rathe than the closest valid entry (0.10).

 

Vic

 

I'm quite sure that other suggested 0.01, not 0.1. Anyway it works really fine with locked frames. When I was on unlimited frames I didn't added FTFF tweak, so it was on default 0.33.

When I was using AM=116 I avoided using FTFF because I didn't locked the frames. Maybe I should lock the frames with AM=116? Whatever it is right, my sim is now ultra smooth, even with Aerosoft Airbus aka stutter monster, so if something is working pretty good, don't touch it, and I shouldn't too.

I have my frames locked but I am also running two 970's in SLI. Perhaps that makes a diff to the blurries.

 

Vic

If it helps anyone this is how I have P3D set up on my 6 year old PC. I am using Nvidia driver 361.43. Not the latest version which causes performance issues and stutters in my P3D.

 

No AM in P3D.cfg. No other "tweaks" in cfg.

 

Like many I use Project Lasso https://bitsum.com/ and have set P3D to run on Cores 1,2,3,4,5,6,7. ASN and other processes (ie antivirus) running on Core 0 only. P3D is in "gaming mode" (option in Project Lasso). Both antivirus (Windows Defender and malwarebytes) have P3D folders added in "exceptions"

 

I don't use Nvidia Inspector. I find the graphics in P3D perfectly acceptable without (on my system at least).

 

I run GPU TWEAK http://www.asus.com/supportonly/ASUS%20GPU%20Tweak%20for%20Graphics%20cards/HelpDesk_Download/ in the background. No overclocking. I just set GPU TWEAK to limit frames to 60fps.

 

In the P3D settings FPS is set to unlimited. No V sync or buffering.

 

I don't use HDR and never have in P3D. In my opinion it makes the sim look like an animated movie. Not realistic. HDR also kills some FPS on my system.

 

I don't use Volumetric Fog, I can't see much benefit and it also kills some FPS.

 

I have cloud shadows on 20000 and set to low quality. No terrain shadowing - it looks awful on my system (shaded areas popping on and off randomly).

 

I run ASN with 3-4 layers depending on the actual weather. In P3D settings clouds are set to "medium".

 

That's my setup. Works nicely in most situations. I've noticed that the Orbx/FTX products are major contributors to stuttering on my PC so will be removing all of them during my next reinstall and just using something like UTX. Had enough of FTX taking over my sim with no easy option to uninstall.

 

Hope this helps!

 

Adam

@Pe11e - I run AM=116 on my 3770 and don't have the blurry issue.  BTW, FFTF 0.01 is an invalid entry - valid are 0.10 to 0.99.  IIRC when you have an invalid input it uses the default of 0.33 rathe than the closest valid entry (0.10).

 

Vic

 

I thought it was 0.01 ?

I thought it was 0.01 ?

Regardless of the people that use it, the valid range is 0.10 and 0.99. An invalid entry like 0.01 will go to the nearest valid setting - in this case 0.10.

 

This is according to Phil Taylor and the guys at Aces and TMK this has NOT changed in P3D.

 

Vic

I don't think SLI makes a difference when it comes to blurries. The autogen is handled by the CPU.

 

I also have noticed that an AM of 116 seems to cause blurries for me in 3.2. 248 seems to work better for me unlocked frames and no FFTF.

Regardless of the people that use it, the valid range is 0.10 and 0.99. An invalid entry like 0.01 will go to the nearest valid setting - in this case 0.10.

 

This is according to Phil Taylor and the guys at Aces and TMK this has NOT changed in P3D.

 

Vic

 

Ok thanks. I have it at 0.01 so it will show as 0.10? So i can just leave it at that then?

Ok thanks. I have it at 0.01 so it will show as 0.10? So i can just leave it at that then?

If that works for you, sure.

 

The problem is that some people just read about a "tweak" and just plug it in. They have NO idea what it does or even if it works on their system.

 

If one must do it that way, my suggestion is to insert the tweak and fly for a week - see how it goes. Then remove it - fly for another week - see any difference? If not - keep flying and ignore the tweak.

 

This is ESPECIALLY true for things like FFTF and TBM - those settings are really system dependent.

 

 

Vic

This is ESPECIALLY true for things like FFTF and TBM - those settings are really system dependent.

 

Having FFTF gives me better smoothness really. Buy yeh i get what you are saying

If this is the case then do you still in PL create CPU affinity on the other apps/addons, i.e. ASN? If so which cores do you select if you don't know which P3D will be running against?

 

EDIT... Ignore this question above... I've read the thread further and this has been answered...

 

 

HOWEVER.. One question I do have around Process Lasso is I have tweaked many settings and want to restore them to default to start again. Can anyone tell me how to do this please??

I would also like too know how PL can be reset too default , without having to reinstall .

Cheers

Riche

In Process Lasso, when you set a program to Game Mode, Process Lasso gives priority CPU processes to that program and its related CPU threads. That is why it straightens out your sound.  

I would also like too know how PL can be reset too default , without having to reinstall .
Cheers
Riche

There is an option for setting PL back to defaults, just don't remember where it is, but it is there. I've used it before. You can also go back to the process you assigned properties to and you should be able to find a way to reverse the settings. Apologize for no specific directions at this moment.