too many graphicsmodes
Archives Forums/BlitzMax Bug Reports/too many graphicsmodes
| ||
I am trying to make a launcher in wich you choose your graphics mode and I ran into somethig weird. when I use the glmax2dDriver the eachin Graphicmodes gives me too many/double results SuperStrict SetGraphicsDriver GLMax2DDriver() For Local mode:TGraphicsMode=EachIn GraphicsModes() Print mode.width+"x"+mode.height+" "+mode.hertz+","+mode.depth Next EndGraphics what is this ? some hidden mode property ? Last edited 2012 |
| ||
Do you have a twin output video card? /guessing |
| ||
What output do you actually get? |
| ||
@matibee : just an onboard intel GMA @blitzSupport : oops here you go all of there are twice in the list Last edited 2012 |
| ||
Are you on Linux ? GraphicsModes() return bad values for me too under Linux. Maybe messing 16bits/24bits & 24bits/32bits ? Don't know... In fact GraphicsModes() was so buggy on most machine I avoid using it and stick to common resolution for 2D games. GraphicsModes() return invalid or unavailable resolutions resulting into crash if you trust them. |
| ||
do you have a 64bit os ? windows 7 64Bit give GMA Chipset as double GPU.. |
| ||
Eeek, I'm getting 3 entries (2 duplicates) for many of the resolutions. |
| ||
Whoa, good call, skids, never thought to actually RUN the code after all this time! (Sorry, nitti, never seen this happen before.) Duplicates are nearer the end for me... Last edited 2012 |
| ||
win7 32 here... |
| ||
If you can rebuild modules, try inserting following at line 240 of brl.mod/glgraphics.mod/glgraphics.win32.cif( mode.dmDisplayFixedOutput!=0) continue; It looks like the different modes in the same resolution represent how the resolution will be up-scaled to the display. |
| ||
i've tried that, but i still see double graphic modes... output: |
| ||
Hmm, just to confirm, you did rebuild modules? Changing that code to this also fixes my problem: if( mode.dmDefaultSource!=0) continue; Last edited 2012 |
| ||
yeah I did, that last code of yours does change the output! sadly it's not right anyway, i reckon i'll just solve it at the blitzmax side by taking out the duplicates. Thanks though |
| ||
sadly it's not right I don't follow. Your example shows four resolutions, all with different refresh rates and/or different color depths, which is correct. |
| ||
well those are the only four resolutions that GraphicsModes() returns, wich is not correct offcourse |
| ||
Ah, didn't realise that was the entire output! |