Hello everyone, hope this message finds the Marathon/Aleph community in good health.
I've been an on again, off again Marathon map maker for, well, basically 20+ years. I've posted some (hopefully cool?) single player levels on here that some of you have downloaded and commented on. Seems about once a year I'll get the Marathon bug and dive headfirst back in, and this year is no different. A few weeks back, I started tinkering around with a level that I have been designing for years--quite literally. It's pretty massive, and I would consider it a magnum opus. Polygon count has surpassed 3000 with still much remaining to be done. But I've recently run into a problem/bug that I will attempt to describe as best I can:
Weland 1.4.4 is the editor I have been using. I use Vasara to texture the level; a version of Vasara I am not certain of, but has been on my hard drive since 2015, so nothing brand new. My problem arises when I attempt to select a texture value which I have assigned in Weland that goes beyond the display maximum of Vasara. In other words, for example, Vasara displays a possible 56 light values (0-55), yet Weland lets me design a theoretical limitless amount of lights. However, when in Vasara I attempt to assign a light value beyond 56, the game crashes.
Even simpler, I have light 57 in Weland, but when I go to Vasara and press the action (tab) key, I am listed with light vales 0-55. I can use the (previous weapon, next weapon) controls to manually go beyond light 55, but when I do, Weland crashes.
In essence, Weland has a 56 light limit. I am certain such errors would be duplicated if I went beyond the maximum display of platforms or tags, as well. And on that note, tags display a massive amount, like 60+, nothing to worry about, though I have build the architecture of my level mostly without assigning platform polygon types, so I am sure to run into this problem with them later.
Most would say 56 lights, 60+ tags, and whatever+ platforms are enough, but not for the level (monstrosity?) I am designing. I guess, when all is said and done, I am reporting to the community a bug with Weland 1.4.4.
Hopefully this makes sense. If not, I can try and figure a way of posting some pictures to illustrate better what issue I am having.
Cheers everyone!