SVN handles and Git names are merged into one person.
more glue, fixes, backtrace for code called back from C.
Replace "if (g_tile[..].execPtr)" -> "if (G_HaveActor(...))".
beginning to glue things together. Introducing LUNATIC_ONLY.
Remove commented code using former engine variable "automapping".
Fix LTO=1 RELEASE=1 Lunatic build.
DEF "voxel": fix a tile range check failure message.
Encapsulate aplWeapon* array accesses in a PWEAPON(Player, Weapon, Wmember) macro.
In the normal game, these arrays are conceptually [MAX_WEAPONS][MAXPLAYERS], allocated as CON per-player gamevars (e.g. WEAPONx_WORKSLIKE). For Lunatic, they are replaced with weapondata_t g_playerWeapon[MAXPLAYERS][MAX_WEAPONS].
Replace wall of dup'd code in Gv_AddSystemVars with something more readable.
Specifically, have a weapondata_t type mimicking the aplWeapon* arrays. Keep a list weapondefaults[] which undergoes some static->dynamic tweaks and then makes its way to the WEAPONx_XXX per-player gamevars.
Replace initialize_engine_globals() with array initialization.
Lunatic translator: pack all translation units into one big blob.
Cleanup of console/on-screen-display (OSD) functionality.
- Rewrite the "clear background" routine in a no-brainer way instead of juggling around with rotatesprite(). Make it common to game+editor. Expose glRectd to glbuild. - Don't stop OSD text line drawing when encountering a non-printable char. Instead, treat it as space. - In OSD_SetTextMode(), don't use swaplong (which really swaps 32-bit ints) to swap pointers. Write an analogous "swapptr" instead. - When changing from/to OSD, don't inject a pause key. This *might* have been the cause of the reported pausing problems. - clean up the code... (Yes, this commit throws together too much stuff. I suck sometimes. :P)
event chaining.
print -> OSD_Printf, error reporting.
Clip printext256() at xdim, don't crash OSD_Printf() with empty string.
Add a couple of test CONs: non-local control flow, rotation-fixed useractors.
Fix rotation-fixed useractors (those having usertype bit 4 set).
Rotation-fixing happens for a couple of hard-coded statnums that presumably never move (DEFAULT, STANDABLE, FX, FALLER, LIGHT), but for actors it wouldn't make sense since the common case is that they do move. For this reason, bit 4 was introduced in r1934. The position of such useractors will not diverge due to error roundoff accumulation in rotating sectors (SE0, train).
more complete gameactor(), misc. translator tweaks.
Pack actor_t's bposx/bposy/bposz members into a vec3_t named "bpos".
save r_usenewshading in configuration file.
Fix build.lua's loadarts(), add bigytiles.lua.
engine.c: remove some old "#if 1"s, add compilation switch MULTI_COLUMN_VLINE.
Unconditionally enabled, but useful for comparing the behavior of the 1-column vline functions against the 2- or 4-column ones.
fix drawing tilesizy=512 walls, use non-pow2 routines with pskies.
The former is really only a workaround. Walls/vertical sprites/pskies with ysize 512 (and presumably greater, but this was not tested) are rendered with one shade higher at the borders (1 pixel vlines) because of a certain assumption in the ASM (see comments there). With very dark shades, the palookup[] buffer is accessed oob. We simply allocate 256 bytes more at the end for each. The latter is only for CLASSIC_NONPOW2_YSIZE_WALLS builds, which is not enabled yet. It seems to matter only for the uncommon case where the such pskies repeat in the height. A 1680x1050 window fully covered with such a sky is then rendered at about 60/85 the FPS for me (mostly due to not using the 4 pixel vline routines), so it may be leaning a bit too much on the side of correctness. A compilation switch DEBUG_TILESIZY_512 is introduced in engine.c for demonstration purposes.
in 3D mode's tile info, highlight members of swapped bottom walls.
- If aiming at a swapped bottom wall, display "Wall <wallnum> -> <otherwallnum>" - highlight pic, shade, pal, cstat in yellow then - in printext256, accept at most 3 digits for the color format string (e.g. ^123)
In Polymost, make r_usenewaspect=2 fog independent of screen x size.
when pasting single wall, take over bits 4, 1+64 and 8+256.
That is, everything concerning orientation. Previously, it was wrongly the bitwise NOT of these bits that got taken over. In particular, if bit 2 (swap bottom walls) would get pasted, ridiculousness could ensue.
Move fog calc routines into polymost.c, declare in engine_priv.h.
Don't enable fog in polymost_printext256() and when drawing tile view in M32.
The new "r_usenewshading 2" mode could darken these otherwise.
Classic-like visibility/fog for OpenGL modes, r_usenewshading 2 (new default).
Implemented using GL_LINEAR fog. The only source of difference (besides the obvious indexed vs. true color) should now be the distance constant, which still had to be determined experimentally. Polymer implements this mode in its fog fragment program part. Parallaxed skies are always drawn with full visibility, I'm not sure if there are any maps that expect otherwise. Also, accidentally committed: factor out initialization code from polymost_printext256() into gen_font_glyph_tex(), small game.c changes.
Fix savegame loading. Bump BYTEVERSION.
Fix CLANG=1 NOASM=1 build.
Factor out multiply repeated code into calc_ylookup().
effectively clamp drawn ceiling/floor tile sizes at 256.
This prevents computing a shift value outside of [0..31].
correct message when changing shade by small steps ([+], [-], mwheel)
Factor out fogcalc() issuing and application of the computed values.
In 3D mode, [,] auto-aligns walls to the left.
fix LAlt (carry over xrepeat) option for auto-alignment [.].
Fix building on Linux; fix WITHOUT_GTK=0 build.
Replace outer apScriptGameEvent[...] checks with G_HaveEvent().
Don't call setaspect_new() at end of rotatesprite.
This fixes 2nd and following rotatesprite calls drawing differently from the first in a context with custom set-up aspect, as reported by Lezing here: http://forums.duke4.net/topic/775-eduke32-20-and-polymer/page__view__findpost__p__143090 Also, back up and restore the aspect state across EVENT_DISPLAYREST.
Implement fade_screen_black() using fullscreen_tint_gl() in GL modes.
Factor dup. code in SDL/Windows layers into baselayer.c:fullscreen_tint_gl().
proper bound checks for {re,}definequote commands.
Rearrange {net,}actor_t for 4-byte alignment of int32_t members.
Bump BYTEVERSION.
Experimental NETCODE Makefile variable, enabled by default.
Disabling netcode compilation can be interesting on memory-constrained systems, or those that have no means of accessing the network anyway. Note: I'm OK with maintaining this myself, i.e. it's fine if netcode dev breaks compilation with NETCODE=0.
drowning in code.
Make EventNames[] an array of (const char *) instead of const tokenlist.
Initialize BADGUY sprite flags for hardcoded enemies.
... instead of switch/case-ing them in A_CheckEnemyTile(). Because this requires bumping BYTEVERSION, we also get rid of the excess trailing bytes in the save game's "rest" data. (See r3052.)
Lunatic translator: warning options, on_state_end, more bad-identifier chars.
submerging in code.
knee-deep in code.
- more codegen - make more members const, some char unsigned - fix some "geom" metamethods - '^' operator
gameexec.c: rip out some inline code into VM_Fall() and VM_ResetPlayer().
implement the non-local control flow needed for some commands.
player stuff (protect some members etc.)
Makefile tweaks, protect sprite[].picnum.
expose more stuff, more codegen (the easy ones).
Some Lunatic cleanup.
Fix build. It was my fault after all since I forgot common.h in r3243.
Fix potential crash in version checker.
1) see if we actually received anything (if http://eduke32.sourceforge.net/VERSION is unavailable, this returns now instead of continuing with nonsensical data) 2) check if we're getting a token from strtok()
Factor dist() and ldist() into common.c.
Move enum vmflags_t to gameexec.c since it's an implementation detail.
compat.h: slightly reformat the NOWARN-related preprocessor directives.
Expose per-tile nofullbright bit (GL modes only) to DEF.
The attribute is set per tile from DEF: either nofullbrightrange <begintile> <endtile> or tilefromtexture <tile> { ... nofullbright ... } As a special case, the list may only contain "nofullbright", in which case the texture is not changed. (This is analogous to "texhitscan".) Example: // make piggy's eyes fullbright red only when it fires the shotgun nofullbrightrange 2000 2034 nofullbrightrange 2040 2049 nofullbrightrange 2055 2061
Misc. engine cleanups, no functional changes.
engine.c: factor out 2 pract. ident. pieces of code into try_facespr_intersect.
The two uses are from hitscan and neartag. The functionality is reproduced exactly (assuming I made no mistake), down to different distance checking (<= vs. <).
better protection of array members inside structs.
