OctaneRender® for Poser beta - build 1.02q [OBSOLETE] Tweet

[C3Design]

Could you be more specific as to exactly where the plug in files are supposed to reside in the PoserPro folder. I've followed the very brief explanation in the PDF and cannot get the plug-in to load when I start Poser. I have Poser Pro 2010, is that the issue? I'd think that if it works in Poser 9 it would work in 2010.

[wimvdb]

Could you be more specific as to exactly where the plug in files are supposed to reside in the PoserPro folder. I've followed the very brief explanation in the PDF and cannot get the plug-in to load when I start Poser. I have Poser Pro 2010, is that the issue? I'd think that if it works in Poser 9 it would work in 2010.

The plugin needs either Poser 9 or Poser Pro 2012. Those are the latest versions. PP2010 is an older version which does not support the plugin modules.

[wimvdb]

I had a problem with a large scene (in number of textures used)
I was updating the materials (selecting in the Poser mat room, then copy/paste materials and some manual changes)
This goes ok for a while (reusing already existing materials) then suddenly a multitude of Cuda errors popup (possibly for each material a separate popup in quick succession).

Attached the cuda log

Edit: Attachment did not work, here is the log file pasted:
Opening OctaneRender for Poser Setup Dialog
Closing OctaneRender for Poser Setup Dialog
Opening OctaneRender for Poser Setup Dialog
CUDA error 999 on device 1: An unknown internal error occurred.
-> Kernel execution failed (pt)
CUDA device 1: Path tracing failed
CUDA error 999 on device 1: An unknown internal error occurred.
-> Failed to copy 2D memory to device
CUDA device 1: Failed to initialise preview RNG buffer
CUDA error 999 on device 1: An unknown internal error occurred.
-> Failed to deallocate device memory
CUDA error 999 on device 1: An unknown internal error occurred.
-> Could not get memory info
CUDA error 999 on device 1: An unknown internal error occurred.
-> Failed to deallocate device memory
CUDA error 999 on device 1: An unknown internal error occurred.
-> Could not get memory info
CUDA error 999 on device 1: An unknown internal error occurred.
-> Failed to deallocate device memory
CUDA error 999 on device 1: An unknown internal error occurred.
-> Could not get memory info

Edited again:
If you continue (without the viewport open), Poser will eventually crash (I did not reset the cuda device here)

[face_off]

Hi Wim

Did you have the Material Preview turned on (MATERIAL_PREVIEW_SAMPLES > 0)?

I have changed the behavior of the cuda error handling in a patched version of 1.02q, which I will post shortly. It should give you a better chance of reseting the card.

From what I can tell, Cuda error 999 appears to be a graphic card failure, and I haven't seen it specifically caused by the plugin. It appears to mean the graphics card failed to start rendering. I get it occasionally with the plugin and Octane Standalone. I have noticed if you leave the plugin open for a few hours, then open the viewport, there is a higher probably of getting 999.

Paul

[wimvdb]

Yes, I had material preview on.

That problem seems to occur when you add image maps. At some point Octane (or cuda) gets the error. Maybe something wrong with garbage collection in Cuda
In one particular occasion I had two image maps. One was a bump map and the other a blend map. When I changed the blend map texture to the bump map texture, the error occurred.

You can only stop the sequence of popups by stopping the plugin. After cleaning up you have to restart Poser otherwise it gets unstable (crash may occur)

[face_off]

Wim, the material preview is quite experimental, and based on some feedback, I think it's best left off When you change a node in the material tree, the Octane engine immediately needs to refresh the nodes and restart the render AND it needs to generate the material preview - and I think that's where you Cuda error came from. Ideally there would be a pause between the above 2 actions, however that would simply introduce another delay. I'll leave the material preview in for the moment in case other people want to check it out.

[face_off]

I have updated the 1.02q installer to include the following changes:

- When finishing rendering an animation, if the update geometry checkbox is OFF, the vertices are no longer refreshed
- Added addition logging for node creation
- Fixed issue where assigning an image file was sometimes not working during rendering
- Fixed issue where File -> Revert was not correctly loading Octane settings from the pz3 file
- Added the ability to load and save kernel and imager settings

Pls re-download 1.02q and reinstall.

Thanks

Paul

[mlru]

I wonder if it would be possible always to do a 'select' when an input field gets 'focus'?
Would make entering of values a lot more fluid in cases when there are more than one input field (X+Y, X+Y+Z)
By now you have to -mark/delete/position the cursor in- the given value after switching with the Tab key to the next field instead of being able to just overtype the selected content.

Uwe

[face_off]

I wonder if it would be possible always to do a 'select' when an input field gets 'focus'?

I have this on the list for the next version. It was bugging me too

[mlru]

Cool. Thanks Paul!