TGEA 1.7.1 Bug:Mega terrain import backwards
by Bill Vee · in Torque Game Engine Advanced · 09/01/2008 (6:43 pm) · 4 replies
I was doing some research on the pros and cons on the 3 different terrains and I discovered that importing a hightmap into a mega terrain the terrain was backwards from East to west but not north to south.
This is an image with the atlas terrain on the right and the mega terrain on the left.
Also when I tried to import a legacy terrain the terrain appears to be truncated.
I think this may be due to the source map was 512 X 512 and the terrain appears to have only imported 256 X 256 of the image.
The GG website is being difficult with me right now so I can't find the info relating to the correct image size for legacy terrains.
This is an image with the atlas terrain on the right and the mega terrain on the left.
Also when I tried to import a legacy terrain the terrain appears to be truncated.
I think this may be due to the source map was 512 X 512 and the terrain appears to have only imported 256 X 256 of the image.
The GG website is being difficult with me right now so I can't find the info relating to the correct image size for legacy terrains.
#2
I am aware of how the mega terrain works for the most part.
My source height map for the atlas and the mega was 512x512.
The odd east west flipping appears to be an error in the import code.
It is reading from north to south correctly but appears to be reading east and west backwards.
I think I just about have it.
I will post a fix if I get if I can figured it out.
09/02/2008 (4:38 am)
Thanks Tom, for the legacy info.I am aware of how the mega terrain works for the most part.
My source height map for the atlas and the mega was 512x512.
The odd east west flipping appears to be an error in the import code.
It is reading from north to south correctly but appears to be reading east and west backwards.
I think I just about have it.
I will post a fix if I get if I can figured it out.
#3
Our current (non-code) fix for this is to flip our images so that they import the correct version. Has a code fix been released for this? If not, we don't have time to wait. We will proceed with development with our heightmap solution.
04/16/2009 (7:54 am)
I can confirm this bug. We just discovered it also. Our heightmaps are the correct size 512x512 .PNG files and the terrain is importing backwards on the East-West plane.Our current (non-code) fix for this is to flip our images so that they import the correct version. Has a code fix been released for this? If not, we don't have time to wait. We will proceed with development with our heightmap solution.
Associate Tom Spilman
Sickhead Games