This is the first release of OctaneRender™ for Blender® 2019 for Blender® 2.8 is available for the first time on Octane’s new free tier!
As with all experimental builds, please do not use this for production purposes.
We can’t guarantee that scenes saved with this version will be compatible in future releases, and we anticipate there being several maintenance releases.
In the meantime, we look forward to your feedback on this release.
At this point, we have hit feature lock and would be moving towards stabilizing the plugin.
I think you are being too sensitive. You could say that this thread could be put into the Octane 4 thread, but with the obvious version change it would be too confusing. Why should I mix them when they are so different? It’s just that a lot was released today from Otoy.
Vectron is some kind of procedural primitive that doesn’t use any vram. Supposedly it can be controlled by displacement maps, OSL, OpenVDB’s, etc. The Linux version isn’t out yet so I haven’t had a chance to play with them.
Now that version 4 stable has been released it should be soon according to the devs. Abstrax said this about the free version being out, “Not yet, but it will be provided soon as far as I know.”
until they release free version - they even can change minds
Will future versions of Octane be supported in the free tier?
For 2018.1 and later, we may need to rethink the 2 GPU limit as a differentiation from the paid tiers . it is meaningless when two GPUs give you 800-1000 OB and 22 GB to 50 GB of combined VRAM:
Overhauled the way you return data in vectron nodes - see above.
Added support for importing / exporting vertex attributes in Alembic files.
Improved partial updates of mesh data loaded from Alembic files, by loading only data that is necessary.
Improved detection of moving vertices at start and end of animation sequences.
Always show bar meter to indicate peer to peer mapping is in being enabled.
Worked around an issue with FBX files exported by Maya, which have their SSS sharpness values scales down by a factor of 10 (see viewtopic.php?p=354044#p354044).
Fixed incorrect render restart if the noise pass gets enabled / disabled when adaptive sampling or the denoiser is enabled.
Fixed loading of the opacity channel of FBX materials .
Fixed “affects alpha” option of specular materials when “keep environment” is enabled (fixed the refraction pass being included in the environment in this case).
Fixed caustic blur for clearcoat.
Added sheen and coating bump and normal texture inputs.
Renamed artistic IOR mode from “Default” to “Artistic”.
Implemented sheen and coating bump/normal mapping.
Fixed visible on specular for universal material.
Fixed specular material rendering incorrectly when given 0 roughness and Octane BRDF.
Fixed node to nodegraph comparison in Lua API raising an error.
Fixed vertex attributes causing a render failure when used with SSS.
Fixed float vertex attributes causing render failure with displacement.
Fixed planes sometimes getting rendered black if there are more than one.
Fixed crash when opening import preferences for unsupported VDBs.
I’m waiting for either Cycles or Octane to get an 8x speedup by using Tensor cores in the Nvidia RTX cards. Until then I’m going to use Cycles. If Cycles gets it first I’m going to continue to use Cycles.
You could say that this thread could be put into the Octane 4 thread, but with the obvious version change it would be too confusing. Why should I mix them when they are so different? It’s just that a lot was released today from Otoy.
I had used the Unity version in the past and it was great!
