You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Windows running on a 144 Hz or higher monitor, my refresh rate will change everytime I Alt-Tab to/from the emulator, since the emulator is running in 120 Hz for me. If I uncheck "Auto" under Monitor Frequency in Video Options I get 60 Hz. (Switching the resolution, of course, is slow and flickers a lot so it would be nice to avoid.)
I checked the source a bit and found in NstDirect2D.hpp (Line 72): MAX_RATE = 120,
which makes my native refresh rate resolution be removed from the list of resolutions in the EnumerateAdapters method.
Unless there is a reason for limiting this to 120, maybe it's an easy fix? There are even some 360 Hz monitors now so I think it might be best to not limit it at all for future proofing.
I just thought I would mention it. Anyway thanks for the great emulator!
The text was updated successfully, but these errors were encountered:
Thanks for pointing this out. I also have a 144Hz monitor, but I usually run at 120Hz. I think maybe I will just remove any refresh rate limitations altogether. I'll take care of it the next time I merge the upstream core code in and prepare for the next release.
With Windows running on a 144 Hz or higher monitor, my refresh rate will change everytime I Alt-Tab to/from the emulator, since the emulator is running in 120 Hz for me. If I uncheck "Auto" under Monitor Frequency in Video Options I get 60 Hz. (Switching the resolution, of course, is slow and flickers a lot so it would be nice to avoid.)
I checked the source a bit and found in NstDirect2D.hpp (Line 72):
MAX_RATE = 120
,which makes my native refresh rate resolution be removed from the list of resolutions in the
EnumerateAdapters
method.Unless there is a reason for limiting this to 120, maybe it's an easy fix? There are even some 360 Hz monitors now so I think it might be best to not limit it at all for future proofing.
I just thought I would mention it. Anyway thanks for the great emulator!
The text was updated successfully, but these errors were encountered: