What changed in EDuke32, build by build

Fixes

terminx/eduke32#316

Some TROR layers were blocking hitscan shots because of the low limit.

* clipmove() - No longer traverses sectors once a distance limit is exceeded, and at most traverses 64 TROR sectors at once. * hitscan() - TROR sectors added to clipsectlist after regular next sectors. Only adds TROR sectors in a single direction, and at most 64 at once. * A_RadiusDamage - only add TROR sectors if inside damage radius. Also increase MAXDAMAGESECTORS to 512, same as MAXCLIPSECTORS. Fixes glitches and error spam in maps that make heavy use of TROR.

This would previously attempt invalid array access with index -1.

If the sector contains a TROR bunch, then whenever clipupdatesector() would normally return 1, instead run updatesector() and return 0 instead. The old approach did not work out in all situations. In Fury, certain flying enemies could not pass some TROR layers properly, and in AMC, trying to submerge in TROR water had the player glitch out on the surface. This exact approach had previously been used in AMC without any major issues for 2 years, before the recent TROR changes.

The problem with the previous version was that it didn't take overlapping geometry into account. This should be a more conservative approach that doesn't affect non-TROR uses of the cansee() function.

Invalid sectnums could previously be added to the clipsectlist if a hitscan shot passed a tror layer.

- Add TROR-awareness in similar fashion to clipmove() and hitscan() - Continue scanning walls to damage even if MAXDAMAGESECTORS is reached - Increase MAXDAMAGESECTORS from 128 to 256

And fix problems introduced by 9070cd2bff6d4547f0765fc483ffd4f923e24383.

The sprite is now properly copied for each sector it stretches across.

- Vertically attached sectors are now added to the clipsectorlist - Entirely remove the previous TROR hack from hitscan() - Instead, hitscan() now also uses clipsectorlist, and detects whether a TROR transition floor or ceiling was hit. If so, any subsequent wall hits in the same sector are skipped. This fixes the following: - Collision and hitscan checks where a sprite stretches vertically across more than 2 TROR layers. - Hitscan shots being unable to clear sloped TROR surfaces. - A potential out-of-bounds array access in hitscan()

Analogous to the previous commit, it also checks the sprites of the upper and lower TROR bunch of the sector. This handles the case where a sprite is intersecting layers, and fixes hitscan shots not hitting enemies properly in such cases.

This makes it so that the sprites of the ceiling and floor bunch sectors of the sector being checked are also iterated over. This handles the case where a sprite is intersecting TROR layers, and fixes projectiles not hitting enemies properly in such cases.

When checking if a point (x,y,z) is contained within a sector, then if x,y is contained, but z is not, it also checks all attached TROR layers. This fixes terminx/eduke32#24

With this enabled, a interrupt signal would lead to an infinite loop.

This only occurred between two maps that had mapart defined each.

Fixes

terminx/eduke32#220

Note: this was already possible by manually editing the repeat.

Prevents the game from showing the glowmap defined for the sprite. Applied to sprite shadows in Duke3D.

Previously, they would get stuck in a deactivated state while the player was still in range.

And apply some cleanup to the code in question.

Fixes

terminx/eduke32#275

Co-authored by

Evan Ramos

Previously, this would be the default selection and say "CVAR"

Fixes

terminx/eduke32#273

These would default to 0 after loading the savegame.

This prevents a visual jitter effect from sprites that aren't moving, but use the "fall" command in a water sector (zombie actors, pickups, etc).