InsideQC Forums

the old quake waterfall textures are not literally the same image shifted down... there are multiple layers of waves moving downwards so each image is somewhat unique in addition to the offset.

doesn't quake ship with a zoom alias (bound to f11) that does this? Perhaps i'm mistaken....

I know one thing I did in my autoexec.cfg was change the alias to modify m_pitch and m_yaw instead, so that I could experiment with different sensitivities without it being reset every time i zoom in/out.

Yeah, i think there is no actual bug; the answer is that lightstyles and skingroups animate at 10Hz, and bsp textures animate at 5Hz, and none of this is a bug, but it confused me for a bit. (since i assumed bsp was 10Hz, I assumed everything else must be wrong somehow.)

i'm more confused now... so first of all, in my memory, I had to have 2 frames on, 2 frames off in a skin animation, to get the same rate of blinking that 1 frame on, 1 frame off achieved in a bsp texture animation.

Just checked the source and everything seems to be based on (int)(cl.time*10), so i ...

i knew glquake broke a lot of the animated skingroup feature, (i.e. forcing it to be either 1, 2, or 4 frames) but I didn't know about the timing bug -- is this the bug that causes it to animate at 20Hz instead of 10?

(I used this for the landing beacon in rub2m2, and I had to duplicate frames -- 2 ...

Is there a reason why textures get misaligned; I texture it properly, tie to entity, compile and it's off centre?

Move it to origin, texture it there, then move it back with texture lock disabled. Yet another issue with rotation that nobody has fixed :)

Thanks for this... But what do you mean ...

ajay wrote:Is there a reason why textures get misaligned; I texture it properly, tie to entity, compile and it's off centre?

Move it to origin, texture it there, then move it back with texture lock disabled. Yet another issue with rotation that nobody has fixed

thicker walls?

there is a feature called "minlight" which tells light.exe to enforce a minimum light value across the entire level. I don't know if it's a command line option or if you have to add "minlight" "x" to the worldspawn entity in your map file. From an artistic point of view, you should not use it -- it ...

path_corner works for monsters as well as func_trains

framerate independence is a good feature, i support it.

However, it's wrong to say that only 72 fps is "correct" quake gameplay -- almost nobody was getting this framerate in 1996 (i got about 30-40 fps on my pentium 166), and yet the game wasn't broken then.

It may be accurate to say 72 fps is ...

Baker wrote:(Quakespasm is basically FitzQuake 0.80 that has been actively developed and improved).

0.85 actually

Hi.... some interesting comments in here.

I just checked the code to see if that frustum culling issue was real; and it seems that Fitzquake already handles it correctly -- lerp state is updated on entities before they are culled, so it can't get stale from frustum culling.

Regarding the entities ...

With this formula many calculations immediately become possible including perspective calculations...

I don't have time to check your work or anything, but if you are talking about perspective texture mapping, it might be good to verify which of these two projections you are doing:

http://i19 ...

blending over time instead of lerping over space sounds good, I like the fact that it means that stationary props get lit the same as in a non-lerping engine (of course enough engines lerp now that there is no way to have consistency across all engines.)

Of course if the blend time you choose is ...