OctaneRender® for Poser (Windows/OSX) 3.03.3 [OBSOLETE]

[RGUS]

I've had installed for a few days now nVidia Driver version 344.65 and Octane for Poser after installing this update still shows (computer model 3.5) even though this version was compile against Octane 2.13 which switched to a CUDA 6.5... is that normal for this version and only one Titan card installed in my system?

Hi Deane - the Compute Model is specific to your card and does not change when you update your Cuda drivers.

Paul

Oh... is that what that means... thanks for explaining that.

Now... while I'm here...
If I open the plugin.... then select a material to change, the 'Material List' selects some part on another prop or figure other than I selected. Picking the material in the Render Viewport again picks the correct material in the list. So basically double picking for the first material selected. Not a biggie... but it happens all the time.

[face_off]

If I open the plugin.... then select a material to change, the 'Material List' selects some part on another prop or figure other than I selected.

How are you picking the material?

Thanks

Paul

[RGUS]

If I open the plugin.... then select a material to change, the 'Material List' selects some part on another prop or figure other than I selected.

How are you picking the material?

Thanks

Paul

From the 'Render Viewport' not the 'Render Setup' list

[face_off]

From the 'Render Viewport' not the 'Render Setup' list

Sorry Deane - I am unclear on your workflow. Can you provide the exact steps to reproduce this issue on the default Andy scene?

Thanks

Paul

[RGUS]

From the 'Render Viewport' not the 'Render Setup' list

Sorry Deane - I am unclear on your workflow. Can you provide the exact steps to reproduce this issue on the default Andy scene?

Thanks

Paul

Nope... doesn't happen with default Andy... and after opening closing and changing textures on a V4, it doesn't happen all the time... and in fact is quite intermittent.
I'll keep playing and try to get a consistent workflow that causes it... stay tuned!

[gazukull]

Hi!

Ok, I started to have an issue where objects / body parts that were checked as invisible within poser properties are no visible in Octane.

I scoured the manual to see if something had changed... but I did not see it. Previously, if I had something invisible it would not even be pushed to Octane.



Here is the current figure I am working on. All the appropriate body parts are invisible in poser, they show up in Octane.

System info:

Windows 8.1 x64
16 GB RAM
5 x 780 GTX 3GB
Geforce 344.11
Poser Game Dev 10.0.5.28164 (sr5)
Octane Plug 2.13.0.36

I am just thinking to myself that his behavior may have started after I went to SR5....

Thanks in advance.

-G

[face_off]

Ok, I started to have an issue where objects / body parts that were checked as invisible within poser properties are no visible in Octane.

I scoured the manual to see if something had changed... but I did not see it. Previously, if I had something invisible it would not even be pushed to Octane.

Yes - I am on Poser SR5 and getting the same problem. It only happens when the Poser Subd is > 0, so you can set it to 0 and set Octane Subd to 1 to get around this for the moment, but I will investigate further.

EDIT: This problem does not occur on SR4, so indeed does appear to be a SR5 issue. It has been reported to Smith Micro.

Paul

[gazukull]

Thanks for the quick response as always!

I think I might just roll back to SR4.

- G

[wimvdb]

There is an easy bypass for the invisible problem with subd at 1 - For the invisible body part check "Subdivide separately from figure", then make sure subd level is at 0 and as usual uncheck Visible for the bodypart.
This will render the bodyparts invisible in Octane

[face_off]

A quick update:

1) The "Visibility" issue above as scheduled for being fixed in the next Poser SR.

2) Wim has proved some plugin tips at http://poserphysics.blogspot.com.au/201 ... -tips.html

3) My current plan is for the next release of the plugin to be build with the next release of Octane (2.16? which is likely to be the 2.1 stable release).

Paul