Community Forums for OTOY Customers
https://render.otoy.com/forum/
Thanks a lot!aoktar wrote:New build (R4) is out with some fixes! Enjoy it!
On your last point re your video, you can still turn on force tonemapping in the current version (2022). But doing so, this is no longer ACES and will produce incorrect color interpretation. You also double dip and turn on ACES in the camera which switches to Octanes implementation of ACES, this isnt needed if you are using the OCIO from the IPR drop down menu. You can pick 1 or the other but don't need to do both.gifmotion wrote: I understand technically why you say Aces doesn't do this and shouldn't.
But as artists wanting speed and primarily caring about what the visual image looks like, this is important. I don't want to look at my image in liveviewer and then be like "I think this will look good if I take it into photoshop or aftereffects or an alternative app to do more color correction". Aces I find is giving me a nice look, however I think its very important as an artist to then have the ability to break the rules and have further ability to force tonemapping and change highlight compression and gamma. It may not be 'technically' the right thing to be doing but visually it looks good. So I believe we want to have this feature or otherwise another color correction set of tools that can be done during the liveviewer process to do this. So we aren't jumping around between programs.
Lastly, I posted a video a few comments back using aces and had this ability in the 2021 plugin. Potentially it may have been setup wrong but from what I can tell from using it for the past year, It was setup correctly and was allowing me to do this feature.
Thankyou for your responses though SSmolak and Arronwestwood
Hi, SSmolakSSmolak wrote:Thank you for Shape Fields ! It is very powerfull for creating dirts around chosen objects. But I found two issues :aoktar wrote:New build (R4) is out with some fixes! Enjoy it!
1. It doesn't work correctly for sdf from objects ( space translation issue ) It works fine for regular sdf's 2. Using SDF's in scene cause crash while restart rendering.
3. Field Shape doesn't work while connecting Projection node to it.
Scene attached.
Hi, scene attached. You need to drag SDF object to Shape Input in Field Texture also link it in Transform Node too to match position.Kalua wrote: Hi, SSmolak
Would you mind sharing the setup on how to make this "Field shape node" to work? Have been trying to make it work with no success.
Regards,
Thank you!SSmolak wrote:Hi, scene attached. You need to drag SDF object to Shape Input in Field Texture also link it in Transform Node too to match position.Kalua wrote: Hi, SSmolak
Would you mind sharing the setup on how to make this "Field shape node" to work? Have been trying to make it work with no success.
Regards,
If you use restart render in Octane LV - it will crash.
It works pretty good as for first implementation. I think that would be great if shape create more wider texture. At the moment it distance is very small even on max setting.aoktar wrote:As wrote in release notes, shape field is not stabilized yet. Crash are expected. Also there are unoptimized structure on my side. You need to wait for stabilization.
[opinion]elsksa wrote: Unfortunately, it's a fallacious thinking. The "digital imaging world" is chaotic enough that such thinking doesn't have its place. Evidently, nobody will arrest you for doing it wrong but it shouldn't be normalized, especially for working around in-renderer limitations (there are none in-post).