How do I increase the size of the buffer used for the console. If I enter a command that outputs a lot of data (e.g. edicts) it runs out of space and half the output is lost.

Also, after scrolling up with pageup, how do I get straight back down to the bottom of the data? pressing end doesn't seem to do anything. 

Also isn't there a -consize option? I'm wrong on this I think... 

try sv_aim -1 for some fun. you can shoot things behind you! 

ok, i get this missing glide2x and i put it in(courtesey of dlldownloads) and it just screws it up worse! help me out here? 

simply delete opengl32.dll from your quake directory 

If I type 'color' at the console I get response that 'color = 0 0' and 'color (0-13) [0-13]'

Can you tell me what this command is for and how it is used? I've looked through the readme but am none the wiser. 

Isn't it just a way to change the player colour ranges you're using for shirt and pants? 

Player's colors. color <shirt> <pants> 

Thanks 

just got some kind of strange error,

Something along the lines of "Couldn't set fullscreen DIB mode"

also, and i think this is related, every so often, FQ will ignore my config.cfg video setting of 100hz, and will set it to 43hz (which also causes the screen to look odd, because i don't think it was really made to display 1280x1024 @ 43 hz...)

anyway, something to look into for the next version, i suppose as it's mildly annoying for me as i'm starting and restarting FQ quite often to test stuff out and see the problem fairly often (i'd say it happens 1 time out of 5 or 6). 

looking above, i see that the problem was already reported...

so did anyone find out why this happens? i had a few applications open at the time the error popped up, mozilla, some explorer windows, foobar, msn messenger, a couple of dos boxes, gtkr and a couple of textpad.exe windows...

did anyone know if it's related to the wonky refreshrate setting? 

they probably are related, though i don't know what's causing it. "Couldn't set fullscreen DIB mode" means the video mode it's trying to set doesn't exist, usually. As to why it thinks that mode exists, I don't know. And video mode includes color depth, resolution, and refresh rate, so the 43 Hz thing could be because it thinks that's the default refresh rate for the resolution you requested.

And finally, if i recall correctly, there is a bug with refresh rate not working from the command line.

Sorry to say that I haven't done much with fitzquake this year; I'd done about a month's worth of work on it in december and then my hard drive failed. Since then I have been too busy to pick it back up. 

i actually have the refresh rate set in the autoexec.cfg.

vid_refreshrate 100
vid_restart
host_maxfps 100

stuck those lines in at the bottom of my autoexec, but it doesn't seem to be any different from setting the settings via the command line (like you said). 

you could try vid_describemodes or whatever the command is to see a list of supported modes. It's possible the one you're requesting isn't in that list. 

but i knew already that 1280x1024 32bit at 100hz was supported (i use it in windows).

i guess it's just the bug. i suppose i could just make an alias to switch res and refreshrate and just press it when it messes up. :X

eagerly awaiting the next version! :P~~

btw, i'm on an ati x850 card, if that helps at all... (current drivers etc etc) 

I have those messages often too. ATI Radeon 9600xt. I never found out what really caused it. I think I made a post about it earlier (maybe somewhere in this thread?). Sometimes it was connected to a program sitting in the systray. 

According to everything I've ever been told, this is almost always when the refresh rate is not supported by the monitor, typically flat screen displays that only support 60 Hz.

The Qrack engine had this problem nearly constantly and the issue was resolved by defaulting to 60 Hz refresh rate like DarkPlaces does. 

It is also a "feature" by ATI drivers. 

Are there any other libraries needed to build Fitz? (all I have is VC++ Standard) And...
Do you know if the Vertex Lighting tut @ quakesrc.org is compatible with your source since you've already made changes to how models are lit? 

First, check out this thread about building fitzquake; it should address most of the problems you are having or will have building it:

http://www.celephais.net/board/view_thread.php?id=60023

Second, i don't know which tutorial you're talking about... got a URL? 

http://www.quakesrc.org/tutorials/old/102 

Thanks for the link, I'll check it out... And here's the tut http://www.quakesrc.org/tutorials/old/102
Tremor is the only Q1 engine that uses it as far as I know of. It's subtle but a nice effect without going per-pixel. I'm just not sure if your overbright code would interfere. 

I think this would work, but you might have to do a little bit of reading and adapting rather than just pasting code in. I have color lighting instead of greyscale, so that's one difference. Overbright shouldn't pose a problem. 

I don't really have interesting to say, but FitzQuake has been one of the engines that I most study for understanding how different changes are implemented and just wanted to say thanks for all the work you put into it.

I've been comparing the incremental changes between the various versions a lot lately, in particular the texture manager which I very much like. 

thanks :)

how's your engine thing going?