Moderator: face_off
It's the functionality in Octane. If you have comments on it, I suggest you post them in the Octane Standalone 3.00 thread, where the Otoy devs when read them.I was using octane render region today with the kernel set to 1000 samples, went off for a break to find the samples clocking over 55,000!.... would have kept going if I went out as I planned. Tremendous waste of electricity and general wear and tear on the gpu.
face_off wrote:It's the functionality in Octane. If you have comments on it, I suggest you post them in the Octane Standalone 3.00 thread, where the Otoy devs when read them.I was using octane render region today with the kernel set to 1000 samples, went off for a break to find the samples clocking over 55,000!.... would have kept going if I went out as I planned. Tremendous waste of electricity and general wear and tear on the gpu.
Paul
My preference is to keep the plugin in line with Octane Standalone's functionality.Maybe so, but would it be possible to do something within Modo to have the render region function more appropriately? Just seems bizarre it would behave that way even in standalone. I'll also be posting this in the OT3 standalone thread
.. of course.face_off wrote:My preference is to keep the plugin in line with Octane Standalone's functionality.Maybe so, but would it be possible to do something within Modo to have the render region function more appropriately? Just seems bizarre it would behave that way even in standalone. I'll also be posting this in the OT3 standalone thread
Paul
May I suggest bring this up in a few weeks, once I am less busy with Octane 3.00 specific issues.How about Modo's functionality. When using the render region tool in the native Modo renderer it has an 'additive' effect when you change the render region, that is to say the previous regions remain rendered after you change the region... so you can still see what you worked on before changing the region. The earlier octane for modo render region worked this way as well. But now when using Modo's render region with octane, if you change the region the previous region is filled with black and you lose sight of what was just rendered. It's like it's wiping the slate clean and starting again from a black slate. I'm not sure if this is because it's an early implementation and will improve or if this is what we're stuck with. If you have any info on this please share because so far with version 3 I'm not impressed with either of the two implementations and there's a lack of inconsistency and functionality in the way they work. Native octane render region doesn't know when to stop and modo region keeps blacking out previous regions. How much of this is octane and how much of is the plugin? pardon my ignorance as I hardly ever use standalone and kindof new to modo as well.
Can you post a screenshot pls? And what does the Octane Log and Modo Event Log show? And check the link in my signature regarding Nvidia driver versions.Hey. I'm sorry if the answer to this is something really obvious, but since I update to v3, I can't see any meshes in the render viewport. I've checked and I have the latest Nvidia drivers, and I am following all of the methods I would have in the past to use Octane with Modo. Do you have any idea what could be going on?
The next release will be out in the next 2-3 days and will resolve this crash.(update): I just saw this thread: viewtopic.php?f=34&t=54304 and it seems the same issue. Is there a forecast for when it will be resolved? Thanks.
