Hello,
I just upgraded from version 2023 to 2024. I see that the gamma of the "octaneImageTexture"
is originally set to 1 instead of 2.2. I've tried some things, but I can't get good results with the gamma at 1. The colors are washed out.
It changes the 2.2 gamma of my old scenes to 1 (gammas other than 2.2 are not changed). All my assets need to be manually edited. If I have to set the gamma to 2.2, it also changes the results of the Roughness, Metalness maps, etc.
I saw that the color management seems to have changed, but it seems the correct gamma is still 2.2, so I don't understand.
Did I miss something?
ImageTexture Gamma
Moderator: JimStar
There are too many variables to precisely diagnose the issue. This general Octane Color Management Guide as well as this one specific to texture files should cover all answers to more than most questions (all besides some 3D DCC specific cases).
Regarding the exponent number (oversimplified and rather erroneously referred as "Gamma") depends on the input file (such as non-linearly encoded or linearly, detailed on the texture-files page).
Furthermore, the "management" depends on the signal processing pipeline, "internal sRGB" (default) or if OCIO is active and a config-file loaded. And so forth (multiple variables, cases, situations).
Regarding the exponent number (oversimplified and rather erroneously referred as "Gamma") depends on the input file (such as non-linearly encoded or linearly, detailed on the texture-files page).
Furthermore, the "management" depends on the signal processing pipeline, "internal sRGB" (default) or if OCIO is active and a config-file loaded. And so forth (multiple variables, cases, situations).
It most cases, the difficulties are easily countered thanks to the aid from all the information available on the suggested pages.
Feel free to report back (with as much relevant information as possible) if facing an issue or how it got resolved, if solved.
Feel free to report back (with as much relevant information as possible) if facing an issue or how it got resolved, if solved.
-
itsallgoode9
- Posts: 894
- Joined: Thu Apr 03, 2014 9:04 am
- Location: New York City
- Contact:
I've had this issue too for quite a few past versions of the plugin--at least a year. It literally just started at after one of the plugin/octane updates. Happened across all machines and all scenes--not just isolated to a single scene file or something like that.
Not sure if it's a bug that's never been addressed or a change in expected behavior of of how octane core handles image textures, but it's most definitely not an "us" issue, as far as trouble shooting goes. Sorry I don't know exactly which plugin/core issue this started with.
Not sure if it's a bug that's never been addressed or a change in expected behavior of of how octane core handles image textures, but it's most definitely not an "us" issue, as far as trouble shooting goes. Sorry I don't know exactly which plugin/core issue this started with.