Not saying this is happening all of the time, but it's the most frequent error I see.
Same here, in fact I got this 28 times in one scene. LOL It happened while UV-Mapping an obj. I'll try a different object later and see if it happens again.
This is a fairly generic error at this point. I've found it usually indicates memory issues. Check the Task Manager and see if the tgd.exe process is using anywhere near 2GB of total RAM. If so you're likely running into memory problems. Remember that total memory use must be considered, including Virtual Memory (Vista has a "total commit size" that I think may be accurate). Note in particular that rendering with multiple cores increases memory use over a single thread.
If you are encountering these errors while not rendering, try pausing the 3D preview. If it still occurs it's definitely something to report in more detail.
- Oshyan
Thanks, I don't think it's a memory issue as I am only using a default scene to texture a object. Nothing else in the scene. I'll report back later if I keep having problems.
Sounds like it's something new then. Please do post with some more detail when you get a chance.
Thanks. :)
- Oshyan
Also getting consistent errors when rendering anything with GI at 2 or higher over four cores. I assume this has also to do with memory? With GI at 1 I can render large formats (I've tried up to 2400x1800) over four cores without a glitch...
@Oshyan - So you know, I'm running XP Professional with the /3GB switch. I have plenty of RAM and it was more like at about 1.5G use of Virtual Memory. I'll keep my eyes open.
I know in some of my previous TGDs, I cannot open the TGD and it seems to be connected to objects inside them.
Quote from: Oshyan on April 28, 2008, 11:58:10 PM
This is a fairly generic error at this point. I've found it usually indicates memory issues. Check the Task Manager and see if the tgd.exe process is using anywhere near 2GB of total RAM. If so you're likely running into memory problems. Remember that total memory use must be considered, including Virtual Memory (Vista has a "total commit size" that I think may be accurate). Note in particular that rendering with multiple cores increases memory use over a single thread.
If you are encountering these errors while not rendering, try pausing the 3D preview. If it still occurs it's definitely something to report in more detail.
- Oshyan
Getting this myself as well: 8 GB, quad.
When I don't get this it is rendering faster- especially the preview.
monks
I also get it. It happens after a little while.
Quote from: monks on April 29, 2008, 11:15:32 AMGetting this myself as well: 8 GB, quad.
When I don't get this it is rendering faster- especially the preview.
monks
The preview window don't render any faster with me either, but the normal render is a lot faster.
I also have gotten this a few times. Usually after doing a bunch of cropped test renders it will happen eventually. I just close TG2 and reopen and it goes back to working just fine. Not really sure what would be causing it however, certainly shouldn't be maxing out memory as I am not working with any objects currently.
Somewhat hard to give more details at this point as it is not (for me) a reproducible bug, just something that happens every 10 test renders or so.
I've had it a couple of times as well. Closing and re-starting solves it every time. So far non repeatable so can't be of much help tracing the cause.
This problem appears to be related to repeated restarts of the 3D preview when changing settings. There may be a memory leak involved. We're looking into it further.
- Oshyan
yep i have this problem as well i also get an error when i put a jpeg image through a imagemap shader
I'm getting it as a memory error.
Sooner or later, TG2 hits the 2GB wall, even on simple scenes and the error messages start coming in.
Quote from: Oshyan on April 30, 2008, 01:27:39 AM
This problem appears to be related to repeated restarts of the 3D preview when changing settings. There may be a memory leak involved. We're looking into it further.
I can confirm that. I can pump up memory usage simply by moving around in the preview. ;D And I can do this up to the point were any further movement causes errors to be thrown.
There is a memory leak that we're working on right now. Hopefully that will resolve these types of errors for simpler scenes.
- Oshyan
Quote from: Oshyan on April 30, 2008, 10:40:59 PM
There is a memory leak that we're working on right now. Hopefully that will resolve these types of errors for simpler scenes.
- Oshyan
So I guess we can sing the song "Theres a hole in your
bucket dear Liza" ;D
Hehe, yes that would be very appropriate. ;)
- Oshyan
not that its goin to help but...
I get it as well. lol
but personally its worth the use of more that one core to render which makes rendering much faster. lol
and those controls for the cam'. wonderful!
and being able to drag out and how you want on the croping of rendering specific areas. :D
so there. made it not all negative. :D
I have had this too and can reproduce the sequence consistently, altough the occurence is intermittent (but frequent, 60-80%).
1: Start TG
2: Add an RGB imagemap (default projection is Through camera) - Error
- (optional) Save file, restart TG or revert to saved, image loads OK and errors in following steps usually stop.
3: Change projection to Plany Y and set dimensions, image displays.
4: Change projection back to Through camera - Error
- repeating 3 and 4 results in consistent behaviour.
If adding the image map succeeds, changing projections doesn't generate an error
5: Create new document and repeat adding an image map - problem may or may not occur
- once the error occurs, points 3 and 4 above apply consistently
- once the error occurs, Full render is black and takes a few seconds.
- once the error occurs, saving the document and reverting to saved appears to fix the problem.
Memory usage with or without the error is around 100Mb RAM, 500Mb VM, 350 GDI
Test images were a 450x150 pixle JPEG and TIF.
Similar sequence looking at multi-threading.
1: Start TG
2: Set maximum threads to 1
3: Add an RGB imagemap (default projection is Through camera)
No errors, but display of image is intermittent.
And again:
1: Start TG
2: Add an RGB imagemap (default projection is Through camera) - If error occurs then proceed...
3: Set maximum threads to 1
4: Change projection to Plan Y and set dimensions, image displays.
5: Change projection back to Through camera - No error, image doesn't display
Hope this helps.
Another consistent error along a similar line
1: Create a surface shader
2: In the Fractal breakup section, create a new image map.
3: Reduce coverage - Error.
This is similar to the behaviour in the previous example in that saving the file and reverting to saved will fix things.
All I need to do is play with Terragen for about 10 minutes or so, and..... baddaboom. There it is. xD
I've had consistent memory errors no matter what. I think I've had maybe three good renders from the Alpha. Thankfully, I have the last version still available. But, I think Matt said something about the next version shoring up some of these memory errors...whew.