Are there any small (credit card size roughly), flexible screens that are cheap on the market?
>>51895162
Not your personal consumer recommendation site.
>>51895162
Yeah, I have 2
I think the 59FPS has to do with how windows report those framerates? like 59 is actually 59.94 instead of the 59 shown.
>>51896717
but OP image is wrong, he is throwing his computer into the trash despite not actually running at 59 but instead it just shows as 59.
>>51896681
Certain monitors report a TV-compatibility timing of 59.94Hz. Therefore, Windows 7 and newer versions of Windows expose two frequencies, 59Hz and 60Hz, for every resolution that is supported at that timing. The 59Hz setting makes sure that a TV-compatible timing is always available for an application such as Windows Media Center. The 60Hz setting maintains compatibility for applications that expect 60Hz.
In Windows 7 and newer versions of Windows, when a user selects 60Hz, the OS stores a value of 59.94Hz. However, 59Hz is shown in the Screen refresh rate in Control Panel, even though the user selected 60Hz.
>>51896681
Windows doesn't know the frame rate of stuff running on the gpu
>>51896789
Fuck off retard, we're trying to discuss something here.
https://support.microsoft.com/en-us/kb/2006076
.
Resolution
No action is needed.
This behavior is by design for monitors and TVs that report only 59.94Hz but not 60Hz. Both 59Hz and 60Hz are translated to 59.94Hz before these values are sent to the driver. Therefore, the display is identical at 59Hz and 60Hz.
This KB article describes the case in which a monitor or TV reports 59.94Hz. However, this issue also occurs for monitors or TVs that report the following TV-compatible timings:
23.976Hz, but not 24Hz
29.970Hz, but not 30Hz
47.952Hz, but not 48Hz
71.928Hz, but not 72Hz
119.880Hz, but not 120Hz
>>51896796
No we aren't.
See >>51895167
>>51896809
>Both 59Hz and 60Hz are translated to 59.94Hz before these values are sent to the driver. Therefore, the display is identical at 59Hz and 60Hz
Mine works at 59 and looks like shit at 60
what the fug
>>51896821
Well fuck I noticed before that in some games when I go fullscreen my monitor changes refresh rates, I can tell because it goes dark for like 2 seconds.
Games like Killing Floor show 59.9 FPS using MSI Afterburner and when going fullscreen my monitor takes time to display the new fullscreen image but games like Battlefield Company 2 do show 60.0FPS in MSI Afterburnet and going into fullscreen immediate.
>>51896874
Yeah this.
I fixed it by using CRU which is a 3rd party application that forces a display rate.
This started happening when switching to nVidia, i never had this issue with AMD.
