Creating a moving platform: Difference between revisions
m (minor tidy & removed unecessary note & categorized) |
|||
| Line 1: | Line 1: | ||
[[Image:moving_platform_01.jpg|right|Width:64]] | [[Image:moving_platform_01.jpg|right|Width:64]] | ||
In this tutorial you will learn how to create a moving platform. | In this tutorial you will learn how to create a moving platform. | ||
| Line 28: | Line 27: | ||
|- | |- | ||
| Name || platform_func | | Name || platform_func | ||
|} | |} | ||
| Line 39: | Line 36: | ||
|- | |- | ||
| Stop sound || <code>Doors.FullClose12</code> | | Stop sound || <code>Doors.FullClose12</code> | ||
|} | |} | ||
== Path tracking == | == Path tracking == | ||
| Line 57: | Line 51: | ||
|- | |- | ||
| Next stop target || <code>P1_S1_O</code> | | Next stop target || <code>P1_S1_O</code> | ||
|} | |} | ||
| Line 69: | Line 61: | ||
|- | |- | ||
| Next stop target || <code>P1_S2_I</code> | | Next stop target || <code>P1_S2_I</code> | ||
|} | |} | ||
| Line 81: | Line 71: | ||
|- | |- | ||
| Next stop target || <code>P1_S2_M</code> | | Next stop target || <code>P1_S2_M</code> | ||
|} | |} | ||
| Line 93: | Line 81: | ||
|- | |- | ||
| Next stop target || <code>P1_S2_O</code> | | Next stop target || <code>P1_S2_O</code> | ||
|} | |} | ||
| Line 105: | Line 91: | ||
|- | |- | ||
| Next stop target || <code>P1_S1_I</code> | | Next stop target || <code>P1_S1_I</code> | ||
|} | |} | ||
| Line 122: | Line 106: | ||
== See also == | == See also == | ||
* [http://myfreefilehosting.com/f/c28a01c6bb_0.1MB Moving platform] - an example map for the above tutorial. | * [http://myfreefilehosting.com/f/c28a01c6bb_0.1MB Moving platform] - an example map for the above tutorial. | ||
[[Category:Level Design Tutorials]] | |||
Revision as of 13:20, 18 February 2008
In this tutorial you will learn how to create a moving platform.
Setting up the model
You will need one from these models
- This one is bigger:
models/props/light_rail_platform.mdl. - This one is smaller
models/props/light_rail_platform_02.mdl. - After you have decided witch one is better for you, name it
platform_model. - Set its parent to
platform_func, which we'll create next.
Creating functions
Create brush with dimensions of chosen platform. It’s not necessary, but it will surely work. Tie it to func_tracktrain entity by pressing Ctrl-T, and set its variables as follows:
Property Name Value Change angles this is up to you, I’m using: never (fixed orientation)Change velocity too, it’s your choice, but: ease in/ease outFirst stop target P1_S1_MInitial speed 100Max speed 10 000Name platform_func
And, you may set sounds:
Property Name Value Start sound Doors.Move12Stop sound Doors.FullClose12
Path tracking
Our platform is using the path_track entities to specify its movement course, so we have to add these now. You can see the architecture we will use.
Create a set of path_tracks, configuring them as follows:
Property Name Value Name P1_S1_MNew train speed 30Next stop target P1_S1_O
Property Name Value Name P1_S1_ONew train speed 200Next stop target P1_S2_I
Property Name Value Name P1_S2_INew train speed 30Next stop target P1_S2_M
Property Name Value Name P1_S2_MNew train speed 30Next stop target P1_S2_O
Property Name Value Name P1_S2_ONew train speed 200Next stop target P1_S1_I
Place them as necessary but make sure they are linked, as shown by a yellow line in Hammer's viewports.
Final touches
Now you have a working platform, so we can add a few models to support it. That oval-shaped object is used on walls, so it's easy to add to your map. The second model looks better, you may even add that stand under it.
- Moving platform mdl 01.jpg
- Moving platform mdl 02.jpg
- Moving platform mdl 03.jpg
See also
- Moving platform - an example map for the above tutorial.