OcDS FIRST RENDERS - FIRST PRIDE :) post here...

[Banti]

Simple Portrait

[Tugpsx]

Looks good, which hair is that? What are your render settings?

[Banti]

Looks good, which hair is that? What are your render settings?

Thanks. Its Haydina Hair: https://www.daz3d.com/haydina-hair-for- ... -8-females

I am using Path Tracing with Agfacolor HDC 200 response curve. Everything else is pretty much default settings.

[Tugpsx]

Thanks for sharing. Are you doing promos? if not check this with Affinity Photo.
Save your current render settings and import this one. Let me know how it works out for you.

With Affinity filters

PhotoMatch.orbx

Render settings

(39.84 KiB) Downloaded 779 times

[Banti]

Thanks for sharing. Are you doing promos? if not check this with Affinity Photo.
Save your current render settings and import this one. Let me know how it works out for you.

PortraitMod.png

PhotoMatch.orbx

I am not familiar with Affinity Photo, i suppose its a photo editor? I do use Adobe Lightroom sometimes, this portrait is unedited tho. I looked at you settings and the only thing different is the highlight compression and a different response curve. The kernel settings are not saved into this file, at least not for me.

[valzheimer]

I am not familiar with Affinity Photo, i suppose its a photo editor? I do use Adobe Lightroom sometimes, this portrait is unedited tho. I looked at you settings and the only thing different is the highlight compression and a different response curve. The kernel settings are not saved into this file, at least not for me.

There's an issue with ORBX files and importing/exporting them. It seems to not memorize Kernel Settings (except on the machine it's been exported from, until data folder is cleared/resetted), it also creates a mess with paths if you try saving the scene that had an ORBX environments and settings imported at the time of saving. This frustrated me so much I stopped using ORBX entirelly for saving settings and only use them if I have to go between the plugin and standalone on the same machine.

[face_off]

I am not familiar with Affinity Photo, i suppose its a photo editor? I do use Adobe Lightroom sometimes, this portrait is unedited tho. I looked at you settings and the only thing different is the highlight compression and a different response curve. The kernel settings are not saved into this file, at least not for me.

There's an issue with ORBX files and importing/exporting them. It seems to not memorize Kernel Settings (except on the machine it's been exported from, until data folder is cleared/resetted), it also creates a mess with paths if you try saving the scene that had an ORBX environments and settings imported at the time of saving. This frustrated me so much I stopped using ORBX entirelly for saving settings and only use them if I have to go between the plugin and standalone on the same machine.

I agree that saving to ORBX is not straightforward. The saving is basically just exporting the nodes within the Octane scene - and it's a mess - with a lot of nodes which are not actually being used in the render. I was unable to find a reasonable solution to this. Regarding not memorizing the Kernel settings, I think this is a general issue, and not specific to the saving to ORBX. I spent a lot of time trying to resolve this issue, but could never get to the bottom of it unfortunately.

Paul

[valzheimer]

I am not familiar with Affinity Photo, i suppose its a photo editor? I do use Adobe Lightroom sometimes, this portrait is unedited tho. I looked at you settings and the only thing different is the highlight compression and a different response curve. The kernel settings are not saved into this file, at least not for me.

There's an issue with ORBX files and importing/exporting them. It seems to not memorize Kernel Settings (except on the machine it's been exported from, until data folder is cleared/resetted), it also creates a mess with paths if you try saving the scene that had an ORBX environments and settings imported at the time of saving. This frustrated me so much I stopped using ORBX entirelly for saving settings and only use them if I have to go between the plugin and standalone on the same machine.

I agree that saving to ORBX is not straightforward. The saving is basically just exporting the nodes within the Octane scene - and it's a mess - with a lot of nodes which are not actually being used in the render. I was unable to find a reasonable solution to this. Regarding not memorizing the Kernel settings, I think this is a general issue, and not specific to the saving to ORBX. I spent a lot of time trying to resolve this issue, but could never get to the bottom of it unfortunately.

Paul

I found a general flaw where when Orbx is imported, and then scene saved as .duf (scene or scene subset) and I found it mentioned here in the forum too, where it seems that OcDs gets confused with Daz folder hierrarchy (like how we save Product textures in Documents/Daz 3D/Content/Runtime/Textures/VendorName/ProductName/texture001.jpg) and cuts down the path at some point bouncing it to non-existing file location in assets/...texture001.jpg which I can only guess is some cached/temporary file.

I've had more luck with paths that aren't that long/burried inside the content folder but it was unreliable for sharing still. I have only had luck importing from Orbx if I don't change machines and don't reset Octane's data folder in C:/Users/Name/Octane Render folder, clearing the folder seems to break some of the saved things as well.

However, I *did* have luck sharing Render Settings including Kernel Settings between 3 machines with different content libraries by saving them into the .duf as scene files, ruling out Orbx use completely/not including Orbx. Downside of this, is scene files pick up all of the settings from Render Settings (Kernel + Camera Imager) and the Environment tab altogether, even more, duplicating that pesky "No Environment" node that can't be removed and gets stacked if it's saved as an additive/scene subset .duf. So, as to share Kernel Settings this way you'd have to create an empty Environment node that would load regardless (and vice versa, if you're sharing Environment it would share default/empty current kernel setup as well).

It is probably just wishful thinking on my part but it would be very helpful if we could completely clear the tab of settings we don't want to save at least giving us option to delete all of the options and not have residues. For some reason at some point I did have the *delete button next to No Environment but it disappeared after one of the resets I did and never opened back up for that again.

Edit to add: To my remark of removing residues: OR if we could at least see what is what in the .duf file, where Octane Data is all hardcoded altogether in a bunch of code even when .duf is decoded and we can't see what part of code represents what from the plugin. If this was somehow broken up in parts we could edit the .duf in text editor to remove things or a string of code we don't want included. I understand hardcoding the plugin is necessary because Octane isn't open source, but giving it some clarity in all the code would be so very helpful.

[Witpapier]

Gimme your thoughts!!

[birdovous]

Gimme your thoughts!!

Umm... Very nice?