[Blood] weird death probably due to collision detection

[Manuel-K]

I've managed to die with the message “You killed yourself!” in the first level when jumping to the last secret. I don't think that should be possible, but this is a Build engine game and I've encountered similar things with both the original exe in Dosbox and NBlood.

This was with commit 410f5a45452c768b6262c100981d01a0121bded3, but that probably doesn't matter.

I know this is pretty vague for a bug report, but I want to know if anyone else has managed to die to weird causes.

[markanini]

You mean the super secret with the napalm launcher?

[Manuel-K]

You mean the super secret with the napalm launcher?

No, the last regular secret where you have to jump over a stone slab to get a box of flares.

[sinisterseed]

No, I am 100% convinced this is due to Build's broken ass collision detection. I've died in vanilla, GDX, and NBlood as well as Raze in all sorts of dubious ways thanks to it.

Some examples? Wallriding, trying to go into sharp corners, trying to squeeze between tighter walls and props, and so and so on.

The collision detection of Build is a steaming dumpster fire, some of the worst I've seen in a classic title...

[Graf Zahl]

... and trying to fix it causes all sorts of follow-up errors - see EDuke32...

[Graf Zahl]

I'm putting this on hold. Seeing how much grief it cost for EDuke trying to fix the collision detection code I declare this a hands-off item for now.

[sinisterseed]

I'm putting this on hold. Seeing how much grief it cost for EDuke trying to fix the collision detection code I declare this a hands-off item for now.

Does trying to fix something as fundamental to the engine even stand any chances though?

I mean, eduke tried to do this and the results we're... not exactly optimal... by seemingly breaking more things than fixing.

[Graf Zahl]

That's precisely why I won't touch this code. It has been abused to hell and back and without thorough use of compatibility settings is never going to work right. Remember Shadow Warrior and the tank?

[sinisterseed]

That's precisely why I won't touch this code. It has been abused to hell and back and without thorough use of compatibility settings is never going to work right. Remember Shadow Warrior and the tank?

Oh how can I forget about it, my #1 glitch , or the semi-broken shrink ray in Duke on... what was it, E1L5 The Abyss?

Yeah, this thing is probably so hopelessly broken that it's not worth messing around with it, like ever... no lifetime is enough to bring it to a higher level of quality...