Exporting to Stand Alone

Forums: Exporting to Stand Alone
DAZ Studio (Export Script Plugin developed by Tugpsx; Integrated Plugin maintained by Paul Kinnane)

Moderator: face_off

Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.

Exporting to Stand Alone

Postby bpzen » Thu Feb 25, 2016 6:01 pm

bpzen Thu Feb 25, 2016 6:01 pm
Can anyone give me some guidance on the best way - if possible - to export a scene with materials form the DAZ Octane plugin to -> Stand alone Octane?
-------------------------------------------------------------------------------

Win 7 64bit, Titan 6 Gig and GTX770 4Gig, Intel 3.75GHZ, 24Gig RAM, Poser 2014 patched
bpzen
Licensed Customer
Licensed Customer
 
Posts: 329
Joined: Wed Dec 19, 2012 1:44 am

Re: Exporting to Stand Alone

Postby linvanchene » Thu Feb 25, 2016 7:33 pm

linvanchene Thu Feb 25, 2016 7:33 pm
Updated:
- added more precise information for animation export
- updated links to lead to the corresponding manual pages


bpzen wrote:Can anyone give me some guidance on the best way - if possible - to export a scene with materials form the DAZ Octane plugin to -> Stand alone Octane?


OcDS System Tab:

OctaneRender export - Complete Scene

- ORBX will create one compressed file including all geometry and materials.
- OCS will create a separate folder with the geometry in .obj form

Scene export to OR standalone.jpg


IMPORTANT: You need to have started rendering with OctaneRender prior to using these export functions, otherwise the Mesh nodes will be blank when you open the exported scene in Octane Standalone.


compare:

https://docs.otoy.com/#60Program%20Overview

- - -

For still images:

- use .OCS when you want to work locally with texture files just referenced in their original position.
- use .OCS when you also want .obj to be created in a separate folder
- use .ORBX when you prefer to just have one file for the whole scene
- use .ORBX to share scenes with others

For animations:

Currently .ORBX has some limitations which animated information is included.

- If you only animated OctaneRender related parameters you can use .ORBX

- if you animated poses, morphs, translation, rotation or any other animateable DAZ Studio values use .OCS

- to export animated cameras use the separate options to export Camera Data as .ocs that includes an .abc

You can export animated parts of the DAZ Studio scene separately and combine all the different files with animated data in OctaneRender standalone by dragging pin connections between the nodes in the scene based Node Graph Editor.

- - -

Saving and loading .OCS in OR standalone is explained here:

https://docs.otoy.com/#60Saving%20%2F%2 ... g%20Scenes

Using .ORBX in OR standalone is explained here:

https://docs.otoy.com/#60The%20Packager ... RBX%20File

- - -
Last edited by linvanchene on Wed Jun 01, 2016 9:26 pm, edited 9 times in total.
Win 10 Pro 64bit | Rendering: 2 x ASUS GeForce RTX 2080 Ti TURBO | Asus RTX NVLink Bridge 4-Slot | Intel Core i7 5820K | ASUS X99-E WS| 64 GB RAM
FAQ: OctaneRender for DAZ Studio - FAQ link collection
User avatar
linvanchene
Licensed Customer
Licensed Customer
 
Posts: 783
Joined: Mon Mar 25, 2013 10:58 pm
Location: Switzerland

Re: Exporting to Stand Alone

Postby linvanchene » Thu Feb 25, 2016 8:21 pm

linvanchene Thu Feb 25, 2016 8:21 pm
For the sake of it I add information how to import the ORBX and OCS in OR standalone.

In OctaneRender standalone the imported DAZ Studio scene files consist of several red "nested group nodes".
This can be a bit confusing at first.

Maybe it can help to read through the official manual section of the Graph Editor first:

https://docs.otoy.com/#60The%20Graph%20Editor

- - -

001 exporting ORBX and OCS - was explained in the previous post.


002 Right click - Import

002 Right click - Import.jpg


003 Browse to the saved ORBX or OCS

003 Browse to the saved ORBX or OCS.jpg


004 imported scene as group node

004 imported scene as group node.jpg


005A double click the group node to open it

alternatively:

005B right click and select ungroup

005B right click and select ungroup.jpg


006 click on the Default Rendersetting node to start rendering

006 click on the Default Rendersetting node to start rendering.jpg


- - -

Update / Edit:
Added information about

Default Rendersetting / Render target nodes
group items / ungroup

in another post:

viewtopic.php?f=44&t=52847&p=278396#p278396

- - -

The OctaneRender standalone manual has a lot of very detailed guides about working with the OR standalone UI:

https://docs.otoy.com/#60Program%20Overview

- - -
Last edited by linvanchene on Wed Jun 08, 2016 5:51 am, edited 4 times in total.
Win 10 Pro 64bit | Rendering: 2 x ASUS GeForce RTX 2080 Ti TURBO | Asus RTX NVLink Bridge 4-Slot | Intel Core i7 5820K | ASUS X99-E WS| 64 GB RAM
FAQ: OctaneRender for DAZ Studio - FAQ link collection
User avatar
linvanchene
Licensed Customer
Licensed Customer
 
Posts: 783
Joined: Mon Mar 25, 2013 10:58 pm
Location: Switzerland

Re: Exporting to Stand Alone

Postby linvanchene » Wed Jun 01, 2016 9:13 pm

linvanchene Wed Jun 01, 2016 9:13 pm
- - -

Changes introduced in 3.04.11

From release 3.0.4.11, when you save to an Alembic file, the plugin will also save to an OCS file which contains that ABC file, with all the material connections in place. The OCS file saved to be the ABC filename with a .OCS file extension.

compare:
https://docs.otoy.com/#60System%20Tab

- - -

State OR 3.0.20.22

previous post updated to include information to use

- for still images use your preferred scene export option either .ORBX or .OCS
- for animations scene .OCS export
- for animated cameras the separate camera export .OCS with .abc

- - -
Win 10 Pro 64bit | Rendering: 2 x ASUS GeForce RTX 2080 Ti TURBO | Asus RTX NVLink Bridge 4-Slot | Intel Core i7 5820K | ASUS X99-E WS| 64 GB RAM
FAQ: OctaneRender for DAZ Studio - FAQ link collection
User avatar
linvanchene
Licensed Customer
Licensed Customer
 
Posts: 783
Joined: Mon Mar 25, 2013 10:58 pm
Location: Switzerland

Re: Exporting to Stand Alone

Postby Veneris » Thu Jun 02, 2016 2:54 pm

Veneris Thu Jun 02, 2016 2:54 pm
- What is the benefit of export to Standalone? What's better?

- Can I use Octane Render Export (DAZ Studio) and import in OctaneRender Import (Houidini)?
Intel Core i5-2500 CPU @ 3.30Ghz (Quad Core), 12.0GB RAM, NVIDIA GeForce GT 620. Windows 7 (64 bits)
Veneris
Licensed Customer
Licensed Customer
 
Posts: 86
Joined: Sun Jun 15, 2014 5:30 pm

Re: Exporting to Stand Alone

Postby face_off » Thu Jun 02, 2016 10:38 pm

face_off Thu Jun 02, 2016 10:38 pm
- What is the benefit of export to Standalone? What's better?
1) It can render vertex motion blur. 2) You can add Volume nodes to render VDB files.

- Can I use Octane Render Export (DAZ Studio) and import in OctaneRender Import (Houidini)?
I'm not sure. I know you can export from DAZStudio and import into OctaneRender for Nuke. But unsure of the Houdini import functionality.

Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke, DAZ Studio
Pls read before submitting a support question
User avatar
face_off
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 13501
Joined: Fri May 25, 2012 10:52 am
Location: Adelaide, Australia

Re: Exporting to Stand Alone

Postby linvanchene » Fri Jun 03, 2016 1:29 am

linvanchene Fri Jun 03, 2016 1:29 am
Veneris wrote:- What is the benefit of export to Standalone? What's better?


The features that are available in OctaneRender standalone but (not yet) supported in OcDS may change over time.

A huge benefit of OctaneRender standalone is it's scene based node graph editor.

In OcDS you can link the same material to multiple surface zones.
What you cannot do is link just a group of nodes to multiple surface zones while other nodes on the same surface zone remain different.

TLDR version:
The scene based node graph editor is one of the strongest features of OctaneRender because it allows a more time efficient workflow by linking nodes to multiple surface zones or even objects. You just have to update the shared node once to see the result on all linked surfaces or objects immediately.


Example - Creating custom skin materials:

A skin material consists of nodes that are different for each surface like the diffuse and displacement maps etc. But there are also values like specular, roughness, absorption, scattering settings.

If those settings are not identical on all surface zones you will see visible edges where surface zones touch and more importantly there is not a volume created for the skin.

This makes experimenting with skin surfaces challening in OcDS because you have to update each surface zone one after the other with the same settings to see the final result.

In OctaneRender standalone you can simply link 1 node with all the absorption and scattering information to multiple surface zones and you see the result on the whole figure immediately by changing just one setting in one node.

And this goes even a step further. If you have multiple figures in the scene you could link the shared nodes to multiple figures.

- - -

Still keep in mind that OcDS offers other unique features like templating, OctaneRender image browser, VRAM management, the ability to animate OctaneRender specific parameters.

I try to perform as much workflow steps in OcDS as possible and then export to OctaneRender standalone for the finishing touches.

- - -
Win 10 Pro 64bit | Rendering: 2 x ASUS GeForce RTX 2080 Ti TURBO | Asus RTX NVLink Bridge 4-Slot | Intel Core i7 5820K | ASUS X99-E WS| 64 GB RAM
FAQ: OctaneRender for DAZ Studio - FAQ link collection
User avatar
linvanchene
Licensed Customer
Licensed Customer
 
Posts: 783
Joined: Mon Mar 25, 2013 10:58 pm
Location: Switzerland

Re: Exporting to Stand Alone

Postby Veneris » Sat Jun 04, 2016 5:22 am

Veneris Sat Jun 04, 2016 5:22 am
Understood.
Intel Core i5-2500 CPU @ 3.30Ghz (Quad Core), 12.0GB RAM, NVIDIA GeForce GT 620. Windows 7 (64 bits)
Veneris
Licensed Customer
Licensed Customer
 
Posts: 86
Joined: Sun Jun 15, 2014 5:30 pm

Re: Exporting to Stand Alone

Postby linvanchene » Sat Jun 04, 2016 8:40 am

linvanchene Sat Jun 04, 2016 8:40 am
In addtion there are 3rd party tools that actively support OctaneRender standalone:

http://www.phantomtechnology.nl/

Phantom Scatter is a procedural instancing technology for OctaneRender that lets you create amazing scenes with instances in a very conveniant way.

viewtopic.php?f=9&t=33791

Phantom Photo Match is an amazing tool to help you figure out the proper camera settings to match computer graphic elements with photographs.

viewtopic.php?f=9&t=48403
Win 10 Pro 64bit | Rendering: 2 x ASUS GeForce RTX 2080 Ti TURBO | Asus RTX NVLink Bridge 4-Slot | Intel Core i7 5820K | ASUS X99-E WS| 64 GB RAM
FAQ: OctaneRender for DAZ Studio - FAQ link collection
User avatar
linvanchene
Licensed Customer
Licensed Customer
 
Posts: 783
Joined: Mon Mar 25, 2013 10:58 pm
Location: Switzerland

Re: Exporting to Stand Alone

Postby Veneris » Sun Jun 05, 2016 8:52 pm

Veneris Sun Jun 05, 2016 8:52 pm
Are there more plugins than this?
Intel Core i5-2500 CPU @ 3.30Ghz (Quad Core), 12.0GB RAM, NVIDIA GeForce GT 620. Windows 7 (64 bits)
Veneris
Licensed Customer
Licensed Customer
 
Posts: 86
Joined: Sun Jun 15, 2014 5:30 pm
Next

Return to DAZ Studio


Who is online

Users browsing this forum: No registered users and 1 guest

Sat Oct 19, 2019 3:10 am [ UTC ]