OctaneRender for DAZ Studio 3.02 [OBSOLETE]

[face_off]

Oh so it's only the Standalone that has moved to a final V3 and not the plugins because this forum says "TEST"

The plugin uses the final 3.00 release of Octane (as the release notes state), however there are some issues still which means it is not as stable as the current STABLE release, so I am reluctant to release a /stable/ Octane 3.00 version right now. But the current version of the plugin is not available to users who have not upgraded their licenses to Octane 3.0.

Hard to work out... the site is not the easiest to get around, but if I click around long enough I might find something

https://render.otoy.com/account/octanelive.php

Hell no, I'd be dead before I get an answer from them, even if they are in te same country, communication is non-existant

If you email support via https://home.otoy.com/get-support/ it will go into the help desk system and someone will respond to your issue.

Paul

[Neuroheaven99]

I can't delete my post
deleted text and repost with original quote text missing.
sorry
N.

[Neuroheaven99]

Hi Everyone

I have upgraded to Octane V3 yesterday, Then I have installed the standalone and the latest plugin for DAZ Studio (v3.0.20.22), but the software crash when appear the vieport.

I use Daz Studio Pro 4.9 (last version);
My card is a Gtx 980 (last drivers installed).

Exact same behaviour here.

I cleaned up octane appdata folder, delete some file of the pluggin as once indicated by Paul but nothing is doing it.
reinstalling several time, lets say I've try all I can I think of.

Also note that uninstaling ocds from the "program and feature" remove the tbb.dll file from Daz Studio install folder preventing it to launch (saying tbb.dll cannot be found on your machine, try to reinsall the product ...)

> update: seems that the last ocds version uninstaller do no remove the tbb.dll file (only previous 'beta' seem to do this)
So without ocds Daz is runnng fine.

Reinstalling ocds to try again but blocked again on the crash during or when activating...

I looked at my otoy license page when DAz has the crash error message and the ocds license is seen as activated!

weird :-/

Daz 4.9.2 last release, nvdia drivers 361.43, win10 64b

Octane standalone v3.0 is running fine.

4 am I give up

ciao

[larsmidnatt]

I do not believe that region render is working properly.

STR:
Start a render
Use the region render/spot render feature in OcDS
Observe regions outside of selected area resolving at the same rate as the selected area

Seems like the entire image is resolving at the same rate, not just the nearby tiles or anything focused.

[linvanchene]

I do not believe that region render is working properly.

STR:
Start a render
Use the region render/spot render feature in OcDS
Observe regions outside of selected area resolving at the same rate as the selected area

Seems like the entire image is resolving at the same rate, not just the nearby tiles or anything focused.

I was not able to reproduce this with
Daz Studio Pro BETA - version 4.9.2.70
OcDS 3.0.20.22

Make sure to use the Region Rendering tool located in the OcDS viewport.
Using the DAZ Studio "Spot rendering tool" will not have any effect.

For testing try again with PMC mode and extremely large dimension values like 6000x4000 to better observe the effect.


Quick OcDS Region Rendering guide:

viewtopic.php?f=44&t=54401

- - -

Side Note:
Daz Studio Pro BETA - version 4.9.2.70 - Public (Beta) Release
http://www.daz3d.com/forums/discussion/ ... ted#latest

is identical to the latest official

Daz Studio Pro 4.9.2.70 - General release.
http://www.daz3d.com/forums/discussion/ ... ase#latest

-> I use the BETA release always for convenience so I do not have to switch between general and public release every few months.

[larsmidnatt]

@Lin, yeah I know how region render works, been using it a long time. It just stopped working for me in 3.0 test. Hence me specifically saying the OcDS plugin. I didn't have this problem in 2.x. Only reason I said spot render is cause I couldn't remember which phrase was used for OcDS I use em interchangeably.

Resolution isn't the issue, I thought because of the new tile rendering that may have been the reason, but not so much. And you shouldn't need PMC mode, I rarely use that. PT is fabulous for most scenarios.

Thanks though.

If it happens to be 4.8 specific, that sucks because I really use the region render a lot. I can prove it doesn't work very easily

STR:
Load character
Set region render area around head
change character shape/height dramatically

ER: Region render would only update head area
AR: Entire frame is redrawn to match changes

It flat out doesn't work.

[larsmidnatt]

I upgraded to 4.9 in hopes to get region render to work and it did not fix anything.

Installed 2.x again. 2.x and 4.8 are working as expected regarding the region render tool. So I will go back to that as my main. I still have 4.9 and OCDS 3 installed separately but no real benefit to 3.x at this time so I'll just wait it out.

And as a bonus surprise...I was able to open my 3.0 saves with 2.x and no crashing or exploding so far...Only tested one file so far...but makes me happy. Only have 3 projects i put into 3.0 but I wanted to go back to them and wanted to try them in 2.2 and they are ok Thats amazing and lucky, never worked like that before.

[face_off]

STR:
Start a render
Use the region render/spot render feature in OcDS
Observe regions outside of selected area resolving at the same rate as the selected area

I could not re-produce any issues with the Render Region functionality on the next release of plugin. So I suggest you re-test it on the next release once it's posted in the next couple of days.

Paul

[larsmidnatt]

sounds like a plan Paul, thanks.

[Laticis]

Hi Paul,

My license where sorted today so I have been able to start testing.

Installed okay, DS plugin open fine......old scene opened fine....basically up and running now.
One thing I noticed, before use to be able to to double click on materials and it would take me to the Nodegraph Editor
but now I see the only way is the click on the Nodegraph Editor button.