hpl3:game:guides:artists_guide
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
hpl3:game:guides:artists_guide [2012/11/09 20:47] thomas [Categories] |
hpl3:game:guides:artists_guide [2014/01/15 15:23] thomas [Categories] |
||
|---|---|---|---|
| Line 71: | Line 71: | ||
| ==== What is an entity? ==== | ==== What is an entity? ==== | ||
| - | It should not part to identify what should be an entity, but if the object you have in mind is made up out of one or several entities. The easierst rule of thumb to have is that an entity only serves a single purpose and allows for a single coordinated movement. For example, if you have a door with a scanner, and lamp above, it and a cog wheels that turn when the door move, this is NOT a single entity instead this would be split into four different. These would be: | + | It should not hard to identify what should be an entity, but sometimes the object you have in mind is made up out of one or several entities. The easiest rule of thumb to have is that an entity only serves a single purpose and allows for a single coordinated movement. For example, if you have a door with a scanner, and lamp above, it and a cog wheels that turn when the door move, this is NOT a single entity instead this would be split into four different. These would be: |
| * Door (and frame) | * Door (and frame) | ||
| * Scanner | * Scanner | ||
| * Lamp | * Lamp | ||
| * Cogwheel | * Cogwheel | ||
| - | Each of these serves a single purpose, the door can be opened, the scanner can be interacted with (and light up/down), the lamp can be turned on/off and the cogwheel can spin or stand still. All of these require different controls and thus need to be made into different entities. Another example (which is differnt from how Amnesia worked) would be a desk of drawers, here there would actually be two different entities. One for the frame and one for each drawer. The reason is that each drawer has its own movement to be controlled, and thus require a single entity for each drawer the desk contains. If the desk had only contained a single drawer the drawer and frame would be one single entity! | + | Each of these serves a single purpose, the door can be opened, the scanner can be interacted with (and light up/down), the lamp can be turned on/off and the cogwheel can spin or stand still. All of these require different controls and thus need to be made into different entities. Another example (which is different from how Amnesia worked) would be a desk of drawers, here there would actually be two different entities. One for the frame and one for each drawer. The reason is that each drawer has its own movement to be controlled, and thus require a single entity for each drawer the desk contains. If the desk had only contained a single drawer the drawer and frame would be one single entity! |
| Do NOT take this this thinking too far though. For example if a machine has lots of lights that light up when it starts working, and no other moving parts, then DO NOT make this into two entities, one lamp and one machine. Because the lamp and machine work in unison (lights light up when the machine start) there is no need to split them up! As always, if unsure, ask someone else (this makes it possible to put the blame on another person ;)) | Do NOT take this this thinking too far though. For example if a machine has lots of lights that light up when it starts working, and no other moving parts, then DO NOT make this into two entities, one lamp and one machine. Because the lamp and machine work in unison (lights light up when the machine start) there is no need to split them up! As always, if unsure, ask someone else (this makes it possible to put the blame on another person ;)) | ||
| Line 125: | Line 125: | ||
| "support"\\ | "support"\\ | ||
| - | Things that cannot really stand on their own and have many uses. Planks, girders, steel bars, beams, stretch of rope, etc. Anything that you use together with the environment and very seldom by itself. | + | Things that cannot really stand on their own and have many uses. Planks, girders, steel bars, beams, stretch of rope, etc. Anything that you use together with the environment and very seldom by itself. Important note: Much of this should probably be in static objects, so only use it here if it has lots of polys or a need to by dynamic. |
| + | |||
| + | "edibles"\\ | ||
| + | Anything that can be consumed, water bottle, food, medicine, etc. | ||
| + | |||
| + | "doodad"\\ | ||
| + | complex stuff that does not serve any purpose other than spicing up the environment. Important is that it is complex enough that it should not be in static objects. | ||
| These are of course not the only categories available but should give a good start. If adding categories, do NOT add to specific ones like "red herrings" or have two categories that could contain the same entities, like "food" and "groceries". | These are of course not the only categories available but should give a good start. If adding categories, do NOT add to specific ones like "red herrings" or have two categories that could contain the same entities, like "food" and "groceries". | ||
hpl3/game/guides/artists_guide.txt · Last modified: 2015/02/17 14:16 by nebej
