Game Development Community

Just trying to follow the terrain tut

by Jon Clark · in Torque 3D Professional · 05/12/2009 (1:26 pm) · 7 replies

Following the Import Terrain Height map tut in the documents using the files that are attach here (sampleterrain.zip)

Following the readings and about ready to import it throws a warning at me.

Import Terrain: The 'C:/Torque/Torque 3d 2009 Beta 1/My Project/game/art/sampleterrain/terrainFiles/Prarie/g' opacity map does not match the height map size

I just redid it again using all 512maps and came up with this/.

Import Terrain: The 'C:/Torque/Torque 3d 2009 Beta 1/My Project/game/art/sampleterrain/terrainFiles/Prarie/rockwallg' opacity map does not match the height map size

I don't see a *g map in any of the files that I DL from the sample.

About the author

Recent Threads


#1
05/12/2009 (2:04 pm)
I believe the opacity maps have already been listed as a none functioning bug. If you ignore that part, you can still load up the heightfield onto a terrain though, it just won't any terrain textures (well a warning texture instead).
#2
05/12/2009 (2:24 pm)
the opacity maps work fine, the pathname to them however must be *short* ive already posted this as a bug elsewhere

http://www.garagegames.com/community/forums/viewthread/91065

but it got burried in obscurity somewhere near page 7 i think i moved the 'game' folder to the root of the drive and it worked fine, the errors it gives are somewhat strange unless you run the debug build
#3
05/12/2009 (5:00 pm)
@Bloodknight - thanks for that, works lovely. I just moved the opacity maps to C:Torque and everything was fine. I'd actually seen your initial thread but hadn't understood it.
#4
05/25/2009 (1:32 am)
On Beta2, debug build (did not try in release build):

Short path did the trick. I wish the openFile dialog would use the last directory and not always reset to a default path.

But I get a lot of

c:\torque\torque 3d 2009 beta 2\engine\source\core\util\tvector.h(657) : Fatal - Vector<T>::operator[] - out of bounds array access!

after import the map.

Makes it hard to save the map ;) After importing the terrain again, the error does not occur.

#5
06/11/2009 (7:59 am)
Glad I found this thread! (That was frustrating!)
Is the long file path issue something that will be fixed? And when?

Strongly agree with Thomas:

"I wish the openFile dialog would use the last directory and not always reset to a default path."
#6
06/12/2009 (3:54 am)
Quote:
I wish the openFile dialog would use the last directory and not always reset to a default path.

I haven't tested it yet but I am told this is fixed in Beta 3 =)
#7
06/12/2009 (6:47 am)
That's nice to hear ... and the issue with the long file path?