Hello to the forum,
I use to run Orbiter since 2008 and never had any issues of low frame rates/ FPS on my old computer, even with best graphic settings and using 2 monitors full of ext mfds.
Now, with a new gaming pc, I am able to run the newest games like Assetto Corsa with stable high frame rates, but in Orbiter it behaves strange.
Starting a scenario it I get ridiciously high rates of sometimes over 200 fps in the beginning, then it levels out at 130 frames.
If I THEN open up just one single external MFD (which I use to place on the second monitor, but it makes no difference), for example the orbit mfd, the FPS-Rate decreases dramatically to 4!!! frames or so.
The whole simulation stucks and stutters and is not playable anymore.
Now if I just push the middle button of the mfd, like for choosing another mode ( just disengage orbit without closing the mfd), the FPS-rate jumps back immediately to those very high rates I had before.
It appears like to be very hard work just to show the orbit content. But this is ridiclious since the internal orbit mfd does not have this effect.
The surface mfd also drops the rate, but slightly less. Both together make it even worse.
Any help would be appreciated. Is it the 64bit-System? Is it maybe DX11?
I do not really search for an optimization like the truetype-thing but rather for a solution to mend some kind of error which lets that monster of computer looking like an idiot. I had already 60 frames on my old computer from 2007.
(I will also accept a scenario in which I was the idiot
I tried the 100830-Version as zip and msi. Located on SSD or HDD. Should I probably try out the beta, from which I heard that 64-bit is mandatory?
Thanks in advance for any hint.
Intel Core i5-4460 @3.20
8 GB Ram
NVIDIA GTX960
OS Win 8.1 64bit
(an "Alternate" Gaming Computer from July 2015)
I use to run Orbiter since 2008 and never had any issues of low frame rates/ FPS on my old computer, even with best graphic settings and using 2 monitors full of ext mfds.
Now, with a new gaming pc, I am able to run the newest games like Assetto Corsa with stable high frame rates, but in Orbiter it behaves strange.
Starting a scenario it I get ridiciously high rates of sometimes over 200 fps in the beginning, then it levels out at 130 frames.
If I THEN open up just one single external MFD (which I use to place on the second monitor, but it makes no difference), for example the orbit mfd, the FPS-Rate decreases dramatically to 4!!! frames or so.
The whole simulation stucks and stutters and is not playable anymore.
Now if I just push the middle button of the mfd, like for choosing another mode ( just disengage orbit without closing the mfd), the FPS-rate jumps back immediately to those very high rates I had before.
It appears like to be very hard work just to show the orbit content. But this is ridiclious since the internal orbit mfd does not have this effect.
The surface mfd also drops the rate, but slightly less. Both together make it even worse.
Any help would be appreciated. Is it the 64bit-System? Is it maybe DX11?
I do not really search for an optimization like the truetype-thing but rather for a solution to mend some kind of error which lets that monster of computer looking like an idiot. I had already 60 frames on my old computer from 2007.
(I will also accept a scenario in which I was the idiot
I tried the 100830-Version as zip and msi. Located on SSD or HDD. Should I probably try out the beta, from which I heard that 64-bit is mandatory?
Thanks in advance for any hint.
Intel Core i5-4460 @3.20
8 GB Ram
NVIDIA GTX960
OS Win 8.1 64bit
(an "Alternate" Gaming Computer from July 2015)