There doesn't seem to be a way to set the height (or rotation) of terrain objects in the editor. Normal hotkeys don't work or work very poorly, requiring direct XML editing.
- Registered User
Member for 9 years, 4 months, and 1 day
Last active Wed, Dec, 28 2011 08:26:51
- 0 Followers
- 18 Total Posts
- 0 Thanks
Apr 30, 2010Sholdak posted a message on [Bug / Missing Feature, Terrain Objects] Object HeightPosted in: Galaxy Editor Bugs and Feedback
Apr 30, 2010Posted in: Galaxy Editor Bugs and Feedback
When you open up a footprint with an existing pathing map, the pathing map is not displayed and is reset to default values. Saving that footprint resets the pathing map to this default. Therefore every time you edit this value, you have to recreate the pathing layer from scratch.
Apr 29, 2010Sholdak posted a message on [Data,Terrain] Bridges - A Terrain Objects and Footprints GuidePosted in: Tutorials
Terrain objects are objects that modify the height terrain via a model. They can be used whenever you want units to walk over a model. This includes bridges, stairs, etc. This can be used to create some very interesting terrain.
In order to create a Terrain Object, go to the Terrain Objects data type, hit Add Object, change Based On to "CTerrainObject" and click ok. Each object has the following important properties:
- Footprint - specifies the pathing map of the object, and placement behaviors of the object. (More on this later)
- Model - specifies the model
- Number of Cells Across (width) / Number of Cells Down (height) - how many terrain cells are hidden by this object. Cells that are hidden can be restored via the terrain editor.
- Radius - Space taken up by this object. 2 terrain objects cannot exist within each other's radii. Set this to 0 to be able to stack terrain objects.
Fields for use in Editor:
- Texture Sets - set this to the texture set you are using so that the object shows up in the Terrain Editor.
Further investigation required:
- Cliff Set - Not clear how objects interact with cliffs. Perhaps though height codes?
- Height Codes - Binding points for terrain objects? Don't seem to have any effect from testing. Perhaps requires special models?
If you actually place the object, you'll notice that the height is defaulted to 0. I haven't be able to figure out a way to set this height via the editor (if someone does, please let me know). For now, the only way to change the height is to open the map in an MPQ editor, open t3Terrain.xml, and find the entries that look like:
<cliffDoodadList num="4"> <cliffDoodad name="Bridge" pos="119.000000 10.000000 4.000000 " rot="0"/> <cliffDoodad name="Bridge" pos="155.000000 10.000000 4.000000 " rot="0"/> <cliffDoodad name="Bridge" pos="103.000000 65.000000 4.000000 " rot="0"/> <cliffDoodad name="Bridge" pos="31.000000 91.000000 4.000000 " rot="0"/> </cliffDoodadList>
Set the last value of pos to the desired height. Note: Most cliffs sets have heights of (-8,0,2,4).
Now that we have an object that modifies the terrain height, it's time to make it pathable via a footprint (to be continued...).
- To post a comment, please login or register a new account.