Hi, I typically have FSX AffinityMask set to 14, with the main FSX load on Core01.

 

The Q400 provides smoother flight when I change back to the FSX default of 15 (for a quad core CPU).

 

So.. question:  Are there specific settings in the Q400 ini file that play nice with AM=14?

 

The comments in the ini file make me think there likely are - but it is not clear to me how to select them.

Ive played around with this and found 14 to still be the best for MY computer using the default Dash-8 ini. Ive lowered to 5 and 7 and seem to have got really blurred textures and no notable difference in performance. But, I had no problem with performance to begin with. I believe this has been extensively tested. perhaps all coincidence. Im not changing anything.

So the question remains:  What is the best ini file setting for those who use AM=14?

I was thinking about this... I personally run with HT on, just because some programs might get something out of it and I have a well cooled case. I've been running with AM=254 for quite a long time now, which works quite well for my system bundled with other tweaks i have. Now just yesterday I tried setting it to 84, which would be only physical cores allocated to FSX and the virtual HT cores off. Now, I got a lot more stuttering while looking around, fps was less stable and with the dash i got the jumping taxi thing that people have reported. All previous flights and flights after setting my AM back to 254 have been fine. 

 

I was thinking that would it be possible to set FSX running on physical cores (AM=84) and have dash-8 on virtual cores? I'm sticking with AM=254 for now as it is definitely smoother for my system. 

I usually have AM=14 on my optimized system, but I had noticed the other night that while on the ground, I was getting the odd stutter, even though FPS were stable and fine.  So prior to last night's flight (with it's other issues that I already posted about :unsure: ), I set AM=7.  Seemed to make a difference while taxiing, seemed smoother, but I'll need more time & testing to tell if that was actually the case.

I was thinking about this... I personally run with HT on, just because some programs might get something out of it and I have a well cooled case. I've been running with AM=254 for quite a long time now, which works quite well for my system bundled with other tweaks i have. Now just yesterday I tried setting it to 84, which would be only physical cores allocated to FSX and the virtual HT cores off. Now, I got a lot more stuttering while looking around, fps was less stable and with the dash i got the jumping taxi thing that people have reported. All previous flights and flights after setting my AM back to 254 have been fine. 

 

I was thinking that would it be possible to set FSX running on physical cores (AM=84) and have dash-8 on virtual cores? I'm sticking with AM=254 for now as it is definitely smoother for my system. 

 

I also have AM=254 set (i7 3770k OCed and well cooled, I do enough things for work on this machine that HT is useful) and I really have not noticed any changes when I decrease the AM; for instance 5 (physical cores 1 and 3 i believe). I do how ever get the start/stop effect with the Dash which apparently is related to AM and CPU usage. I am working with Majestic support via email and troubleshooting with different settings and have not been able to get rid of the start/stop. I was wondering what you all are using in terms of AM for the Majectic (can be set through the ini file) and FSX. 

Can you get Majestic support to explain what the ini settings actually mean?

Can you get Majestic support to explain what the ini settings actually mean?

+1 on that. I found the minimal instructions in the .ini file itself a bit "cryptic" - ie. confusing ... and I'm hoping there's a "magic bullet" hidden in there :lol:.

 

Are the .ini tweaks expalined in a user manual somewhere (I couldn't find anything)?

Not to the extent that anyone really understands... hence all the questions both here and on the majestic forum...

 

A

Not to the extent that anyone really understands... hence all the questions both here and on the majestic forum...

 

A

 

It's actual rather easy only some info typed wrong by the devs which can be confusing.

See my post here...

http://forum.avsim.net/topic/405948-q400-bouncing-at-startup/?p=2656680

 

Cheers,

I have always run my i7 2600K (I've disabled HT) with affinity of 14 but had horrible choppiness on the ground in the Dash. I set mine to 6 and immediately saw improvement. It doesn't appear to have affected the performance of FSX in general, but I've only flown the Dash since I made the change. I can't believe there has come a time when my precious little available opportunity for simming has been occupied by anything but the NGX, but I digress... I'll have to see if there is a performance difference when I do get around to the NGX again.

For me, 6 is working splendidly (details in sig). For someone with a nearly identical setup, 5 or 7 or 14 may work better. You really have to test each and see what you like/works best.

I believe there are two approaches that work..

 

You can change the Affinity Setting to accommodate the Q400, AM=7 works best for me..

 

Or, you can keep your favorite AM setting, AM=14 for me, and change the Q400 ini file.

 

Try this:

 

disableFSXCPUBypass=1
systemThreadsCPUMask=1
graphicsThreadCPUMask=1

I've got 2 cores, 4 threads, Affinitymask=5.

Can someone tell me which threads are used for FSX & what settings in the Q400 ini.file would be best for me with AM=5?

I would think that with Hyperthreading enabled, AM=5 means that FSX is running on your two physical cores.

 

5 = 0101

 

That does not leave any cores idle, so the ini file is best left alone, I would think.

 

Maybe the authors have programmed this so that the Q400 code can run on the "virtual cores",

but then they they need to show up here and provide some guidance (please!)  :unsure:

Thanx for answering Bert :biggrin: good to know I don't have to touch anything!