United3dArtists Archive

You probably encountered that error message at the start of a VRay render from Modeler scene.

I am trying to identify the factors that generate that error.

First, it seems that it is resolution-relative.
If you try to render a big scene at a resolution of 8000*6000 pixels, it fails. But it will render at 2000*1500 pixels.

But I also noticed that a scene may fail when running tS with a graphic card powered with only 128 Mb of Graphic RAM, and succeed with an other one boarding 256 Mb.
So, this might be linked with the real-time engine of Workspace (that handle the scene during VRay rendering).

I wonder if I that error message could be removed for good if I run a graphic card having 1Gb of DDR5.

Any ideas ?

well, I had that msg few days back. It was in a house viz. scene. Problem was with a grass, so I removed it and placed it again, maybe less "particles". In my case, it was NOT resolution dependent, coz I coulnt render 800 x 500 and smaller too.
Next thing, graphics card - I have ATI Radeon HD4870 with 512 DDR5 and I had that msg too.

I thing you should try to find problematic object - propably some texture, transparency or procedural texturemap (as in one of my two cases - strip procedural textured ball object. I made a texture map instead and it worked)

btw: iam pretty not happy with these "limitations"/bug, it costs lot of time to find and tweak it. really not professional stuff then. :(

bitkar wrote: I thing you should try to find problematic object - propably some texture, transparency or procedural texturemap (as in one of my two cases - strip procedural textured ball object. I made a texture map instead and it worked)

Hum... interesting. Thanks for the report Bitkar.
I never use procedural maps, but I realize some large textures could be involved in this bug. Will try to investigate more.

Every experience report is welcome to try to find out how that issue comes and why.

too large texture could be the cause too... you just need to search, delete objects, render and again again... let us know what was the problem. Try to get back in the scene history, where it worked yet.

bug seems like some buffer or something is too small or something similar :-/

I had the error msg yesterday lately. It acts strange, but I got it to work finally. Iam not sure If I made it work or it began to work itself. Sometimes I was able to render it to screen, not to file, mostly I wasnt able at all.
Strange bug needs strange workaround, this is mine:

1) delete one by one all objects in scene, then reload the scene
or
2) delete and then undo objects
something will "reset" this way

Sometimes I experience, that vray renders object on position where is no more, or in position where it never was. I dont know why. Solution 2) works to solve it. I find the object in the scene, delete it, then undo it and next render is ok. Maybe its the same part of code, that is wrong. But Iam happy that I rendered my image at 23:50 h and could sleep at least those 7 hours.

Other trick that may work :

1. Simply save the scene and restart tS.

2. Delete scene in Workspace side.

3. Render again.

That solution also helps with the "ghosts objects" = objects that are not present in Modeler side but show up in the render.