Well as you've posted this in Oolite-PC I'm going to presume you're a Windows user - and therefore I'm confused as to why you can't set a refresh rate in the nvidia drivers - what nvidia control panel/driver/card are you using?
I've always been able to pick my refresh rate, in the nvidia control panel - and even created game specific profiles...
However, is vsync on? is your monitor running at 60Hz too?
Finally, I thought A_C wrote sometime ago that the default refresh rate was going to be locked to 60fps or did I imagine that?
nVidia dropped the refresh rate override since 9x.xx drivers. I'm using latest (169.something, if I'm not mistaken).
And, yes, I can set refresh rate, but that doesn't affect the full-screen mode in oolite, and game profiles don't include refresh rate settings.
Only way I managed to get 75 Hz in full screen is by switching to nVidia control panel after I start the game and change it to 75. It sticks for the session.
Edit: I've contacted nVidia when they dropped the override option, and they responded by advertising Powerstrip...
Ah, that explains it - I've got such an old card (FX5900) that I haven't bothered with any of the new drivers - they're just bloatware for a card of my generation!
Finally, I thought A_C wrote sometime ago that the default refresh rate was going to be locked to 60fps or did I imagine that?
Actually, what I had written is that the default frame rate is locked to the current monitor's refresh rate. So it can be different to 60fps.
About Chaky's problem, I am not really sure why it happens. I have seen in the past such behaviour with GeForce cards, but not with ATI, so my educated guess is that it is driver related. It's difficult to test, as I do not have an nVidia card myself.
This is to expect with displays with no profiles, a.k.a. "default displays", but mine is well documented and recognized by display driver (exact model with all hw specs).
I guess that's refresh rate override nvidia style.. to eye-mutilating 60 Hz.
OK, just had a look at the code. It is not driver related, it is Oolite (or to be more precise SDL) related.
What happens is that the SDL internal representation for video modes is an array of pointers to SDL_rect, which is two dimensional. As a result, the refresh rate is not considered and even if set through .GNUstepdefaults it comes up always as zero.
I am not sure we can do too much about it without hacking further the SDL.dll or refactoring completely the way we scan for video modes in the game. Presumably this will be looked at after 1.73.
One of my many uncompleted projects is a rewrite of the display management code. While looking at that, I concluded that SDL’s approach to display management is amazingly, astoundingly, flabbergastingly, jaw-droppingly bad. And that is, if anything, putting it mildly.
One of my many uncompleted projects is a rewrite of the display management code. While looking at that, I concluded that SDL’s approach to display management is amazingly, astoundingly, flabbergastingly, jaw-droppingly bad. And that is, if anything, putting it mildly.
This is why I no longer look at code unless I must, otherwise it depresses me...