So what you are saying it that some of the standard/preset soft15khz modes use more than 60hz then???
He was talking about the high refresh modelines.
SS: I'll try again - those high refresh modes obviously have higher modeline values in them, yet say @59 or @60hz, or in the case of 352x288 still says @51hz - which in practice is really 106hz. However, just as the 15khz version runs at 51hz and is choppy, wouldn't it be better for the high refresh version to run at or around 120hz? (You know, similar to making a 60hz version whose scanrate is 18khz.)
Yeah, I just doubled the pixel clock on those modes, not the "mode name" field (which isn't used for anything at all).
All of these modes should have 31kHz. So most likely they don't use the full spectrum of your monitor.
This brings up a couple other related things:
a. I created and put in my own high refresh modeline, but it said '@120hz' and it was superceded by the original, stock modeline. Is that why?...that it has to say something close to 60hz for soft15 to install it?
Hm... If you add it in "custom15khz" it will overwrite the stock resolution, if theres any, and will add it as "60hz" to windows (though it is still output as 120).
If you add it in "usermodes" then it will be added with the real refresh rate to windows, and also will not overwrite any stock modeline.
b. I've notice there is some looseness in the txt file syntax allowed. What exactly are the limits, character-wise?
Hm... in the most simple case, just use basic chars and numbers.
modeline "name" pixelclock h_active h_syncstart h_syncend h_total v_active v_syncstart v_syncend v_total optionsThe
name field is ignored, but should not contain any spaces or stuff (could fry my parser).
the resolution added to windows is
h_active *
v_active.
The vertical refresh rate is calculated by
h_total *
v_total / pixelclock (doublescan halves the output refresh, interlaced doubles it!)
The options field can contain pretty much everything but soft-15kHz only parses "-hsync", "+hsync", "-vsync", "+vsync", "interlace" und "doublescan" atm.
All values except the pixelclock should be integer values (means no dot/komma whatever).