or jsut make the water out of func walls with water texture on them -- it will be solid and block bullets but render as water. 

Thanks guys, learning all the time :)

In a few days I'll throw a deathmatch map I've been making up for critique. The basic geometry is done, entities are done and lighting is getting close.
I'll upload with the mechanics all finished for critiquing before finishing the texturing and decorative brushes. 

 

 

 

 

 

Warning: 256 Models Exceeds the Standard Limit of 256.

Okay, so what is it really? 255? Or do I actually have more that 256 and it's just not telling me? 

It will still load in unmodified ports despite the warning. You just can't add any more if you want to keep it vanilla.

If this or any of the other limits become a serious problem in your map, feel free to give me a shout. It seems I'm getting pretty good at optimizing these things... :P 

func_illusionary details, try grouping some of the ones that are close together into one model. 

I well understand the limits and have gotten pretty good at optimizing stuff. What I was pointing out is this:

256 exceeds 256

Which it actually does not.

I'm guessing it has to do with counting that starts at zero instead of one. I probably have 257 models.

I've been adding one unnecessary func_wall off and on over the last several builds just to see how close I was to the limit.

I'll take one out now and the warning should go away.

Nevertheless, 256 is not more than 256

The good news is, I still have 5 or 6 models left to play with :) 

It's probably a counting issue and a bug of that message. The index would 0-255, the range of that is 256 items. So the model with index 256 would be one over the 0-255 range as it is actually the 257th model. 

negke: are you sure > 256 models loads in engines that don't support it? i remember having to remove bmodels from some maps like nesp09 because there were over 256 and it was crashing the engine. 

What I meant is that a map with exactly 256 unique models will still load despite the warning in Fitz and BJP. Anything above that number will cause a crash. 

It might load, but I suspect that you'd have problems with model 256. The limit is because vanilla quake sends the model value as a single byte over the network. If you try and send 256, the server's going to send 0 instead - and 0 is interpreted by the client as "no model". As long as you're happy with the last model only being visible in engines with higher model limits, you can have 256. 

the message is slightly buggy i think. The true limit is that a model with index >255 will break the network code on protocol 15 (you'll have some invisible entities.) So 256 models is okay, 257 is bad.

The bug in fitzquake is I used >=256 instead of >256 as my check for displaying that message. 

As we were talking about it in the thread of mfxsp6 and in others, i became more curious about it, and want to know more before i get this one in my maps. So i ask:

What is HOM exactly? What causes it? How do you fix it? 

it's the polygons that are not being rendered.

this happens if you have erroneous brushwork: too little trianlges, too many intersecting edges on one face, textures of various nature touching each other (water+sky or something). or just huge room with too complex geometry, bsp-vis compilers just can't cope and make erroneous polygons.

so just build clean and simple and with r_speeds in mind and you'll never get this hom thingy. 

It stands for Hall Of Mirrors. 

I don't know about other engines, but in Fitzquake if you set gl_clear 0 and noclip outside the map, there will be HOM everywhere that's empty space and you'll see why it's called "hall of mirrors". 

I had an idea about doing it on purpose using skipped textures. For that crazy 'down the rabbithole effect'.

Anyone:

Has that been done yet? I think it could work really well, maybe having chunks of other realms in weird positions as the player moves through some sort of rift. I nearly had a go on my last release. 

for me HOM as an effect is ruined by it's associations with errors, problems, bad mapping, whatever 

might be interesting as a breaking the fourth wall type of map 

Okay, I've been having to go very slow with making changes. Basically I'll make a few changes, only in one particular area, then copy the map over to my fast computer and BSP it. If the difference in marksurfaces is reasonable, I keep going, otherwise I start hitting the undo button.

Today I cloned a light fixture, not very big and kind of detailed, made from about 12 or 13 relatively small brushes. Connects to the wall at a 16x16 section of brush.

Copied the map and ran TxQBSP. When I saw the marksurfaces number I almost fell out of my chair. The increase was from 32,258 to over 33,000 !?!

Started thinking, well that light fixture didn't really look too good in the map, and there's two others exactly the same, I'll delete them all and maybe get a reduction of a thousand or more marksurfaces. Wrong.

New marksurfaces was only about 100 less, which is probably pretty close to how many surfaces there actually were on the two fixtures.

I'll take what I can get, back to mapping. 

I worked at trying to reduce marksurfaces all day yesterday. It seemed like every time I simplified brushwork, the marksurfaces went up. I remembered negke's comment about rebb's modified txqbsp, so I downloaded that and gave it a shot. Magic.

Using the -forcegoodtree switch I got an immediate reduction from 32,266 to 31,763 with no other changes. That's some breathing room. Which is good because I had more stuff to add that was absolutely necessary.

I added another small room with an elevator and an arched doorway. I recompiled the map and... more magic. Marksurfaces went down again, by over 250!

I'm now at 31,507 and I think my marksurfaces problems may be over because there's not much more stuff that needs to be added.

I did a full compile and played it through to the end, looking for any bsp errors the whole time and didn't see any problems at all.