Method wrote:I would like to see an alpha channel to work in direct light.
The CUDA compiler used too much memory and crashed when had this option enabled for the direct lighting kernel. We only way to solve that problem was to take out the option. I'm currently trying out a few things that might help, but I don't know yet.
Cheers,
Marcus
The cool Marcus and thanks for the reply. DirectLight may be sufficient to animate the exterior, just a little help it (fake gi, alpha light ...). For still images of the interior (exterior, etc.), and OctaneRender (PathTracing) absolutely brilliant!
Animators are always handicapped:)
Anyway, I still CUDA 3.2 does not work. There is still a distribution of both the GPU 50 to 50% loading.
Peace.
ASUS P6X58D-E / Nvidia GeForce GTX 780 / 24GB Ram (DDR3) / i7 950 (OC4.2Ghz-without HT) / Windows 7 x64 / and million cooling fans
VFX/CGI, Animation for documentary movies, Music videos, Products renderings, Advertising....3D/2D (small production)
Hmm, there aint nothing to update. Sorry. What's interesting though is how often the render thread gets killed, although it shouldn't get killed at all. That might cause the trouble we see here. I will have a look at it.
If you just retry to render the frame that crashed, does it work?
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
hi marcus,
thx for your fast reply.
it was no animation just a single shot to be cooked for a while.
night before i had the same experience.
the scene uses 750 mb of vram (1280x1080 gtx470 1280mb) only directlighting works if i switch to pathtracing, no matter which small res i choose it seems not to work. the picture just gets darker and darker. not really rendering, strange spp "hopping"..
after reset to directlighting it keeps on rendering.
what can i do to make more of the vram useable? if i add only a few mb to the vram (800mb) also directlighting stops workin.
dave62 wrote:hi marcus,
thx for your fast reply.
it was no animation just a single shot to be cooked for a while.
night before i had the same experience.
the scene uses 750 mb of vram (1280x1080 gtx470 1280mb) only directlighting works if i switch to pathtracing, no matter which small res i choose it seems not to work. the picture just gets darker and darker. not really rendering, strange spp "hopping"..
after reset to directlighting it keeps on rendering.
what can i do to make more of the vram useable? if i add only a few mb to the vram (800mb) also directlighting stops workin.
should i use the 3.0 release?
cheers dave
You can try the CUDA 3.0 build, but I don't expect any better VRAM usage. If you want to give it a try, you have to install the CUDA 3.0 toolkit, but you can leave the graphics driver.
It would be great, if you could send us the scene so that I can investigate the problem.
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
dave62 wrote:may the vram usage depend on which os you use? is it possible to use more %vram under win or osx?
Sorry, I don't know. I wouldn't expect big differences. One thing you can try though: Before you start the actual render job: Just save the scene, close and relaunch Octane, load the scene and start rendering. It's unlikely but there may be also fragmentation issues in which case it might help to removing everything used by Octane before you start the rendering. Just an idea...
Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
abstrax wrote:- connecting the preview render target with a different camera changes the camera view - the same applies to all other connections like environment or kernel
It would be possible when rendering from the command line, that Octane would save the render for each imager node previously created in preview configuration? When done rendering it would iterate through each defined imager node (which need not to be connected) and save a tonemaped .png for it. This way when rendering overnight, you could get as much out of your render as if you would be present at the computer.
dave62 wrote:may the vram usage depend on which os you use? is it possible to use more %vram under win or osx?
Sorry, I don't know. I wouldn't expect big differences. One thing you can try though: Before you start the actual render job: Just save the scene, close and relaunch Octane, load the scene and start rendering. It's unlikely but there may be also fragmentation issues in which case it might help to removing everything used by Octane before you start the rendering. Just an idea...
Cheers,
Marcus
thx for your help! i will try.
squeeze here, squeeze there..but at the end i think i will simply need a bigger boat:)
