Game Development Community

TGEA 1.7 BUG - exportAtlasFromLegacyTER

by J.C. Smith · in Torque Game Engine Advanced · 05/27/2008 (6:48 am) · 3 replies

I attempted to get the exportAtlasFromLegacyTER function working today. I changed the mapformat to 5 from 4, to get this to work. It should be noted that the atlasExportLegacy command was tried first but it locked up each time I tried it. export AtlasFromLegacyTER did work almost flawlessly, except that the terrain was flipped in Atlas. It was flipped either horizontally or vertically. For some designs that wouldn't matter but in my case I was making a terrain to line up to the contours of a race track, so this flip made things line up incorrectly.

Glad to see a converter though, as personally I enjoy the performance of atlas. In a case like this though where I was using a polysoup track it was easie to design the terrain in legacy as I could do it in realtime in-game and then try exporting.
NextNext Thread
PrevPrevious Thread
More from Torque Game Engine Advanced


Torque 3D Owner Mark Dynna
#1
05/27/2008 (1:55 pm)
You know, that would be an almost ideal workflow: create the terrain as Legacy, edit and texture it to your liking and when it's complete, convert to Atlas for final shipping. Does it export as a Blended or Unique Atlas terrain?

Torque 3D Owner J.C. Smith
#2
05/27/2008 (2:09 pm)
Blended. There are some configuration options for it too. You can find the functions in atlas/editor/atlasconvertlegacy.cpp. I only noticed it when merging some stuff between builds so figured I'd try it out. Works very well, creates a nice blended atlas. Only problem is that the bitmap needs to be flipped before it generates the heightmap/opacity maps for it to display the same as the Legacy terrain, but unfortunately it doesn't spit out a bitmap file or anything so can't do this manually. Probably would be a pretty easy fix, and something that was just overlooked when it was created. When I first exported it I was surprised to see a small and efficient atlas file so easily, it took me a little headscratching wondering why my track wasn't lining up, and then after comparing some shots and angles I realized that it was a flipped bitmap. So instead of reading things from left to right for example when doing your grid it is reading them from right to left.

Torque 3D Owner Mark Dynna
#3
05/27/2008 (2:20 pm)
Cool stuff JC, I'll have to keep that function in mind.