OTOY Forums

Paul here's one that kinda interesting- anytime I save a pose to one of the pose dots, it forces a plugin refresh. And if I use that same dot to revert back to the original pose, it does not force a refresh.

Thanks Sam

face_off wrote:I couldn't reproduce this problem, so I suspect there is an figure/prop in your scene which is triggering this. Does the above error occur with the default Andy scene? If you can send me the simplest scene this occurs with, I can track the problem down. Also, there are some issue with displacement in 2.02 which are fixed in the next release (available very soon). So if that scene had a displacement map, it may have caused that error, but will be fixed in the next release.

Paul

Okay I will try later
(But something is pretty interesting, after I hit the 'stop update' button, if I don't change the scene and hit it again, error. If I change it, and then hit the button everything is fine.)

Steven

Hi Paul
Default Scene works fine alone with any other scene that i created, should be a problem with props.

Goin to do further test tomorrow ^^

Steven

I have refreshed the installers at the top of this thread with:

2.3.0.21
- Compiled against Octane 2.03, which fixes a number of displacement mapping issues
- Added option in the configuration to disable the conversion of displacement maps when converting Poser materials to Octane materials
- The camera->fov and focalDepth are now animated when exporting an animation to ORBX/ABC format
- Once a render is completed, the result is saved to "LastOctaneRender.jpg" in the Poser Temp Directory
- Resolved camera gimbal lock issues at certain camera angles (in both normal rendering, and with motion blur/export to ABC)

A reminder, make sure you are not running Poser when installing any Octane plugin update.

Paul

Due to an issue with the installer for the above release, I have rolled back to 2.2.0.20 for the time being.

Paul

face_off wrote:Due to an issue with the installer for the above release, I have rolled back to 2.2.0.20 for the time being.

Paul

Yeah the octane render button is mission after I install it :O
Don't worry , it will be fixed real quick

The installer issue is now resolved, and I have again refreshed the installers at the top of this thread with:

2.3.0.21
- Compiled against Octane 2.03, which fixes a number of displacement mapping issues
- Added option in the configuration to disable the conversion of displacement maps when converting Poser materials to Octane materials
- The camera->fov and focalDepth are now animated when exporting an animation to ORBX/ABC format
- Once a render is completed, the result is saved to "LastOctaneRender.jpg" in the Poser Temp Directory
- Resolved camera gimbal lock issues at certain camera angles (in both normal rendering, and with motion blur/export to ABC)

A reminder, make sure you are not running Poser when installing any Octane plugin update.

Paul

Thanks for the update, Paul.

Rendering a scene right now, quite similar to the one, which always crashed for me in the previous version (the CUDA 999 error).
It's rendering for over an hour by now and goes perfectly smooth so far
Looking very promising right now.
Thanks for all the excellent work.

This is a great update! But what does this mean?

Started logging on 17.07.14 01:10:10

OctaneRender version 2.03 (2030000)

Could not load HDR result, because we have no render threads.

Find a bug. When loading an animation and click Auto Refresh to ON and then move the timeslider, the render runs in a loop and never stops. It just keeps restarting when it hits max samples.