SVN handles and Git names are merged into one person.
fix screentext problem introduced in 5997fee3c6b9c2bda5aa31e8a80782f3901c4be1 by folding the relevant change into the new screentext flag introduced in 03a39f4d64a9131138eeecab08003d5c6b67da1c
update lz4
clean up mimalloc integration
Can now build with USE_MIMALLOC=0 if desired.
update mio.hpp
bump max bunches to 8192
Avoid calling dragpoint on invalid wall indexes in SE 20 code
Fix renderer menu option hiding logic
Prevents duplicate entries from appearing, which then crash when changed.
Fix sloped sprite shading preview in editor
Fix sloped sprites to once again take on ceiling/floor shade
If the texturecache.index file cannot be read, invalidate it
This fixes a problem where the texcache file could grow without limit if something managed to corrupt the texcache index.
add new TEXT_CENTERCONSTWIDTH flag for screentext to center glyphs within their allotted region in constant width mode
respect xbetween value for screentext between chars in constant width mode
only use debugbreak.h when actually debugging
undef SMMALLOC_DLL
lower Polymost SCISDIST to 0.1f
Prevents rendering errors with low fov.
add warning if TROR somehow tries to draw the same wall more than once per frame
don't pass SDL_INIT_HAPTIC to SDL_InitSubSystem() because it's not actually used for game controllers
add .ang member for walls in CON
clarify windowsHandleFocusChange() logic
disable glGetGraphicsResetStatus() stuff for now
print sprite number and tile of sprite when clipsectnum >= MAXCLIPSECTORS in clipmove()
Kinda shit tier, but whatever.
Increase YAX_MAXCLIPSECTORS from 64 to 256
Some TROR layers were blocking hitscan shots because of the low limit.
Engine/Duke3D: Several changes to TROR traversal in clipping functions
* 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.
Don't try to interpolate rotatesprite calls if the clock difference is negative.
avoid passing -1 as bunchnum to SECTORS_OF_BUNCH
minor optimization of 209bc8793d0838bb02d487bd8a74e6199a9911d1 + similar blocks in fgrouscan
improve slope sprite interpolation on edges
update xxHash to 6f9771f2c014a703f151ac646d5f8074b6236c84
only update a maximum of one VIEWSCREEN tile per frame
Improves performance greatly in all renderers in scenes using more than one concurrent VIEWSCREEN sprite displaying unique cameras.
Fix globalsound being broken in 3D Mode
This would previously attempt invalid array access with index -1.
Revert clipupdatesector() changes from df868267 and replace with a different approach
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.
Rework the cansee() changes from 86e5fe7f to only affect TROR transitions
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.
Fix hitscan() and clipmove() by checking for invalid sectnums
Invalid sectnums could previously be added to the clipsectlist if a hitscan shot passed a tror layer.
fix actors on lotag 1 sectors not being squishable
Squishing is now prevented if SE7 is present (as previously intended), or when the actor is standing on submergible TROR water.
fix regressions with clipupdatesector() from df868267
This resolves a bug in Duke3D where the player couldn't move while shrunk if a TROR sector was present on the map. It also ensures that the original clipping is used if no TROR bunch is present inside the sector in question. This should reduce the amount of backwards-compatibility problems.
Fix clipmove() problems with TROR wall geometry resulting from commit 7f00d5ce
The changes are now more conservative and only affect sprites on TROR layers.
Improvements to A_RadiusDamage()
- 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
Fix many cases in which cansee() would fail with TROR
This commit adds a failsafe which corrects the given origin and destination sectnums of the "cansee()" function, by checking if the corresponding (x,y,z) coordinates are actually contained within the given sectors. The problem with TROR in particular was that the calculation done to determine the point of intersection on the TROR layer requires the coordinates to be within the given sectnums. Else, cansee() would simply return 0, even if there was a clear line of sight. This should also implicitly fix any other cases where the coordinates of the cansee() call do not exactly match up with the given sectnums.
Fix sprite shadows being drawn on transparent TROR layers
Also fixes sprite shadows being drawn floating above floor slopes.
Account for floor and ceiling slopes in renderAddTsprite
Fix tsprite cutoff if the sprite stretches across multiple TROR layers
The sprite is now properly copied for each sector it stretches across.
Overhaul TROR handling for hitscan() and clipmove()
- 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()
Add TROR-awareness to sprite clipping 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.
Add TROR-awareness to sprite clipping in clipmove()
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.
Clean up voxflags[] a little bit
Fix voxel visibility rolloff in classic mode to match sprites
TODO: Polymost
