Recent Posts
1
Forest Pro (*) / Re: AcesCG workflow
« Last post by grue on Today at 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.
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.
2
Forest Pro (*) / Re: edge mode in vray 6 gpu
« Last post by grue on May 10, 2024, 10:02:31 PM »huh. so i was using a test scene with a circle edit spline offset like a donut and edit poly on it as my surface. still getting that error.
i went into the scene i was working on when i noticed this problem. not only did i get the error that edge mode was not supported, but 3ds max would completely lock up on me.
i noticed that the flat surface i was using to distribute one of the grass presets(which came from Revit) had thickness to it. i deleted all polygons except for the top - nice and flat too. i isolated just the newly modified surface and the forestpro object, hit render in point mode, then switched to edge mode and this time no error, no lock ups and edge mode worked as expected. all while in RTX mode.
so the original scene is working just fine which is great. not sure why a completely new scene (the donut one) was a problem. i had closed max and re-opened it to create the new test scene. i will give that a try.
it makes sense that edge mode would freak out on a solid object with top/bottom/sides.
i went into the scene i was working on when i noticed this problem. not only did i get the error that edge mode was not supported, but 3ds max would completely lock up on me.
i noticed that the flat surface i was using to distribute one of the grass presets(which came from Revit) had thickness to it. i deleted all polygons except for the top - nice and flat too. i isolated just the newly modified surface and the forestpro object, hit render in point mode, then switched to edge mode and this time no error, no lock ups and edge mode worked as expected. all while in RTX mode.
so the original scene is working just fine which is great. not sure why a completely new scene (the donut one) was a problem. i had closed max and re-opened it to create the new test scene. i will give that a try.
it makes sense that edge mode would freak out on a solid object with top/bottom/sides.
3
Forest Pro (*) / edge mode in vray 6 gpu
« Last post by grue on May 10, 2024, 09:11:23 PM »i'm getting an error in vray 6, update 2.1 (6.20.06 build 00000) and forestPro 8.2.6.702
i'm loading a preset lawn, layered lawn, or autumn leaves and applying it to a circle spline with a hole in it and an edit poly modifier.
when i switch from point mode to size mode, it works just fine and i see it update in my viewport.
when i switch to edge mode, i get an error that say "Edge mode is not supported for the current render. See documentation for details. point mode will be used instead"
now, i opened a scene from about 6 months ago (created in an earlier version of vray and forestpro) and those rendered just fine, i confirmed the grass were set to edge mode.
i have been using Vray GPU in RTX mode for just over a year now. The video card drivers are appropriate for Vray GPU, sometimes they lag behind a version or two.
I switched my Vray GPU to CUDA mode, started an IPR render while in Point mode for the forest object, then i stopped the IPR and switched to edge mode and the error went away and it was working.
Finally, i stopped all IPR rendering, switched back to RTX mode, and switched between Point - Size - Edge mode and got no errors. The edge mode even worked as expected. Oh and I also switched to one of the Large gravel presets having deleted all the leaves in the Geometry rollout, clicking on library and imported a Large gravel preset.
so this is all very interesting. thanks.
i'm loading a preset lawn, layered lawn, or autumn leaves and applying it to a circle spline with a hole in it and an edit poly modifier.
when i switch from point mode to size mode, it works just fine and i see it update in my viewport.
when i switch to edge mode, i get an error that say "Edge mode is not supported for the current render. See documentation for details. point mode will be used instead"
now, i opened a scene from about 6 months ago (created in an earlier version of vray and forestpro) and those rendered just fine, i confirmed the grass were set to edge mode.
i have been using Vray GPU in RTX mode for just over a year now. The video card drivers are appropriate for Vray GPU, sometimes they lag behind a version or two.
I switched my Vray GPU to CUDA mode, started an IPR render while in Point mode for the forest object, then i stopped the IPR and switched to edge mode and the error went away and it was working.
Finally, i stopped all IPR rendering, switched back to RTX mode, and switched between Point - Size - Edge mode and got no errors. The edge mode even worked as expected. Oh and I also switched to one of the Large gravel presets having deleted all the leaves in the Geometry rollout, clicking on library and imported a Large gravel preset.
so this is all very interesting. thanks.
4
Forest Pro (*) / Re: Colour Display OCIO
« Last post by Michal Karmazín on May 09, 2024, 01:56:50 PM »Hi Jason,
Well, according to the provided screenshots, all objects in the scene (not just Forest objects) look darker in the viewport. But what's more important, as posted in this "AcesCG workflow" thread:
"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,
Well, according to the provided screenshots, all objects in the scene (not just Forest objects) look darker in the viewport. But what's more important, as posted in this "AcesCG workflow" thread:
"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,
5
Forest Pro (*) / Re: Slow material assigment
« Last post by Michal Karmazín on May 09, 2024, 01:47:59 PM »I'm sorry to hear that you're facing these troubles. If you can reproduce these troubles in a minimal scene that you can send to us, it would be greatly appreciated.
Thank you in advance for any additional comments you may have regarding this issue that you can share with us and our user community (in case some users will encounter similar difficulties).
Best regards,
Thank you in advance for any additional comments you may have regarding this issue that you can share with us and our user community (in case some users will encounter similar difficulties).
Best regards,
6
Forest Pro (*) / Re: Slow material assigment
« Last post by frodo on May 09, 2024, 01:39:57 PM »Maybe its because forest multisub automat material its rebuilding somehow wrong?
7
Forest Pro (*) / Re: Slow material assigment
« Last post by frodo on May 09, 2024, 01:38:38 PM »Hi again, I'm back after a while.
This issue really slowing me down can someone check it?
Example.
1) Forest object with 30 obejects.
2) Each object have its own material, no material overrides inside forest object.
3) Each material is quite complex, blend, multisub, etc. 20+ SME nodes each.
4) I have to change all the materials on object from this forest object. Word change is important because I reaasigning each material and not modifying current one.
5) This reassigment takes ages. 20+ minutes
This issue really slowing me down can someone check it?
Example.
1) Forest object with 30 obejects.
2) Each object have its own material, no material overrides inside forest object.
3) Each material is quite complex, blend, multisub, etc. 20+ SME nodes each.
4) I have to change all the materials on object from this forest object. Word change is important because I reaasigning each material and not modifying current one.
5) This reassigment takes ages. 20+ minutes
8
Forest Pro (*) / Colour Display OCIO
« Last post by EH2026 on May 09, 2024, 12:50:36 PM »Hi guys,
Anyone notice weird behaviour with the newish OICO colour setup?
Please see two attached screen grabs showing Gamma & OCIO workflow, notice the colours of the FP objects being very dark and substantially different than the Gamma method.
Any help appreciated.
Jason
Anyone notice weird behaviour with the newish OICO colour setup?
Please see two attached screen grabs showing Gamma & OCIO workflow, notice the colours of the FP objects being very dark and substantially different than the Gamma method.
Any help appreciated.
Jason
9
RailClone Lite / Re: No Size or Spline on X
« Last post by Michal Karmazín on May 09, 2024, 10:26:03 AM »As mentioned previously: "Once you link the Spline node, the X Size parameter isn't available ...". If you want to define it numerically, you should remove the Spline node from the Spline Input of the Generator. I hope that helps.
Best regards,
Best regards,
10
Forest Pro (*) / Re: Activated but out of support
« Last post by m.lamme on May 08, 2024, 11:48:58 AM »Thank you Paul for you help! True, my plan expired nov 28 and the latest build I have is from feb 2. Odd that it stopped working just yesterday though?
