Page 1 of 2
a problem with raise\lower
Posted: Fri Mar 31, 2006 8:52 am
by Helvene
*feels dumb*
Well... it's the first time I'm trying to work with this feature, so I'm almost sure I'm doing something wrong.
This is how the raised terrain looks in toolset:
Everything seems to be fine, but when I test the same area in game it turns into:
And when I'm trying to put any feature on the raised terrain:
In game it looks like everything was put on floor height=0
Posted: Fri Mar 31, 2006 8:57 am
by acropole
it looks like you have wrong settings in the set file.
Code: Select all
[GENERAL]
Name=DX01
Type=SET
Version=V1.0
Interior=1
HasHeightTransition=1 <-------------- must be 1 if raise is possible
EnvMap=tde01__ref01
Transition=3 <---------- number of heights. 1 height = 100 3ds max units
DisplayName=56
Border=Wall
Default=Wall
Floor=Floor
Posted: Fri Mar 31, 2006 9:03 am
by Helvene
Primary rules used in the tileset
Code: Select all
[PRIMARY RULE0]
Placed=Floor
PlacedHeight=0
Adjacent=Floor
AdjacentHeight=0
Changed=Floor
ChangedHeight=0
[PRIMARY RULE1]
Placed=Floor
PlacedHeight=0
Adjacent=Floor
AdjacentHeight=1
Changed=Floor
ChangedHeight=1
[PRIMARY RULE2]
Placed=Floor
PlacedHeight=1
Adjacent=Floor
AdjacentHeight=0
Changed=Floor
ChangedHeight=0
[PRIMARY RULE3]
Placed=Floor
PlacedHeight=1
Adjacent=Floor
AdjacentHeight=1
Changed=Floor
ChangedHeight=1
Code: Select all
[GENERAL]
Name=wei01
Type=SET
Version=V1.0
Interior=1
HasHeightTransition=1
EnvMap=ttf01__ref01
Transition=0,75
DisplayName=-1
UnlocalizedName=Wooden Elven Interiors
Border=Wall
Default=Floor
Floor=Floor
Posted: Fri Mar 31, 2006 9:42 am
by acropole
I never use primary rules and everything works fine in my raise/lower tiles
Transition=0,75 <---- I don't know if you could use non integer values here...
and if you could, perhaps you should use a . instead of a ,
Posted: Fri Mar 31, 2006 10:02 am
by Helvene
Acropole wrote:Transition=0,75 <---- I don't know if you could use non integer values here...
Transition should be a float value, not integer.
And, one of DOA sets uses 2,75 as a transition value. So, it should work.
Acropole wrote:if you could, perhaps you should use a . instead of a ,
And then tileset crashes with a mistake "0.75 is not a valid floating point value"
Posted: Fri Mar 31, 2006 10:31 am
by acropole
it's strange that it works fine in the toolset and not in the game.
Perhaps you use raised tiles ? I mean that you don't need to create a tile with height=1 on every corner. The default floor square must be used for that.
Posted: Fri Mar 31, 2006 10:45 am
by Helvene
Acropole wrote:Perhaps you use raised tiles ?
I do not. As you've said, default floor tiles are used.
Posted: Fri Mar 31, 2006 11:04 am
by acropole
do you use cornerHeights, like this ?
Code: Select all
[TILE230]
Model=dx01_a58_01
WalkMesh=msb01
TopLeft=floor
TopLeftHeight=0
TopRight=lava
TopRightHeight=1 <----------------
BottomLeft=lava
BottomLeftHeight=1 <----------------
BottomRight=floor
BottomRightHeight=1 <----------------
Top=
Right=
Bottom=
Left=
or do you use 0,75 ? The right setting is always 1. It mean 1 raise. So no matter if your raise height is 0,75 or 1 or 2 or anything else, you should write 1 here.
Posted: Fri Mar 31, 2006 11:09 am
by Helvene
As an example
Code: Select all
[TILE39]
Model=wei01_c02_04
WalkMesh=msb01
TopLeft=Floor
TopLeftHeight=0
TopRight=Floor
TopRightHeight=0
BottomLeft=Floor
BottomLeftHeight=1
BottomRight=Floor
BottomRightHeight=1
Top=
Right=
Bottom=
Left=
MainLight1=0
MainLight2=0
SourceLight1=0
SourceLight2=0
AnimLoop1=0
AnimLoop2=0
AnimLoop3=0
Doors=0
Sounds=0
PathNode=A
Orientation=0
ImageMap2D=mi_wei01_a04_01
Posted: Fri Mar 31, 2006 11:16 am
by acropole
well, I don't understand where's the problem
