[bluedevil2k]

Yeah, the load times on this are crazy. 1-2 mins to start the app and get to the main menu, another 30s-1min after you pick your itinerary to get to the runway. And I have one of the fastest chips (3900x), m.2 SSD, and RAM. How long are people willing to wait to play it, especially given how often I crashed in my first few flights.

[ornitorrincos]

Funny, I have the same loading times on an hdd with a 2700 and 64gb of ram, so the slowdown seem something relatively indenpendent.

[btgeekboy]

I’ve been running the task manager on a separate monitor to see where the bottlenecks are. Those long load times appear to be, for me, GPU bound. It’s probably pre-rendering something. I'm running a 3700X, 32GB RAM, M2 SSD, GTX 1070, gigabit internet.

[g_p]

I've been doing similar, although reached a slightly different conclusion. It seems to me that the menus (even idling in them) use full GPU. I'm not convinced it's necessarily rendering stuff (and if it was, it really ought to cache it after the first time!) - I think this is just the result of a really bad performance UI they got away with launching.

I don't seem to max anything out when flying - even GPU has a little headroom according to task manager.

Hopefully Asobo will spend time on performance, rather than just bare functionality, as there's definitely lots of scope to fix things like frame pacing and overall performance.

[bluedevil2k]

I was watching my task manager as I played. On my 4k @60fps on the Very High graphics settings and the GPU was spiked at 100% the whole time (GTX 1660). Sounded like the propellor was in my computer room. On my 1440p monitor are @75fps I was at Extreme graphics settings and GPU was at 40%.

[ornitorrincos]

I also been running the task manager, mostly to check when it seemed to hang it was using 100% of the transfer with the hdd, didn't look at gpu usage though, will have a look the next time.