Thread 718791669

>30fps on PS5 Pro
We need to get rid of Unreal Engine completely

>>718791669 (OP)
Wait it's not Fox Engine? What were they THINKING?

Just turn on framegen bro.

>>718791749
They were thinking a horde of indians have no earthly idea how to use a proprietary engine and opted to use one where they can simply click the right boxes and it works ‘well enough’.

>>718791669 (OP)
>PS5 Pro
>$100 GPU
>WHY ISNT IT GOODS?
a true mystery of the ages

>>718791669 (OP)
Human eye can't see more than 24fps anyway.

>>718792189
>Pure optimization because there's only one consistent piece of hardware to aim at and pool resources into
>30fps ugh that's all we could do!!

>>718792189
Its going to run worse on PC

>>718792189
weird cope

>>718792283
some people can, it depends on how often you blink

>>718791749
Why do retards think you can just pick up an engine in like 5 seconds. no one has worked with fox engine for close to a fucking decade

>>718792330
>pool resources into
ask me how I know you cant code,
throwing money at the problem doesnt improve rendering speed

>>718792554
Look how well they did with an engine everyone has worked with for close to a fucking decade.

>>718792416
>walking through an environment with no collision detection or AI computation is really smooth
I'm shocked

>>718792729
yeah they actually released something instead of fucking nothing wowzers

MGS3 is best enjoyed at 30 fps.

>>718792808
you are genuinely a very stupid person

>>718792416
>Just lower the resolution and upscale it with fsr3
It's pretty easy if you did your homework from the beginning, isn't it?

>>718793124
>>718793124
MGS Delta is using the same PSSR sony upscaler that Death Stranding 2 uses

So how is it a game like MGS3, with small compact level design, can’t reach 60 fps while plenty of other UE5 sloppa can?

>>718793264
Regular ps5 doesn't have it, which is what I was referring to in my post, that they just lowered the resolution to achieve the 60fps in the base model.

>>718792970
kek

>>718793415
60 polygon tree leaves and forced memetracing.

Stop blaming ue5!
You dont know shit about graphic engines!

>>718793415
>small compact level design
They made the whole game seamless without loading which means EVERYTHING has to be constantly rendered at all times including the tree you saw six hours ago that you will never see again

>>718793581
>They made the whole game seamless without loading
no they didn't you retard

>>718792813
They could've released something with any engine. What point are you even trying to make, retardbro?

>>718793415
they wrote their physics in python

>>718792189
It's mainly the CPU. It still has the same CPU as the base PS5 which will be a bottleneck. Same thing happened with the PS4 Pro.

>>718791669 (OP)
Now show the normal gameplay and not cherrypicked photographs of rare circumstances where the worst dip imaginable happened. Performance mode on base PS5 is 50sfps most of the time. Cope tendie faggot.

>>718792890
tell me what programming languages or game engines you know.

>>718793642
no they can't that's kinda the point dumb fuck that's why there's so many dead engines out there because you need specific people to know how to use it dumb fuck. You can't just pick up an engine in 5 minutes, you need to be trained to use it unless you build it yourself because propriety engines are not documented like public ones. dumb fuck

>>718794258
https://www.youtube.com/watch?v=Am0ER7iW2lo&t=&start=809

>>718791669 (OP)
What is impressive about this is that the game design at its core can run on a PS2. It's the same kind of game, rebuilt with higher quality graphics. Thing is, graphics are scaleable. And indeed they scale: the game features worse settings in performance mode and can hit lower resolutions (down to 720p!). Yet it can't hit a constant 60 fps? How is that possible? It surely can't be a CPU limitation? I mean, this style of game can literally be made on a PS2?

So what is going on here? Is it an engine problem? An optimization problem?

>>718792808
>no collision detection
retard

>>718794409
Yeah, most of the normal gameplay on base PS5 is 720-1080 that resolves to 4k quality at 50ishfps most of the time. It goes into the high 40s but also up to 60. You are spreading misinformation Tendtard cherrypicker

>>718791669 (OP)
>We need to get rid of Unreal Engine completely
And consoles.

>>718794518
anon how about you open your dumb fuck eyes and see the ps5 pro is sitting at a worse framerate than the base console

>>718791669 (OP)
Don't care, playing it on max with RT on PC

>>718794603
Nobody is saying the Pro doesnt have its fair share of bizarre issues. It is what it is. But to go around saying its running at 720 at 30 is just plain wrong. It uses upscaling to reach a 4k image and is 40-60fps most of the time being closer to 60.

>>718792554
Look, Bashkir or whatever: if you have a competent director and even a few technical guys, you can lasso the artists to do whatever the engine needs. No one is "picking up" or "working on" the engine except the 1 or 2 dudes who can read code. The other 50 brown clones are just shtting out verts and bmps from whatever program you've got running to make models/textures/environments.

>>718791669 (OP)
UE5 is too easy to build a game with. It's gotten so bad that even idea guys can shit out a game without having to know much code, which then leads to unoptimized dogshit like this remake of MGS3.

>>718794759
I see it was that easy the whole, I guess that's why MS dropped their billion dollar slipspace engine for Halo for UE5. Or why Square drop Luminous for UE5 or why CDPR dropped red engine for UE5 or why-

>>718791669 (OP)
>console

>>718795013
To be clear, there is no reason for a base PS5 game not to run at 1440p 30 fps, and 1080p 60 fps in case of no cpu limitations (there shouldn't be any since games nowadays don't feature particularly complex systems).

If a game is going below these numbers it is a sign of jeet optimization. It's funny you use Jedi Survivor as an example of poor console performance when the PC version was borderline unusable even on enthisiast class hardware.

>>718795013
It even says in the caption that it was even worse on PC.

>>718794942
You're translator is fucking up. What?

>>718795312
But it runs better on PC bro

>>718795318
Didn't have a real argument or what

>>718795492
See >>718795304

>>718795590
It runs better on PC bro, cope harder lmao.

>>718795638
All of the platforms have probably been patched at this point. So maybe. But in relation to that video that anon posted, DF said that pc was worse. So his case is just bullshit.

Halo? Dead
Square? Dead
Witcher & Cyberpunk? Remains to be seen
Almost like, UE is the kiss of death

>>718795738
Guaranteed the PS5 version doesn't run that much better even after patches. Either way the reality is that you'd be lucky to even be playing 1080p60fps on consoles especially after it's 3 years old.

>>718794274
NTA but I know none of them but present myself as an expert on the entire industry, and no one can possibly stop me.

>>718794674
I love it when gamers like you make these kind of excuses.
It's always gamers. You know how they say people get what they deserve? It's always gamers.

>>718791669 (OP)
Yes. Unreal is the reason games run like shit on an underpowered AMD APU.

>>718793581
Anon if you don't know anything about game design please shut up

>>718796025
I dont know if elden ring was patched or not there but the Pro even has better ray tracing capability than even the 6800. Jedi survivor is fine on ps5 at least now. Ps5 pro runs it at 1800p.

>>718792416
Why does it run so poorly on the PS5 Pro? I thought it was 100x the power of a 5090.

>>718796193
No excuse was said. It was all explanations for the bullshit this guy is saying.

>>718794942
>MS dropped their billion dollar slipspace engine
They dropped that engine because they don't want to permanently hire competent engineers. MS wants a revolving door of jeet contractors which isn't a good idea when paired with a custom engine.

>>718796243
Yes actually it is the engine's fault

>>718796398
>shows 2 more games performing like shit

>>718796315
A pro can run GTA 6 on release and a 5090 cant

>>718796462
kek

>>718796376
"it is what it is"

>>718796303
>PS5 Pro runs it at 1800p
>definitely at higher settings too
Fell_for_it_again_award.jpg

>>718796473
A 5090 can play Curse of Monkey Island and a PS5 Pro can't.

>>718794759
It's not 90s anymore unc

Unreal Engine sirs...not like this

https://www.youtube.com/watch?v=KQ2W9wHTL6M

>>718796508
Lower stated resolution vs 4k. What did you expect idiot?

>>718796386
I was told you only needed 2 guys to work on the engine

>>718796462
The pro is probably running that game at frame rates comparable to some of the highest end graphics cards in the world.

>>718793581
lmao every single time you brownoids whining about UE5 open your mouth you expose yourselves as knowing less about game development than the average normie holy fuck

>>718793816
>PS5 CPU can't cope with PS2 game design
We need to shut down the games industry until we figure out what the fuck is going on

>>718793581
If the entire game was rendered at all times this would be a technological marvel just for running above 1/100th of a frame you dumbfuck

>>718796653
2 permanent hires yeah, instead they didn't do that and ended up with an engine that was so jeeted that it couldn't have playlists updated without huge code changes.

>>718794674
>it’s not 720
>it uses upscaling to get (fake) 4K
which way, brown man?

>>718796594
SAAAR DELETE THIS NOW
BLOODY BENCHOD

>>718791669 (OP)
buy a decent PC like a person from the first world

>>718793581
you niggers cannot be this stupid

>>718791669 (OP)
>WE GOTTA USE EVERY SHITTY GRAPHICS TECHNIQUE THE ENGINE CAN DO OUT OF THE BOX!
that's the real problem. fox engine wasn't anything special, very basic but effective tech.

>>718796568
"nef" that only makes sense when you're trying to fund your extended family

>>718796904
of course just 2 permanent guys, why didn't they do that ahh how can MS be so stupid. Every company should hire you, you have like max IQ

>>718791669 (OP)
it doesn't matter if its going to be UE5 or any other engine
as long as bunch of untrained hires make the game it will work like shit

a decade ago

>>718797156
>people playing 60fps slideshows for over a decade

>>718797156
wow, a PS3 game with an empty map runs at 60 fps on PS4?
that's, like, crazy man...
so what does it have to do with this PS5 game?

>>718797156
>less pixels than a nokia

>>718791669 (OP)
I knew this game was going to run like shit the second I found out it was using UE5. That new Silent Hill game won't be any different. This is another year of sloppy UE5 indian Diarrhea games.

>>718797156
>decade ago
it shows

>>718797156
Fox engine was so optimized it ran on PS2!

>>718797118
You could do with just 1. That other guy is just padding payroll.

silent hill 2 remake was a god awful. same with unreal PES. i dont trust konami to make a unreal game

>>718797452
At this point every engine should have built in AI for maintenance and upgrades. Would do a better job than any jeet because whities and japs forgot how to code.

>>718797303
MGS3 is a PS2 hallway simulator. There is no reason for the remake to run under 60fps

>>718797517
>this post
are UE haters the real indians?

>>718797567
Don't fuck around

>2013
>we made the best videogame engine to ever exist
>https://youtu.be/FQMbxzTUuSg
>2025
>same company
>we can't render a blade of grass without dropping fps tenfold because
>because we just can't okay!!!!!!
hard to believe there are söylent chugging golems defending this and blaming it on the nogames 5

>>718797721
>fox
>best videogame engine to ever exist
I knew kojimadrones were deluded, but wow

>>718791669 (OP)
30fps drop just because of 1 explosion/fire. We really are going backwards.

>>718794873
Probably like 8 out of every 10 game trailers released in the past 4 or so years are literally fake bullshit made up in UE5. I've been watching tons of them released over the past 6 months or so (and especially from Gamescom) and it's so obvious that none of these fucking things will ever see the light of day. Unreal has always had its unique problems but UE5 has spawned an entire stream of garbage.

>>718797791
>SAAR DO NOT REDEEM THE BLOODY UNREAL!

>>718796594
any explanation for this?

>>718797921
Uh sar.. you're redeem?

>>718797828
Tim's gunning for the movie market. That's all. It's Huang's "we're not a gaming company anymore" schtick, just with Hollywood instead of AI. These guys think they're better than videogames. They're wrong.

>>718792813
you sound like a faggot

>>718798110
I typing shit not talking the voice you're hearing is your own

>>718798237
nah you say stuff like wowzers and have to insert fuck every other word you sound like a faggot.

>>718798312
I'm typing not talking again that's your own voice

>>718798087
so if he's "gunning for the movie market", why is it free for use in games but paid for movies?
kinda encourages the opposite

>>718796935
Youd be surprised at how similar upscaled 4k can look to native. Just because it uses reconstruction doesnt mean it doesnt look better than 720 idiot

>>718794324
>we forgot how to train people bro please buy our unreal slop

>>718791669 (OP)
Probably a cpu bottleneck like in Oblivion, can't imagine any other reason for the weird choices they made with the graphics options in this game
Can't the cpu in the pro perform worse than the base console under certain scenarios?

>>718794759
only good post ITT

>>718799015
yeah they still got all those guys that made the engine and haven't use it since from 10 years ago

>>718798431
Ever looked at a movie vs game budget? What depth the pockets? It's routine for a movie to have a $100mm budget, but threre's only a few games/year with that money. And it's not "free for use" what are you talking about?

>>718792416
its rather easy to make pretty pictures when you dont have to add gameplay to your "game" you dumb cunt

>>718797674
yeah

so UE5 has to have been developed by indians right?

>>718794274
OpenGL, Unreal, O3DE, C, C++, Python, Lua. You are a brainlet, and defending this poorly optimized demake is embarrassing.

>>718799185
the license is free for games until like you generate 1 million in revenue, and you're only charged for the money generated after that

>>718799876
The stuttering is unfortunate (and allegedly fixed in the new versions) but most of the games on ue5 are actually pretty low end/console friendly while looking good.
This is probably more just gooks or indians pushing things too hard on a 6700(ps5)/9060(pro)+r5 3600 equivalent

>>718791669 (OP)
I'm not seeing the problem
Just buy a PC with a mid range GPU like a 4080

>>718800046
Shockingly, no response to this btfo.

>>718791749
Fun Fact there's a remake of MGS3... ON FUCKING PACHINKO MACHINES

>>718791669 (OP)
The price of 60fps on consoles:
■ Assassin's Creed: Shadows at 720p
■ Cyberpunk 2077 at 900p
■ Dead Space Remake at 936p
■ Dragon Age: The Veilguard at 500p
■ Final Fantasy XVI at 720p
■ Forspoken at 720p
■ Immortals of Aveum at 720p
■ Metal Gear Solid Delta 720p
■ Monster Hunter: Wilds at 900p
■ Senua's Saga: Hellblade 2 720p
■ Silent Hill 2 Remake at 864p
■ Skull & Bones at 720p
■ Star Wars Jedi Survivor at 648p
■ Star Wars Outjaws >>718791669 (OP)
at 720p
■ Wuchang: Fallen Feathers at 540p

>>718791669 (OP)
Optimize things again.

>>718791669 (OP)
That's actually disgusting. Anyone ever feel a sense of fatigue with how half ass everything is now?

>>718793549
It's good if your dev team is two dozen white guys and not 500 jeets.

>>718795638
but your pc doesn run better

>>718791669 (OP)
it's not unreal's fault that consoles are dogshit

>>718799609
he's 100 percent correct however PC ports have been dog shit lately too so the real issue is industry wide

>>718809132
see
>>718796594
consoles are fully capable at delivering real framerates

>>718791669 (OP)
Total ue5 death

>>718792970
>just a murky underwater scene with an alligator, 27fps
>>718792808
>BUT THAT'S JUST A MOUNTAIN THAT YOU'RE ON, 60fps

I'd rather the mountain

>>718791669 (OP)
How? The levels are small as fuck and linear as shit.

>>718809709
UNREAL
ENGINE
FIVE

>>718809709
powered by unreal engine

sirrs...
it run fine...
you will wait for patch sirs
it run fine on PC too ...
just wait ok?
sirs preorder please

>>718796887
More like coders can't

>>718796398
Didn't BF6 go down to 720p in performance mode on the regular?

>>718812375
so does Delta

>>718812556
That's expected since Delta's on UE5 shit. Frostbite is usually a little better about resolution stability.

>>718809043
It does though. What is this retarded projection?

>>718791749
More than half of the OG Kojima staff left Konami shortly after MG: Survive came out. Less than 50 people still at Konami worked on the engine and that was almost a decade ago. It'd be almost no different.

>>718813238
I keep forgetting Survive was a thing, and it sits forever unopened in my PS4 collection I got from the $10 bargain bin.