OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Forums: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7
Sub forum for plugin releases

Moderator: juanjgon

OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby juanjgon » Tue Jan 26, 2021 9:08 pm

juanjgon Tue Jan 26, 2021 9:08 pm
Hi,

This is a beta release of the OctaneRender™ 2020.2 for Houdini™ plugin compiled with the Octane 2020.2 RC7 core. This 2020.2.0.2 release is available for the latest Houdini 17.5/18.0/18.5 production builds on Windows x64, Linux gcc6.3.1 and MacOS 10.12.

Make sure to use a NVIDIA Studio driver with version at least 456.38 on Windows or 455.23 on Linux to use this version. No driver updates are required for macOS 10.13 (CUDA).

As with all experimental builds, we advise not to use this release for production purposes. We can't guarantee that scenes saved with this version will be compatible in future releases, and we anticipate there being several maintenance releases.

New features
To learn more about the new features and improvements of OctaneRender 2020.2, please check out the 2020.2 XB1 release post, but this is a quick list of the main new features that have been added.

  • Improved RTX performance.
  • Fast Spectral Nested Dielectrics.
  • Denoiser support for the new NVIDIA Ampere devices.
  • ACEScg and filmic processing. New color options available in the Octane ROP node.
  • OpenColorIO Management, Display and Export (OCIO profile). Configured from the "OCIO" environment variable.
  • OpenColorIOColor graph nodes. Look, Profile and View nodes
  • Integrated multi-scatter from volumes or surfaces. Available in the Octane OBJ spare parameters.
  • User generated compositor AOV passes for combining render and light passes in full a compositor node graph.
  • Null material.
  • Spotlight texture.
  • New ray type, texture composite and channel tools shader nodes.
  • Improved color correction node.
  • New chaos texture node.


Release 2020.2.0.2 Enterprise subscription license
https://render.otoy.com/customerdownloa ... rprise.zip
https://render.otoy.com/customerdownloa ... rprise.zip
https://render.otoy.com/customerdownloa ... rprise.zip

Release 2020.2.0.2 Studio subscription license
https://render.otoy.com/customerdownloa ... studio.zip
https://render.otoy.com/customerdownloa ... studio.zip
https://render.otoy.com/customerdownloa ... studio.zip

Standalone 2020.2.0 RC7 version for the network rendering nodes
viewtopic.php?f=33&t=76774


Release Notes
=============================================
RELEASE 2020.2.0.2
=============================================

* PLUGIN FEATURES AND FIXES:

- Added new H18.5.462 plugin build.
- Fixed a problem affecting all the nodes including underscores in the pin names (displacement, kernels, postprocessing, etc.)
- Added the new "Octane_enableNetworkRendering" and "Octane_disableNetworkRendering" hscript commands to control the network rendering state.
- Network rendering enabled automatically when the plugin is loaded from hython.
- Added support for packed geo instancing (SOP level packed geo instances, enabled from the Octane OBJ spare parameters).

* OCTANE 2020.2 RC7 FEATURES AND BUGS FIXED:
- The composite texture and AOV nodes have the inputs of their layers grouped in a separate layer node.
- The priority range for nested dielectrics is now [-100 .. 100].
- Improved the performance of changing non-image inputs of the chaos texture node.
- Any error messages collected during startup are logged before Octane is stopped.
- Improved error message if an OCIO tranformation can't be generated.
- OSL Ng is now returning the non-interpolated normal for triangles - calculated from the geometry. To get the interpolated vertex/smooth normal you can use getAttribute("hit:smooth-normal", ...).
- Fixed crash when a CUDA error happens during denoising (see viewtopic.php?p=394386#p394386).
- Fixed a crash caused by a specific combination of empty texture and material pins.
- Fixed denoiser crash on Maxwell GPUs.
- Fixed CUDA failure when peer-to-peer rendering is enabled and you stop+start rendering (see viewtopic.php?p=395065#p395065) or toggle RTX while rendering.
- Fixed filter pass not rendering anything for hair material and universal material's specular transmission + diffuse reflection layer (see viewtopic.php?p=394519#p394519).
- Fixed artefacts around objects inside glass if nested dielectrics and dispersion are enabled (see viewtopic.php?p=394893#p394893).
- Fixed thin wall materials rendering incorrectly when sitting inside a specular material (see viewtopic.php?p=395013#p395013).
- Fixed a renderer stall caused by not always adding an extra blank material name when needed when loading an animated Alembic file and using an importance sampled environment.
- Fixed that the dirt radius map often doesn't work/update.
- Fixed too dark shadows of large emitters behind glass with fake shadows enabled.
- Fixed a bug where auto bump map is not applied properly on all geometries (see viewtopic.php?p=394971#p394971).
- Fixed incorrect update of the texture displacement offset in the compiled geometry data.
- Fixed missing update of internal auto bump map resolution.
- Fixed slow down in scenes with planes that have a shadow catcher material.
- Fixed bug that caused the AO texture of the direct light kernel to get ignored in the very first rendering.
- Fixed loading of EXR files with no default layer. In that case we fall back to the first layer stored in the EXR file.
- Fixed hang in the network render master when the heartbeat of a daemon connection stops / times out.



Happy rendering,
Your OTOY Team
Last edited by juanjgon on Mon Feb 08, 2021 5:25 pm, edited 1 time in total.
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby galleon27 » Tue Jan 26, 2021 10:43 pm

galleon27 Tue Jan 26, 2021 10:43 pm
SOP level packed geo! Love it. Works like a charm.

Keep up the good work.
Cheers.
Win 10 64bit // GTX 4090 + GTX 3090 // 5900x // 64GB // SideFX Houdini // C4D
User avatar
galleon27
Licensed Customer
Licensed Customer
 
Posts: 240
Joined: Wed Jul 15, 2015 11:55 am
Location: Serbia

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby pxlntwrk » Wed Jan 27, 2021 8:41 am

pxlntwrk Wed Jan 27, 2021 8:41 am
galleon27 wrote:SOP level packed geo! Love it
very nice thanks too :D
:::::::::::::::::
pxlntwrk.net
User avatar
pxlntwrk
Licensed Customer
Licensed Customer
 
Posts: 436
Joined: Sat Mar 23, 2013 2:21 pm
Location: France

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby caseyhupke » Wed Jan 27, 2021 8:33 pm

caseyhupke Wed Jan 27, 2021 8:33 pm
Same cuda 700 crashes as last time.

happens whenever I'm using an attribute in my material.

Here is a simple file that will CUDA 700 every time.

Code: Select all
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 0: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate pinned memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate pinned memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device array
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device array
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered

 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy texture objects
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy texture objects
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to unload module
 *** OCTANE API MSG: OptiX error for device 1: [ERROR] Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
 *** OCTANE API MSG: OptiX API error for device 1: CUDA error
 *** OCTANE API MSG: OptiX error for device 1: [ERROR] Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
 *** OCTANE API MSG: OptiX API error for device 1: CUDA error
 *** OCTANE API MSG: OptiX error for device 1: [ERROR] Error synching on OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error destroying OptixPipeline event (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
 *** OCTANE API MSG: OptiX API error for device 1: CUDA error
 *** OCTANE API MSG: OptiX error for device 1: [ERROR] Failed to destroy launch resources (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
 *** OCTANE API MSG: OptiX API error for device 1: CUDA error
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to destroy CUDA event
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> failed to deallocate device memory
 *** OCTANE API MSG: CUDA error 700 on device 1: an illegal memory access was encountered
 *** OCTANE API MSG:   -> could not get memory info


https://share.getcloudapp.com/Z4u6eBg6

Doesn't matter if its Alpha, Cd, or any other float/color attribute the scene fails to load and says to check scene complexity.

I even tried just doing a Cd into Albedo and Emission, removing the multiply and dirt. Same crash each time.

Houdini 18.5.462 - Studio Driver 460.89 - 2x RTX 3090 FE
caseyhupke
Licensed Customer
Licensed Customer
 
Posts: 42
Joined: Tue Jan 15, 2019 8:08 pm

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby juanjgon » Wed Jan 27, 2021 9:21 pm

juanjgon Wed Jan 27, 2021 9:21 pm
Yes, I can reproduce this problem even in Standalone after exporting the scene from Houdini. I'll report this issue to the core devs.

Thanks for the repro scene!
-Juanjo
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby Gregor.Zimmermann » Thu Jan 28, 2021 10:22 am

Gregor.Zimmermann Thu Jan 28, 2021 10:22 am
Hey,

sorry for the noob question - could you explain what SOP level packaged geo is and how it works?

Thanks so much!
Best,
Gregor
Gregor.Zimmermann
Licensed Customer
Licensed Customer
 
Posts: 44
Joined: Mon Jul 16, 2018 8:18 pm
Location: Frankfurt, Germany

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby juanjgon » Thu Jan 28, 2021 8:56 pm

juanjgon Thu Jan 28, 2021 8:56 pm
Gregor.Zimmermann wrote:Hey,

sorry for the noob question - could you explain what SOP level packaged geo is and how it works?

Thanks so much!
Best,
Gregor


This feature makes possible the automatic instancing of the packed geo instances that you can create for example with the copy sop.

Check the attached scene for example. With this option disabled, all the objects are expanded to full geometry, but with the packed geo option enabled, each object is rendered as an Octane instance, saving memory and scene extraction time.

Hope it helps,
-Juanjo
Attachments
33-packedGeoInstancing_01.zip
(55.15 KiB) Downloaded 186 times
2021-01-28 21_52_11.jpg
Last edited by juanjgon on Fri Jan 29, 2021 7:35 am, edited 1 time in total.
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby Gregor.Zimmermann » Thu Jan 28, 2021 10:06 pm

Gregor.Zimmermann Thu Jan 28, 2021 10:06 pm
Thank you so much for the great explanation and the example file, Juanjo!
Best regards,
Gregor
Gregor.Zimmermann
Licensed Customer
Licensed Customer
 
Posts: 44
Joined: Mon Jul 16, 2018 8:18 pm
Location: Frankfurt, Germany

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby Fake Pilot » Mon Feb 01, 2021 12:05 pm

Fake Pilot Mon Feb 01, 2021 12:05 pm
Is it possible to export .orbx now? And does it work with "Full Scene Reload"?

I have Archive > [x] "Export ORBX and Alembic files" checked in my Octane ROP.
Export Mode "Full ORBX scene". Base file name "$JOB/yes.orbx"
But it doesn't work. There should be a Save button, confusing to click "Render to Disk",
cause that starts to render all of the frames instead. Maybe I'm missing something?

I really want to use RNDR, but cannot export from Houdini!
Work machine: Utopia Computers, 4 x GTX 1080 Ti 11GB, 128GB RAM, 10-Core 3.0Ghz Intel Core i7-6950X, Windows 10 Pro.
Home machine: Komplett Xtreme i100, 3 x GTX Titan X 12GB. 32 GB RAM. 8-Core 3.0Ghz Intel Core i7 -5960X. Windows 10 Pro.
User avatar
Fake Pilot
Licensed Customer
Licensed Customer
 
Posts: 71
Joined: Fri Aug 24, 2012 11:54 pm
Location: Stockholm, Sweden

Re: OctaneRender 2020.2 for Houdini Beta build 2020.2.0.2 RC7

Postby juanjgon » Tue Feb 02, 2021 7:38 am

juanjgon Tue Feb 02, 2021 7:38 am
Nope, sorry. You can't export animated .orbx files in full scene reload mode. The exporter only can build animated .orbx files in update mode. The only solution for that is exporting a single .orbx file for each frame rendering frame by frame using a script or a render controller.

What kind of scene do you have that can't be rendered in update mode? Be aware that now the plugin can update the scene even while working with objects without a constant topology.

Thanks,
-Juanjo
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain
Next

Return to Releases


Who is online

Users browsing this forum: No registered users and 0 guests

Wed Apr 24, 2024 4:54 am [ UTC ]
cron