Yep, that solved it. Thanks. 

Yay, another issue. The music doesn't loop. Has anyone else had this problem and/or have a solution?

I tried using fitzquake085_mp3.exe but I have the same problem as poster #326. 

profile during demo playback segfaults the engine. 

wait, that was 0.80.
Quakespasm works. 

What's the purpose of the command anyway? 

thanks for?

profile dumps stats on which progs functions are being called the most. you can use it to see which functions are using up the most cpu time and take measures to either make them simpler (thus requiring less calculations) or make the functions get called less often. 

http://celephais.net/board/view_thread.php?id=60097&start=85&end=85 for more info 

thanks for making me try that command. 

Good Day folks, pleasure to see Quake enthusiasts are still alive and kicking, even if the golden era of the mapping scene has long died away.

Simply put, upon modifying console cvars such as "scr_conalpha, r_lerpmodels, r_shadows" Fitzquake won't save this settings upon exit. I've tried setting 'Savedgamecfg' to '1' but to my frustration no effect. Any assistance would be appreciated.

Thank you! 

This bug has always befuddled me but in both conventional GLquake and Fitzquake the weapon models appear from below the HUD rather than sit above it. Needless to say, it looks awkward and I've seen a YT vid of GLQuake where this problem does not occur 

just put them in autoexec.cfg 

I thought this was fixed in FitzQuake 0.85 versus FitzQuake 0.80 but somehow it happened:

http://quake-1.com/docs/any/arwop_skin_trashed.jpg

Situation:

FitzQuake 0.85 on windows hosting a coop game in listen mode with maxplayers 2 playing ARWOP with other client being a QuakeSpasm client (not that I can see how that'd matter).

On ARWOP start map, other player's skin is fine but after advancing through changelevel teleporter to first ARWOP map, other player's skin is trashed. 

is this the heapsize thing? i had a problem with the player skin getting mangled (along with other textures) and solved it by increasing heapsize.
but your question leads me to believe this isn't the same thing. 

That looks more like a texture cache problem to me. 

More info: Fitz's texmgr uses CRC to identify matching textures, but CRC is horribly prone to collisions. RSA have published some nice public domain MD5 code that I would generally recommend be used instead. 

I'd love to see 5 Mousebutton support being added to FitzQuake so I can use it as my default SP engine. 

yeah, this! ^^^

well, actually if all engines supported more than just mouse 1-3 that'd be awesome. :) 

The reason for 5 MB support is that I have +/-attack aliases for the weapons. As far as I know, all good players, like speedrunners, need to be able to fire the correct weapon instantly, without having to cycle through them to select and then using another button to fire. That is just stupid and you'll never get good in Quake that way, you only think you are.

It's painful enough that there's no 'bestweapon' support, which is supported by ProQuake, JoeQuake, DarkPlaces and QRack, but it feels even more handycapped when I can't at least use the extra mouse buttons to create some simple aliases.

Yes, I know that there's this little group of people here that is against everything that's different from how Quake was in '96 in terms of movement and weapon scripts, but I'm bringing it up once more because if FitzQuake would have these things, it can become much more popular in the SP scene and people like myself would actually be interested in playing all these great looking maps (from the screenies it looks great).

If you wanna be oldschool yourselves, fine. But at least let people have the choice for THE shooting-experience that sets Q1 apart from the sequels...and perhaps all other FPS games for that matter.

http://quakeone.com/forums/quake-help/multiplayer/382-binds-weapon-switching.html 

Bah, you don't need such binds for singleplayer unless you are a pussy. Just like FOV 90 (or the widescreen equivalent) is fine. 

fov 90 is evil 

Bah, you don't need such binds for singleplayer unless you are a pussy. Just like FOV 90 (or the widescreen equivalent) is fine.

bollocks on both counts 

..that was sarcasm i failed to pick up in time. hrm 

I actually think that in terms of features FitzQuake is pretty fine. Maybe it errs a little on the side of features for maps/mods while in development at the expense of features useful for actually playing the game, but that's understandable enough given the author's background, and overall there's nothing dramatically *wrong* with it (in terms of general features that is; I do think that there is some room for improvement elsewhere). A few nips and tucks in places is really all that it needs (let's have mouselooking enabled by default in the next version *please*). 

I welcome these types of requests... if I haven't added a feature to fitzquake yet, it's usually because my to-do list is huge; not because I think the feature is a bad idea.

Also Baker: Thanks for the bug report; is it consistently repeatable? I'll see if i can track it down. It seems unlikely that it's a cache/crc problem (player skins are allocated specially) but it could be anything at this point. 

I am serious. I used a bind to fire grenades with a key for ages but it felt like cheating.

Also I played with FOV 120 for a long time (because I was like OMG I CAN SEE SO MUCH MORE AND IT FEELS FASTER TOO!!!1), then I realise that it was idiotic. So I gradually went down again. 110 for a while, then 90. Now I have a widescreen monitor where ~110 is like old 90 according to some list by LH.