Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Metroid on the GameCube ran at 60 FPS, it didn't need motion blur to keep strobing from judder from causing eyestrain.
You are discussing two opposite problems :-\ You likely got motion sickness in that game from lack of motion blur, some racing games have this problem as well.
You may want to whip out ReShade and actually add some very subtle motion blur to fix these problems.
Correct, the cutscenes have motionblur :) That's exactly what was already discussed.
But any motion blur outside of cutscenes is incorrectly being described because there is none. Portions of the game run at 20 FPS and are slightly interactive cutscenes, this is where motion blur is applied to stuff you have control over.
Outside of those scenarios, whatever you are describing, it is not motion blur. It's more than likely just judder on a fixed-refresh LCD.
I was playing 12+ hour sessions of quake1 so I can play fps no prob. Still doing 6+ on overwatch.
As for ffx, what are those ghosting trails then? Screenshots I took were via nvidias apps so this is unrelated to the monitor.
I also just whipped up castle Vania sotn on an emulator, set my TV to output and I didn't experience any issue with lower fps and what not.
Motion blur is used in the game, but only during cutscenes and one or two other places that use it for dramatic effect. If you're just walking around the world casually and seeing something you think is motion blur, it's not.
It has NOTHING to do with anybody's screen though! please stop saying that! It is a DELIBERATE ghosting effect, for example when you touch the stones in the thunder plains and other actions, it's very intentional and is in the game, was in the original which I played on a CRT and I see no ghosting in other games, so please, stop trying to tell us it has something to do with monitors! Gawd you are stubborn!
Read the second paragraph again and stop being a jackhole.
http://i.imgur.com/VWSyxRE.png
It seems likes its coming down to semantics on what exactly the issue is. But regardless of what it's called, it's there. And again, this is taken with nvidia's built in screen shot tool so its totally independent of the display used.
Motion blur exactly as discussed during cinematic scenes. Dunno what your problem is? This doesn't happen during normal gameplay, only during a handful of specially crafted scenes such as that.
You cannot capture display artifacts in a screenshot, by the way :P
And I do believe I said the screenshots I took would be independent of the display since its at the point the video card is rendering it.
Would you prefer me to do a video cap that shows me simply walking left and right and it having these echoes all over?
I won't be doing anything to get rid of that post-processing effect, it's intentional. It doesn't happen any other time during the game, but if it did you would still want it to prevent judder from the game running at 30 FPS and I still wouldn't remove it :)
If the game ran at 60 FPS and had motion blur, you'd have a real problem on your hands. But motion blur is desirable at 30 -- without it you see strobing as stuff moves across the screen and this causes nausea in many people.
The brain does not like motion that is not continuous. Seeing something warp across the screen in discrete still-frames with nothing in-between makes you queasy; this is solved one of three ways:
We can't do (3) in this game, and (1) is generally out of the question on modern PC displays... that leaves (2) :-\
Fact: you are wrong
Fact: the game does indeed have ghosting/blur as it did in the original
Fact: You won't admit you are wrong.
The irony of your statement above, leaves me completely bewildered, because there's really something wrong with you. Is English not your first language or something?
None of those things are facts, and if you would read the second paragraph like you were told to, you would know why your second "Fact" has no relevance.
You are a complete failure as a troll, do you remember when you claimed that HDMI 7.1 channel audio was a compressed bitstream? Keep spurting wrong information, I really do not care but at some point you will probably get tired of being wrong.
I do want to say that I remember this ghosting effect being a real issue years and years ago when I played FFX on an emulator, and it's the same thing as the image posted about the Al Bhed. I remember it being a lot worse, though, and the ghosting applying to battles - primarily looking really bad in Macalania. The fix for this was to set Skipdraw to 1, which I would presume skips that post processing effect that creates the ghosting, right?
Motion blur is directly tied to FPS when using a sample and hold type display, which is what most people use.
At 30fps you end up with 33.33ms of pixel persistance
At 60fps/hz you end up with 16.67ms of pixel persistance
At 120fps/hz you end up with 8.33ms of pixel persistance
At 240fps/hz you end up with 4.16ms of pixel persistance
For every 1ms of display persistence, there is 1 pixel of additional motion blur during 1000 pixels/second motion.
This means 30fps(33.33ms) has a 100% increase in motion blur vs 60fps(16.67ms) (Assuming the repsonse times are keeping up with the refresh rate, which isn't too hard at lower hz)
See this blurbusters image which shows the motion blur vs display persistence in ms:
http://www.blurbusters.com/wp-content/uploads/2014/03/motion_blur_from_persistence.png
---
In saying that the game could also be adding in additional motion blur(ie post-processing) to help make the motion appear smoother, so your getting a double hit. Motion blur from the game? and the low frame rate adding blur.
If somehow you managed to keep focused at the center of the screen even despite the persistence you would not see blur, what you would see is an image warping across the screen in discrete steps.
More often than not, THIS, is what happens at low framerates on 100% persistence display devices. There are too many things in a scene to focus on so the intrinsic blurring from your eye moving across the screen tracking one object does not affect background image judder. This is why motion blur is needed at lower framerates, having a nasty full persistence display doesn't solve that problem.
Removing motion blur at low framerates is never something you want to do. Watching objects warp across the screen rather than smoothly slide across it induces nausea. If anything you usually want to strengthen motion blur at low framerates.