OTOY Forums

face_off wrote:

Haven't had a chance to test the latest (and I'm at work ATM), so I'm not sure if this has been fixed at this point ...

In any case, if you could address this one, I'd be appreciative:

viewtopic.php?f=44&t=47686&p=254293#p254293

I could not reproduce this issue on the latest release (2.24.2.5).

Paul

Thank you. Was able to retest and can confirm it is now fixed.

Regards

something was changed on network rendering again? worked like a charm, since i updated to .5 version it doesnt autostart sometimes or doesnt work. but maybe its just me, even if i have no idea why

something was changed on network rendering again? worked like a charm, since i updated to .5 version it doesnt autostart sometimes or doesnt work. but maybe its just me, even if i have no idea why

Nothing changed with Network Rendering on 2.24.2.5. "doesnt work" doesn't give a lot of info to trace down your problem. In general, firewall seem to be the biggest impediment.

Paul

works again, was my own fault the reason was that i rendered one image while opened up another instance of daz studio to prepare the next picture... didnt work for number 2 then. same kind of mistake as it is on GOZ for example, but not the fault of the plugin itself so nevermind

btw once again, thank you so much for that fantastic work you all do on this plugin, now its getting really gold and fun to work with!

So far so good. Old scenes are working from what I can tell.

need some time to really test though

But I do want to say thanks for the work and I am excited for the future. Using the OcDS plugin is typically a bright point in my day so I am happy to see it isn't over just yet. I will report issues as best I can when they arise. But I am a bit jaded as I have learned to work around the quirks...so I might unintentionally avoid them and I can't remember all the issues I reported historically. Typically the stuff I reported was later avoided...but anyway thanks for the update.

I am aware that now may not be time to look into this.
But I guess it should also be mentioned in case this is not a well known issue:


OctaneRender specific camera values?

I noticed when exporting from OcDS to OctaneRender standalone the camera values Focal length and F -stop values seem to be different.

As far as I remember this was not the case in earlier combinations of DAZ Studio and OcDS.
Focal length values in OcDS used to match up with the focal length values in OctaneRender standalone.
F - stop values used to yield a somewhat accurate image similar to real world values.

Then DAZ3D may have changed some camera related settings in 4.7 in order to prepare for the Iray release .
In any case at least since 4.8 now the focal length and F-stop values do not anymore match up at all when exporting to OR standalone.

- - -

Is it possible to somehow reverse engineer the camera values so that when we use OctaneRender camera sliders for focal lengths and F -stop in OcDS already the corrected values will be displayed that will be used when importing the scene in OR standalone?

Basically this would mean:
- DAZ Studio camera sliders show DAZ Studio camera values
- OcDS camera sliders show OctaneRender standalone camera values
- OcDS camera sliders use limits to make sure no extreme values are selected that cannot be processed properly when importing in OR standalone.

- - -

Alternatively:

In the long term it might be interesting if we could add a "real" OctaneRender "Thin lense camera" to the scene that uses exactly the same camera values as the cameras in OctaneRender standalone.

Instead of using the option "Add default Camera" OctaneRender for DAZ Studio users could use the option " Add Thin lense camera" to place an OctaneRender camera in the DAZ Studio scene.

As the DAZStudio plugin will be coming out of beta shortly, I have moved this thread from TEST to STABLE status. New TEST releases will be posted at viewtopic.php?f=44&t=51808&p=258727#p258727

Thanks

Paul

FACEOFF.......... UR DA MAN........!!!!!! Glad you in this corner bru......!!!!

Hi Paul,

I have a bug with the last release 2.24.2.5 (with one scene I test yesterday) :
- load a G3F
- apply hair
- apply TGX shader (or not)
- set HDRI
- test render : OK
- export to orbx (to test on OR 3 alpha) : Good and faster
- save scene.
- delete orbx (was for test)

restart DAZ :
- reload scene
- on system log : could not find orbx !!?
- all textures are lost !

Has discover this also on the test version 3.0 of OcDS.
Hope that could be fixed on this version. Else do not save after export to orbx (only test this export)