EDuke32 Changelog Unofficial archive

Build 2237

7 January 2012 · 1 commit by 1 author · SVN

Builds by month 47 builds

Original log file · 20120107-2237.txt
------------------------------------------------------------------------
r2237 | helixhorned | 2012-01-07 09:48:55 -0800 (Sat, 07 Jan 2012) | 4 lines

When defining a model with the 'model' token and there were errors, don't
let it hang around causing trouble later on; delete it right now and inform
the user.
Add a couple of 'static's to some functions and file scope data in mdsprite.c
------------------------------------------------------------------------
r2236 | helixhorned | 2012-01-05 13:58:23 -0800 (Thu, 05 Jan 2012) | 9 lines

- When saving game, clear all polymer lights before. Not doing this makes
the SE ones douple, triple, ... after each save.  Maphack lights are reloaded
with polymer_resetlights() (though I've had them disappearing after load, I
couldn't reproduce it afterwards).
- in debugging builds, print a message when polymer_resetlight is called on a
nonexistent one.  The problem is not so much the call itself (it's guarded),
but the fact that resources on the caller side may not have been freed if it
thinks that those lights do in fact exist. Right now, it's not the case though.
- add 'loaded map hack' messages after some other successful loadmaphack calls
------------------------------------------------------------------------

When defining a model with the 'model' token and there were errors, don't

Philipp Kutin (Helixhorned) 7 Jan 2012, 09:48 UTC−8 r2237

let it hang around causing trouble later on; delete it right now and inform the user. Add a couple of 'static's to some functions and file scope data in mdsprite.c

Engine
Already listed in build 2236

- When saving game, clear all polymer lights before. Not doing this makes

Philipp Kutin (Helixhorned) 5 Jan 2012, 13:58 UTC−8 r2236

the SE ones douple, triple, ... after each save. Maphack lights are reloaded with polymer_resetlights() (though I've had them disappearing after load, I couldn't reproduce it afterwards). - in debugging builds, print a message when polymer_resetlight is called on a nonexistent one. The problem is not so much the call itself (it's guarded), but the fact that resources on the caller side may not have been freed if it thinks that those lights do in fact exist. Right now, it's not the case though. - add 'loaded map hack' messages after some other successful loadmaphack calls