Post by Paril on Apr 14, 2009 18:10:06 GMT -5
I'm asked this a lot, so I thought I'd put the final answer here.
What is the difference between an info_null and an info_notnull?
To put it lightly, the difference is existence.
info_null does not exist, while info_notnull exists.
info_null is an entity used by RAD, and only exists inside the map "temporarily". Basically the RAD program reads the entity list for these info_nulls for spotlight information. info_null entities are terminated in Quake2, and never actually used in-game.
info_notnull is an invisible entity used for positioning. Basically it exists during gameplay and can even move (see turrets).
If you aren't sure which one to use, just remember, lights are opaque to the game! Lights are built into the map itself, and are only used in one or two places in the game code (for lightramps basically). Lights = null, everything else = notnull.
-Paril
What is the difference between an info_null and an info_notnull?
To put it lightly, the difference is existence.
info_null does not exist, while info_notnull exists.
info_null is an entity used by RAD, and only exists inside the map "temporarily". Basically the RAD program reads the entity list for these info_nulls for spotlight information. info_null entities are terminated in Quake2, and never actually used in-game.
info_notnull is an invisible entity used for positioning. Basically it exists during gameplay and can even move (see turrets).
If you aren't sure which one to use, just remember, lights are opaque to the game! Lights are built into the map itself, and are only used in one or two places in the game code (for lightramps basically). Lights = null, everything else = notnull.
-Paril
![X7[Q2C] Avatar](http://x7q2c.site90.com/av/x7.gif)
