OctaneRender 3 for DAZ Studio [TEST and STABLE] [OBSOLETE]
Moderator: BK
Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.
There appears to have been a delay in posting the subscription release to the Download page (I provide a VR version to Otoy when I post a release here). May I suggest you submit a ticket to Otoy requesting the latest version.An ETA of 3.06 for subscribers?
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Hi Paul,
Reporting on a problem that can consistently be reproduced. Latest plugin version - 3.6.5.33. It has to do with the the Perspective correction and Spherical distortion in the Camera OctaneRender properties. If you use a wide angle for the camera and turn on Perspective correction and set the
Spherical distortion to full, the Octane Viewport shows the effect correctly. Now if the scene is saved and closed and then opened again, the settings of Perspective correction and Spherical distortion are still there under the camera setting as per the last values set, but scene rendered in the Octane Viewport does not have the effect of those settings. One needs to modify the Spherical distortion value and / or turn off and on the Perspective correction and / or switch back and forth between cameras etc to try and get the Octane Viewport to render with the perspective correction and spherical distortion values.
Seems like the values do get saved with the scene and read back properly. But the effect of the settings is missing when the scene is loaded again. I have also noticed the focus point moves back to the middle of the scene in instead of remaining where the focus was before the saving of the scene.
Can you please take a look at this ?
Thanks,
Rajib
Reporting on a problem that can consistently be reproduced. Latest plugin version - 3.6.5.33. It has to do with the the Perspective correction and Spherical distortion in the Camera OctaneRender properties. If you use a wide angle for the camera and turn on Perspective correction and set the
Spherical distortion to full, the Octane Viewport shows the effect correctly. Now if the scene is saved and closed and then opened again, the settings of Perspective correction and Spherical distortion are still there under the camera setting as per the last values set, but scene rendered in the Octane Viewport does not have the effect of those settings. One needs to modify the Spherical distortion value and / or turn off and on the Perspective correction and / or switch back and forth between cameras etc to try and get the Octane Viewport to render with the perspective correction and spherical distortion values.
Seems like the values do get saved with the scene and read back properly. But the effect of the settings is missing when the scene is loaded again. I have also noticed the focus point moves back to the middle of the scene in instead of remaining where the focus was before the saving of the scene.
Can you please take a look at this ?
Thanks,
Rajib
Windows 10 Pro i9-9980XE 128GB RAM|4 x Titan RTX
Houdini 18.5(2020.2.1.2)|Cinema C4D R26|Daz Studio Pro 4.21.0.5(Octane 2021.1.6.83)
NVIDIA 460.89 Studio Standard
Houdini 18.5(2020.2.1.2)|Cinema C4D R26|Daz Studio Pro 4.21.0.5(Octane 2021.1.6.83)
NVIDIA 460.89 Studio Standard
@Lactis:
I am curious if you ever got your system functioning with the current NVidia drivers?
-Notiusweb
I am curious if you ever got your system functioning with the current NVidia drivers?
-Notiusweb
Win 10 Pro 64, Xeon E5-2687W v2 (8x 3.40GHz), G.Skill 64 GB DDR3-2400, ASRock X79 Extreme 11
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise
This is probably best implemented by having a proxy system where an Octane ORBX/OCS file would replace a DAZStudio primitive. However this is a complex change, and unlikely to be implemented in the near future. Your best option at the moment is to export from the DAZStudio Studio to OCS or ORBX and load into Octane Standalone and add the VDB there.When will it be possible to import .VDB files?
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
- Laticis
- Posts: 154
- Joined: Sun May 02, 2010 2:23 pm
- Location: Darwin, Northern Territory, Australia
- Contact:
Hi Notious,Notiusweb wrote:@Lactis:
I am curious if you ever got your system functioning with the current NVidia drivers?
-Notiusweb
Still having some troubles but not so bad. Still getting freezes most of the time its this error: video tdr failure (nvlddmkm.sys)
I started fresh with my system, clean OS of 8.1 Pro Unfortunately. Latest Nvidia Drivers installed.
I am starting to think it may be a faulty GPU but stress testing it has been fine. Only crashes using DS ( Haven't done much with Octane lately too busy )
I have found though that once the system goes down and I restart it seems to go fine.
Either way, its doing my head in. There is still a few months warranty left on my cards, but it one of those things if I send them or one off there goes my system and I need it for work.
I could fork out and buy another GPU but would hate to spend money if it's not them...could be the motherboard.
The most complicated thing about this is the erratic behavior.
How about your system ?
Hello, sorry to hear about the continued issues. My system has an issue as well, albeit under only 1 circumstance...and I've held it at bay for the moment by keeping driver at 372.90.Laticis wrote:Hi Notious,Notiusweb wrote:@Lactis:
I am curious if you ever got your system functioning with the current NVidia drivers?
-Notiusweb
Still having some troubles but not so bad. Still getting freezes most of the time its this error: video tdr failure (nvlddmkm.sys)
I started fresh with my system, clean OS of 8.1 Pro Unfortunately. Latest Nvidia Drivers installed.
I am starting to think it may be a faulty GPU but stress testing it has been fine. Only crashes using DS ( Haven't done much with Octane lately too busy )
I have found though that once the system goes down and I restart it seems to go fine.
Either way, its doing my head in. There is still a few months warranty left on my cards, but it one of those things if I send them or one off there goes my system and I need it for work.
I could fork out and buy another GPU but would hate to spend money if it's not them...could be the motherboard.
The most complicated thing about this is the erratic behavior.
How about your system ?
Using Win 7 64, I can run any combination of card(s) EXCEPT the 6 Titan Z's simultaneously. Something happens in both Daz and Octane standalone in that scenario, where the system freezes upon loading either application.
In Octane, a freeze (predictably) occurs on 2.17 and 3.06.2, and in Daz it could be 4.8 or 4.9, so it's not even version dependant on the application end. It's like the driver can't mix 12 GPU + Win 7 64 or something...Maybe Titan Z is the bad variable if quantity is > 3 cards? I don't know..
Note- I never tried exactly 12 GPU, or 13 Titan X, because I don't have.
3 Titan Z + 2 Titan X + 3 Titan X Pascal (regular, not "Xp") = 11 GPU cores = no issue on any driver > 372.90.
6 Titan Z + 1 Titan X = 13 GPU = Freeze on any driver > 372.90
Weird right? On my system a similar issue as you, but only when powered up with 6 Titan Z running.
I would only imagine suggesting trying 372.90. Do a system restore and back up, then try, if no good I'm thinking you can always go back to the driver you are using.
Win 10 Pro 64, Xeon E5-2687W v2 (8x 3.40GHz), G.Skill 64 GB DDR3-2400, ASRock X79 Extreme 11
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise
Mobo: 1 Titan RTX, 1 Titan Xp
External: 6 Titan X Pascal, 2 GTX Titan X
Plugs: Enterprise
- Laticis
- Posts: 154
- Joined: Sun May 02, 2010 2:23 pm
- Location: Darwin, Northern Territory, Australia
- Contact:
Hi....well it seems I can say the same thing, sorry to hear you are still going through yours. It's not a nice feeling, especially seeing these cards weren't cheap.Notiusweb wrote: Hello, sorry to hear about the continued issues. My system has an issue as well, albeit under only 1 circumstance...and I've held it at bay for the moment by keeping driver at 372.90.
Using Win 7 64, I can run any combination of card(s) EXCEPT the 6 Titan Z's simultaneously. Something happens in both Daz and Octane standalone in that scenario, where the system freezes upon loading either application.
In Octane, a freeze (predictably) occurs on 2.17 and 3.06.2, and in Daz it could be 4.8 or 4.9, so it's not even version dependant on the application end. It's like the driver can't mix 12 GPU + Win 7 64 or something...Maybe Titan Z is the bad variable if quantity is > 3 cards? I don't know..
Note- I never tried exactly 12 GPU, or 13 Titan X, because I don't have.
3 Titan Z + 2 Titan X + 3 Titan X Pascal (regular, not "Xp") = 11 GPU cores = no issue on any driver > 372.90.
6 Titan Z + 1 Titan X = 13 GPU = Freeze on any driver > 372.90
Weird right? On my system a similar issue as you, but only when powered up with 6 Titan Z running.
I would only imagine suggesting trying 372.90. Do a system restore and back up, then try, if no good I'm thinking you can always go back to the driver you are using.
At least yours is consistent but it doesn't make sense, who knows what is going on with the drivers.
That's the part that is hardest, not knowing and potential fixes are cheap
I might do what you say and install 372.90...but after everything I have done I feel it is hardware. MB or GPU...everything was running smoothly for so long.