Itoo Software Forum

Author Topic: AcesCG workflow  (Read 607 times)

grue

  • Full Member
  • ***
  • Posts: 104
AcesCG workflow
« on: February 28, 2024, 04:36:54 PM »
hello.  is forestpro working with acescg workflow in vray 6.x and 3dsMax2024?  as of now, i have to select the material from the scene object and convert bitmaps to vray bitmaps, then manually set "Color space transfer function"  and "RGB color space parameters".

i tried using a vray bitmap converter, and that really messed up those two things i mentioned above. then i have also just right-clicked and changed the bitmap type.

thanks.

Michal Karmazín

  • iToo Software
  • Hero Member
  • *****
  • Posts: 2501
Re: AcesCG workflow
« Reply #1 on: February 29, 2024, 10:04:27 AM »
Hi,

The recently introduced Color Management (Rendering > Color Management) is now supported, and you have the option to use the OCIO Color Management Mode. However, I should mention that currently, the texture maps included in our bundled assets do not have "_lin_srgb," "_srgb", or "_acescg" suffixes. These maps are loaded within the Bitmap maps, so if you opt for the ACEScg workflow, you will need to make these adjustments as needed. Thank you for your understanding.

Best regards,

grue

  • Full Member
  • ***
  • Posts: 104
Re: AcesCG workflow
« Reply #2 on: May 11, 2024, 12:08:37 AM »
from what i could tell from reading vray docs and looking at vray assets from cosmos, the idea is that you could also go through the bitmaps > convert them to vraybitmaps > then set the color space transfer funtion & further down, RGB primaries to sRGB & sRGB primaries.

now, for forest objects i was using the built in vray converter bitmap to vraybitmap.

for my last playing around with it, the colors aren't going to be super exact render-to-render, but it's pretty close to the old gamma workflow.

the other thing is, in the 3ds max color management settings i set my displays and views like the attached image.  this gives me the benefit of saving out a 16bit tif file from the vray frame buffer. so you get not only the wider color gamut, but also greater bit-depth in the image which is the best way to capture and work with all the colors you can.

in the vray frame buffer, when you are going to save, make sure include the option to save the color profile (aRGB) in the image when you save it.

finally, i think that doing the "the color space transfer funtion & further down, RGB primaries to sRGB & sRGB primaries" set like this assumes the maps are in srgb to begin with.  which i think is pretty safe to assume depending on where you get your actual bitmaps.  downloading a logo  for a company from their website, you assume it was prepared with srgb in mind.  srgb is more or less the standard and has been for a long time.

the cosmos trees i have in a scene right now are all set to srgb/srgb so that means they prepared the leaves and the trunk/branch maps in srgb.

grue

  • Full Member
  • ***
  • Posts: 104
Re: AcesCG workflow
« Reply #3 on: Today at 08:38:40 PM »
i shold also mention, for me to get the closest match to the frame buffer when opening a file saved out... i save the file as a 16bit tif and again check that box for saving the profile in the image.  when i open it in photoshop, i set it so that PS prompts me what it wants me to do because there is no color profile embedded.  i choose "assign adobe rgb". 


edit: and by the way, what i don't show as a screen shot is that there are Input Image Files > Automatic Color Space Assignment Rules rollout further down the color management settings.  i have my rules set to be the following screen shot. 

if i'm correct on all of this, you no longer necessarily need to change image file names with _srgb or _lin_srgb  this looks like a place where we can set the default of images from the web or manufactures (carpet, tile etc) all can be assumed to srgb so we don't have to change anything. and playing around with this lately, the grass preset does look different from a gamma workflow render but it's not rediculously out of wack.
« Last Edit: Today at 08:43:26 PM by grue »