Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Getting a new system for FSX

Featured Replies

My recommendation would be to turn HT off and use AM=14, but I know there are others who like HT on..

Bert

  • Replies 31
  • Views 4.6k
  • Created
  • Last Reply

Top Posters In This Topic

The benefits of using AM settings (and using none at all) are pretty much tied to the software mix of individual systems.  That being said, using AM=252 in fsx.cfg would probably yield terrible performance for any hyperthreaded (HT) system (BTW where did you get that value?).  FSX itself does not benefit from HT, though it's not harmed by it either (except for AM values which put the main thread and a texture loader thread on the same physical core, e.g. 252).  I suggest not using any AM value initially and take it from there (and beware that the placebo effect can be overwhelming).  I hope that system has a pretty good CPU cooler, for running a haswell OC with HT on really boosts temps, and that's why lots of OC'ed FSX system owners disable HT (myself included).  BTW, that is a really great system for FSX.

CPU: AMD 9800X3D PBO MB +200 CO -25| Motherboard: MSI MAG X870e Tomahawk WiFi | GPU: MSI RTX 5090 Ventus 3X OC | RAM: G.Skill 2x32GB DDR5 6000 cas 30 | M.2 SSDs: Samsung 990 EVO Plus 2T, WD Black SN750  M.2 1T | Hard Drive: WD Black HDD 6T 7200 | Optical Drive: LG Bluray writer, internal | Cooling: Thermalright Phantom Spirit 120 EVO | Case: Fractal Design Focus G | PSU: NZXT C1200 1200W

Win 11 Pro 64|HP Reverb G2 revised VR HMD|Asus 25" IPS 2K 60Hz monitor|Saitek X52 Pro & Peddles|TIR 5 (now retired)

Agreed... AM=244 might be worth a try if you have HT enabled

 

11 11 01 00

 

or AM=84

 

01 01 01 00   which is essentially the same as 14 with HT off  (1110)

Bert

  • Author

The benefits of using AM settings (and using none at all) are pretty much tied to the software mix of individual systems.  That being said, using AM=252 in fsx.cfg would probably yield terrible performance for any hyperthreaded (HT) system (BTW where did you get that value?).  FSX itself does not benefit from HT, though it's not harmed by it either (except for AM values which put the main thread and a texture loader thread on the same physical core, e.g. 252).  I suggest not using any AM value initially and take it from there (and beware that the placebo effect can be overwhelming).  I hope that system has a pretty good CPU cooler, for running a haswell OC with HT on really boosts temps, and that's why lots of OC'ed FSX system owners disable HT (myself included).  BTW, that is a really great system for FSX.

 

I've read it on the internet that AM=252 is 11 11 11 00 are you sure on that? And the system is water cooled and passed huge stress tests without issues

 

Agreed... AM=244 might be worth a try if you have HT enabled

 

11 11 01 00

 

or AM=84

 

01 01 01 00   which is essentially the same as 14 with HT off  (1110)

 

I will try those out soon as my FSX is installed. So if I set AM=244 it uses all of the virtual cores except 3 right? Which in the second one only 3 of the cores, and the other 5 being left off

 

Best Regards

Orcun Günaytekin

 

Banner_FS2Crew_Supporter.jpg

 

I will try those out soon as my FSX is installed. So if I set AM=244 it uses all of the virtual cores except 3 right? Which in the second one only 3 of the cores, and the other 5 being left off

 

Best Regards

 

Correct

Bert

  • Author

Correct

 

So I will probably use the first one to make the most out of it, thanks for the help. Now the only question is if AM=252 is really that wrong or not

 

Best Regards

Orcun Günaytekin

 

Banner_FS2Crew_Supporter.jpg

There is no right or wrong here... it is a matter of trade-offs.

 

But remember that FSX loads up the first core that it has access to with it's main rendering load (the one responsible for fps..)

 

The other cores are used for texture loading..

 

So, 252 allocates both virtual cores on the second physical core to FSX - and FSX will fully load this core anyway..

 

So that is why that decision would raise eyebrows.. -_-

 

252 = 11 11 11 00

Bert

  • Author

There is no right or wrong here... it is a matter of trade-offs.

 

But remember that FSX loads up the first core that it has access to with it's main rendering load (the one responsible for fps..)

 

The other cores are used for texture loading..

 

So, 252 allocates both virtual cores on the second physical core to FSX - and FSX will fully load this core anyway..

 

So that is why that decision would raise eyebrows.. -_-

 

252 = 11 11 11 00

 

Alright so AM=244 feels just right or which one would you use? This is the only thing im unsure at about FSX

 

Best Regards

Orcun Günaytekin

 

Banner_FS2Crew_Supporter.jpg

Alright so AM=244 feels just right or which one would you use? This is the only thing im unsure at about FSX

 

Best Regards

Use 244. FSX still has several more threads that arn't and can't be assigned with the affinitymask and those can utilize all your cores.

 

Do not use 252 as has been pointed out earlier its a bad setup that induces stutters and FPS drops.

 

Finally, put both OS and FSX on the SSD. That will give you the smoothest flight.

Do not use 252 as has been pointed out earlier its a bad setup that induces stutters and FPS drops.

 

AM=252: been there, done that...you will get the above results using it even with that OCed DC processor.  As for which AM value is right?  Try them all (no none at all) and see which works best for your setup; there is nothing to lose doing this, except for some of your time, of course.

CPU: AMD 9800X3D PBO MB +200 CO -25| Motherboard: MSI MAG X870e Tomahawk WiFi | GPU: MSI RTX 5090 Ventus 3X OC | RAM: G.Skill 2x32GB DDR5 6000 cas 30 | M.2 SSDs: Samsung 990 EVO Plus 2T, WD Black SN750  M.2 1T | Hard Drive: WD Black HDD 6T 7200 | Optical Drive: LG Bluray writer, internal | Cooling: Thermalright Phantom Spirit 120 EVO | Case: Fractal Design Focus G | PSU: NZXT C1200 1200W

Win 11 Pro 64|HP Reverb G2 revised VR HMD|Asus 25" IPS 2K 60Hz monitor|Saitek X52 Pro & Peddles|TIR 5 (now retired)

  • Author

Alright guys many thanks!!! Finally my problems solved! :lol: ^_^

 

Happy flyings! :-)

 

Best Regards

Orcun Günaytekin

 

Banner_FS2Crew_Supporter.jpg

So what AM do you use now ?

5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 -  MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb -  Corsair 5400  case - Corsair 360 liquid cooling set  - 3x 75’ TCL tv.

13600  6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb  - 1x SSD M2 2800/1800 2TB - 2x  Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - 

FOV : 200 degrees

My flightsim vids :  https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0

 

  • Author

So what AM do you use now ?

 

The truth is I didn't even need to set any tweaks in the FSX.cfg and it still was running at 30 FPS locked without problems + all sliders to the max. But im using AM=244 just in case.

 

Best Regards

Orcun Günaytekin

 

Banner_FS2Crew_Supporter.jpg

  • 3 weeks later...
  • Author

Turned HT completly off and deleted AM off the .cfg it caused blurries. VSYNC at 1/2 and frames locked and stable at 30.

 

Best Regards

Orcun Günaytekin

 

Banner_FS2Crew_Supporter.jpg

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.