Reading many post about multi-core use and it being the future, I feel not only should the developers at ACES be working towards writing programs to make use of it but so should add-on developers.This can be a very useful marketing tool and since this is where the tech industry is going then so should "all" developers. Not all add-ons can make use of multi-core but the ones that can should.Planes that have involved systems should- as an example.I have recently joined the camp of those who feel its time that we retire the format of FS2000-FSX and use the next version to make the needed changes to start a new series which might require not all add-ons work for the next version as long as the next version makes high use of multi-core.This is a great time for ACES to make the next version designed with mulit-core and DX10 benefits. One more thing to add about the auto-gen problem...I like many are to blame for the fact that we got what we asked for. We wanted plenty of eye candy and we got it. The only problem is the sliders aren't set low enough.Its just a shame that many new users might not know about how to fix it unless MS puts out a patch.

How exactly do you suppose addon companies can do multi-core when the platform the addon is running on isn't really using it? That'd be like asking for multi-core applications for Windows 98 or something.

>How exactly do you suppose addon companies can do multi-core>when the platform the addon is running on isn't really using>it? That'd be like asking for multi-core applications for>Windows 98 or something.All depends on what the add-on is doing. If it's linked into the system via the SimConnect interface, then it's already running in a seperate process/thread from the sim itself and then there's no reason you couldn't make your add-on make use of multiple threads.If you're working on something that is more directly tied into the simulator (like an aircraft or gauges, etc.) then yes, you're stuck with whatever the platform gives you.I suspect that many of the add-ons that currently are linked via FSUIPC will get changed over to SimConnect and that will help as us Dual core users will see those apps run in the 2nd core while the Sim is pounding on the 1st core.There have also been statements by the ACES team members here that they ran out of time to fully implement all their ideas for multi-threaded behavior because they had to get features done. Now that the release is due out soon, they are going back and looking at finishing up the multi-threaded support so it's ready for the first big patch.--2002cbr600f4i

The biggest consumers of processing cycle from the primary core is AI and Addons ceneries like Fly Tampa and like you said.. Aircraft systems.I am not sure if these two would benefit from Sim connect.Manny

Be it gauges or Flight Sim, the biggest consumer is not systems but graphics (rendering and displaying graphics). Well, sure enough, I know some TAWS systems implemented in a commercial aircraft that indeed prooves the contrary (in this case, systems are the biggest consumer in bringing FPS down to a few with a TAWS update rate of 1Hz) but most of the systems are usually well coded and should take very little of our 2GHz+ CPUs nowadays.However, while everyone complains about FSX not using the other core, maybe like you say this is an opportunity for add-ons to exploit the unused power available out there to some extent in order to reduce the load overall.