OTOY Forums

Hi there Paul. long time no talk,

Ive been getting this errorwith the last 4 or 5 updates and its getting more frequent. If you look at the image at the bottom where it says messages you will see the sequence of the error messages. this happens under PMC and Pathtracing Kernel, I thought it might be something to do with overheating or driver crashes but none of the sorts. when I close Daz and start again everything works well. hope you can help me with this. Thanx again!

Redz

Ive been getting this errorwith the last 4 or 5 updates and its getting more frequent. If you look at the image at the bottom where it says messages you will see the sequence of the error messages. this happens under PMC and Pathtracing Kernel, I thought it might be something to do with overheating or driver crashes but none of the sorts. when I close Daz and start again everything works well. hope you can help me with this. Thanx again!

Looks like a faulty card. The most important log message will be for the first one (scroll down to the bottom of the log). Have you tried turning off one or more of your cards to identify which might be causing the issue?

Paul

I have actually disabled the Gigabyte GTX780 ti GHZ edition, and so far so good.... Seems they are pushed a bit far on the overclocking, Ill test and just make sure.... Thanx Paul.

PS has the question of whether HDR Lightmap would create a bridge for Daz Studio been asked to them internally?
Just wishing there was a heads up about it ever happening or not by chance.

This is something I can implement - as I have done with the Poser plugin. However it's sufficiently complex enough that I would rather wait until the DAStudio plugin bug list is shorter, and Octane 3 is further down the development cycle. I suggest re-raising this issue in a few months.

Paul

Hi Paul
I didnt used the plugin for a while, or i'm getting old. How do you do the turntable rendering? Or was that something you had to do in the Standalone Renderer? I dont remember, it's been ages since i did that last time.
Would be great if there was a easy way to create Turntable Renderings in the DAZ Plugin itself, if that would not be to complex to program.
Thanks for your help and support. The last month where lightyears of pogress.

How do you do the turntable rendering? Or was that something you had to do in the Standalone Renderer? I dont remember, it's been ages since i did that last time.
Would be great if there was a easy way to create Turntable Renderings in the DAZ Plugin itself, if that would not be to complex to program.
Thanks for your help and support. The last month where lightyears of pogress.

You will need to animate the camera to rotate around the item you want to o the turntable animation for.

Paul

I second Paul :
- create a null and center it at the figure you want to turn around.
- place the camera in the scene targetting the figure.
- parent it to the null (camera under null in the scene tab)
- add a keyframe at the first frame in null rotation parameter
- go to mid animation timeline, set 180 to the Y rotation of null
- go to end animation timeline and set 360.
--> you have your turn-around.

Thanks a lot Paul and itou. Finally learned something again! It's quite simple if you know how to do!

Paul, hope all is well. I have to ask you about this:

- Removed all saving to JPEG format options (since this was conflicting with Octane 3)

This is causing some problems.
1 Windows OS Meta data are not same for PNG as they are for JPEG. PNG does not embed same EXIF info as JPEG.
2 PNG files are much larger as resolution increases (I had in V2 compared a 500-sample 3840x2160 JPEG @981kb vs PNG 38.1Mb), PNG-only will make for very heavy file space usage (ie animation frames)

On a partnered production level, this is a workflow pain to have to go and convert back to JPEG so that they can be emailed, uploaded, etc.

Just looking to see if this is something that will be returned to the V3 of OcDS. While .jpg is not currently available as an export format by the Octane Standalone, as precedent it is supported by Daz Studio itself (ie for still frame and animations).
Curious too, what way was it conflicting with V3 to have an export to JPEG.

Thanks.

Just looking to see if this is something that will be returned to the V3 of OcDS. While .jpg is not currently available as an export format by the Octane Standalone, as precedent it is supported by Daz Studio itself (ie for still frame and animations).
Curious too, what way was it conflicting with V3 to have an export to JPEG.

Sorry this has caused you problems. Saving to JPEG was implemented in the Octane 2 version of the plugin by having the JPEG save process grab the render buffers in the Octane API, whilst the Viewport was also accessing the same render buffers. I am surprised this even worked, and I believe there would be potential for crashes using this approach. This method does not work at all in the Octane 3 API, in that the JPEG save process is unable to get access to the render buffers whilst the Viewport is open. So saving to JPEG is something that the Octane API would have to support, so may I suggest putting this to Otoy as a feature request.

Paul