when running FSX in windowed mode, press ctrl + alt + del, go to performance.
you will notice that one core is doing alot and the other is more or less idle
this can be fixed very easily

simply go to the processes tab
find fsx.exe
right click and go to set affinity
deselct cpu 1
then close the affinity window
go bk to the winow and reselct cpu 1
now when you go to the performance tab u will see the load is being shared across the two cores

and also if you have 1024mb of memory this is useful
start FSX normaly
while on the flight select screen
open up task manager (ctrl + alt + delete)
find fsx.exe
right click on it and set priority to high
this basicly gives more of your ram to FSX
DO NOT set the priority to Real time because this will more than likely lock up your system.

these 2 things helped my performance just thought i would post em incase people hadnt seen them before

cheers

john

EDIT: this has only been tested on an AMD x2 im not 100% if it will work with a intel core 2 duo, should do just thought i would add this

wow thanks man, anything to get rid of any lag 

wow flymo thanks for this find i will try it as soon as i get back home 

Quote:

Quote:



Hyperthread is not dual core.. the patch and fix only applies to dual core processors (one slug with 2 cores)or dual slug motherboards that use 2 physical processors.

Quote:


Did you apply the microsoft dual core hotfix, edit the regisrty and make sure the code line I showed in the thread posted above is in the boot.ini file?

If you are using all of the above and it is correct, then my question would be, was Windows installed while the dual core was in the system or did you go from a single to dual core processor?

If you installed windows on a single core and then installed a dual core after, you may be dealing with a known bug that can not be fixed without a clean install of Windows with the dual core in the system.

If you have indeed installed everything I posted correctly, when you boot any 3D application Windows should automatically assign affinity to CPU Core-0 without any need for the user to make a change... if it does not do that then there is something wrong.


However... if it works for you, stick with it. I am just letting you know what is correct and what is not correct with respect to how that works when everything is installed and running to spec.

The reason I posted that thread was so the user would not have to make the timing change manually, as we all had to do in the past prior to those updates, and so Windows would apply the correct resorces to the cores as needed.

Quote:



I was told when I was briefed on the project in March FSX would have a VISTA update that would address multithread however that may have been shelved.

Had the software been released for multithread, you guys on single cores would be angry right now.. and it would not have been released on time either.

I know VISTA handles a dual core differently from XP and because of that, FSX, even with without multithread code, will run better on a dual core than it will single simply because of the OS.

There are issues with multithread only a programmer or developer would understand. Most think... "hey, enable multithread and the program will run like a rocket".. That’s simply NOT true. There are allot of coding issues adding multithread would create and as I said before, you guys running single cores would be angry at the prospect. It would also require M$ come up with 2 different versions... another issue entirely.

We shall see what they do with the DX10 and VISTA update.

I cannot stress enough that VISTA and FSX will need 3 gigs of memory... 2 is the absolute minimum.

cool, i'm getting 4 anyway...