If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Quad, first off, I see you have tried a new engine!!
Second, to get rid of those ugly, ugly white pixely blocks, type -bpp 32 in your command line. BEHOLD:
BTW, those commads don't have to be in any certian order. I'll explain what each ons is for.
-game FvF20917: -game tells Quake to search for a folder named FvF20917. Quake then activates the files in that folder, which are the mod known as FvF version 20917.
-height: the "height" perimeter of the resolution
-width: the "width" perimiter of the resolution
-bpp 32: bits ber pixel. This determines how many color bits are in a pixel. 16, 24, and 32 are known to work with quake, at least to my knowledge.
-mem 256: tells Quake how much memory to use. With GLQuake, the higher resolution, more bits per pixel, and the workings of the fvf mod, at leadt 64 megs of memory are recommended. 256mb is overkill I know, but with 512mb ddr (at that time, 1GB ballistix now), it did'nt seem to matter anyway.
And I'm pretty sure Quad doesn't know cause you can see that he's clearly not useing the -bpp 24 or -bpp 32 perimiter. I dont know anybody who would willingly allow those ugly blocks.
Maybe I'm still exploring my options for a new quake engine, and didn't necessarily want to get chewed out for my quake "not looking up to your expectations".
I mean, Gunter didn't like my screenshots because I used Proquake and not something more up-to-date, so I decided to be brave and try Qrack out. I just started using it so it's not like I'm going to know everything.
By the way, if you're talking about those white gridlines that you can see in the dark corners, try clicking the picture and maximizing it to it's original size, and those disappear.
One more thing, I've only had Qrack for about a week.
Comment