Saved render output does not match the OctaneRender Viewport

Forums: Saved render output does not match the OctaneRender Viewport
3D Studio Max Plugin (Export Script Plugins developed by [gk] and KilaD; Integrated Plugin developed by Karba)
Forum rules
Please post only in English in this subforum. For alternate language discussion please go here viewforum.php?f=18

Saved render output does not match the OctaneRender Viewport

Postby DMAEuropa » Fri Nov 13, 2020 8:41 pm

DMAEuropa Fri Nov 13, 2020 8:41 pm
I am beginning to notice major issues when it comes to saving final rendered images.
It does not matter on the scene, file type, or render settings, the issue is still there.
I have even tried versions 4.05 all the way up to the latest 2020.1.5.

Basically upon saving a file, some strange artifacting/compression/gamma issue is occurring, but in the OctaneRender Viewport the issues are completely gone.

I have attached two images showing a closeup of the issue in question, with the left image showing a screenshot of the Render Viewport and the contrast bumped up so you can see it still retains lots of detail.
And the right image shows what happens when an image is saved in any fashion.

The gamma settings are 2.2 across the board and I'm using linear workflows, I'm completely baffled! I'm wondering if it's an obscure 3DS Max setting somewhere.

For now I'm stuck with harshly clipped dark areas and lots of colour banding. Any help is appreciated!
Attachments
OctaneRenderIssue.jpg
DMAEuropa
Licensed Customer
Licensed Customer
 
Posts: 26
Joined: Thu Jun 04, 2015 10:47 am

Re: Saved render output does not match the OctaneRender Viewport

Postby DMAEuropa » Tue Nov 17, 2020 9:48 am

DMAEuropa Tue Nov 17, 2020 9:48 am
Update!

I managed to figure this out, it turns out I was using tonemapping wrong as I was used to the way 4.04 worked.

I switched tonemapping to HDR and made sure my camera settings were all using a gamma of 1, which meant that I could still compress highlights and get a lot more control.
Now I'm exporting 32 bit images once again and I'm very happy!
DMAEuropa
Licensed Customer
Licensed Customer
 
Posts: 26
Joined: Thu Jun 04, 2015 10:47 am

Re: Saved render output does not match the OctaneRender Viewport

Postby DartFrog » Mon Jan 04, 2021 3:27 pm

DartFrog Mon Jan 04, 2021 3:27 pm
This is still an issue. According to Paride, the sdk is missing LDR which is causing this issue. Somehow this bug has carried all the way from octane v4.05 to the newest 2020 plugin. For those of us that don't have the space for saving out 32-bit images, we still cannot upgrade to any of the newest octane plugins until this is solved.
DartFrog
Licensed Customer
Licensed Customer
 
Posts: 148
Joined: Fri Oct 18, 2013 8:54 pm

Re: Saved render output does not match the OctaneRender Viewport

Postby paride4331 » Mon Jan 04, 2021 4:06 pm

paride4331 Mon Jan 04, 2021 4:06 pm
Hi DartFrog,
there's been some misunderstanding, maybe I did not explain myself very well.
I meant about the v2020 UI went into the v4.05 UI, nothing about the SDK; you can save out 32-bit.
Regards
Paride
2 x Evga Titan X Hybrid / 3 x Evga RTX 2070 super Hybrid
User avatar
paride4331
Octane Guru
Octane Guru
 
Posts: 3686
Joined: Fri Sep 18, 2015 7:19 am

Re: Saved render output does not match the OctaneRender Viewport

Postby DartFrog » Mon Jan 04, 2021 4:55 pm

DartFrog Mon Jan 04, 2021 4:55 pm
Sorry, I meant as far as storage space goes, we are unable to save 32-bit images. We work on too many projects to save out 32-bit images for each project. Our workflow requires LDR 16-bit PNGs, and currently we can not save out a png in any new plugin because the image gets clipped and if it's saved with an alpha, the whole image ghosts and has alpha applied to it instead of just the areas with transparency (per my post here viewtopic.php?f=80&t=76179 ).
DartFrog
Licensed Customer
Licensed Customer
 
Posts: 148
Joined: Fri Oct 18, 2013 8:54 pm

Re: Saved render output does not match the OctaneRender Viewport

Postby DartFrog » Thu Jan 07, 2021 5:16 pm

DartFrog Thu Jan 07, 2021 5:16 pm
paride4331 wrote:Hi DartFrog,
there's been some misunderstanding, maybe I did not explain myself very well.
I meant about the v2020 UI went into the v4.05 UI, nothing about the SDK; you can save out 32-bit.
Regards
Paride


Hi @Paride,

I just wanted to make sure you know what I mean. As it stands we cannot work in low dynamic range in any plugin past 6.20. Saving out the images with alpha adds alpha to the whole image instead of just the areas with transparency (per my attached images). LDR also clips black and white levels per the images above in this original post. I would happily save out 32 bit images, but they are too large for the amount of projects our studio works on per day. We have to be able to save out tonemapped 16-bit PNGs the same way we save them out in 6.20.

Is there any plan to release an update with this fixed? Please let me know if you need any more info from me too.

Cheers
Attachments
transparency issues png settings.PNG
transparency issues png settings.PNG (8.34 KiB) Viewed 2159 times
transparency issues settings.PNG
transparency issues.PNG
DartFrog
Licensed Customer
Licensed Customer
 
Posts: 148
Joined: Fri Oct 18, 2013 8:54 pm

Return to Autodesk 3Ds Max


Who is online

Users browsing this forum: No registered users and 11 guests

Thu Mar 28, 2024 12:35 pm [ UTC ]