Global Warming?

[Guest pfunkmusik]

 

I don't get it. I finally managed to get the sea tiles to work in the TE and now I can't get them to go away. Obviously, I've got some elevation issues. What do I need to adjust to get them corrected?

 

Here is the Tile Object List. Someone suggested putting a 'Void' in there to keep the numbers correct. Is that what's getting me?

 

pfunk

 

[VVoid]

Water=0

UseAutoPlacement=0

CheckAltitude=0

MinAltitude=0

MaxAltitude=0

CheckCity=0

MinCityDistance=0

MaxCityDistance=0

CheckSlope=0

MinSlope=0

MaxSlope=0

Priority=0

RandomFactor=100

GroupingFactor=0

ExclusionRegion=0

ExcludeMaxX=0

ExcludeMinX=0

ExcludeMaxY=0

ExcludeMinY=0

 

[sSea]

Water=1

UseAutoPlacement=1

CheckAltitude=1

MinAltitude=0

MaxAltitude=0

CheckCity=0

MinCityDistance=0

MaxCityDistance=0

CheckSlope=0

MinSlope=0

MaxSlope=0

Priority=0

RandomFactor=100

GroupingFactor=0

ExclusionRegion=1

ExcludeMaxX=0

ExcludeMinX=0

ExcludeMaxY=0

ExcludeMinY=0

 

[RGrass]

Water=0

UseAutoPlacement=1

CheckAltitude=1

MinAltitude=1

MaxAltitude=800

CheckCity=1

MinCityDistance=10

MaxCityDistance=99999999

CheckSlope=1

MinSlope=15

MaxSlope=90

Priority=1

RandomFactor=30

GroupingFactor=0

ExclusionRegion=0

ExcludeMaxX=0

ExcludeMinX=0

ExcludeMaxY=0

ExcludeMinY=0

 

[GField]

Water=0

UseAutoPlacement=1

CheckAltitude=1

MinAltitude=1

MaxAltitude=600

CheckCity=1

MinCityDistance=0

MaxCityDistance=100

CheckSlope=1

MinSlope=0

MaxSlope=10

Priority=2

RandomFactor=75

GroupingFactor=60

ExclusionRegion=0

ExcludeMaxX=0

ExcludeMinX=0

ExcludeMaxY=0

ExcludeMinY=0

 

[JForest]

Water=0

UseAutoPlacement=1

CheckAltitude=1

MinAltitude=100

MaxAltitude=1500

CheckCity=0

MinCityDistance=0

MaxCityDistance=0

CheckSlope=1

MinSlope=0

MaxSlope=10

Priority=1

RandomFactor=100

GroupingFactor=100

ExclusionRegion=1

ExcludeMaxX=325

ExcludeMinX=0

ExcludeMaxY=325

ExcludeMinY=0

 

[ASnow]

Water=0

UseAutoPlacement=1

CheckAltitude=1

MinAltitude=1200

MaxAltitude=9999

CheckCity=1

MinCityDistance=10

MaxCityDistance=9999999

CheckSlope=0

MinSlope=0

MaxSlope=0

Priority=3

RandomFactor=100

GroupingFactor=0

ExclusionRegion=1

ExcludeMaxX=325

ExcludeMinX=0

ExcludeMaxY=325

ExcludeMinY=0

 

[CCity]

Water=0

UseAutoPlacement=0

CheckAltitude=0

MinAltitude=0

MaxAltitude=0

CheckCity=0

MinCityDistance=0

MaxCityDistance=0

CheckSlope=0

MinSlope=0

MaxSlope=0

Priority=0

RandomFactor=100

GroupingFactor=0

ExclusionRegion=0

ExcludeMaxX=0

ExcludeMinX=0

ExcludeMaxY=0

ExcludeMinY=0

 

[MMarker]

Water=0

UseAutoPlacement=0

CheckAltitude=0

MinAltitude=0

MaxAltitude=0

CheckCity=0

MinCityDistance=0

MaxCityDistance=0

CheckSlope=0

MinSlope=0

MaxSlope=0

Priority=0

RandomFactor=100

GroupingFactor=0

ExclusionRegion=0

ExcludeMaxX=0

ExcludeMinX=0

ExcludeMaxY=0

ExcludeMinY=0

 

[NMarker2]

Water=0

UseAutoPlacement=0

CheckAltitude=0

MinAltitude=0

MaxAltitude=0

CheckCity=0

MinCityDistance=0

MaxCityDistance=0

CheckSlope=0

MinSlope=0

MaxSlope=0

Priority=0

RandomFactor=100

GroupingFactor=0

ExclusionRegion=0

ExcludeMaxX=0

ExcludeMinX=0

ExcludeMaxY=0

ExcludeMinY=0

[+Gepard]

I would set the Sea tiles min alt = 0 and the max alt = 1

[Lexx_Luthor]

mmm, I do sea with min and max both zero. I'm not sure it matters if the detail spans multiple meter ranges.

 

pf, do you have 3-way transitions with sea?

 

A number of things can cause what looks like sea tile contamination there. Another is lack of definition of tile placement. If TE can't find a defined tile it uses the first one listed, and that may be sea in your case. I'll take a closer look later tonight.

[+Brain32]

Lex is correct, tile types MUST be arranged by altitude you can not have gaps or the above happens, if you have for example:

"Grass" going from 1 to 400m; but the first next type...let's say "Farm" going from 600 to 800m you will have the gap...

[Lexx_Luthor]

Yeps. Another form of gap is slope gap...a gap in slope checking. TileA and TileB have the same altitude ranges, but TileA slopes 0-5 and TileB slopes 7-90. There is no tile checking for slope 6. I assume these are degrees. Any combination of slope and altitude gaps must be watched for.

 

Another tip: Priority=N with N=0,1,2,3... In case of equal definitions (not just altitude), the higher priority tile will be used instead of a lower priority tile. I see no limits on priority definition within the non-negative integers. Say TileA has Priority=N and TileB has Priority=(N+M), M=0,1,2,3.... If N+M > N, TileB will be used instead of TileA (ie...M > 0).

 

In English: You can have priority gaps, but they don't matter. Just what number is greater than another, no matter by how much.

 

Pf, it seems in the other thread you got this working right?

[Guest pfunkmusik]

Yeps. Another form of gap is slope gap...a gap in slope checking. TileA and TileB have the same altitude ranges, but TileA slopes 0-5 and TileB slopes 7-90. There is no tile checking for slope 6. I assume these are degrees. Any combination of slope and altitude gaps must be watched for.

 

Another tip: Priority=N with N=0,1,2,3... In case of equal definitions (not just altitude), the higher priority tile will be used instead of a lower priority tile. I see no limits on priority definition within the non-negative integers. Say TileA has Priority=N and TileB has Priority=(N+M), M=0,1,2,3.... If N+M > N, TileB will be used instead of TileA (ie...M > 0).

 

In English: You can have priority gaps, but they don't matter. Just what number is greater than another, no matter by how much.

 

Pf, it seems in the other thread you got this working right?

 

It, uhhh...(snicker), looks a little wierd. But, yeah.

 

pfunk