Getting Errors importing a Terrain into Atlas
by Emil Diego · in Torque Game Engine Advanced · 10/02/2006 (10:37 am) · 4 replies
I have created a height map using l3dt. The dimensions of the map are 1025 x 1025 pixels. Right now I am having two problems importing the terrain.
1. Whenever I use atlasOldGenerateChunkFileFromRaw16 to create the chunk file I get 2 error messages in the output.
AtlasOldActivationHeightfield::generateNodeData - Max exceeded! May have paging issues!
AtlasOldActivationHeightfield::generateNodeData - Min exceeded! May have paging issues!
At first I was using a highter value for the tree depth, but I reduced it to 2 and that seemed to generate fewer error messages. Here is the statement that I executed.
atlasOldGenerateChunkFileFromRaw16("terrain_water_demo/data/terrains/terr5.raw", 1024, 2.0, 1.0/256.0, "terrain_water_demo/data/terrains/terr5.chu", 2.0, 2);
and here is the full output from the log
==>atlasOldGenerateChunkFileFromRaw16("terrain_water_demo/data/terrains/terr5.raw", 1024, 2.0, 1.0/256.0, "terrain_water_demo/data/terrains/terr5.chu", 2.0, 2);
Generating chunked geometry (depth=2, baseMaxError=2.000000)
o Calculating activation levels...
- done.
o Propagating activation levels...
- done.
o Writing file header...
- done.
o Generating empty TOC...
- done.
o Generating meshes...
AtlasOldActivationHeightfield::generateNodeData - Max exceeded! May have paging issues!
AtlasOldActivationHeightfield::generateNodeData - Min exceeded! May have paging issues!
- done.
=== Chunk Statistics ===\
\===== Level Count Avg. Size
0 4 7746.250000
1 1 30432.000000
========================================
chunks: 5
input verts: 1048576
output verts: 9783
avg verts/chunk: 1957
output bytes: 213
bytes/input vert: 0.00
bytes/output vert: 0.02
real triangles: 61417
2. My second questions, which I am certain is related to the first is whenver I use the importOldAtlasCHU command to convert the chu into a atlas file I get the following exception
Fatal: (c:\source\tse\engine\atlas\resource\atlasgeomchunk.cpp @ 767) AtlasGeomChunk::generateCollision - bad child quadtree node min/max! (negative a)
Here is the full log output for the command.
==>importOldAtlasCHU("terrain_water_demo/data/terrains/terr5.chu", "terrain_water_demo/data/terrains/terr5.atlas");
importOldAtlasCHU - opened 'terrain_water_demo/data/terrains/terr5.chu' for conversion.
AtlasDeferredFile::ensureStreamWritable - switching file into writable mode... This may cause a crash if you have other copies of Torque accessing it!
importOldAtlasCHU - created new Atlas file 'terrain_water_demo/data/terrains/terr5.atlas'
importOldAtlasCHU - Atlas file initialized, converting...
importOldAtlasCHU - Headers read, remapping chunks...
importOldAtlasCHU - Importing geometry chunks...
importOldAtlasCHU - level 1 chunks...
Fatal: (c:\source\tse\engine\atlas\resource\atlasgeomchunk.cpp @ 767) AtlasGeomChunk::generateCollision - bad child quadtree node min/max! (negative a)
DirectInput deactivated.
Activating DirectInput...
Error, a DecalManager (1b4c3b8) isn't properly out of the bins!
Error, a WaterBlock (1b586e0) isn't properly out of the bins!
Error, a Sky (2d5d7a8) isn't properly out of the bins!
Error, a AtlasInstance2 (2d5eee0) isn't properly out of the bins!
Error, a Camera (2fe5554) isn't properly out of the bins!
Error, a AtlasInstance2 (2a2b870) isn't properly out of the bins!
Error, a Sky (2c216e8) isn't properly out of the bins!
Error, a WaterBlock (2c15e3c) isn't properly out of the bins!
Error, a Camera (1b4e578) isn't properly out of the bins!
Error, a Camera (1b4e578) isn't properly out of the bins!
Error, a Camera (1b4e578) isn't properly out of the bins!
Error, a Camera (1b4e578) isn't properly out of the bins!
Anyone have any ideas what I am doing wrong? Any help is appreciated.
1. Whenever I use atlasOldGenerateChunkFileFromRaw16 to create the chunk file I get 2 error messages in the output.
AtlasOldActivationHeightfield::generateNodeData - Max exceeded! May have paging issues!
AtlasOldActivationHeightfield::generateNodeData - Min exceeded! May have paging issues!
At first I was using a highter value for the tree depth, but I reduced it to 2 and that seemed to generate fewer error messages. Here is the statement that I executed.
atlasOldGenerateChunkFileFromRaw16("terrain_water_demo/data/terrains/terr5.raw", 1024, 2.0, 1.0/256.0, "terrain_water_demo/data/terrains/terr5.chu", 2.0, 2);
and here is the full output from the log
==>atlasOldGenerateChunkFileFromRaw16("terrain_water_demo/data/terrains/terr5.raw", 1024, 2.0, 1.0/256.0, "terrain_water_demo/data/terrains/terr5.chu", 2.0, 2);
Generating chunked geometry (depth=2, baseMaxError=2.000000)
o Calculating activation levels...
- done.
o Propagating activation levels...
- done.
o Writing file header...
- done.
o Generating empty TOC...
- done.
o Generating meshes...
AtlasOldActivationHeightfield::generateNodeData - Max exceeded! May have paging issues!
AtlasOldActivationHeightfield::generateNodeData - Min exceeded! May have paging issues!
- done.
=== Chunk Statistics ===\
\===== Level Count Avg. Size
0 4 7746.250000
1 1 30432.000000
========================================
chunks: 5
input verts: 1048576
output verts: 9783
avg verts/chunk: 1957
output bytes: 213
bytes/input vert: 0.00
bytes/output vert: 0.02
real triangles: 61417
2. My second questions, which I am certain is related to the first is whenver I use the importOldAtlasCHU command to convert the chu into a atlas file I get the following exception
Fatal: (c:\source\tse\engine\atlas\resource\atlasgeomchunk.cpp @ 767) AtlasGeomChunk::generateCollision - bad child quadtree node min/max! (negative a)
Here is the full log output for the command.
==>importOldAtlasCHU("terrain_water_demo/data/terrains/terr5.chu", "terrain_water_demo/data/terrains/terr5.atlas");
importOldAtlasCHU - opened 'terrain_water_demo/data/terrains/terr5.chu' for conversion.
AtlasDeferredFile::ensureStreamWritable - switching file into writable mode... This may cause a crash if you have other copies of Torque accessing it!
importOldAtlasCHU - created new Atlas file 'terrain_water_demo/data/terrains/terr5.atlas'
importOldAtlasCHU - Atlas file initialized, converting...
importOldAtlasCHU - Headers read, remapping chunks...
importOldAtlasCHU - Importing geometry chunks...
importOldAtlasCHU - level 1 chunks...
Fatal: (c:\source\tse\engine\atlas\resource\atlasgeomchunk.cpp @ 767) AtlasGeomChunk::generateCollision - bad child quadtree node min/max! (negative a)
DirectInput deactivated.
Activating DirectInput...
Error, a DecalManager (1b4c3b8) isn't properly out of the bins!
Error, a WaterBlock (1b586e0) isn't properly out of the bins!
Error, a Sky (2d5d7a8) isn't properly out of the bins!
Error, a AtlasInstance2 (2d5eee0) isn't properly out of the bins!
Error, a Camera (2fe5554) isn't properly out of the bins!
Error, a AtlasInstance2 (2a2b870) isn't properly out of the bins!
Error, a Sky (2c216e8) isn't properly out of the bins!
Error, a WaterBlock (2c15e3c) isn't properly out of the bins!
Error, a Camera (1b4e578) isn't properly out of the bins!
Error, a Camera (1b4e578) isn't properly out of the bins!
Error, a Camera (1b4e578) isn't properly out of the bins!
Error, a Camera (1b4e578) isn't properly out of the bins!
Anyone have any ideas what I am doing wrong? Any help is appreciated.
#2
oh and yeah, use the Sept. 22nd HEAD build, it fixes some atlas stuff...
10/02/2006 (3:21 pm)
For a 1024 terrain I have been using .5 or 1.0 for error level, and 4 or 5 for tree depth, it always seems to give me those warnings no matter what I set it to, but those seem to work. also, for the 1.0/256.0 I usually replace that with the info from the l3dt header which is usually like 0.002722 or something similar.oh and yeah, use the Sept. 22nd HEAD build, it fixes some atlas stuff...
#3
Thanks again for the help.
10/03/2006 (6:18 am)
Thanks for the info. I was able to get my terrain imported into the game. I was still getting the same error when creating the chunk file from the raw data. How serious is that error and how do I go about making it dissapear?Thanks again for the help.
#4
10/03/2006 (6:42 am)
I've been getting that error since Atlas1 and so have many other people it seems. You can reduce it by doing as the message suggests, but I think your geometry or LOD gets very blocky (if I recall correctly from way back when). The error causes no harm as far as I can see. I guess if your terrain starts paging in a peculiar way you should worry about it. Otherwise not. 
Torque Owner Dennis Trevillyan
WatreGames