OTOY Forums

I've noticed the cameras created while Octanerender is active turns out of focus if rendered in 3Delight. Is there a way to "fix" the camera so one can render in 3Delight if one wants to. i've also noticed that in the first release I could open another session of DAZ Studio and just create another camera with the same position as the Octanerender camera so I could use 3Delight as an option but since the latest beta I cannot open a DAZ Studio scene that has been saved with Octanerender active so another session of Studio won't open the scene in question.

SimonWM wrote:I've noticed the cameras created while Octanerender is active turns out of focus if rendered in 3Delight. Is there a way to "fix" the camera so one can render in 3Delight if one wants to.

in the (most probably) next update the focal distance control will be separated for octane and DS. i admit, with all the different focusing options for octane it gives not much sense to have these two coupled. if i understand you right, this should solve that. more about that here: http://render.otoy.com/forum/viewtopic.php?f=44&t=29895

SimonWM wrote:i've also noticed that in the first release I could open another session of DAZ Studio and just create another camera with the same position as the Octanerender camera so I could use 3Delight as an option but since the latest beta I cannot open a DAZ Studio scene that has been saved with Octanerender active so another session of Studio won't open the scene in question.

afaik this was never possible (at least if i - again - understand you right); if you start DS a 2nd time with the plugin, it will just cease to work. if what you saying is, it didn't crash then, but it crashes now - this is probably possible but not intended a crash during load might come (and go) silent, resulting in just nothing showing up, if this is what you see. will need a workaround, will need some time...

t_3 wrote:

SimonWM wrote:

SimonWM wrote:i've also noticed that in the first release I could open another session of DAZ Studio and just create another camera with the same position as the Octanerender camera so I could use 3Delight as an option but since the latest beta I cannot open a DAZ Studio scene that has been saved with Octanerender active so another session of Studio won't open the scene in question.

afaik this was never possible (at least if i - again - understand you right); if you start DS a 2nd time with the plugin, it will just cease to work. if what you saying is, it didn't crash then, but it crashes now - this is probably possible but not intended a crash during load might come (and go) silent, resulting in just nothing showing up, if this is what you see. will need a workaround, will need some time...

I understand what you say; there can only be one DAZoctanerender session active. What I mean is that in the first beta, the second DAZ Studio session with no Octanerender loaded (inactive) I could open the same duf scene (saved from the first Studio session) and select the out of focus camera and tell DAZ Studio to copy the settings of that camera. With the updates looks like I cannot open the duf file if it has octanerender data and octanerender is not loaded.

SimonWM wrote:I understand what you say; there can only be one DAZoctanerender session active. What I mean is that in the first beta, the second DAZ Studio session with no Octanerender loaded (inactive) I could open the same duf scene (saved from the first Studio session) and select the out of focus camera and tell DAZ Studio to copy the settings of that camera. With the updates looks like I cannot open the duf file if it has octanerender data and octanerender is not loaded.

yeah, most probably because it crashes (silently). if you look into the DS log file after closing the 2nd session (when it did not load) i expect you see soemthing like "error while loading...". the way the pluging currently quits a 2nd session it rather dirty. my problem here is i can't shut it down completely (otherwise you will loose all data if you save a octane scene in this state), so it needs to still at least active to a point where it reads the octane data, and securely saves it again if the scene is saved. and apparently this works not as expected. in the first beta it would have most probably not saved the data back, so this was also not really the wanted behavior...

Hmm, I've been getting errors that say Microsoft Visual C++ Runtime Library, Runtime Error Program:C\ProgramFiles(x86...
R 6016 -not enough space for thread data This after closing DAZ Studio. This didn't happen before. Now I think that might have been that silent crash.

SimonWM wrote:Hmm, I've been getting errors that say Microsoft Visual C++ Runtime Library, Runtime Error Program:C\ProgramFiles(x86...
R 6016 -not enough space for thread data This after closing DAZ Studio. This didn't happen before. Now I think that might have been that silent crash.

most likely. after sthg. like that happens, everything is really mixed up. there are 3 stages where DS supresses any crash: during scene clear, during load, and during save. makes it really hard to get by possible problems in this areas btw...

Just found out the way to fix the Octanerender cameras for use in 3Delight is simply to turn off "Depth of Field" and then you can render in 3Delight. That was easy!

SimonWM wrote:Just found out the way to fix the Octanerender cameras for use in 3Delight is simply to turn off "Depth of Field" and then you can render in 3Delight. That was easy!

btw, in the next update these settings (including the dof switch) are already decoupled. in the end it seems it had more disadvantages than advantages to bind the daz switches/values to octane and vice versa. so dof will be controlled through the common aperture and a new octane-only f/stop (which one you prefer), and focal distance is now also independent. there are already a lot focus options for octane, and in addition you can always grab the current daz camera focal distance...

t_3 wrote:

SimonWM wrote:Just found out the way to fix the Octanerender cameras for use in 3Delight is simply to turn off "Depth of Field" and then you can render in 3Delight. That was easy!

btw, in the next update these settings (including the dof switch) are already decoupled. in the end it seems it had more disadvantages than advantages to bind the daz switches/values to octane and vice versa. so dof will be controlled through the common aperture and a new octane-only f/stop (which one you prefer), and focal distance is now also independent. there are already a lot focus options for octane, and in addition you can always grab the current daz camera focal distance...

Sounds great! Can't wait! Let me know when you start working on LIE support and I can send my sets via dropbox and test if necessary.