ProQuake 4.36 (way higher FPS)

[R00k]

Something i found out the hard way...

change the zNear value from 4 to 1 for my chase fix to work... not sure of the side effects but havent seen any yet...

	MYgluPerspective (r_refdef.fov_y,  screenaspect,  1,  farclip);

[Baker]

Something i found out the hard way...

change the zNear value from 4 to 1 for my chase fix to work... not sure of the side effects but havent seen any yet...

	MYgluPerspective (r_refdef.fov_y,  screenaspect,  1,  farclip);

What was the bad side effect?

The reason I ask ... I use your chasecam fix in my wqpro too.

[I haven't seen a bad side effect yet, but I haven't done any extreme testing with it. I did reduce 0.9 to 0.8 in the ... I'm thinking the LerpVector or the VectorLength2 ... without looking I can't recall, but the reason I did was I just slightly could see into the void against some walls at certain angles.]

[MH]

It will definitely affect depth buffer precision as the depth buffer isn't linear, so you'll get a higher percentage of it clustered to the near Z.

[R00k]

would it hurt to dynamically set the zNear to 1 if in chase_active and 4 units if not?

	if (chase_active.value)
		MYgluPerspective (r_refdef.fov_y, screenaspect, 1, farclip);
	else
		MYgluPerspective (r_refdef.fov_y, screenaspect, 4, farclip);

actually Darkplaces defaults the zNear to 1...

cvar_t r_nearclip = {0, "r_nearclip", "1", "distance from camera of nearclip plane" };

So, it might not fubar too much.

[MH]

It's worth a try anway.