2 Obscure WinQuake fixes

[Baker]

Do these kind of things crash the id386 asm too?

I ask because some of calculations in C work slightly dfferently if id386 is defined.

Like does the sprite draw Z issue crash the asm code too?

[mankrip]

[leileilol]

It also happens in pure C. I believe it has to do with drawing one whole pixel covering the screen, and trying to draw the next but it couldn't find a space for it and has an access violation right there. An alternative way to fix this would be better sprite clipping code that's more aware of screen boundaries

[qbism]

Is there a specific scenario that can duplicate this crash?

[Baker]

[mankrip]

[qbism]

Got it. Easiest to duplicate with a stationary sprite. Move back and forth through it slowly. Normally engine will stop rendering the sprite when pixel height is almost full screen but eventually will crash.