OTOY Forums

This is the recommended thread for downloading, and posting any questions, suggestions or support queries for OctaneRender for Poser TEST and STABLE releases.

SOLUTIONS TO COMMON ISSUES

1) Make sure your NVIDIA drivers are up to date.

2) Make sure you have the latest Poser Service Release installed.

3) Pls read http://poserphysics.blogspot.com.au/201 ... pport.html prior to posting support issues.

4) Cuda error 999 - failed to load shader code: Multiple definition of 'cpSptStatistics' in 'cuda_teturemode' means that your plugin version is too old for the Nvidia drivers that are installed, so update to the latest version of the plugin.

5) LiveDb materials containing OSL nodes will not load into the plugin correctly. The plugin does not currently support OSL Projection or Texture nodes. Instead, copy these Livedb materials into the clipboard from Octane Standalone and paste them into a NodeGraph material in the plugin.

5) If you get render artifacts at a joint between two Body Parts of a Figure, switch the Figure's Skinning Method to "Poser Unimesh".

Poser Version
This release only runs on Poser 12 and Poser 13. It will not run on Poser 11

To use this version, you need a GPU of compute model 3.0 or higher. Support for Fermi GPUs (like GTX 4xx and 5xx) has been dropped. Also make sure you use a driver of version 452 or higher and if you are working on Mac OS that have a CUDA driver installed that supports at least CUDA 9.1.

Network Rendering
For Network Rendering, you must use the Octane slave release from the Octane Standalone installer which matches the exact Octane version of the plugin you are using.

Support Issues
If you have a support issue, pls provide the following information:
- OctaneRender for Plugin version (ie. 2.23.1.56)
- Poser version (Poser -> Help -> About Poser) - list the build number (eg. 9.0.3.23027)
- Operating System (ie. Win XP, Vista, 7, 8)
- Amount of RAM
- Graphics Card(s) - model (ie. GTX 580, 3GB)
- Nvidia driver version

Also have ready a copy of
- octaneplugin.log and cuda.log file from your Poser temp direction (Poser -> Edit -> General Preferences -> Misc tab to find the temp directory), and
- config.xml, which is in C:\Users\[username]\AppData\Roaming\Poser Pro\9 for Poser 9/2012 and C:\Users\[username]\AppData\Roaming\Poser Pro\10 for Poser10/2014.

If you have questions
- Read the latest up-to-date on-line manual
- Read Wim's Poser Plugin User Guide
- Watch the Features Video
- Read the Features Blog Posting
- Watch the Introductory Tutorial
- Watch the Instancing Video
- Watch the HDR Light Studio Video
- Post your question on this forum thread

Download Links

Current STABLE build for Poser 12 and Poser 13 (Octane 2024.1)

• For users with a Studio+ subscription license
  • - Windows - OctaneRender for Poser 2024.1.0.125
  Demo version
  • - Windows - OctaneRender for Poser 2024.1.0.125

Release Notes

2024.1.0.125 (29-Sep-2024)
- Compiled with Octane 2024.1
- Added all the 2024.1 features from viewtopic.php?f=33&t=82267
- Added the Output AOVs "Apply LUT", "Open Image Denoise", "Texture" and "Dither for 8-bit display" nodes from Octane 2024.1
- The "Output AOV"->"Apply Imager and Post Processing" node from Octane 2024.1 has not been added to the plugin
- The "Value"->"Time" node from Octane 2024.1 has not been added to the plugin
- Saved images from an animation are now saved with a filename in the format "[Poser scene filename]_[frame number].png/exr"
- When exporting a material, the default filename is now the prop/figurename followed by the material name
- When exporting an animation, the default filename is now the Poser scene filename
- When exporting all materials for a figure/prop, the default filename is now the figure/prop name

Paul

Thanks for the update
Is it the same version as in viewtopic.php?f=45&t=82277&start=20#p433986 ? (as it has the same version number, but it's compiled to a different 2024 version of OR?)

Erick wrote:Thanks for the update
Is it the same version as in viewtopic.php?f=45&t=82277&start=20#p433986 ? (as it has the same version number, but it's compiled to a different 2024 version of OR?)

The build in that thread was a pre-release, so this has some python code changes, and is build with the final Octane 2024.1 release.

Paul

face_off wrote:

Erick wrote:Thanks for the update
Is it the same version as in viewtopic.php?f=45&t=82277&start=20#p433986 ? (as it has the same version number, but it's compiled to a different 2024 version of OR?)

The build in that thread was a pre-release, so this has some python code changes, and is build with the final Octane 2024.1 release.

Paul

Alright! Thank you

Hey Paul,
I know this when exporting animation. The plug-in still refreshes vertices each frame even though I unchecked refresh geometry each frame. I also have refresh scene each frame unchecked as well.
Is that a bug?

spartan00j wrote:Hey Paul,
I know this when exporting animation. The plug-in still refreshes vertices each frame even though I unchecked refresh geometry each frame. I also have refresh scene each frame unchecked as well.
Is that a bug?

Hello. Yes, the two "Refresh" options apply to rendering the animation rather than exporting. The idea behind exporting the animation is that it is the only way to render vertex motion blur - and for this it needs every vertex of every frame. So exporting the animation ignores those "Refresh" options, and yes, the tooltip could be clearer on this.

Paul

face_off wrote:

spartan00j wrote:Hey Paul,
I know this when exporting animation. The plug-in still refreshes vertices each frame even though I unchecked refresh geometry each frame. I also have refresh scene each frame unchecked as well.
Is that a bug?

Hello. Yes, the two "Refresh" options apply to rendering the animation rather than exporting. The idea behind exporting the animation is that it is the only way to render vertex motion blur - and for this it needs every vertex of every frame. So exporting the animation ignores those "Refresh" options, and yes, the tooltip could be clearer on this.

Paul

Okay I understand. But what if I don't want to render out motion blur.
There are times I just want the camera animation.

Okay I understand. But what if I don't want to render out motion blur.
There are times I just want the camera animation.

Understood. However the original intention of exporting to Octane Standalone was to render vertex motion blur, so that's what the Export Animation function does. I understand that now with cloud rendering, etc there are other potential objectives for exporting to ORBX, however they will need to be done exporting all geometry for each frame.

Thanks

Paul

I have posted the Octane 2025.1 version of the plugin at viewtopic.php?t=84694.

Thanks

Paul