Changing color values

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
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

Hi
When we change saturation in color tab from 255 to 250 results dont get saved. If we change to like 255 to 240 they are saved. same apples with saturation near 1 and 255. values dont get saved. is it max bug? Video attached
Attachments
colro values.MOV
(1.42 MiB) Downloaded 2096 times
Top
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

it looks like problem with 3ds max curves. they do not move until value is 248 for saturation. So it moves in 7s Why is this?
Attachments
values.jpg
Top
User avatar (Default)
neonZorglub
OctaneRender Team
Posts: 1019
Joined: Sun Jul 31, 2016 10:08 pm

Hi Coilbook,

This is just a result of numerical conversion done by max ..
The color is stored and used internally as RGB.. : if it doesn't change, it won't be saved ..
The Hue, Sat, Value version is just a temporary helper .. and for low RGB like your sample (20,2,0), several values of Sat gives the same RGB result..
So this is normal, and a result of the precision loss while converting with integer values of RGB ...
Top
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

neonZorglub wrote:Hi Coilbook,

This is just a result of numerical conversion done by max ..
The color is stored and used internally as RGB.. : if it doesn't change, it won't be saved ..
The Hue, Sat, Value version is just a temporary helper .. and for low RGB like your sample (20,2,0), several values of Sat gives the same RGB result..
So this is normal, and a result of the precision loss while converting with integer values of RGB ...


Thank you !
Top
User avatar (Default)
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

neonZorglub wrote:Hi Coilbook,

This is just a result of numerical conversion done by max ..
The color is stored and used internally as RGB.. : if it doesn't change, it won't be saved ..
The Hue, Sat, Value version is just a temporary helper .. and for low RGB like your sample (20,2,0), several values of Sat gives the same RGB result..
So this is normal, and a result of the precision loss while converting with integer values of RGB ...

I got this reply on autodesk. Not sure if octane can do this one day

You got an reply in the thread you linked, that's not how it works - legacy shaders support 8-bit RGBA values, i.e. four integer values from 0 to 255, hence the limits. You shouldn't use them if you want higher precision for any reason, use for example Arnold shaders, Vray color or anything else that supports floating point values:
Attachments
medium.jpg
medium.jpg (17.41 KiB) Viewed 2094 times
Top
Post Reply

Return to “Bug Reports”