Hi nibbler,
we don't have a distributed render solution like Team Render, but you can already do something similar via Standalone connected in Network Render, using the Render Job nodes or the following LUA script:
viewtopic.php?f=73&t=70855#p403251
Similar to RNDR, if you export in .orbx format, all the scene data are correctly exported too, independently from operating system, plugin used.
ciao,
Beppe
OctaneRender® 2022.1 XB 2
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
This build still has issues with the new Nvidia Studio Drivers. Making any changes in texture node tree even procedural cause delay and live viewer freeze. This is much more noticeable in Cinema 4D version : viewtopic.php?f=85&t=80135#p414049
Architectural Visualizations http://www.archviz-4d.studio
You can already do this by setting the dirt texture's "Include object mode" to Self. Is this not working for you?coilbook wrote:Any development on locking dirt texture to a certain mesh so if another mesh gets closer to it it won't show dirt texture there? Thanks
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
The whole Nvidia 5xx drivers are borked, there are issues for all apps that depend on GPU, including stuff Redshift.SSmolak wrote:This build still has issues with the new Nvidia Studio Drivers. Making any changes in texture node tree even procedural cause delay and live viewer freeze. This is much more noticeable in Cinema 4D version : viewtopic.php?f=85&t=80135#p414049
Please try older drivers like 497.29 (Game Drivers)
-
sethRichardson
- Posts: 95
- Joined: Thu Feb 27, 2014 2:16 am
Theres a bug with bump mapping when using a mapping mode that isn't UV.
Textures get scaled up when switching resulting on having to scale down the transform far lower than octane allows.
Image shows UV mapping vs box/triplanar/any other mapping scaled to the same size. You can see there are actual shading differences as well as the bump appearing to be low resolution or split.
Textures get scaled up when switching resulting on having to scale down the transform far lower than octane allows.
Image shows UV mapping vs box/triplanar/any other mapping scaled to the same size. You can see there are actual shading differences as well as the bump appearing to be low resolution or split.
-
eyeonestudio
- Posts: 329
- Joined: Fri Oct 18, 2013 5:49 pm
- Location: Seoul, South Korea
- Contact:
Normal Vector Node...
It's been waiting for years, but it hasn't been added.
There are some OSL scripts, but they are very slow and unstable. Now it should be added.
It's been waiting for years, but it hasn't been added.
There are some OSL scripts, but they are very slow and unstable. Now it should be added.
C4D R2025 / Win11 / AMD TR WX Series / 256Gb RAM / RTX3090 / 100GbE
The snapshot shows a Blender material, can you explain what you want to do in the context of an Octane material? Typically this would be a texture input in Octane so you can already feed it OSL, images and simple vectors (via "Float3 to color"). Or are you looking to feed a texture into a vector value? which one?eyeonestudio wrote:Normal Vector Node...