It's just an ilusion thoough.... 

The "mouse look" menu option doesn't bother me anymore; +strafe is the command I was looking for to temporarily disable it and allow moving with the mouse.


But unfortunately "cd off" command only works if you actually have a CD drive. So as I mentioned upthread, there's no way to disable the loading of MP3s -- or to make them play -- if you have no CD drive (so I'll have to create a virtual CD drive before playing Quake even if I'm not going to use MP3s, just to prevent the considerable delay as it loads them into memory).

As I mentioned before, E1M2 and E2M3 will crash if you try to toggle external_textures on or off. I noticed that when these levels load, there is an error: "mod_loadtexinfo: 1 texture(s) missing from bsp file." And Fitzquake V does not handle missing textures very well (crashing). I know there's that one weird untextured button on E2M23 in DM mode. tool_texturepointer says it's "notexture."


New issues:

You can't use % in normal chat messages.... For example, I tried to say, "we need to kill 100% monsters" and it comes out "we need to kill 100(invalid macro ' ')monsters"


In Proquake, you get the little color boxes with scores (representing the top two players) in the HUD, to the right of your Cells ammo. Proquake will show no more than 2 of them, because if it were to show 3 or more there, they would block the clock. Fitzquake V blocks the clock with 3 ore more of them....


And more issues with centerprint: When you die, the scoreboard appeared right in the middle of the screen, the same as with the centerprints, so that if there are 3 or so names in the scoreboard, it will block the centerprint. For example, when you die in FvF there is a centerprint message "Press 2 to Observe" but you can't read it because names in the scoreboard will hide it. Proquake keeps the scoreboard at the top of the screen and avoids this issue. 

Was playing today on END map. Me and another player were using Fitzquake Mark V (server was proquake). He got disconnected and could not reconnect, because Fitzquake was giving him the error:

"host_error: Colors slots full."

I didn't encounter this, but he couldn't reconnect until we were at the next map. I know that has to do with the colormaps for the dead bodies, right? But why would it prevent him from connecting to the server at all?



Not so critical continued reports:

Toggling high-quality textures on or off in a game causes the player skin to go completely white. Other players will look solid white after you do this. But rarely it doesn't happen.... It seems to require restarting Fitzquake to fix it.


Oh, and you can use the PAUSE button even in Deathmatch on a server that has Pause disabled. It won't pause the server -- it will just pause YOU and your view of the action will be completely frozen until you unpause yourself.... Of course, you'll probably be dead by then....


And... I have a modified DM6 map with a few small extra areas. It seems to no longer be recognized by Fitzquake as far as applying high-quality textures to the walls. The wall texture names are still all the same, but Fitz won't apply them to my modified DM6. High-quality item textures still work fine. 

Gunter, hats off that you have singlehandedly brute-force revealed weaknesses in the engine.

And this is the kind of gauntlet of testing that almost any engine author could only dream to have --- in the thoroughness and the rigor.

I'm replying out of this admiration.

In a perfect world, I could correct these and the other bugs that others have graciously found -- and this level of bug-testing is frankly incredible compared to what I can recall seeing in maybe anything except maybe Quakespasm and ezQuake (I got really high levels of feedback for "modern" ProQuake, and the detail and testing in this thread seems to vastly exceed even that).

Mark V Final was apparently not as bug-free as I hoped when given a wide-array of testing in different environments and the kinds of uses that normal FitzQuake didn't even typically encounter (like as a client to a multiplayer server, as an example. I'm sure it got drilled and grilled in SP and coop not only up/down but left/right and forward/backwards).

I wish there were 2 of me. The one of me that exists isn't likely to ever have the time to revisit Mark V. :(

On the plus side, it is open source. And I don't see much posted that wouldn't be somewhat easy to remedy by an experienced engine coder.

Ultimately, attention is probably better served by people contributing to or whole-heartedly endorsing Quakespasm. Mark V doesn't contain too much that couldn't be ported to that engine to achieve a singular "old school" classic engine ... 

You have to admire his resilience in finding all these bugs...

It's a shame you don't have time to revisit the engine (in particular my biggest peeve being the distorted texture scaling issues).

I have always envied people who can code, I tried to learn how to code for best part of a year when I was unemployed and I just don't have the mindset for it. 

Yeah, it's a great misfortune that you don't and probably never will have time to put a little more polish on this... :/

Maybe some other engine coder will decide to pick it up. I'm tempted to take up engine coding myself to see if I could fix some of these things, but I doubt I'd have the time for that either.

I tried Quakespasm but I just don't like it. It's just not right, somehow. Perhaps if they imported some of the Fitz V features, like the ability to disable custom textures. Additionally, I find the Quakespasm website to be nothing but annoying. Yeah, great, they chose to have an "artistic" presentation with vague, arcane-sounding words and messages, but that's just stupid and irritating when I'm trying to find solid information about the thing. It's even difficult to find any real documentation of the features (as far as like console variables, etc.) in the included readme files... and I don't feel motivated to bother with the effort of digging through all the changelogs in the file to try and figure it out.

Digressing a bit, I remember giving feedback and reports for modern proquake, but the farther that project went along, the farther and farther it got away from standard Quake in feel and function, and it was a major hassle to track down all the console variables I needed to reset back to the defaults in order to get the right Quake feel back, so I gave up on that and just stuck with Proquake 3.5 (the last version by the original author). Modern Proquake was just no longer the same game. Apparently that's what hard-core runequake players wanted (to disable all special effects and change the defaults in order to get any and every advantage in deathmatch)... however, I feel that was against the spirit of the original Proquake to fix things without making too many changes to the presentation. Also, after "string safety" stuff was added in to Proquake 3.39+, it broke the FvF vote menu.... So yeah, I just can't use modern Proquake. It made too many changes.


I always liked Fitzquake, but it was just lacking some features to push it to the top of the pile. With the great additional features added by Baker (NAT fix possibly being the biggest factor for online play), I just can't prefer anything else over Fitzquake Mark V.

Going "back to basics" with usability improvements and bug fixes (and optional graphics enhancements that can be toggled off easily), instead of just cramming in everything everyone wants (I cringe a little when people start asking for Darkplaces stuff to be added in to this) is why this little engine has received so much attention. It's refreshing to go back to how Quake was meant to feel, instead of getting a bloated engine full of too much eyecandy, changed defaults, and hyperactive tweaker features.

I've found ways to work around most of the bugs (hah, I hard-coded some Fitz-specific workarounds into the FvF mod!), and I even put up a Fitzquake configuration page on the FvF website to help people get it setup, heh.... So yeah, I'm goiing to stick with Fitz V and I'll keep recommending it to people who play FvF. It just looks and feels "right" and has all the right enhancements in the right places (well, almost -- it would benefit greatly from a few specific proquake features).


Anyway, you have my admiration, Baker, for taking this little engine which had so much unrealized potential, and unlocking some of that potential. Even if seeing some of the potential unlocked just leaves us wanting to see MORE of it unlocked, heh.



The rest of you, come play FvF using Fitzquake Mark V :P

www.fvfonline.com
fvf.servequake.com:26008 

is there a port for Macs? 

Mark V release 14. All reported bugs fixed (*) and thank you for the bug reports!

1) BSP2 support via Spike
2) MP3 playing on top of each other = fixed
3) White HUD bug for some video cards = fixed
4) jdhack/Requiem "automatic impulse 12" for non-supporting progs
5) jdhack/Requiem "automatic fish fix" (jdhack is brilliant!!)

6) scr_crosshairscale 0 draws a dot

There are about 20 other improvements, the details are in the readme.

Download:

http://quake-1.com/docs/utils/fitzquake_mark_v.zip

Read Me

(*) Except Gunter's bug reports relating to mods missing skins and skin with toggling external textures.

If you notice any bugs, please let me know ASAP!

This should be a very polished release because I had no time pressures! 

Nice update! 

yay, that's a nice surprise! the release notes look really delicious! bugfixes, bsp2 and even requiem features implemented, just wow.

looks like warpspasm works fine now, the skies/liquids and polyblend effects were messed up for me in previous release.

old version http://imgur.com/jvqZZAY
new version http://imgur.com/xLNOiT0

it's always nice to have more engine choices just in case something goes wrong with certain hw setup or map release... dynamic light performance fix and various improvements make mark v a strong contender for the best performance/mod compatibility ratio out there imo. 

Can't check right now, but does this also address the issues with over-limit maps and/or demo playback in such maps that were first discovered in Backsteingotik as well as the Custom Gamer video thereof? 

Does it adress the non standard texture resize issue? 

@negke

I wasn't aware of that, but I will fix. Am I correct to assume if I check the Backensteinogtik thread I'll find the description of the bug?

@Fifth

Quakespasm did a power of two texture patch.

http://sourceforge.net/p/quakespasm/patches/25/

I have no eye for this sort of thing, does it look like their patch solved this issue to you? 

There's some mention of it in the release thread, something about monsters becoming invincible under certain circumstances. sock would know in more detail.

This is the video in question. MarkV was used to playback a video for capturing, not sure which engine the demo was recorded on. IIRC, what happens is that some models are rendered black/unlit. 

xoxoxoxoxoxoxoxoxoxoxooxoxoxoxoxox 

That bug in the Daz video was fixed in the October 2013 update. The some models rendered black/unlit thing wouldn't have been the October 2013 update either.

However, should anyone spot anything like that, please record a demo and save a savegame.

At the moment, I have time to fix bugs.

Next week I have new 2 new mapping features I want to introduce into Mark V, but unless every known bug is smashed I won't be happy. 

should i expect ne_ruins pack not working with this engine? looks like it was mentioned previously mark v was going to run out of edicts on this map, and i got a crash at a certain point playing it. 

jdhack/Requiem "automatic fish fix"

Curious about how exactly this works. 

Ran out of edicts in smqe08d_lun, which is id1. 

was it during gameplay or just at spawn? 

It was the teleporting monsters after the GL teleporter. 

Checking the monster count before and after swimmonster_go is run. 

I never heard of r_skyalpha before. I thought it might be great for taking "outside the map" screenshots, but no such luck. I did finally figure out what it was for though. 

Curious about how exactly this works.

The engine sets a flag if the total monsters increases when a monster_fish spawnfunction is run. It then watches think functions on the first two frames after spawns, watching for any entities of class monster_fish running swimmonster_start_go. If it finds one, and the flag is set, then the engine reverses a second increase of the monster totals (should one occur). 

Will it cause problems if that's fixed in my id1 progs.dat?