Viper96720
Diamond Member
- Jul 15, 2002
- 4,390
- 0
- 0
Originally posted by: Viper96720
Just run a Quake 3 bench you'll notice its over 60fps.
Originally posted by: futuristicmonkey
Huh? Couldn't u just run the film through faster? Why would it cost more to make 60fps film instead of 30fps? It doesn't make sense.
Originally posted by: Viper96720
Just run a Quake 3 bench you'll notice its over 60fps.
LOL you are silly VIAN.Originally posted by: VIAN
You may not be able to tell, visually the difference between 85 and 100, but try playing for a bit on 85 then 100 and then back to 85 in a fast paced deathmatch. You will feel the difference and that means that you can see the difference.
You will never be able to run a game at that framerate unless you have new hardware running at least a year old game will all details on, so the effort to get to the target frame rate of 85 if fruitless. Then Vsync makes it all the more difficult to get 85fps. Your best bet is to just try to get a constant framerate of 30 or above.
Originally posted by: Jeff7181
I don't believe there is a physical limit to what the human eye can detect.
To whoever said the human eye refreshes 30 times per second. That's probably the biggest load of BS I've seen in this thread so far since the human eye doesn't "refresh." Eyes don't have a "refresh rate" because no part of them is digital... they recieve "streams" of light and your brain puts it all together. If you train your brain to put together the information it recieves through the eyes faster, you'll become more sensative to motion and refresh rates of monitors. An example of that was in my speed reading class in high school... we did exercises where the teacher would darken the room, and use a device to flash a word on a white screen for a fraction of a second. At first he started at 1/10 of a second... by the end of the class, 50% of the students were reading complete senteces flashed on the screen for 1/100th of a second.
Try something like 60 and 120.i set one side to 60 and the other to 80, the funny thing is with 60 fps , i noticed a lot less blur
This just keeps getting better and better.The human eye can only take 20 or so, actually.
A lot of people can see jerking and stuttering during camera panning/rotation on 24 FPS blurred film.But common sense will give you the answer, if you watch a movie and then play a game.
Make sure you aren't running at 60 Hz.If i took it below 60 though the difference began to show.
Now's your chance to prove yourself wrong. Load the program up, put one side on 30 FPS and the other on 120 FPS.And opposing BFG, I heavily support consistancy. At any framerate 30fps and up will be great if consistancy is maintained. When you notice choppiness when playing a game, unconsistancy is setting in and that just sucks.
Ok, dude, you are not understanding. I know that 120fps is smoother than 30fps. My point is that - take COD for instance. I am indoors running at 80fps, then I get outdoors and the fps drops to 40 - there you notice some choppiness. If you move indoors and outdoors a lot, why not just make the minimum 40 so that your eyes don't have to adjust to another framerate each time and, therefore, take away from the experience.Now's your chance to prove yourself wrong. Load the program up, put one side on 30 FPS and the other on 120 FPS.
According to your logic they should both be equally smooth because they are both constant.
Of course that's a load of rubbish as consistency has nothing to do with it.
Regardless of any objects speed, it maintains a fixed position in space time. If the plane that just flew by was only going say, 1 times faster than you, you probably would have been able to see it. Since your incredible auto focus eye had been concentrated on the ground before it flew below, your visual cortex made the decision that it was there, but well, moving really fast, and not as important. A really fast camera with a really fast shutter speed would have been able to capture the plane in full detail. Not to limit our eyes ability, since we did see the plane, but we didn't issolate the frame, we streamed it relative to the last object we were looking at, the ground, moving slowing below.
You can also do the more technical and less imaginative tests above, including the star gazing, and this tv/monitor test. A TV running at only 30 FPS is picking up a Computer monitor in the background in its view, and with the 30 FPS TV Output you see the screen refreshes on the computer monitor running at 60 FPS. This actually leads to eyestrain with computer monitors but has everything to do with lower refresh rates, and not higher.