Game Development Community

Shoreline Problem

by Fredrik Sparf · in Torque Game Engine · 04/22/2004 (12:03 am) · 7 replies

My water has bad shorelines. I don't know if my terrain file is bugged or if the terrain and water settings in my mission file mismatch. If I raise my water high enough all my shorelines disapper (as they should). But they mismatch with the terrain I have. There are shorelines where they shouldn't be and no shorelines where they should be. So there is something which affects the lines but it is not the visible land.

Are there some other files than my mission file and my terrain file that shouldn't be write protected?

Anyone else who has this problem?

Thanks in advance!

/Fredrik

#1
04/22/2004 (12:49 am)
I have this when I edit a map (of course). But when i save/relight everything it's fine.

So try to resave everything or first of all delete the *.ml file to force a relight of the hole scene.
#2
04/22/2004 (1:18 am)
I have tried that but sadly it doesn't work.
If I pull the water high enough, I can see all shorelines disappear. So maybe it's the terrain file which is corrupt...
#3
04/22/2004 (6:17 am)
Is your terrainblock size set at anything other than 8? If it is, shorelines get funked up. I found that out the hard way. If this is your problem as you raise the water level up and hit the shore the "blocks" of the water block will disapear in square chunks.

Apparently this is a bug and the only way to fix it is to set your block size back to 8 which will foo up your current map. Once again, something I found out the hard way :)

Hope it helps.
#4
04/22/2004 (8:26 am)
That was the evil demon in the mission file. That little bastard was set to "6".
Well, one more found out the hard way.

Thank you for the swift answer.

/Fredrik
#5
04/22/2004 (9:25 am)
I think Desmond Fletcher had submitted a fix for the terrainblock/waterblock problem, IIRC.
#6
04/22/2004 (12:46 pm)
Thanks for the tip.
I found it and I will look into it tomorrow.

3166

/Fredrik
#7
04/23/2004 (2:48 am)
It's not working for me... :(

That fix is over 2 years old, so it's probably outdated.

/Fredrik