What's the usual entity count for the standard quake maps?

It feels fairly easy to hit the 512 entity limit! 

I hope it's not 512... 

Pretty sure it's 512 entities before you start getting in-game error messages.

(it might even be less because I t hink if you're shooting nails and stuff that adds to the in-game count or something) 

If you're refering to the edicts limits, that's 600. 

so far I've got 2161 entities and no warnings or errors.

I'm using TxQBSP 1.13 and Light 1.43, release 2, the one modified by MH for colored lights and multithreading. Can't remember which vis. 

As far as i know, lights are count as ents by light.exe, but they don�t add to the edicts. 

lights are not edicts, unless they have a targetname.

KillPixel: don't worry too much, modern engines handle well above 600 edicts. It's just that the standard id engines can't go over 600. 

Are things that do stuff during runtime.

A light without a target name is effectively deleted before runtime, and so not an edict. 

i believe light.exe actually delete them if they don't have targetnames? 

I use Worldcraft 1.6. Working on a Quake level, I compile to check my latest round of progress. Oddly, the batch file I'm using to run TXQBSP returns 28 warnings.

Checking back with the rmf. file, it claims that I have 28 instances of invalid structures. Which is odd since I've been careful about my vertex manipulation. When I zoom to the problem, it's a shapeless object at the grid's top view origin. It's a solid with one face, larger than the grid itself. 28 of them.

I deleted them all, and progress continued, but I'm wondering if anyone's ever come across this before. And what it may possibly mean... 

probably just a bug with the editor. i've seen that kind of thing is just about every editor i've used at one point or another. 

A blog post on when light gets removed and how to remove other things. Save entities, save the planet!

http://tomeofpreach.wordpress.com/2014/04/19/saving-entity-tricks/ 

Ok, can anyone out there spoon feed me some literature on custom entities and how to make gtkradiant see them.

I've asked someone on quakeone to make me a couple and he compiled a new progs.dat for me as well as gave me some cut/paste stuff to put in a radiant file.

I've got several more things I need but don't wanna harass the guy every time I need a new entity.

Currently, what I'm looking for is a way to arm/disarm triggers, silent spawns (that is, remove the "thud" that models make when the teleport in). I'd also like to be able to trigger any sound, i.e type a path to a sound file to be played. That way one could make a pretty dynamic and awesome sound scape.

My QC knowledge is nill at the moment, I know, I know... 

The empty object error is something that occurs in Worldcraft or Hammer.

How to Reproduce:
Create a brush.
Tie it toEntity (eg. make it a func_door)
Create another brush.
Select both brushes.
Tie them toEntity.
Oops, now there's a func_door without a brush.

What is going on:
The editor when it creates an entity from a brush, takes the brush data moves it out from under worldspawn and puts it under an entity like this:
Was:
"classname" "worldspawn"
{###....1}

Now
"classname" "worldspawn"

"classname" "func_door"
{###....1}
So what happens when the brush is already within an entity as above, the brush data gets moved/stolen from under the entity it's already in (worldspawn is an entity!), then put under the new entity. Like this:
Was:
"classname" "worldspawn"
{###....2}
"classname" "func_door"
{###....1}

Now:
"classname" "worldspawn"
"classname" "func_door"
"classname" "func_door"
{###....1}
{###....2}
Notice that there is nothing under the first func_door. And that is why the editor puts in at 0 0 0 and it looks like there is one superbrush covering all of reality. But really, there's nothing.

Best Practice: NEVER create an entity out of brushes that are part of an entity.

Source: I've been a mapper for Quake for over 10yrs. Also, the .MAP file format. 

this happens in gtkradient 1.5 as well, took me a while to figure wtf was going on.

"Best Practice: NEVER create an entity out of brushes that are part of an entity."

now I know... 

Best to keep it in mind and check the map for it before release. BJP's Glquake prints a warning if it detects a rogue brush entity, but none of the other ports do. 

 

Someone in here asked for polycount reduction tips or where was it? Just stumbled across http://web.archive.org/web/20020112020304/http://www.gamedesign.net/?file=rust/content/quake2/tutorials/poly_count when fixing links on http://quakewiki.org/wiki/Mapping_tutorials 

http://web.archive.org/web/20030219113111/http://www.planethalflife.com/davej/detail_versus_design.htm

What I'm desperately trying not to suggest is that complete mis-alignment of textures is the way forward. That is underkill. I've almost said aligning of textures to edges isn't important. That's a lie. It is. What is important however is knowing when to do it, when it is worth the time, and when it isn't. 

very helpful/informative links! 

I see where he's coming from, but I feel patronized by the article. There's a point about putting too much focus on "unnecessary" (debatable notion to begin with) detail at the cost of gameplay. Yet, just because the players may not see or appreciate certain details, or because they may not add to the gameplay, it doesn't mean it's bad practice. Besides, the On A Rail chapters doesn't work as a general example for all kinds of games and maps like he seems to be doing. 

In a nutshell, the point he's trying to make is that details shouldn't interfere with the overall theming of a level's design.

But he focuses on pointless detail (funny considering that's what he's trying to write about) and doesn't resolve the topics he's bringing up.

Yes ok, On A Rail was bland but it worked. You could say that about most of Half Life. Why not mention that software improvements allow us to have better graphics without sacrificing game play?

Yes ok, LDs shouldn't waste their time sticking doorknobs on things. Why not discuss using prefabs or other tools? 

It's worth noting though that the page was written in 2001. Some angst from back then about aesthetic fiddling getting in the way of playability is understandable (especially from someone working against commercial deadlines).