 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Quakespasm works fine.
"Allocblock:full" sounds like bsp2 isn't supported. The Valve-communitiy-board defines it as: map hits some sort of memory limits, level to large,... http://www.quaketastic.com/files/demos/gsh_tod_digs.dem.zip
It's very, very strange map :) ps. In console warning: monster_movetarget no targetname At first I wasn't too thrilled but as the map "opened up" I started to like it a lot more. It's fun and a bit nerve wracking!
I've played a bunch of Quake tonight so I have a save file ready to continue the map tomorrow. But I have to say it's a crazy map in a good way. Very ambitious and epic. A little light on the ammo for a lame player like me. I'll have a more detailed write up when I complete it. GG And I like the music... more suitable to DooM or Heretic maybe but was a nice change of pace in Quake. "Allocblock:full" is nothing to do with protocol and nothing to do with BSP2.
It happens when the map has too many lightmaps. Allocblock is used in the process of converting the light data in the BSP file (irrespective of BSP version) into lightmap textures, and is specifically used for selecting a region of each lightmap texture for a surface's light data. If there is not enough space in the current lightmap texture, the engine will go on to the next, then the next, and so on until it runs out of lightmap textures - and that's exactly what causes "Allocblock:full". Most Quake source ports raise the limit on lightmaps - the original engine only supported 64, but raising to 256 or 512 is common. There is a practical maximum in that light data is stored in a big static array so raise it too high and you'll run out of memory. But if you're getting "Allocblock:full" all it means is that you're probably using an older version of your preferred engine, and you should just update that. Thanks for the clarification. I would love to read up on bsp2 and the various protocols and perhaps pass this along in a video one day. The Quake Wiki is quite out of date or incomplete.
The finalised BSP2 format uses the magic number BSP2 and has the following limits: TODO, why are those numbers nowhere to be found :( I tried this map in the latest version of Mark V with no luck. So perhaps the limits in that engine need to be revised. Making an absolutely enormous map with a focus on size rather than quality.
Getting too ambitious. Mixing up base enemy and features and medieval enemy and features with no clear reason. Lots of completely full-dark areas. Massive open areas that take ages to run across. Barrel mazes. Crate mazes. Rock cave mazes. Going a bit too far with coloured lighting especially unsourced. Having huge amounts of stairs to jump up. Combining interesting and exciting designs with simple box rooms. Having progression buttons as semi-secret. Making the progression too unclear and complex for people who are playing the map without having made it. Having lots of waste space with little combat or stuff to do. OTOH the main cave bit was pretty spectacular, and the gameplay seemed fairly balanced. Next time focus purely on simple refined quality. Thank you very much!
This was a hard piece of work in the beginning. Now its absolute fun. Thanks for the crazy. Haha! There was a lot of headache thinking this map to an end. The music too. :D I've done so many versions of this song that it lasts for six more maps. :) You're absolutly right with Doom and Heretic. I thought about some 90's Metal doom style mixed with classics like Edward Griegs Hall of the mountain king, Mars and the LotR OST. I'm curious about your write up. Quakespasm did bump it's maximum number of lightmaps sometime around that version for ad_sepulcher support.
All that BSP2 does is replace short or unsigned short data types in the format with int or unsigned int. What that means is that wherever there used to be a limit of 32k or 64k, that limit in BSP2 is 2 or 4 billion. For practical reasons individual engines may use lower limits, but those limits are imposed by the engine, not the format. I don't consider MarkV to be a suitable engine for large maps. Baker is IMO somewhat too insistent on retaining the original and suboptimal GL 1.0/1.1 code, and too fond of gimmicky features like mirrors. Use Quakespasm instead, you'll have a much more pleasant experience.
Thanks for the critiques!
I agree with you in all points but one. There can't be enought ambition. I think you only can set your goals to high. And that I did definitely. It will not surprise you that my motto for the second map is "small is beautifull". :) |
|
|
|
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |