Does anybody know how to remove the annoying FSL's Recommendations prompt to change the Affinity mask?

I get it every time I launch P3Dv4 (via SIMstarter) even if I'm flying a different plane.

And if I select A320X it overrides my custom AM in a scenario no matter what I pick in FSL's Recommendations prompt every time I launch A320X.

Very intrusive and annoying attitude from FSL btw. 

Please check your custom AM in a scenario with FSL A320X, but not at a startup screen. You'll see it changes AM to 0 (all LPs are selected in Task Manager)

 

Edited March 4, 20188 yr by Dirk98

A kind soul on fsl forum suggested this edit:

Quote

Follow this path C: \ Users \ ........ \ Documents \ Prepar3D v4 Add-ons \ FSLabs \ Libraries \ FSL_Configurator.exe. And change FSL_Configurator.exe to FSL_Configurator ___. exe

 

Unfortunately no, this edit does not work for me. Something in A320X changes the AM back to =0 right before a scenario is loading.

  

I just moved that file to a different folder. Seemed to work.

5 hours ago, Dirk98 said:

Unfortunately no, this edit does not work for me. Something in A320X changes the AM back to =0 right before a scenario is loading.

  

Unfortunately it's impossible to remove. Apparently they're going to address this in an update.

I really hate when developers try to force their "i think this is the best" settings into you without a chance to remove or change them. In a product priced this high, it's ridiculous :(

I use Process Lasso Pro with a permanent "always" AM mask for Prepar3D.exe, which enforces an affinity setting externally.  I set the mask to disable CPUs 1 and 3 (equivalent to AM=245/11110101) and watch the CPU activity, and I don't see activity on the two disabled CPUs, where without the Process Lasso mask I see CPUs 1 and 3 loading up.

Regards

 

3 hours ago, w6kd said:

I use Process Lasso Pro with a permanent "always" AM mask for Prepar3D.exe, which enforces an affinity setting externally.  I set the mask to disable CPUs 1 and 3 (equivalent to AM=245/11110101) and watch the CPU activity, and I don't see activity on the two disabled CPUs, where without the Process Lasso mask I see CPUs 1 and 3 loading up.

Regards

 

Bob, what is your CPU? Anyway, what do you infer from your observations?

Thanks

1 hour ago, Dirk98 said:

Bob, what is your CPU? Anyway, what do you infer from your observations?

i7-7700K, HT on

It seems that Process Lasso Pro is able to force the affinity I want externally...if I let P3D use the second virtual CPU on Core 0, it's much less smooth.  With Lasso forcing the affinity it seems to work OK.

Regards

 

6 hours ago, w6kd said:

i7-7700K, HT on

It seems that Process Lasso Pro is able to force the affinity I want externally...if I let P3D use the second virtual CPU on Core 0, it's much less smooth.  With Lasso forcing the affinity it seems to work OK.

Regards

 

Yes, PLP is known to somehow overtake AM dynamically, but it may introduce its own problems to the performance. When you compared smoothness with FSL's affinity (255 for a 4Core HT on) did you launch PLP at all?

Yes.  Smoother with the AM applied externally by Process Lasso Pro than allowing FSL to hijack the affinity and set it back to unmasked (all processors enabled).

Regards

 

I'll try that as well, thank you.

1 hour ago, Nuno Pinto said:

I'll try that as well, thank you.

Just make sure that you set the affinity using the "always" dialogue in Process Lasso.  If you don't, it just sets the affinity at load and doesn't watch over it at runtime.

Regards