Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: When choosing a CPU for your build how do you make sure it won't bottleneck your  (Read 9622 times)

0 Members and 1 Guest are viewing this topic.

Geek-9pm


    Mastermind
  • Geek After Dark
  • Thanked: 1026
    • Gekk9pm bnlog
  • Certifications: List
  • Computer: Specs
  • Experience: Expert
  • OS: Windows 10
Did somebody already mention that the difference between 60 Hz and 120 Hz has almost no visible difference for normal people.  Clark Kent can see the difference.

BC_Programmer


    Mastermind
  • Typing is no substitute for thinking.
  • Thanked: 1140
    • Yes
    • Yes
    • BC-Programming.com
  • Certifications: List
  • Computer: Specs
  • Experience: Beginner
  • OS: Windows 11
Did somebody already mention that the difference between 60 Hz and 120 Hz has almost no visible difference for normal people.  Clark Kent can see the difference.

Nobody mentioned that because it isn't true. There is no "upper-limit" with regards to how many "frames" we see, because our visual perception is hardly so simple. This becomes even more pronounced when the display is interactive with your input, though it is usually considered an almost ineffable quality. The way we see things is incredibly subjective, situational and context-sensitive. Even if a person reports that it "looks the same" a 120fps display can have effects such as causing motion sickness where a person has never experienced it at lower framerates.
I was trying to dereference Null Pointers before it was cool.

Geek-9pm


    Mastermind
  • Geek After Dark
  • Thanked: 1026
    • Gekk9pm bnlog
  • Certifications: List
  • Computer: Specs
  • Experience: Expert
  • OS: Windows 10
Point well made, BC.
Which gives rise the the question, what if a display have no frame rate? That is, the amount of time to create a frame would be indeterminate. Would that be bettor? Worse?