Ummm...yeah...What does this mean?

[darthvader]

I get this problem whenever I try to render this image above 1200 x 600 pixels. what does it mean? and is there any way to fix it like setting a higher GI setting? The image in photoshop was initially rendered at 1600x900 pixels.

[attachthumb=#]

[rcallicotte]

This is related to how much memory you're trying to use.

[Volker Harun]

It might be related to the scale of 16:9, as that LOTR-contest image of Moodflow and me had the same problem.
And it took 15 days on 8 cores to finish the render due to this issue.
Well, finally I went down to one core on a slower machine, which has been very reliable for years.

The is related to memory issues ... not enough memory maybe, maybe problems with the hardware itself.

I would like to see the following solution ... on an error, the core is going for another cluster to render, and another core is rerendering the problematic part (optionally).
This will cause longer rendertimes, but should - at some time - finish at least.

I am sorry, that I cannot give you any help right now ... the only approach is to render smaller, overlapping parts (like announced in 2007 by moodlflow) and to stitch them in photoshop.

Volker

[Tangled-Universe]

It might be related to the scale of 16:9, as that LOTR-contest image of Moodflow and me had the same problem.
And it took 15 days on 8 cores to finish the render due to this issue.
Well, finally I went down to one core on a slower machine, which has been very reliable for years.

The is related to memory issues ... not enough memory maybe, maybe problems with the hardware itself.

I would like to see the following solution ... on an error, the core is going for another cluster to render, and another core is rerendering the problematic part (optionally).
This will cause longer rendertimes, but should - at some time - finish at least.

I am sorry, that I cannot give you any help right now ... the only approach is to render smaller, overlapping parts (like announced in 2007 by moodlflow) and to stitch them in photoshop.

Volker

I don't think the amount of available RAM is an issue.
I get this same error with relatively simple scenes which don't consume much RAM.

At my computer most of the times the error occurs when using TG2 for a while or doing a series of node copy/paste and deleting.
I still haven't been able to convince PS about the instability of TG2 regarding this because it isn't reproducible and acts in a kind of random fashion.

Volker's suggestion is correct. However, even then the error might occur, so even smaller crops can be necessary.

Martin

[jo]

Hi Martin,

At my computer most of the times the error occurs when using TG2 for a while or doing a series of node copy/paste and deleting.
I still haven't been able to convince PS about the instability of TG2 regarding this because it isn't reproducible and acts in a kind of random fanshion.

We understand that there are problems, it's just that if they're random and hard to reproduce it makes it hard to find the problem and fix it. There is a lot of code effected and it's difficult to verify it all in all situations. I'm planning on giving some time over to look into these copy/paste problems in the next week or so.

Project files for scenes that go screwy are always very useful, but we need to have everything which goes into the scene - all models, textures etc.

Regards,

Jo

[GioMez]

At my computer most of the times the error occurs when using TG2 for a while or doing a series of node copy/paste and deleting.

The same thing happens to me

[darthvader]

Hmmm, weird...the past couple renders that I have done of the scene havent had the same problem and my computer has been doing wxactly the same workload.

[Oshyan]

This is a somewhat general error that does occur in different situations. But you can generally well when it is memory-related in 2 ways. First, if it is a scene you have rendered successfully before and you are now just rendering it at higher resolution or detail, then it is probably a memory issue as the *elements* of the scene would not appear to be the issue. Second, you can of course check Task Manager for memory use near 2GB for 32 bit OS's (be sure to check Virtual Memory too), and 4GB for 64 bit OS's. In this case I think it is very likely to be a memory issue.

- Oshyan