Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I've got theories as well regarding certain textures or other visual resources connected to airports and specifically certain taxiways, and I've never believed that the airspace transitioning bug was ever fixed despite the claim that it was. I also have theories regarding the Azure voices causing stutters or crashes, but that's harder to test for. Well, you can try turning off Azure and see what happens, but I doubt that will do much for you.
EDIT: I'm also formatting this post backwards. I should have started with how you should be looking at FPS in the Dev Mode. There's a very detailed graph you can use to discover where the bottlenecks are in real time: CPU, GPU, threads, whatever.
https://www.youtube.com/watch?v=sRoCVuQo-E8
All the GPU does is rendering, and there's not that much to render.
Calculations are made by the CPU and there is a lot to calculate in this game. Way more than in regular games.
So games like this will always remain CPU heavy.
There are lots to render, definitely not "not that much to render". You are rendering a small country's worth of terrain at a time. Even with LOD that's still a pretty impressive amount.