OTOY Forums

Thanks Paul, I understand V2 and V3 are different, and I appreciate the response and the hard work.

I am surprised this even worked, and I believe there would be potential for crashes using this approach.

If this is the case, can we then have a "Legacy JPEG image export" mode in preferences, with a disclaimer that it is not recommended by the developer.
Rationale for reinsertion could be: "There was user request for legacy .jpg image export support due to JPEG's smaller file size and unique EXIF data format. As such, "Legacy JPEG image export" mode was added to preferences with disclaimer that it is not recommended by the developer due to potential concerns with Octane 3 API."

Set it to default "Off" and let the user decide to suffer any consequences. Notify us in update that there is "Option for Legacy JPEG image export added (outdated and not recommended)"

Can we have this, consider that there are any # of things that the plugin can do that the standalone cannot do (ie render Daz animations, etc.), so the plugin need not be contingent upon what the standalone does in all regards, especially since OcDS could do it, in its Alpha 1 and 2, of V3. (OcDS did it in V2 while Octane standalone did not in its V2)...After all, you said it best yourself, "I am surprised it even worked". Please don't force it to not work and let us have an option to choose a mode at least.

Thanks for the time and support!

If this is the case, can we then have a "Legacy JPEG image export" mode in preferences, with a disclaimer that it is not recommended by the developer.

The legacy DAZStudio code to save to JPEG does not work at all with Octane 3. No file is saved. The JEPG process times out because it cannot get the render image data.

Paul

The legacy DAZStudio code to save to JPEG does not work at all with Octane 3. No file is saved. The JEPG process times out because it cannot get the render image data.

Paul

Thanks Paul. I know you removed it between 3.0.06 and 3.0.1.7 (based on V3's transition alpha 1 to alpha 2). You explained you removed it as it might potentially cause crashes.
I know we had option and ability to render still frame or animation frame JPEGs at 3.0.0.6, which had the V3 medium/scattering/volume stuff (shown below with my pics).
We do not have it in 3.0.1.7. But then I ask if we can have a legacy mode and you said it does not work at all with Octane 3. But it would only be legacy after 3.0.0.6, which was 3...see my confusion
Did it work in Alpha 1 and stop working in Alpha 2? At least I can address that with OTOY specifically to troubleshoot.
The resulting still frame .jpg is attached, rendered with OcDS 3.0.0.6.
Thanks.

I know you removed it between 3.0.06 and 3.0.1.7 (based on V3's transition alpha 1 to alpha 2). You explained you removed it as it might potentially cause crashes.
I know we had option and ability to render still frame or animation frame JPEGs at 3.0.0.6, which had the V3 medium/scattering/volume stuff (shown below with my pics).
We do not have it in 3.0.1.7. But then I ask if we can have a legacy mode and you said it does not work at all with Octane 3. But it would only be legacy after 3.0.0.6, which was 3...see my confusion
Did it work in Alpha 1 and stop working in Alpha 2? At least I can address that with OTOY specifically to troubleshoot.

I'm sorry, I don't know when it stopped working, and it's not a trivial matter to retest the plugin against previous version of the Octane API, since I need to rollback the plugin code, which in turn rolls out other internal changes to the plugin that were made for Octane 3. I can try and re-activate the code in a future Octane alpha/beta build is you like. However at the moment I am trying to fix bugs, address crashes and implement Octane 3 functionality - so if there is suspect code in the plugin which if not working, it's a no-brainer to disable it.

Paul

I'm sorry, I don't know when it stopped working, and it's not a trivial matter to retest the plugin against previous version of the Octane API, since I need to rollback the plugin code, which in turn rolls out other internal changes to the plugin that were made for Octane 3. I can try and re-activate the code in a future Octane alpha/beta build is you like. However at the moment I am trying to fix bugs, address crashes and implement Octane 3 functionality - so if there is suspect code in the plugin which if not working, it's a no-brainer to disable it.

Paul

I appreciate it Paul. I understand. As a user in a production relationship things like this are not small for me, so I go after it.
I would, yes, very much like to see the code reactivated.
Thanks again,
Notiusweb

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

3.0.3.8
- Compiled with Octane 3 alpha 3
- Add manual page for Octane 3 features - https://docs.otoy.com/DazStudio/?page_id=1237
- Fixed bug where node names could not be changed in the NGE
- Reworked the display of the amount of VRAM being used, since the calculations were incorrect. Now only the VRAM numbers returned by Octane are displayed - and these should be accurate.

Paul

face_off wrote:I have refreshed the installer at the top of this thread with:

3.0.3.8
- Compiled with Octane 3 alpha 3
- Add manual page for Octane 3 features - https://docs.otoy.com/DazStudio/?page_id=1237
- Fixed bug where node names could not be changed in the NGE
- Reworked the display of the amount of VRAM being used, since the calculations were incorrect. Now only the VRAM numbers returned by Octane are displayed - and these should be accurate.

Paul

Thanks Paul . Will give it a go. I had been away so had skipped on the last update. Now back and need to get rendering again. Will report what I find.

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

3.0.3.9
- Added Cutout Opacity to the Template options

Paul

Since after Daz 4.6 + plugin 2.x, the Daz Studio has been really really really slow for even moderate scenes. Is this a known issue? And which is it coming from? Daz 4.8 or plugin 2.(later)/3.0? Has anyone else noticed the dramatic slowdown?

Thanks,

Hi Paul, just a quick question :
I still haven't use the Octane version because of the fireflies issue. Is this issue still present ?

Anyway, I'm checking the forum and I see that the updates come out steadily. Thanks a lot