How big of a RAW has anyone completed?

#1 Around 200 megabytes.

#2 The treedepth makes a massive difference to the file size. I've had huge multi-megabyte files for 1024 x 1024 terrains. If you're having probs you can reduce the depth and see if it helps.

#3 And what if I'm not even getting that far. We have a 16,385x16,385 file that is over 500MB and when I try to convert it I get a memory error and TSE crashes. Can it even handle something this big?

#4 Which parameters do you use for GenerateChunkFromRAW16?
You probably also mean your terrain is 16385x16385.

#5 Yes I do mean 16,385. Last time I tried I used:
Square Size = 2.0,
vertScale = 1/256 (however I just learned from our artist that the scale is much larger than +/- 128m)
Error metric = 2.0
Tree Depth = 3

I don't even think it is getting to the point where it *tries* to convert the file, it seems to crash as soon as it tries to load it.

#6 Try to increase your error metrics : try 3.0 to 6.0

And Of course (if it crash when it try to load it), increase your tree depth. (try 6 +)

#7 I tried running it with an error metric of 10.0 and a Tree Depth of 8 and every time I get this error:
"Torque Memory Error"
"Error allocating memory. Shutting down."

Vincent, didn't you write that HTC utility? I noticed you mentioned something about increasing TSE's memory (or was it file?) limit to handle up to 4GB. Am I hitting that limit here?

#8 Ok, I ran it in the VS debugger and tracked it down. In platformMemory.cpp there is a call dRealMalloc (this probably gets called a billion times) but the call to it made from within the generateChunkFile... console function returns a NULL pointer. After that it throws the Memory Allocation Error. I think the file is too big, and I don't have enough memory.

#9

Quote:The treedepth makes a massive difference to the file size. I've had huge multi-megabyte files for 1024 x 1024 terrains. If you're having probs you can reduce the depth and see if it helps.

Reduce the Tree Depth of the function call or reduce the tree depth of the image itself? Is this something that needs to be done by editing the RAW image?

#10 I Work mainly with 8192x8192 files, because TSE can't handle JPEG more than 8192x8192 pictures. for this terrain size I use an error metrics of 6.0 and a tree depth of 7.
A solution to your problem could be to take a pixel over two for your terrain to make it 8193x8193 and to generate with Em : 6.0 and Td : 7. and increase square size to 4.
I Had the same problem with platformMemory.cpp but it was the my createJpeg function which crashes TSE.

#11 Ok, I'm making some progress. We have an 8193 RAW file that actually starts to convert. If I'm getting lots of Min/Max exceeded warnings and lerpedHeight Overflow errors, what should I be adjusting?

#12 Mark, check out my post at http://www.garagegames.com/mg/forums/result.thread.php?qt=45598 about using multiple Atlas terrain chunks in a single mission. That might make your situation simpler if you can chop your terrain into 4 or even 16 separate pieces.

By the way I didn't figure this out, someone else graciously pointed it out to me.

Tim

#13 Just an FYI note here. I was pushing TSE to see how big I could make the terrain and I recently converted a 2048x2048 heightmap using a Square Size of 8, and vertScale of 1/32. It would not convert to CHU with a Tree Depth less than 10 (!), and then it created a 482MB CHU file. I tried loading this up in TSE and it crashed.

#14 I've tested with up to 8192 square raw files. For that I don't think you'd want a tree depth of more than 8 or so - with a tree depth of 10 you not only have over a million chunks, but each one is for only a tiny, tiny area of terrain - very inefficient!

#15 Our TQT for GDC was over 4 gigs in size. That was a long week.