printz Posted February 5, 2016 I see that both PrBoom+ and Eternity decide to create the blockmap (P_CreateBlockMap) internally if the lump has more than 65536 (0x10000) blocks. But why do they do it, if the lump exists already? 0 Quote Share this post Link to post
VGA Posted February 5, 2016 Does that mean they invalidate blockmap tricks by doing so? Do you have a test wad, sounds interesting. 0 Quote Share this post Link to post
printz Posted February 5, 2016 A quick example is exactly the map you showed me in the Eternity forum (Hellbound's full MAP29). I fixed the bug that prevented it from starting (get the latest build from here), but besides that, it has so many map blocks that it triggers the blockmap internal creation (see the console). I don't know of any special effects that may be cancelled. It's just that the map loader does work without needing to (also beware of demo compatibility with PrBoom Boom/MBF complevel when blocks are re-created). 0 Quote Share this post Link to post
scifista42 Posted February 5, 2016 printz said:I don't know of any special effects that may be cancelled. They are certainly at least theoretically possible. If you consider this:doomwiki said: Removing the blockmap from a level will not affect the rendering of the level or any line of sight calculations, but all collision detection will be nonfunctional. You could purposefully prevent a particular linedef from being included in blockmap, and then it would be rendered but not collided with, or do the opposite, include a linedef only to blockmap but not to segs, making it invisible but collidable with. 0 Quote Share this post Link to post
printz Posted February 5, 2016 Sorry, I meant that I don't know of any potential special effects in that particular map, in case VGA asked me for such map examples. Anyway the main question was: an entry is merely 2 bytes in the lump. So why are lumps limited to 128k like this in these ports? Answer: I assume it's because of the limits of the vanilla BLOCKMAP format, using 16-bit ints everywhere. New question: what's up with the big BLOCKMAP lumps? Are they in an extended format? 0 Quote Share this post Link to post
Graf Zahl Posted February 5, 2016 The general assumption was that any blockmap with such dimensions cannot exist in the original format and must be considered broken. Don't ask me about the specifics here, though. There is no extended Blockmap format. It was never needed, because recreating a blockmap is dirt-cheap and can be done on the fly without worrying about overhead. 0 Quote Share this post Link to post
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.