c4d wrote:kavorka wrote:c4d wrote:please, pretty please, add autosave exr feature
Autosave the Octane file and autosave your render at x intervals. Really needed feature.
HI, otoy dev team, would u guys please don't ignore our request please? autosave is really important feature that several engines are already have, but not in octane, or should I say you guys are never never never losing rendering process during any kind of issues like gpu too heat or crash? even the new vray 3.5, they already support autosave and resume feature, same to corona render. so you guys just hit the render button and let many gpu running, finally you always get what you want and never had crash or any issue that cause losing render process???
3dworks wrote:apologies if i repost this same question here from the development forum, i found out only now that 3.0.6 is final, but have to wait until it is supported by the LW plugin.
i did see reported this already somewhere else, just not sure if that has been fixed: when using the PMC kernel, on my networked windows machine with 5 x geforce 980ti GPU's connected, i can see that the GPU activity never goes beyond 75% on the single GPU. in fact, the fans don't even make any noise when rendering that way. totally expected behaviour when rendering with path tracing: 100% GPU usage and quite some fan noise! has this been fixed with the latest stable update? using octane with the latest lightwave plugin, here...
cheers
markus
andw wrote:Looks like there was some breaking changes in 3.05 -> 3.0.6 work with opacity maps: I tried the 'Materials/Non-organic/Cloth/Roman shades' material from LiveDB, in 3.05 it renders well, in 3.06 the surface looks completely transparent (even if I render only material on test ball). So, is it a bug in OctaneRender or just that material needs some fixes?
abstrax wrote:3dworks wrote:apologies if i repost this same question here from the development forum, i found out only now that 3.0.6 is final, but have to wait until it is supported by the LW plugin.
i did see reported this already somewhere else, just not sure if that has been fixed: when using the PMC kernel, on my networked windows machine with 5 x geforce 980ti GPU's connected, i can see that the GPU activity never goes beyond 75% on the single GPU. in fact, the fans don't even make any noise when rendering that way. totally expected behaviour when rendering with path tracing: 100% GPU usage and quite some fan noise! has this been fixed with the latest stable update? using octane with the latest lightwave plugin, here...
cheers
markus
Yes, I answered that one multiple times already: The problem is that modern GPUs produce samples faster than they can be splatted in the film buffer. We are working on tone-mapping that runs on the CPU, which will then allow us to structure the film buffer differently which should improve splatting speed. At the moment the tone-mapping is done on the GPU, which requires a specific arrangement of the film channels, which doesn't work very well for PMC.
Phantom107 wrote:When I hook up a Scattering medium to a Diffuse material it does not do anything in Path Tracing, even when I play with the settings. Seems to work fine when I hook up the same Scattering medium to a Specular material.
Am I missing something?
Return to Commercial Product News & Releases (Download here)
Users browsing this forum: No registered users and 8 guests