2 October 2011 · 5 commits by 2 authors · SVN
------------------------------------------------------------------------ r2061 | hendricks266 | 2011-10-02 00:18:49 -0700 (Sun, 02 Oct 2011) | 2 lines Fix GCC 4.6 out-of-bounds and uninitialized warnings involving bossmove[]. My choice of solution is simply to add an extra set of values duplicating the previous five because doing so would definitely show the user no changes. I could have tinkered with the messy loop where the out-of-bounds references are made but there is no guarantee I could have succeeded or kept compatibility. ------------------------------------------------------------------------ r2060 | hendricks266 | 2011-10-02 00:18:17 -0700 (Sun, 02 Oct 2011) | 1 line remove two instances of duplicate USE_OPENGL preprocessor checks missed by the removal of the POLYMOST definition ------------------------------------------------------------------------ r2059 | hendricks266 | 2011-10-02 00:16:57 -0700 (Sun, 02 Oct 2011) | 1 line move Electric Fence (EFENCE) handling from build/Makefile to Makefile.common ------------------------------------------------------------------------ r2058 | plagman | 2011-10-02 00:09:15 -0700 (Sun, 02 Oct 2011) | 4 lines Polymer: constantly get the textures handle for projective spotlights Getting the texture handles without requiring invalidation means we can handle ART-animating tilenums without impacting performance too much. ------------------------------------------------------------------------ r2057 | plagman | 2011-10-02 00:09:04 -0700 (Sun, 02 Oct 2011) | 7 lines Polymer: fix horizontal spotlight SEs constantly getting invalidated Polymer has a hack that snaps horiz values of spotlights between 90 and 110 to 90 and 110 to avoid triggering aliasing artifacts with perfectly horizontal spotlights. Propagate that change all the way to the spotlight SE sprite so that the code won't think that the horiz is always different from the light and mark it invalid each frame. ------------------------------------------------------------------------ r2056 | plagman | 2011-10-01 22:56:35 -0700 (Sat, 01 Oct 2011) | 9 lines Polymer: preliminary support for GL_ARB_debug_output This won't actually do anything until the a debug bit is added when creating the context, but that requires support for GLX_create_context which SDL doesn't support. I'll add support for WGL_create_context to winlayer in a bit as a stopgap. Also updates our local copy of glext.h with a fresh one from the Khronos registry. ------------------------------------------------------------------------
My choice of solution is simply to add an extra set of values duplicating the previous five because doing so would definitely show the user no changes. I could have tinkered with the messy loop where the out-of-bounds references are made but there is no guarantee I could have succeeded or kept compatibility.
Getting the texture handles without requiring invalidation means we can handle ART-animating tilenums without impacting performance too much.
Polymer has a hack that snaps horiz values of spotlights between 90 and 110 to 90 and 110 to avoid triggering aliasing artifacts with perfectly horizontal spotlights. Propagate that change all the way to the spotlight SE sprite so that the code won't think that the horiz is always different from the light and mark it invalid each frame.
This won't actually do anything until the a debug bit is added when creating the context, but that requires support for GLX_create_context which SDL doesn't support. I'll add support for WGL_create_context to winlayer in a bit as a stopgap. Also updates our local copy of glext.h with a fresh one from the Khronos registry.
