EDO Update9: how is your performance?

Now that I've played a little more, there still seems to be the issue of the performance dropping after you've played for a while. It's not as bad as it was originally, but I can still see occasions, where the framerates drop closer to 25-30 when you change from one location to another.

But, again, this is the most playable Odyssey has ever been for me.
 

Deleted member 182079

D
I did say 1280x720 (and I genuinely aver that you won't notice much difference on a laptop screen.)

The 960m is below the minimum GPU (1050 Ti), so yeah.

With all that said, stop trying to play at 1080p. And don't expect miracles.
Let's remember this is a DLC to a 7 year old game, not a brand new standalone one. You need Horizons if you want to play it.

Horizons runs perfectly acceptable to me at 1080p all things considered. I knew of course that EDO wouldn't match that but it's still shocking how bad it still is, after 9 (!) updates now. There is absolutely nothing on display that justifies that sort of performance hit.

As for min specs, have those changed again? I thought it was a 780 or some such? Regardless, I still remember the words quite well how the game should run on the same hardware at performance similar to Horizons (would be a reasonable expectation given the DLC nature). This is nowhere near similar.

Anyways, it was just an experiment but despite tempered expectations it still managed to limbo underneath those.

And playing this at 720p with its awful aliasing and the fact that medium settings default SS to 0.5 (I don't think Horizons does this? Would need to check) makes this a seriously ugly mess to look at, and text very difficult to read.
 
Last edited by a moderator:
Rather strange results since I play on a very similar system and saw a major uplift in performance.

Have you done the basic housecleaning diagnostics (reset settings, clear shader cache, deleted GPUWorkTable, etc)?

What resolution is that?
I play at 1440p and I tried to restore all settings and then re-apply them.
No luck, I can't get over 60 FPS even at the smallest settlements.
 
Would be nice if that CPU bottleneck would be fixed once and for all
Easier said than done.

I'm not much of a programmer (C64 BASIC doesn't count for this) and I have next to no knowledge of the inner workings of the Cobra engine, but I do know that just conjuring more parallelism out of legacy game code is not often straightforward and that a lot can go wrong (and evidently has) in satisfying various dependencies.
While I'm not a programmer and I understand ZERO of how the Cobra engine works, it seemed to me that FD made changes to things that dropped frame rates to really bad levels.

When you have Horizons and then add "Beyond" to it and it doesn't kill frame rates, one would expect that any new DLC would just add certain content without changing the WAY the game is rendered. Those who have more knowledge than you or me have mentioned that Odyssey is doing things in a way that cause frame rates to drop, i.e., having the CPU do things now that the GPU used to do before. THAT is what was meant by "seems to be a CPU bottleneck" (in my opinion). This is why we're up to 9 updates to fix it, why we're spending so much time adjusting our graphics settings, and why XBOX and PS4/5 users are still waiting for THEIR copy of Odyssey to become available.

Call it a bit of frustration on my part (and it most likely is) but it seems this "poor graphics FPS issue" should have been addressed on update 1 (or update 2 at least). They had an Alpha (and never did a Beta). Lots of those who tried out the Alpha gave advice and it looked like, after 4 or 5 updates to it, they seemed to have tossed out all the corrections they compiled from testers and now we're up to 9 corrections (that in my humble opinion) shouldn't have been needed if they had released what we all saw after the last alpha test. I'm still scratching my head over that.

BTW, the only thing I remember from my dad's Atari 800LX (he was the first in my family to get a computer) a little BASIC and F-15 Strike Eagle.
 
As title says. Please respond by saying, if you know it:

Hardware
GPU
RAM
CPU

Settings & Results
Resolution
Settings (most notable any FSR/upsampling usage)
Location & Activity
Average/min FPS
Previous FPS in similar conditions, if you know it
Looking at all these posts - how is the performance on your rig. Mine seems to have not changed much but then i‘m nowhere near populated space but apart from some visible things like screen dirt, planet lighting something feels smoother though but i can’t tell what it is. With locking off 120+ in space 60 ish on planets. Lots of jittering now and again when drawing all the little details a first time but similar experience otherwise. Rig in sig.
 
Performance wise, every update made some progress. With the latest update 9 i can run around settlements with an average of 50fps. In space 120fps (which is my max setting)

Running on my old 1080gtx with an i58500k.
Frame wise im super happy now!

But, your gamedesigner realy need to step up there game. These new features we got with the recent patch, are realy more of a letdown on top of a buggy mess.
 
Those who have more knowledge than you or me have mentioned that Odyssey is doing things in a way that cause frame rates to drop, i.e., having the CPU do things now that the GPU used to do before. THAT is what was meant by "seems to be a CPU bottleneck" (in my opinion).

That's not what a bottleneck is. A bottleneck is simply the limiting factor, something holding back performance for everything else.

The CPU isn't doing things that were formerly done on the GPU, the CPU is hung up on something, forcing the GPU to sit idle for want of frame from the CPU. There is always a bottleneck, a constraint that limits frame rate, somewhere. The problem with EDO is that it's current CPU bottleneck is largely inexplicable.

Call it a bit of frustration on my part (and it most likely is) but it seems this "poor graphics FPS issue" should have been addressed on update 1 (or update 2 at least).

Oh, I agree here. These issues should never have made it to release.
 
Hardware
Graphics: nVidia RTX 2060
Memory: 32 GB Ram
CPU Intel i7-10700K @ 3.80GHz

Settings & Results
1920x1200 (1200p)
Settings - High (default High settings)
Anywhere (Space, Walking around stations, Walking/Driving on planets)
60 FPS
Odyssey before Update 9 - 50-60 FPS
Horizons - 60 FPS (I usually frame rate lock it using vertical sync at 60 FPS)

Update 9 has removed a slight annoying stutter when entering stations so I'm happy. :)

Edit: I usually have my frame rate locked at 60 FPS or 60Hz (same as my monitor) using Vertical Sync in game because it stops screen tearing (although I don't experience that in Elite Dangerous) and I'm happy with 60 FPS.

However, I disabled Vertical Sync temporarily and I got the following frame rates:

Supercruise / Space: 200 - 250 FPS
Walking around Stations: 60 - 80 FPS
Walking around Settlements: 60 - 65 FPS
Walking around on Planet surface: 80 - 90 FPS
 
Last edited:
Well I've just managed to do a quick test and I'm impressed: 144fps in space (limited by the 2k monitor), and on a par with Horizons, and almost double the FPS in Update 8.
This was with 2k resolution at 1.25 SS and the CAS set to about half way along the slider. I use this to help with VR, which was also working fine at 90fps for the first time in Odyssey (still in space).
BUT it wasn't a good comparison, as for the first time I set the Hardware Accelerated GPU Scheduling set to ON, and I suspect that a lot of the benefit came from that.

On a planetry surface it was another story: about 45-50fps both in flat screen and VR (which was however quite smooth, much better than Update 8).
Much less popping of surface features as well, so exploring in an SRV in VR is now feasible again.

Haven't tried a settlement yet.

EDIT: just tried again without Hardware Accelerated GPU Scheduling and there was no noticeable difference: 144 FPS in space, around 45 on planets and in settlements, so update 9 for me is a nice +40%.

i7 4790k / GTX 1080, 16GB ram.
 
Last edited:
Hardware
Graphics: nVidia RTX 2060
Memory: 32 GB Ram
CPU Intel i7-10700K @ 3.80GHz

Settings & Results
1920x1200 (1200p)
Settings - High (default High settings)
Anywhere (Space, Walking around stations, Walking/Driving on planets)
60 FPS
Odyssey before Update 9 - 50-60 FPS
Horizons - 60 FPS (I usually frame rate lock it at 60 FPS)

Update 9 has removed a slight annoying stutter when entering stations so I'm happy. :)
You would have to remove the 60 FPS limit to see where you stand with update 9 - if you have 60 FPS on planets I would say you'll have at least double that in space.
 
Let's remember this is a DLC to a 7 year old game, not a brand new standalone one. You need Horizons if you want to play it.
I appreciate that, but the engine has been updated. I think the new lighting system is head and shoulders better than the system in Horizons, which is a 6 year old engine. There are also more detailed models and larger textures.

Horizons runs perfectly acceptable to me at 1080p all things considered. I knew of course that EDO wouldn't match that but it's still shocking how bad it still is, after 9 (!) updates now. There is absolutely nothing on display that justifies that sort of performance hit.
I don't know if you remember, but the Horizons update also significantly upped the system requirements. I updated from my ageing GTX 670 2GB, and even then a triple head setup for Horizons brought my brand spaking new GTX 970 to its knees. We have more detailed models, higher resolution textures, significantly improved lighting (it really is much better!) and lots of new animations.
As for min specs, have those changed again? I thought it was a 780 or some such? Regardless, I still remember the words quite well how the game should run on the same hardware at performance similar to Horizons (would be a reasonable expectation given the DLC nature). This is nowhere near similar.
You're right - I was confusing my games. Battlefield 2042's minimum is a 1050 Ti. The recommended card for Odyssey is a GTX 1060 6GB.

However, I would point out that minimum and recommended specifications are often interpreted as "will run at 720p/30fps low" for minumum and "will run at 1080p/60fps high" for recommended. I can't speak to the minimum requirements, because I don't have a machine approaching them, but performance is now nearing that for the recommended; I get close to 60 fps in most situations now with my laptop, whose CPU and GPU are weaker than the desktop variants.

You are, of course, correct about the requirements, although IIRC the actual wording was that FD were aiming for similar requirements to Horizons, and the pre-release specifications reflected this until shortly before alpha went live. That's not a defense - I think what angered the community the most was the lack of transparency about the update; I didn't play the game for four months. The lack of transparency certainly annoyed the hell out of me. But things are what they are. The game should not have been released in the state it was, but it was. I do wonder what issues there were during development (apart from the obvious one) that led to the update releasing like that.

With that said, given that a GTX 780/R9 280x are the minimums, a 2GB 960m would always struggle.
Anyways, it was just an experiment but despite tempered expectations it still managed to limbo underneath those.

And playing this at 720p with its awful aliasing and the fact that medium settings default SS to 0.5 (I don't think Horizons does this? Would need to check) makes this a seriously ugly mess to look at, and text very difficult to read.
I tried playing Fortnite on my wife's old GTX 650m laptop once. It wasn't pretty, but it ran.
 
but performance is now nearing that for the recommended; I get close to 60 fps in most situations now with my laptop, whose CPU and GPU are weaker than the desktop variants.
Wellll there's a bit more nuance to it than that I think. I believe that the bare minimum should be a little higher than 60fps because it would allow for a bit of extra GPU headroom for when things get extra heavy. It's one thing to hit 60fps with your GPU being hammered to the max and then dropping to 40 when you do anything flashy. But ideally the game should be able to maintain at least 60fps at all times, where the most visually demanding of scenarios can still keep that fps even if it's at 99% usage.

For example, Death Stranding on PC lists almost the exact same Recommended Specs as Odyssey: 1060 6GB and an i5 8600. I have a 1070 Ti and an 8600K, and at 1080 max settings the lowest my framerate will ever go is around 70fps, but is often over 100. So even though I'm only one tier above the recommended GPU, I still have quite a decent amount of GPU headroom to keep 60fps as a minimum. A 1060 6GB would easily hold 60fps at Ultra and never break a sweat.

In Odyssey I struggle to even keep 60fps in most planetary or concourse situations. CZs are a writeoff. Imho it isn't quite enough to just hit 60fps at all, it needs to go a little bit beyond that to keep it consistent across the whole game.
 
Imho it isn't quite enough to just hit 60fps at all, it needs to go a little bit beyond that to keep it consistent across the whole game.
I wholeheartedly agree! As I said though, my laptop is a little below the recommended spec.

The devs still have a lot of work to do. However, it's not as if the game is unplayable in its current state, which was not the case at release and for far too long aftrerwards.
 
Oh really? I find it rather weak to talk about "unplayable" just because the game runs slightly below 60 FPS, while other bugs are far more serious.
The devs have said that they will release a patch on Monday to address the critical bugs. Moreover, the point I made was that the game is, actually, a lot more playable than it was at release. This is not difficult to divine from the words I used.

In other words, unclench.
 
Last edited:
father-jack-i-love-my-brick.jpg
 
I do realise that this is about performance. I'm only bothered by the term "unplayable" in the context of a few FPS more or less. In the overall context of the current situation, that comes very close to nitpicking.
I think we're talking at cross purposes here. I'm not saying the game is unplayable; I'm saying it is playable. That would be the opposite of nitpicking, in my view.

Are we talking about the same thing or not?
 
You are, of course, correct about the requirements, although IIRC the actual wording was that FD were aiming for similar requirements to Horizons, and the pre-release specifications reflected this until shortly before alpha went live. That's not a defense - I think what angered the community the most was the lack of transparency about the update; I didn't play the game for four months. The lack of transparency certainly annoyed the hell out of me. But things are what they are. The game should not have been released in the state it was, but it was. I do wonder what issues there were during development (apart from the obvious one) that led to the update releasing like that.
The problem is that at least the frame rate was running perfectly fine and to their standards on their set up and indeed some people reported the same on their PCs. Which probably why they are having so many issues fixing it, it seem to be set up specific.
 
Back
Top Bottom