mirror of
https://github.com/ZDoom/raze-gles.git
synced 2024-11-11 07:11:39 +00:00
spriteclip.txt: refer to _clipshape0.map instead of _clipshape_.map.
git-svn-id: https://svn.eduke32.com/eduke32@3538 1a8010ca-5511-0410-912e-c29ae57300e0
This commit is contained in:
parent
deeb6306a9
commit
1252e0d8e5
1 changed files with 2 additions and 2 deletions
|
@ -16,7 +16,7 @@ loading a single map with all sectors/walls/sprites thrown together.
|
|||
|
||||
* To associate a picnum with a bunch of sectors, place a sprite with that picnum in
|
||||
some inner sector of the lot. At the end stage of editing, align the sprite so that
|
||||
the model matches the sectors well. See samples/_clipshape_.map for examples.
|
||||
the model matches the sectors well. See samples/_clipshape0.map for examples.
|
||||
|
||||
* A picnum may be associated with many "layers" (called "indices" in the code) of
|
||||
sectorwork. This serves two purposes: one is to enable more complex shapes than
|
||||
|
@ -35,7 +35,7 @@ loading a single map with all sectors/walls/sprites thrown together.
|
|||
of any wall of an inner sector to the picnums to be aliased to layer containing the wall.
|
||||
If only one of them is set, it is taken as a picnum, otherwise as a both-sided inclusive
|
||||
range, the order doesn't matter. The pigcop tank is present as an example in
|
||||
samples/_clipshape_.map. If a picnum has multiple layers, it is advisable to set the same
|
||||
samples/_clipshape0.map. If a picnum has multiple layers, it is advisable to set the same
|
||||
lotags/hitags for each layer. Note that you do not need to set tags unless you intend to
|
||||
have more than one picnum to share a clipping shape.
|
||||
|
||||
|
|
Loading…
Reference in a new issue