[Build] Reaching the memory limits
Once upon a time reaching the memory limits of Build would crash it and if you hadn't saved recently you'd loose hours of work. This does not seem to be the case now though. I've reached and surpased the default limits of Sectors, Walls and Sprites and Build (actually Mapster32) has just doubled the new maximums for me.
Is this actually a problem? If I were to attempt to run this map on a 486 then maybe, but on a modern PC?
I'd like the updating of my maps to work in both Classic and Megaton and have just about finished updating my Funhouse map but now that I've gone past those initial maximums I'm worried something bad is about to happen - so are my worries unfounded?
To put this into context I just went over the default Wall limit of 8192 and this has now jumped to 16384, along with the maximums for Sectors and Sprites. So do I carry on as normal and make this map even more epic? Will it have an effect on Classic mode? And what happens if I go over the new 16384 limit? That is very, very unlikely though.
Some clarification would be helpful.
The only "old" problem that has returned is some kind of bizzare sector corruption. I made a video and I think I posted a thread on here actually.
Last edited by Lunick
Feb 7, 2014 @ 9:44pm