Products Support > GSX Support FSX/P3D

Performance decrease noticed after installing GSX

<< < (2/3) > >>

virtuali:

--- Quote from: tnorton776 on February 03, 2012, 02:05:19 am ---Yes but thats the catch, because we all know how rediculously CPU intensive FSX is. If the coatl engine is now taking more processing power from my CPU to run all the airport services, it is definetly going to have varrying degrees of performance hit if it is not yet fully optimized.
--- End quote ---

That's exactly the opposite: if FSX has a problem, is that it doesn't use ENOUGH CPU! Of course, I'm referring to the total amount of a modern multicore system. The biggest problem in FSX is that it occupies ONE CPU at 100%, and the rest not really so much.

Which means, there's a lot of spare power in those other cores, enough probably to run another entire simulation in parallel...

If Couatl was an internal module, running in the same process space as FSX, it would have to either not being multithreaded at all, so it would have the ability to decrease FSX fps or even pausing it when doing its own calculations, or if it was multithreaded, it would have real concurrency problems working with FSX, which is not really thread safe, having a multithreaded module inside FSX, assuming it's even possible, is so complex and unreliable, that I doubt any FSX developer has even tried it.

Which is why, OTHER modules, loaded as .DLL, have the ability to slow down FSX, but NOT GSX.

BECAUSE, if you followed all the explanation so far, with Couatl being an separate Executable, has its own separate threads that can't conflict with FSX, so it can be as multithread as it could without any issues AND, it will be scheduled automatically by Windows to use those famous spare CPU cycles that every modern systems has in quantity.

So, to give an example, if GSX needed to calculate a path for a vehicle on a very complex AFCAD with hundreds of nodes, the only effect of this would be that the vehicle might start a *bit* later, but FSX wouldn't be slowed a bit in that time.

Not to mention that, when you are not using GSX, is not running any code at all, let alone a complex one (which wouldn't slow down FSX in any case).

That's why I'm saying it's really not possible that GSX could slow down FSX, just by being installed.

And, if you already had any FSDT scenery before, you already had Couatl running in the background.

tnorton776:
well if that is the case, which I really hope it is.. then shame on microsoft for only making the game utalize one core... I cant understand why a game so graphically intensive would only utalize 1 core... they had quad core CPU's in 2006-07... And surely microsoft is smart enough to know that high tech multi core CPU's were going to be utalized and greatly enhance game performance

Nocaltom:
My system has no performance hit at all with GSX installed and both FSDT airports, klas and kdfw. Just my 2 cents.

Tom

Joe Porter:
My FPS has been cut in half.  I had this happen with another of your products before and it has something to do with your install/ manager program where you can change CFG settings for you scenerys.  I made the mistake of saving when I activated GSX with it.  It makes changes to FSX cfg when using it, especially if you save the FSX CFG setting from there.  I had to fix this before.  It was not necessarily from GSX itself. 

I will have to go back to tweaking again. Unfortunately.

Joe

virtuali:

--- Quote from: Joe Porter on February 03, 2012, 07:25:49 am ---I had this happen with another of your products before and it has something to do with your install/ manager program where you can change CFG settings for you scenerys.  I made the mistake of saving when I activated GSX with it. 
--- End quote ---

Well, of course changing settings and pressing "Save to FSX", you should expect that settings *will* be saved to FSX.

But note the settings you see in the Addon Manager before you touch any of the sliders, are taken from your actual FSX.CFG file so, if you just change FSDT-only settings, and press Save, nothing will change compared to before, because it would write back the same values you had before opening it.

It's only if you play with FSX-related sliders (or press the "Defaults" button) and THEN Save, that you are making a difference in your settings.

Navigation

[0] Message Index

[#] Next page

[*] Previous page