Archived

This topic is now archived and is closed to further replies.

captain420

Affinity Mask setting causes P3D to crash

Recommended Posts

Not sure but I read on here that a few users report that they get better performance by adding the affinity mask line into there p3d.cfg. Well I tried this and it crashed p3d upon startup. Any ideas?

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Never heard this. Can you please show what you entered in the cfg file?

Spirit

Share this post


Link to post

I had this:

 

[JOBSCHEDULER]
AffinityMask=14

 

I tried setting it to 84 also, so I removed those lines and P3D loads again. Is this setting suppose to improve anything?

Share this post


Link to post

I'm running this entry (AffinityMask=14) to help texture loading with photoscenery, and it seems to work, as it did with FSX... I've not had any issues with it added to the cfg like the op.

 

Is it a true crash, or going to a black screen?

Share this post


Link to post

It actually crashes P3D when I have that setting in my cfg file so I'm not sure what the deal is. It loads up with a black screen then it crashes.

Share this post


Link to post

Did you place it correct? Even LM recommend this entry in their P3D v2 manual.

Spirit

Share this post


Link to post

Could be an unstable overclock.. and by spreading the load with affintymask triggers the crash.

Share this post


Link to post

I have had that tweak/fix all the time and have no problems with it.

Share this post


Link to post

If you have an i7 with hyper threading (HT) enabled then affinity mask should be 244.

 

An i7 with HT disabled in the BIOS should have AF=14

 

An i5 doesn't have HT so AF should also be =14

Share this post


Link to post

If you have an i7 with hyper threading (HT) enabled then affinity mask should be 244.

 

An i7 with HT disabled in the BIOS should have AF=14

 

An i5 doesn't have HT so AF should also be =14

 

I thought it was suppose to be 84 for i7 with HT enabled?

Share this post


Link to post

EDIT: You need to provide more detailed info on exactly what happens when you say "Crash" ... error message, anything in event log, screen just freezes, blue screen, RTD?

 

Affinity setting shouldn't make it crash unless you have an unstable overclock.  For me, Affinity=14 actually introduced a texture loading problem (black texture titles), I'm running Affinity = 4088 (on my 6 x 6) and lock frames at 20 fps.

 

I would get repeatable crashes when I defaulted my startup Airport to any of those under Virtuali (FSDT/FB etc.) -- try defaulting startup to another location that is a default P3DV2 airport (I use Minnesota St.Paul).

 

Another product that would crash P3DV2 was DXTORY (Video capture software similar to Fraps).

 

I don't know if this is relevant, but I always start P3DV2 in a "Paused" state.

 

Another good thing to do is delete your shaders folders (especially after a crash or OOM in P3D) in case something got corrupted because of a crash.

 

And finally, go thru your EXE.XML and DLL.XML to see what else is enabled and try disabling entries and determine if one of those is the source.

 

Hope this helps.

Share this post


Link to post

I believe AM=84 disables the 4 virtual cores, without needing the BIOS to be changed, while 244 uses 7 of the 8 total cores.

I am no expert, just reporting what I have read!

Share this post


Link to post

Are you sure? Because I got my number from a website that calculates it out for you and tells you what affinity mask level you need to use. I have an i7-3770k OC to 4.5ghz with HT (I'm assuming so because when i go to the task manager, I see 8 bars). It says to use 84.

 

This was the site I used. Affinity Mask Calculator

 

http://www.gatwick-fsg.org.uk/affinitymask.aspx?SubMenuItem=hardware

Share this post


Link to post

No need for a fancy site - it's a simple bit correlation, with 1=on and 0=off.  You read right to left starting with physical core zero.  84 in binary is 1010100, thus core 0 will not be used at all, and cores 1, 2 and 3 will have their physical cores used, but not the HT cores.  This is basically the same as 14 (1110) on a 4 core, no HT system.   Which one is "correct" depends on what you're trying to do.  Do you want only the last 3 physical cores enabled in system with HT enabled?  Then 84 is "correct".  Do you want the last three cores with full HT?  Then you want 252 (11111100).  And so on...

 

BTW, the only real "tool" I use for quick'n'dirty decimal to binary conversion when I get much past 16 is the built-in Windows calculator. :-)

 

Scott

Share this post


Link to post

 

 


while 244 uses 7 of the 8 total cores.

 

No, 244 gives you this: 11110100

 

Reading from right to left, cores 0 and 1 are not used, core 3 is used,

core 4 is not used and the remaining 5,6,7,8 cores are used.

 

gb.

Share this post


Link to post