Alright, I was half-wrong; there does appear to be a CPU-side limitation in settlements...

Whoever made the decision to bolt FPS onto ED is . . . not FD's MVP.

Can't really blame FD on THAT. Sorry. The community was crying for this for years.

On the rest of what you wrote, i could go through old posting of mine, where i pointed out just that: other FPS are made as pure FPS games and still are many years in the making. It was obvious that Odyssey would not manage to match up to that and it was also obvious that it would still be compared to these games. (So, i could not make a big "told you so" posting... but i guess that would be quite pointless. ) What i was not able to predict was, what a utter mess the release itself would be, though...
 
Last edited:

 
Yeah, only thing is that every component of my system exceeds the recommended specs of the game, including the CPU...

Something is going to be the limiting factor. This is only an issue when utilization is very lopsided on otherwise well-balanced systems, or performance isn't up to specification.

Unfortunately, EDO has both of those problems.

Actually, after a few more hours of playtime last night, I started seeing a larger pattern. The FPS issues do come back periodically on my system. Its 80% better than before, but they do indeed return eventually.

This is interesting, because on the setups I've been testing on, I don't get intermittent FPS issues. Some areas have bad frame rate (concourses) and everywhere has bad frame rates relative to similar areas in Horizons...but they don't improve or get worse over the course of a session.

Perhaps I haven't played long enough at a stretch, or in the right areas, for me to notice this issue.

After upgrading the CPU and motherboard the GPU utilization went through the roof. Yet I saw very little improvement in performance.

Battlefield was showing similar issues but the upgrade brought nice rise in performance. I stopped looking for the reason because until Frontier fixes it, there's nothing I can do about it.

Average per core utilization is still fairly low, which is likely why CPU scaling is poor. Increase per-core performance and the spikes can spike higher, but the spikes are only a fraction of CPU time.

But yeah, very likely little we can do about it.



Looks like I'll need to play some more conflict zones.
 
Last edited:
Fire kills my frame rate... Suddenly, for no reason, I had one reactor room that was on fire and my frame rate was reporting 100fps like it was locked there and the game ran smoothly!
 
Fire kills my frame rate... Suddenly, for no reason, I had one reactor room that was on fire and my frame rate was reporting 100fps like it was locked there and the game ran smoothly!

Whatever FDev does to render fire is very GPU intensive and is about the only way for settlements to not be significantly CPU limited...the effective cap makes frame intervals more consistent.
 
Whatever FDev does to render fire is very GPU intensive and is about the only way for settlements to not be significantly CPU limited...the effective cap makes frame intervals more consistent.

NPC's seem to be real fps killers for me lately in Horizons.

Random part of San Tu 3 ring w/o NPC's: 90+ % GPU load, 130 to 150 fps.

Same ring, Res site: 50 to 70% GPU utilization, fps down to 90ish figures (CPU load low, too, but that's just the average value).

A few updates ago this difference definitely did not exist.
 
Back
Top Bottom