Lego Batman is advertising 60 FPS, but it's really 15 FPS. Frame generation is supposed to make good performance better, not hide the fact that a game is running poorly. Lego Batman's spec sheet just crossed that line.
Lego Batman is advertising 60 FPS, but it's really 15 FPS. Frame generation is supposed to make good performance better, not hide the fact that a game is running poorly. Lego Batman's spec sheet just crossed that line.
60 will WORK, but the latency issue doesn't really go away until you hit at least 90. I'm not really anti frame gen, but its downsides don't really go away unless you're already getting good performance and unfortunately, 60 fps isn't what it used to be. Due to game engines like UE5, 60 FPS has a higher latency than older games running at 60 FPS.Yeah FG never fixes bad performance, 100% correct but the technology can be useful to increase fluidity, mostly usable with high refresh rate monitors as you need 60 fps minimum before enabling it.
Hence why you need 120 Hz as bare minimum pretty much.
60 base fps + FG = Around 120 fps, and with a 120 Hz panel, it for sure will both look and feel more smooth than 60 fps. People that claim otherwise, have not tried it. Or tried some crappy form of FG.
Tons of people use 144 Hz or higher these days. Even 240 Hz is pretty common.
I'd say 120-144 Hz is bare minimum for any gamer these days. Even for work I can't stand 60 Hz. 75 Hz makes no difference. Dell, Lenovo and many other brands are also pushing 100+ Hz for work monitors these days. Feels much easier on the eyes. Things are actually somewhat smooth at 100 Hz instead of being jaggy at 60-75 Hz. Gamers should aim for higher than 100 Hz - 120-144 Hz or higher for that.
FG will never fix 15 fps, or 30 fps for that matter. FG don't work well when performance is crap to begin with. Too much latency but it will improve on performance that is already decent, making it very good instead of decent and improve the smoothness even further.
I am talking about proper FG here, that being DLSS FG. Not simple interpolation like Loseless Scaling but you will find many people that say it works good too. DLSS FG is many times better tho.
Even FSR FG is much better than LS but even FSR trails DLSS FG by a big margin overall. Hopefully AMD will improve FSR FG like they improved FSR with version 4.
So yeah, FG can be good, if you know what you are doing. Just like upscaling, even tho this is easier for people to understand how to use (at least till we start mentioning the different presets, dll versions etc.)
Not all Unreal Engine 5 games run like garbage (e.g. Assetto Corsa Rally runs great) only ones where management have forced the game out the door before it's finished.
Don't buy this garbage until it's patched and / or on sale
FG is what gamers want! Ask Nvidia. They make this crap and stupid people gobble it up because they can now run a game with RT (which initially tanks performance by upwards of 50%) and slap on upscaling (DLSS/FSR/XeSS) and now they're happy because they have an image getting taken down in resolution and reimaged to a non-native resolution to give the illusion it is native....
Even with upscaling in play, sometimes you're just not hitting your magical FPS and need a little extra help so Nvidia gave you Frame Generation! It creates a frame that wasn't there, but now is! Oh, so you have latency issues now? We've a fix for that, too! Run a fourth piece of software called Reflex!
Done!
A game you once played that looked good at 120 FPS, now has some slightly changed lighting with RT, upscaled imaging, FG and latency reduction to give you a performance of around that 120 FPS. All these other things have done is introduced ghosting, blurriness and latency. But that's okay, right? You can now stand at a window or puddle and see your reflection because RAY TRACING! YEAH!
This is misinformation. 60fps base, 120fps with frame gen will look smoother, it will not feel smoother. People like you are completely wrong about frame generation. Frame generation is for top tier hardware already capable of high frame rates, for the sole purpose of taking advantage of monitors with really high refresh rates.Yeah FG never fixes bad performance, 100% correct but the technology can be useful to increase fluidity, mostly usable with high refresh rate monitors as you need 60 fps minimum before enabling it.
Hence why you need 120 Hz as bare minimum pretty much.
60 base fps + FG = Around 120 fps, and with a 120 Hz panel, it for sure will both look and feel more smooth than 60 fps. People that claim otherwise, have not tried it. Or tried some crappy form of FG.
Tons of people use 144 Hz or higher these days. Even 240 Hz is pretty common.
I'd say 120-144 Hz is bare minimum for any gamer these days. Even for work I can't stand 60 Hz. 75 Hz makes no difference. Dell, Lenovo and many other brands are also pushing 100+ Hz for work monitors these days. Feels much easier on the eyes. Things are actually somewhat smooth at 100 Hz instead of being jaggy at 60-75 Hz. Gamers should aim for higher than 100 Hz - 120-144 Hz or higher for that.
FG will never fix 15 fps, or 30 fps for that matter. FG don't work well when performance is crap to begin with. Too much latency but it will improve on performance that is already decent, making it very good instead of decent and improve the smoothness even further.
I am talking about proper FG here, that being DLSS FG. Not simple interpolation like Loseless Scaling but you will find many people that say it works good too. DLSS FG is many times better tho.
Even FSR FG is much better than LS but even FSR trails DLSS FG by a big margin overall. Hopefully AMD will improve FSR FG like they improved FSR with version 4.
So yeah, FG can be good, if you know what you are doing. Just like upscaling, even tho this is easier for people to understand how to use (at least till we start mentioning the different presets, dll versions etc.)
Finally, someone gets it! Frame gen is for top tier hardware that is already capable of high frame rates, for the sole purpose of being able to take advantage of monitors with really high refresh rates. Frame gen was never meant for low frame rates like 60fps.60 will WORK, but the latency issue doesn't really go away until you hit at least 90. I'm not really anti frame gen, but its downsides don't really go away unless you're already getting good performance and unfortunately, 60 fps isn't what it used to be. Due to game engines like UE5, 60 FPS has a higher latency than older games running at 60 FPS.
I like the Lego game series, but I also like 120+ FPS without FG.
Maybe by the time Batman hits $5 on steam, I'll have a RTX 7080 to run it.
You're right, I got too carried away.The subheading is incorrect.
It says, "Lego Batman Is Advertising 60 FPS, But It's Really 15 FPS"
It's actually advertising 30 FPS and really 15 FPS. Not that that's good either, but still it's worth correcting.
Yes it will. The end result is what matters and 120 fps with FG will be prefered by 99% of people if the alternative is 60 fps and the display is 120 Hz.This is misinformation. 60fps base, 120fps with frame gen will look smoother, it will not feel smoother. People like you are completely wrong about frame generation. Frame generation is for top tier hardware already capable of high frame rates, for the sole purpose of taking advantage of monitors with really high refresh rates.
And this is why this feature is mostly for people with high refresh rate monitors.60 will WORK, but the latency issue doesn't really go away until you hit at least 90. I'm not really anti frame gen, but its downsides don't really go away unless you're already getting good performance and unfortunately, 60 fps isn't what it used to be. Due to game engines like UE5, 60 FPS has a higher latency than older games running at 60 FPS.
While I agree with most of that, I think people are ignoring the growing latency problem. When games weren't doing much on the back end, average FPS was all that really mattered. The game engine wasn't doing stuff that was causing dips. Then the late 2000s and early 2010s came around and 1% lows started to be useful when measuring performance as games were doing more on the back end. In the last few years game engines have started doing so much more that you can be getting 100ms+ from input to display and I think in the next few years latency will become the new 1% lows. In today's environment you can absolutely be getting 300FPS while having 100ms+ of latency.W this is why this feature is mostly for people with high refresh rate monitors.
I would not call 60-90 fps good performance but that is subjective I guess. I don't really play games below 200 fps anymore, on 240 and 360 Hz OLEDs and I am talking about 1% lows here.
Average fps is worth nothing. Minimum fps is what matters, and the only fps number that actually matters.
60 fps is the new 30 fps in my eyes. Also, 60 Hz monitors = dumpster worthy. I don't own a single panel that is not 120 Hz minimum.
For FG to really work well, you also need a top tier gaming CPU, like AMD X3D, that is capable of delivering great 1% lows and the best part about FG is that 1% lows are doubled as well, part of the reason why game looks and plays much smoother.
Latency can for sure be a problem with FG, never claimed otherwise and it will never fix performance if performance is crap to begin with.While I agree with most of that, I think people are ignoring the growing latency problem. When games weren't doing much on the back end, average FPS was all that really mattered. The game engine wasn't doing stuff that was causing dips. Then the late 2000s and early 2010s came around and 1% lows started to be useful when measuring performance as games were doing more on the back end. In the last few years game engines have started doing so much more that you can be getting 100ms+ from input to display and I think in the next few years latency will become the new 1% lows. In today's environment you can absolutely be getting 300FPS while having 100ms+ of latency.
I agree in principle to what you're saying here about only reviewing frame rates in their native state. The problem I see though, is you would need to extend this testing philosophy to cover other aspects of game testing eg. CPU overclocking, RAM overclocking, GPU overclocking etc, to ensure a pure native testing result. This kind of testing methodology would give people a baseline performance indicator. It would also make testing a lot easier for reviewers.Here's an off-the-wall suggestion: review sites could quit reviewing and reporting on games' frame rates using any upscaling or frame generation technology. Let people know how badly games are being "optimized" at release so that consumers will avoid those studios (ahem, Epic Games) who release software that just won't run on machines that require crutches. We have special olympics for disabled athletes - we don't give them scooters or mechanical exoskeletons or outboard motors and have them compete against unassisted athletes, then compare their records against each other. If consumers want to know what games designers are capable of delivering, stop reporting on their slop and hold their feet to the fire for the stuff the actually are putting out.
If Lego Batman can only deliver 640p at 15 fps on the minimum hardware, so be it. Report that as the number. Same with their "Top Tier". If that's 1440p at 30fps on a 4070, welp, that's what they delivered as far as their software. I get that development is hard, and that the crunch is real. So are reviews that show the true picture. Thanks to you and some other sites, this is a (small) step in the right direction.