OTOY Forums

face_off wrote:

. . .

The "Path settings" are not always retained from one Daz session to the next. I'll save some custom paths for the "Project" and "Default," but they randomly get replaced by Octane default values over time.

Deleting C:\Users\[username]\OctaneRender\Data\OctaneRender_settings.oczdb should resolve this issue.

Thanks Paul, deleting that file seems to have helped after re-setting the directory values!

On the other issue I mentioned, where changing the rendering type in the Octane pane had no effect on the Octane viewer (whether that was open at the time of the change or not), that issue has magically gone away . I was trying to create a simple scene to share which demonstrated this issue, so if I eventually see this again I'll try to share a hard example.

Hi Paul,

Any chance we will get a 3.08 version soon ?

Regards,
Rajib

Any chance we will get a 3.08 version soon ?

I need to wait for the next test release of Octane 3.08 for this, and there is no ETA on the test build yet.

Paul

face_off wrote:

Any chance we will get a 3.08 version soon ?

I need to wait for the next test release of Octane 3.08 for this, and there is no ETA on the test build yet.

Paul

Thanks for the update Paul. Btw. is there any doc that I can refer to fully understand the sqlite table data (MaterialPreview OctaneRender_presets.oczdb) or can you PM me that info ? I am trying to build and test the "My Presets" preview image repair tool.

Btw. is there any doc that I can refer to fully understand the sqlite table data (MaterialPreview OctaneRender_presets.oczdb) or can you PM me that info ? I am trying to build and test the "My Presets" preview image repair tool.

I just had a look in OctaneRender_presets.oczdb and it is indeed pretty hard to work out to work out what is what. You might need to delete it (make a copy first) and then add a preset in the plugin and see what tables get populated. Not ideal, but there is no doco on the contents of that database.

Paul

face_off wrote:

Btw. is there any doc that I can refer to fully understand the sqlite table data (MaterialPreview OctaneRender_presets.oczdb) or can you PM me that info ? I am trying to build and test the "My Presets" preview image repair tool.

I just had a look in OctaneRender_presets.oczdb and it is indeed pretty hard to work out to work out what is what. You might need to delete it (make a copy first) and then add a preset in the plugin and see what tables get populated. Not ideal, but there is no doco on the contents of that database.

Paul

That is what I suspected. Will do some RnD. Whatever I manage to figure out, will share.

Paul,

Now that the second 3.08 RC is out. Can we get a test build of the Daz Plugin ? Hope you have been fixing the open items during the past few months.

Btw. I also heard under Carrara Octane plugin Open VDB files are supported. Can the same be added to Daz plugin ?

Regards,
Rajib

rajib wrote:Paul,

Now that the second 3.08 RC is out. Can we get a test build of the Daz Plugin ? Hope you have been fixing the open items during the past few months.

Btw. I also heard under Carrara Octane plugin Open VDB files are supported. Can the same be added to Daz plugin ?

Regards,
Rajib

I already mentioned it to him but I think he gets angry when I tell him that we need VDB in DAZ Studio, because I think that is not in his plans for the plunging in the short or long term. I think that is very difficult to implement.

To be frank, the DAZ Studio plug-in was in a terrible state of development, when Paul took over.
A lot of the more recently introduced Octane features never made (and probably never will make) it into the plug-in, Paul is hardly to blame for that though.

It's essentially still leftovers from t_3...

TRRazor wrote:To be frank, the DAZ Studio plug-in was in a terrible state of development, when Paul took over.
A lot of the more recently introduced Octane features never made (and probably never will make) it into the plug-in, Paul is hardly to blame for that though.

It's essentially still leftovers from t_3...

You're right I agree with you. But as customers we must see improvements, to be able to continue paying the plugin when the fee for the new version is charged again.