New Alpha Consistant Error

[rcallicotte]

Not saying this is happening all of the time, but it's the most frequent error I see.

[joshbakr]

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.

[Oshyan]

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

[joshbakr]

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. 

[Oshyan]

Sounds like it's something new then. Please do post with some more detail when you get a chance.

Thanks.

- Oshyan

[bertrand]

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...

[rcallicotte]

@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.

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

[monks]

Getting this myself as well: 8 GB,  quad.
When I don't get this it is rendering faster- especially the preview.

monks

[sjefen]

I also get it. It happens after a little while.

Getting 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.

[RArcher]

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.

[Mr_Lamppost]

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.

[Oshyan]

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

[lightning]

yep i have this problem as well i also get an error when i put a jpeg image through a imagemap shader

[nikita]

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.

[nikita]

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.  And I can do this up to the point were any further movement causes errors to be thrown.