Cool, but you can set cvars from the command line too, can't you? 

yes, but they don't work exactly the same way. The command line video settings affect the creation of the initial fitzquake window, while vid_* cvars will only ever take effect on the next vid_restart. For people suffering from the -dinput bug, vid_restart isn't an option. 

It would be really great if when you switched games (as in changed from the id1 folder to a mod folder) if fitzquake would tell you the maps in that folder when the "maps" command is used. At the moment, it only tells you what maps are in id1, even when the game is something else.

Actually, it should already work this way. The list should tell you all custom maps that are available, including id1 AND your game dir. Are you sure that it doesn't work that way? 

'cause remember, maps in /id1/maps can be loaded while running a mod as well as those in /mod/maps 

Oh, what do you know, they do appear. Sorry about that. The only real problem i have with fitzquake then is that i can't figure out the console command to increase the sound sampling rate. 

I really haven't added any sound system features, so fitzquake has the same features as glquake in that respect. If there's a command or variable for that in glquake, it should be in fitzquake as well. If not, then there isn't one. 

Might you implement playing CD tracks from the sounds folder at some stage in the future? 

immensely cool, hurt my eyes after a few minutes, but definitely a fun gimmick to play with every so often. :) 

i have it on my 'maybe' list. I think it would be cool, just a matter of finding time :) 

Thanks. I had forgotten that Quake had music and only remembered after reading a thread about it.

I have use 'another' engine just to try it out but prefer Fitzquake as my "engine of choice" 

It'd be neat if when you took screenshots, the filename was named after the .BSP you are taking shots in. 

Is it possible/feasible to have a 'r_showbboxes 2' so that only the bboxes within the confines of the area of visible surfaces are shown? In other words, so I can't see the bboxes of things on the other side of a solid wall.

I'm just trying to make things look a little less complicated when viewing bboxes. 

It seems like the new video mode switching means that users of Windows 9x/ME can only get 640x480x16bpp. This isn't just one machine as it happens on 2 of mine with ATi and nVIDIA. If you try and switch modes user Windows 9x it'll end horribly saying that the video mode can't be found.
Doing vid_describemodes shows them all as 0Hz. Manually setting the refresh rates from the console doesn't seem to get it working.
You'll have to try it to see, any ideas of a work around?

Over all, seems to be better, I just wish I could get it working properly under Windows 9x. 

It seems like the new video mode switching means that users of Windows 9x/ME can only get 640x480x16bpp. This isn't just one machine as it happens on 2 of mine with ATi and nVIDIA. If you try and switch modes user Windows 9x it'll end horribly saying that the video mode can't be found.
Doing vid_describemodes shows them all as 0Hz. Manually setting the refresh rates from the console doesn't seem to get it working.
You'll have to try it to see, any ideas of a work around?

Over all, seems to be better, I just wish I could get it working properly under Windows 9x. 

KVM: I don't have access to a 9x/ME box, so I can't reproduce the problem. For a workaround, you should be able to use the old functionality of setting -width -height -bpp at the command line, just like with previous versions and just like with glquake. Sorry i can't be of more help.

Mike: that should be pretty easy to add

Phait: i've thought about that. What would be even better is a way to format the filename the way you like, for example "%MAPNAME%_%DATE%_0000.tga" or something like that. Just lowere priority than other stuff. 

Metislime: Setting by -width -height -bpp doesn't work under 9x, it crashes with the same error while the console starts up.

If someone else can sonfirm that this happens then I think it means that 0.80 isn't as good for 9x as 0.75 as with 0.80 it seems like you can only use 640x480x16bpp. I will try some more things in drivers.

PS. Sorry about the double post. 

I had the same thing happening-

I'm also stuck on a 9x box for now.
I could start 0.75 just fine in any mode using -width -height -bpp, but using 0.80 I could only get it to work at 640x480x16bpp, just like you.

Then a strange thing happened-
I tried 0.80 in 300x200x16bpp, just to see what happened, and it started up okay.
Then I tried 800x600x16bpp again, and it worked!
I tried higher settings, and they worked also.
Strange...

Kudos to metlslime, it looks great! 

very strange, but i'm glad you finally got it working. 

Is there a way to toggle mouselook to always be on? I find this to be the most enjoyable way of playing. Thanks and I've enjoyed fitzquake thus far, keep up the good work! 

type it in the console. It should be saved across sessions. 

I guess there is also a the possibility to add it in your config.cfg or quake.rc file (I don't know exactly where...) in order to enable it each time your start Quake, and avoid annoying console use each time.. 

fitzquake automatically saves "+mlook" to your config.cfg. But other engines do not, so for them you have to add it to autoexec.cfg or whatever. 

Thanks for the tips ;) 

...are we going to see 0.85 anytime soon? 

Thanks for the help guys (girls?) ;-)