Build 9449
GIT-
fix warnings introduced by e0ee1bfe
June 2021 3 builds · 11 commits
Build 9441
GIT-
fix Polymer rotatesprite texture clamping
Show details
- Fixes
- terminx/eduke32#150
-
fix Discord streaming issue
Show details
- Fixes
- terminx/eduke32#152
-
add missing check for r_useindexedcolortextures cvar in polymost_usetileshades()
Show details
- Fixes
- terminx/eduke32#153
-
fix usage of GrowArray for osdstrings
-
fix allocator mismatch in GrowArray
Build 9382
GIT-
fix sloped sprite drawing error
-
bump MAXYDIM to 4320 and fix two marginally related assertions in dorotatesprite()
Show details
Note that MAXXDIM and MAXYDIM only really control which video modes will be added to the list of available modes found in the startup window and in-game menu, and that the engine itself hasn't had an arbitrary limit imposed on which resolutions are actually supported for a while now.
-
fix backwards EDUKE32_NO_XINPUT getenv check...
-
fix clipping issue where the player could get squished between a 2-sided blocking wall sprite and a wall in rare instances
August 2020 5 builds · 5 commits
Build 9253
GIT-
experimental TROR rendering fixes
Build 9252
GIT-
fix TROR rendering glitch in polymost when camera Z is outside of sector boundaries
Build 9242
GIT-
Implement tileflags member of picanm, and added support for new flag: TILEFLAGS_TRUENPOT, that allows you to enable true non-power-of-two texture support per-tile.
Show details
(Fixes classic's buggy tiling and panning behaviour and bypasses the emulation of it in Polymost)
Build 9239
GIT-
fixes for including compat.h in a C program built with MSVC
Show details
I needed to change the weird VS workaround in order for the EDUKE32_STATIC_ASSERT on line 850 to succeed. Things seemed OK when I tested them, but I'd like more information on the suspected compiler bug in question and why this was necessary in the first place.
Build 9206
GIT-
Apply pogokeen's fix for hightile texture seams in polymost.
July 2020 1 build · 2 commits
Build 9202
GIT-
fix microprofile warnings
Show details
Some of these fixes aren't optimal, but I'm not exactly looking to make heavy changes here.
-
add microprofile (https://github.com/zeux/microprofile)
Show details
Build with "make MICROPROFILE=1" and browse to http://localhost:1338 to use. A pass over it to fix warnings will probably be in a future commit.
June 2020 6 builds · 7 commits
Build 9144
GIT-
fix function signatures of ksqrtasm_old() and clip_nsqrtasm()
Show details
These functions were specified as accepting int32_t values, but wrap functions (or are wrapped by functions) that take uint32_t.
Build 9130
GIT-
fix sprite rendering order in polymost
Show details
- Fixes
- terminx/eduke32#65
Build 9123
GIT-
fix compiler warnings
Build 9122
GIT-
potentially improve dealing with corrupt .md2/.md3 models
Show details
I didn't test any actual corrupt models, just noticed the lack of any error checking when looking at something else.
Build 9073
GIT-
fix rev.cpp so it works properly outside of builds on Windows
Build 9070
GIT-
fix winlayer wm_setapptitle() to deal with being passed a pointer to apptitle[]
-
change calcFrameDelay() to no longer reduce the frame limit by 1 fps per 60Hz of refresh rate with r_maxfps -1
Show details
This worked fine with G-SYNC displays, but I guess it sucked for regular 60Hz setups for some people. This should be tested for regressions...
May 2020 2 builds · 2 commits
Build 9049
GIT-
fix sprite sorting issue that caused broken voxel rendering in polymost
Build 9040
GIT-
fix poorly written time comparison in vsync handling
Show details
This only affected KMT mode, and only on certain system configurations.
January 2020 1 build · 1 commit
Build 8533
SVN-
Fix -Wunused-parameter warnings
July 2015 1 build · 1 commit
Build 5312
SVN-
fix unbalanced begindrawing()/enddrawing() pair in printext16().
April 2013 1 build · 1 commit
Build 3701
SVN-
stricter map load time checking for sprites with oob sectnums.
Show details
Sprites are now considered to have out of bounds sector numbers if it is < 0 or >= numsectors (not merely >= MAXSECTORS). If such a sprite is now encountered during post-load, an attempt is made first to assign it a sector number (using updatesector()). If that fails, the sprite is removed from the map. The background is that a dozen of maps do come with such sprites and could previously corrupt the sprite list when loaded.