Original log file · 20120708-2820.txt
------------------------------------------------------------------------
r2820 | helixhorned | 2012-07-08 14:49:31 -0700 (Sun, 08 Jul 2012) | 1 line
a.m32: add some commented out example code for the screenshot functionality.
------------------------------------------------------------------------
r2819 | helixhorned | 2012-07-08 14:47:25 -0700 (Sun, 08 Jul 2012) | 6 lines
Classic: draw walls with non-pow2 ysizes in the old fashion for the time being.
I'm willing to make this one concession to correctness in the name of backward-
compatibility. I think that one reason why this has never cause a crash is that
tiles in BUILD are allocated in Ken's big allocache buffer, so oob accesses were
dampened by that (though they hit uninitialized data).
------------------------------------------------------------------------
r2818 | helixhorned | 2012-07-08 14:47:23 -0700 (Sun, 08 Jul 2012) | 6 lines
m32script: EVENT_DRAW3DSCREEN, screenshot functonality.
The event is run after drawing the scene, but before the overlays. To
make a screenshot from a script, set DOSCRSHOT to non-zero. It will then
be scheduled to run once after the drawing but before the above-mentioned
event. The screenshots will be called mcapXXXX.{png,tga}.
------------------------------------------------------------------------
r2817 | helixhorned | 2012-07-08 14:47:19 -0700 (Sun, 08 Jul 2012) | 6 lines
Comment out printext256's GL mode fallback code.
This would only hit when polymost_printext256 erred out (mem alloc failure,
glGenTextures failure), i.e. "almost never".
Also, tweak a bound check in polymost_printext256.
------------------------------------------------------------------------
r2816 | helixhorned | 2012-07-08 14:47:16 -0700 (Sun, 08 Jul 2012) | 3 lines
m32script: if printext256's <col> arg is negative, use editorcolors[-<col>].
The editor colors are the ones listed on page 9 of the Mapster32 built-in help.
------------------------------------------------------------------------
r2815 | helixhorned | 2012-07-08 14:47:14 -0700 (Sun, 08 Jul 2012) | 1 line
Polymost: factor out y panning coefficient calculation code.
------------------------------------------------------------------------
r2814 | helixhorned | 2012-07-08 14:47:11 -0700 (Sun, 08 Jul 2012) | 6 lines
Add ART loader for the LuaJIT BUILD struct loader module, 2 more examples.
The map iterator now has init/finish capability, making it possible to
write scripts that aggregate data over multiple map files. One such example
calculates some statistics, the other loads art metadata and looks for
red walls with non-pow2 ysize tiles.
------------------------------------------------------------------------
r2813 | helixhorned | 2012-07-08 14:47:06 -0700 (Sun, 08 Jul 2012) | 1 line
Add LuaJIT-based BUILD map loader and batch processing script + example.
------------------------------------------------------------------------
draw walls with non-pow2 ysizes in the old fashion for the time being.
I'm willing to make this one concession to correctness in the name of backward- compatibility. I think that one reason why this has never cause a crash is that tiles in BUILD are allocated in Ken's big allocache buffer, so oob accesses were dampened by that (though they hit uninitialized data).
EVENT_DRAW3DSCREEN, screenshot functonality.
The event is run after drawing the scene, but before the overlays. To make a screenshot from a script, set DOSCRSHOT to non-zero. It will then be scheduled to run once after the drawing but before the above-mentioned event. The screenshots will be called mcapXXXX.{png,tga}.
Comment out printext256's GL mode fallback code.
This would only hit when polymost_printext256 erred out (mem alloc failure, glGenTextures failure), i.e. "almost never". Also, tweak a bound check in polymost_printext256.
if printext256's <col> arg is negative, use editorcolors[-<col>].
The editor colors are the ones listed on page 9 of the Mapster32 built-in help.
factor out y panning coefficient calculation code.
Add ART loader for the LuaJIT BUILD struct loader module, 2 more examples.
The map iterator now has init/finish capability, making it possible to write scripts that aggregate data over multiple map files. One such example calculates some statistics, the other loads art metadata and looks for red walls with non-pow2 ysize tiles.