While trying to export my heightfield to LWO for obj conversion by adding the "heightfield LWO export" node, TGTP3 crashes every time with this message:
"Runtime Error!
Program: D:\Terragen 2\tgd.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
So that's what I'm doing... ;D
Is LWO export supported by TP3, or is it still work in progress?
Hmm, while looking for the also exported .ter file, it seems the .lwo files did export, and are loadable in PoseRay.
Up to a certain point they are, but the file "x04y02" made Pose Ray crash. Besides that I have the files 'x00y00' to 'x07y02' and only y00, y01 and y02 of every x... So I guess I'm missing half of the heightfield anyways.
Can you look into this?
Could you post the TGD? I can debug it with Visual Studio. If you put the export node just after the heightfield generat and plug it into the shader then it should work fine.
That's what I did... Ohw well, have a look. It'll give a lot of errors for not finding hundreds of objects and textures, but just ignore those...
hm, worked fine. from x00y00 to x07y07 I've sent them in a zip to your email you should get it in about 15 minutes. If you want a direct link I can give you that too.
Got it, downloaded, thanx a lot!!!
So the question is, why didn't it work on my pc?
Are you using more than one core also what's your RAM and page file size?
2 cores at 2.3 GHz, 6 Gb RAM (but Win XP 32-bit, so only 3 GB actually used), and a total pagefile size of 13.8 GB divided over 3 Harddisks.
So the system should be able to handle it, right?
I'd reduce that paging if I were you. Using hard drives as random access memory can lend extra quick access storage but only as a final solution to RAM limits. As soon as a program starts using a page you'll notice a drop in performance as the data is read, only then will paging be effective. If you've got 13GB of pagefiles then all you're doing is allowing a larger chunk to be written off when those packets of data are being written. Try cutting your pagefile down to 2 or 3GB. I've set mine to 2GB with a maximum of 4 and I've never had any memory problems.
I'd also suggest getting vista, I know it sucks right now but it'll take advantage of your 6gb ram. Plus the service pack fixes loads of problems for most people. Just remember that it's processor dependant, what problems you have depends on the CPU you have.
Quote from: Mohawk20 on May 25, 2008, 10:20:18 AM
Hmm, while looking for the also exported .ter file, it seems the .lwo files did export, and are loadable in PoseRay.
Up to a certain point they are, but the file "x04y02" made Pose Ray crash. Besides that I have the files 'x00y00' to 'x07y02' and only y00, y01 and y02 of every x... So I guess I'm missing half of the heightfield anyways.
Can you look into this?
I've also tried to export a piece of terrain and then load it into poseray but it return an error saying the object has no vertices?
Do you guys know what I (probably) did wrong?
Thanks in advance.
Martin
TU, did you open the lwo or the lws?
Quote from: Mohawk20 on May 26, 2008, 04:09:28 AM
TU, did you open the lwo or the lws?
euhhh....lwo? didn't notice there's an lws...I have to doublecheck that when I'm back home.
Opening the LWS of only 6Kb would give a message like that...
The LWS has the information to load all the LWO's at ones, in stead of importing and merging one at a time (as is the only way to get them into poseray!)...
I found a copy of LightWave, so I tried to combine all the terrain pieces to reconstruct the complete heightfield, but it couldn't. It ran out of memory half way trough. I really need to upgrate to Xp 64...
Depending on the size of the area you're exporting I think you may be running into memory limitations. I'm not certain but I believe if you reduce the size in pixels in the source heightfield shader (it's the set of numbers above size in meters), it should reduce geometry complexity and potentially memory use.
- Oshyan