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.] 

I used the d\l link from the first post of this news, but I did it recently.

the readme says it's revision #15 

i'm running a mod with 1280x1024 via fitz its loads exactly 1280x1024
next i'm running the very same mod via mark5 and its loads exactly 1280x1024 too

NOW i'm running a mod using fitz again and it drops to 640x480x16 what gives?

there's no any comment(width height bpp) in the command line 

when i'm running quake at 1920x1080 (my desktop resolution) and switching between fitz and mark5 it doesn't drop to 640x480x16 

it seems adding vid_restart to autoexec.cfg do the job 

@pulsar: thanks for the info and the detail is much appreciated. I'll see what I can do.

@spy: FitzQuake 0.85 saves vid_restart at the end of the config. What 0.85 does is start up video at 640x480x16, then run the config.cfg. Mark V (and Quakespasm) read the config before video startup, so it doesn't need the vid_restart.