Control drops to 10fps on base consoles (DF)

[Mr Puggsly]

Pemalite said:

Mr Puggsly said:

As I just mentioned it may not be a simple GPU bottleneck issue.

Also, outdated hardware can't be the issue if you actually build a game for that hardware. I mean consoles seem to be lead, so they must have noticed limitations at some point...

Its likely just bad optimization that will be improved with patches.

Consoles aren't the lead platform, the PC was. - It has Ray Tracing.

The engine has multiple bottlenecks depending on scene, for consoles the CPU becomes a limiting factor rather rapidly thanks to the anemic performance of Jaguar.

JRPGfan said:

Time to get a new engine.... and learn how to optimise games Remedy!

QB had horrible performance issues at launch too.
Now the same thing is happending for Control? thats not acceptable.

The engine is actually rather good, just some of the options they are enforcing just isn't doing it justice... Like frame reconstruction with it's overhead when certain platforms have different forms of frame reconstruction which is hardware accelerated that is being unused.

More often than not, engines aren't entirely scrapped... It's a waste of time and money to do so, but re-engineered, overhauled and repurposed.

For example... Fallout 76 uses the creation engine which is derived from Gamebryo which in turn is derived from Net Immerse that came out in 1999.
The Call of Duty Engine has roots dating back to Quake 3 from 1999 and so does Valves Source Engine.
Battlefield V uses a derivative of Frostbite which stems from Bad Company in 2008...
Unreal Engine 4.0 still has some roots with Unreal Engine 1.0...

And the list goes on.

In short, you don't reinvent the wheel if you don't have to.

Mr Puggsly said:

Well its not usual for games to improve performance post launch.

Indeed. Doom 2016  and Wolfenstein on Switch is a good example.

Mr Puggsly said:

Its also worth noting the game mostly sticks to 30 fps on X1X. That tells me they did optimize for a console, the most powerful one.

Or it's not optimized for the Xbox One X and the Xbox One X simply has the required baseline hardware required to run it semi-adequately.

Either way... Wait for the patches.

I think the ray tracing aspect was built for PC, but not the game entirely. Other games built with consoles in mind also have ray tracing, some get it unofficially patched in.

X1X has the same CPU and its not significantly faster. Yet that version does a much better job targeting 30 fps.

I don't think the engine is bad per se, QB did run at a solid 30 fps but that came with compromises.

Given people are waiting for patches to fix the performance, where is the performance problem coming from? Is the game in general just too demanding for the hardware or was it rushed?

I sense you're trying to use this as an example of console specs being too limited. I just see it as poorly optimized game if we feel patches can improve it. They didn't have MS money for this project so that might have meant less time to optimize.