[2020] OSL textures loose inputs when loading a saved file

Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Post Reply
llennoco22
Licensed Customer
Posts: 13
Joined: Wed Jan 28, 2015 7:56 pm

When opening a Blend file, OSL texture nodes aren't compiled and loose their inputs and are therefore disconnected, breaking the node network that they are in. This is an issue in all 2020 versions of then plugin I have tested.
To reproduce is you can set up an OSL texture with inputs, save the file and click revert from the file menu to return to the save state.

Windows 10
RTX 2080ti
32GB
Geforce driver: 445.87
Blender Octane Edition 2020.1 RC4 21.6 beta
J.C
Licensed Customer
Posts: 1857
Joined: Thu May 13, 2010 6:35 pm
Location: Wrocław

I confirm this too.
Also if the inputs have been set some values they are reset after loading the file.
CPU – i9 13900KF, 128GB RAM, GPU – RTX 4090
System – Windows 11
My Behance portfolio, Blender plugin FB support group
linograndiotoy
OctaneRender Team
Posts: 1355
Joined: Thu Feb 01, 2018 7:10 pm

OSL options appear as you start the IPR.
Connections are not lost, at least with the OSL nodes I've tried, but yes, values get reset, which is the real issue.
Thanks!
Post Reply

Return to “Bug Reports”