I'm a simple man with simple needs. 

allow ctrl+v of server/ip addresses into the menu for joining multiplayer games 

map sm169_ijed - sky and water textures won't load, although they work fine in quakespasm. that only affects the bsp2 version of the map, the regular bsp version (sm169_ijed2) performs fine in both mark v and quakespasm.

also, i hope the compatibility with ne_ruins and other potentially edict breaking maps (arwop with its icon of sin scenario?) will be improved...

great thanks to Baker for all the work however! 

"ctrl+v of server/ip addresses into the menu for joining multiplayer"

In console type "connect " and then paste IP address? 

Yay, nice work, Baker.

I don't have tons of time to really give this a proper workout, but I'm checking out some of the things I previously reported, and I found some issues are still there. Search the "quoted" phrases to find my previous (more-detailed) reports on this page.

"windowed resolutions" -- text chopped off at the top in certain resolutions, like windowed 800 x 600

"mp3 soundtrack" "delay" -- describes the problem of how if you don't have a CD drive (physical or virtual) the MP3 tracks will not play, but there is no way to stop them from trying to load, because with no CD drive, Quake won't respond to "cd" commands like "cd off"

"what am I chasing?" -- whatever it is, I'm still chasing it....

"there is no bolt1" -- unless this is something from another mod? So it's un-needed in the noshadow list. Though I still think k_spike and lavaball should be in the list, since they glow and shouldn't cast shadows (looks really weird to me to see lavaballs casting shadows, when they are casting light...).

"always run" -- Not exactly a fitzquakeV issue (except defaulting it ON), since it's a standard Quake "feature" (read upthread about why it's bad).

"gamma goes lower than 0.5" and "gl_overbright_models" -- blindingly bright blends and models when at the lower gamma settings.

"cshift" -- well, the water color in Fitz is changed from the default.... Not sure, but Ring/Pent/Quad blends might also be changed from the defaults.

Of course, fog and skybox settings don't save across levels, but hey, skyalpha does save across levels, and it works right too!


And then just the "not bugs but pleeeeeease?" enhancements:


Proquake positioning for centerprints (higher on screen) so they don't block the view.

Proquake RCON protocol

And Gulliver really wants Proquake IP/Name logging thing. 

fog and skybox settings don't save across levels

oh god here we go 

on the coag3 pack. Check out ericw's map, for some reason I am getting a problem with the fact that the skybox of 16x16 is causing it. 

I'll see what's up with that. 

I'm wondering if this was an intentional change?

The relevant bit of the SCR_CalcRefdef source looks odd:

#define SCREEN_CORRECTION_ASPECT 1.33333f
// if (scr_fov_adapt.value)
// {
r_refdef.fov_y = CalcFovy (fov_base, r_refdef.vrect.height * SCREEN_CORRECTION_ASPECT, r_refdef.vrect.height);
r_refdef.fov_x = CalcFovy (r_refdef.fov_y, r_refdef.vrect.height, r_refdef.vrect.width);
// }
// else
// {
r_refdef.fov_x = scr_fov.value;
r_refdef.fov_y = CalcFovy (r_refdef.fov_x, r_refdef.vrect.width, r_refdef.vrect.height);
// }

With the current commenting, those last two lines will clobber the result of the previous two (which would account for the FOV no longer adapting to the aspect ratio). 

Revision 16 will be out soon and has wide-screen perfect and there won't be a need for a cvar.

The long version is technical, but I've always hated the widescreen correction. Short version: MH's version of widescreen correction if properly applied (really long conversation, involving status bars) --- is perfect.

But that conversation is so dreadfully boring ...

I would have release version 16 by now, except I've been combing over fine details and have a couple of more things to do ... 

Am I silly, or does Fitz Mark V behave odd for recording demo?

If do 'record blahblah' before starting a map, i'll get a 1kb junk .dem that hangs MkV if I attempt to play it.

If I start the record while in the map, it records just fine.

Feels odd to me that the old behavior of how you would record demos in older Quake engines is the one that's messed up :(

(sorry if this is an old complaint or something, I just switched to using MkV after seeing z-fighting in my Jam1 map that wasn't visible in Quakespasm) 

(I'm using "Revision 14: July 11, 2014", btw) 

I get the same thing, with the 7/13 MkV. 

I'll investigate that thoroughly before releasing #16.

Thanks for letting me know. 

with this engine. Not sure how to describe it.
When you running forward, your field of view has started to jumping upward
i got the same shit with Quakespasm engine 

If I can understand the issue and recreate it, I can probably fix it.

There isn't a relation between field of view and the mouse. If you use the keyboard to move forward, does it happen as well?

Need more information. 

its related to your point of view somehow
its shakes upwards when you running
i'll try to use the keyboard to move forward and let you know 

http://quaketastic.com/files/demos/markV-issue_dem.rar

basically when you looking beneath your feet and run, Fitzquake Mark V(and quakespasm) is always trying to centered your point of view
theres no such issue in fitz085, just watch the demos 

Try with a clean Quake. No configs, nothing but pak0 and pak1. I am sure that will solve it. 

"lookspring 0" will fix? 

"lookspring 0" will fix?
yeah "lookspring 0" do the job, thank you!
i'm wondering though, lookspring 0/1 has no such effect to fitz
and i'm missing "m_filter 1" command 

lookspring defaults 0. Has to be turned on by the player.

Lookspring is a keyboarder player option.

Since mouselook defaults on in Mark V if someone decides to turn on lookspring, it works regardless of the mouse look setting. In Fitz 0.85, mouselook defaults off so turning lookspring on would automatically work.

m_filter -- with the frames per second in a modern client, m_filter is effectively on all the time with or without the setting. 

By the way, thanks for taking the time to fix all these issues despite earlier announcements. 

i have an issue that the hud is always blank white, while it appears normal when I call a menu or when I shoot or take damage. Videocard is Geforce 240 

Pulsar: Revision #14 or #15 should not have issue.

Is this with a recent Mark V released in 2014?

Please let me know.

[The white HUD on some video cards was bug in July 2013 and October 2013 releases because I used a method not consistently supported by all video cards.]