> > > > > i wasn't able to get 1600x1200 to work properly coz apparently the GTS can't do it. instead it seems to use 1024x768 and let the extra graphics go off the edge of the screen. yah i know i'm supposed to put error checking when setting modes.

> > > > 1600 x 1200 shouldn't be a problem, even my 3dfx voodoo 3 can do it.

> > > ok.

> > depends on the bitdepth, I would guess. If you use 32-bits (why? unless you are doing direct assembler pixel framebuffer manipulation, when having a bitdepth the same as the processor word size might simplify code? but surely you ought to use primatives instead of pixels, and let the 'accelerator' Geforce do the accelerating for you?) then don't expect high resolutions (especially if you have a deep z-buffer) since you are using so much framebuffer memory. On the other hand, if you use 24-bits you should get better resolutions and 16-bits is my favourite resolution (I can't tell the difference between 16 and 24 anyway). But why bother with 32-bit unless you have some fancy alpha blending?

> i haven't touched 3d acceleration yet, but i will keep in mind what you say for when i add 3d-acceleration. anyway, about my software 3d engine, i like 32-bit color because it is a much nicer memory arrangement than 24-bit; it is simpler and makes the code much cleaner. i very much notice the difference between 16-bit and 32-bit color, and when 3d acceleration is used with 16bit so that it adds dithering, i think the graphics look appalling. i will make sure it is not possible to run my programs in 16-bit color.

I think some people would call you a 32-bit-nazi :eek:
(j/k) :)

> > > > > i still haven't been able to get rid of the stupid blank window opening up and trying to kill epileptics. i won't release my program like this coz i'm not a murderer.