OctaneRender for DAZ Studio 2022.1.1 - 304 [OBSOLETE]

Forums: OctaneRender for DAZ Studio 2022.1.1 - 304 [OBSOLETE]
DAZ Studio Integrated Plugin (Integrated Plugin maintained by OTOY)

Moderator: BK

Forum rules
Please keep character renders sensibly modest, please do not post sexually explicit scenes of characters.

OctaneRender for DAZ Studio 2022.1.1 - 304 [OBSOLETE]

Postby toby_a » Wed Apr 19, 2023 1:44 am

toby_a Wed Apr 19, 2023 1:44 am
This is the recommended thread for downloading, and posting any questions, suggestions or support queries for OctaneRender for DAZ Studio - TEST (ie. pre-release) releases.

TEST releases contain new features or substantial changes that, while expected to work, have not yet been proven stable.
PLEASE do NOT use them for important work and DO report any issues or suggestions as a reply to this post.


SOLUTIONS TO COMMON ISSUES

1) Make sure your NVIDIA drivers are up to date.

2) Make sure you are running the latest version of the OctaneRender for DAZStudio plugin.

3) If you experience a DAZStudio crash - deleting C:\Users\[username]\OctaneRender\Data\OctaneRender_settings.oczdb may resolve the issue.
This also resolves the "COULD NOT INITIALISE IN-MEMORY DB!" error on startup and a number of other issues.

4) If the Save button is disabled when using the Final button - disable the Final button and in Render settings select the SuperScope (2:1) Size / aspect ratio and drag the Viewport height or width until you reach required resolution.

5) If rendering an animation fails after 11 frames - make sure the DAZStudio viewport is visible when you render the animation.

6) If Octane materials are not loading when you load a previously saved scene - tick Preferences->Load OctaneRender materials from .duf user presets. If ticking this option does not stick between DAZStudio restarts, delete OctaneRender_settings.oczdb as per NOTE 3 above.

7) If you get a "Could not save a frame for X times!" - please search the forum for potential solutions.

8) If you get a "Bogus Scene Path" error - this is due to having an apostrophe in the filepath of a texturemap (so store your textures in foldernames which do not have apostrophes).

9) Octane panel title bar is off the screen and cannot be closed - click anywhere on the Octane panel and then press Alt-F4.

10) Rendering animation results in the scene emitter intensities changing - this is because rendering animations is done in "Final" mode, where meshes are merged. To resolve this, UNTICK the Preferences->Use Combined Mesh, or ENABLE the Surface Brightness pin on each of the emission materials in the scene.

11) Denoiser is not working - make sure you have a graphics card selected for Denoising in the System tab->Open Device Settings window, and that you are using the Path Tracing kernel.

12) Render artifacts near eyebrows - this is due to the eyebrow geometry going inside the head mesh surface. So morph, move or scale the eyebrows so they do not intersect with the head mesh.

13) Octane panes do not appear on the screen (ie. they open off the screen) - Main Menu Bar->Window->Workspace->Select Layout->Accept (you might choose a different layout to the current layout to make this work).


KNOWN ISSUES AWAITING RESOLUTION

1) Panoramic camera and OSL nodes are not currently supported.
2) Templating is not currently working for specular and roughness maps from Iray materials. - FIXED (please report any issues)
3) UDIM Tiles are not currently supported. - FIXED (please report any issues)
4) Some of the newer OctaneRender material and texture types are not supported. - FIXED (please report any issues)
5) VDB volume and volumetric spotlight nodes are not currently supported.

DAZ Studio Version
DAZ Studio 4.8 or later on Windows 8, 10 or 11 64bit

To use this version, you need a GPU of compute model 3.5 or higher. Support for Fermi GPUs (like GTX 4xx and 5xx) has been dropped.
Also, make sure you use an Nvidia Studio driver of version 456.38 or higher.

Network Rendering

For Network Rendering, you must use the OctaneRender Studio+ Node release from the Octane Standalone forums/download page which matches the exact Octane version of the plugin you are using. This version matches OctaneRender Studio+ 2022.1.1 Render Node builds.

Support Issues
If you have a support issue, pls provide the following information:
- Operating System (ie. Win 8, 10, 11)
- Amount of RAM
- Graphics Card(s) - model (ie. GTX 580, 3GB)
- Nvidia driver version
- DAZ Studio version
- OctaneRender for DAZ Studio version (e.g. 2022.1.1_304) and subscription type (Studio+/Prime)

- The most important part of resolving a problem is being able to reproduce that problem. So pls provide as much detail as possible in order for me to do this, and if the problem is specific to the scene, send me the scene.

Changes since 2022.1.1 - 303

  • Added a new property to camera nodes that makes it easier to choose a node to follow with the focus

    focus-follow-node-prop.png

    Note that if you load a scene with existing cameras, this (and other) new properties will appear at the very bottom of the list of properties instead of in the most logical place. Creating a new camera should show the correct ordering of properties.
  • Fixed the calculation of focal depth when following a node that was not in the center of the camera film
  • Fixed focus follows node mode to actually update the focal depth when the followed node moves
  • Fixed a problem with setting property values relating to the panoramic camera after loading a scene

Changes since 2022.1.1 - 302

  • Fixed a regression that caused the context menu in the node graph editor to not work
  • Added the ability to use the Panoramic camera

    There is a new property "Camera Type" on DAZ camera nodes that can be changed from the default of "Thin-lens camera" to "Panoramic camera".

Changes since 2022.1.1 - 301

  • Fixed some issues with saving and loading scenes containing duplicated nodes
  • Fixed a crash caused by deleting an Octane material from the DAZ Studio Scene tab
  • Fixed a case where changes in the scene were not picked up following clearing the scene using File->New

Changes since 2022.1.1 - 212

  • Redesigned material node value animation

    This version includes a complete redesign of the way material properties can be animated. In previous versions, there was a way to define animations for material nodes in the node editor, but this did not work properly and has been removed.

    Please see the announcement post for version 2022.1.1_301 (viewtopic.php?f=44&t=81456) for details.


Download Links





Please feel free to report any issues you encounter.



Happy rendering
Your OTOY team
Last edited by toby_a on Wed May 03, 2023 12:03 am, edited 2 times in total.
toby_a
OctaneRender Team
OctaneRender Team
 
Posts: 261
Joined: Tue May 10, 2022 11:59 pm

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby SiliconAya » Thu Apr 20, 2023 1:03 pm

SiliconAya Thu Apr 20, 2023 1:03 pm
On start-up this is showing in the Octane Log under the system tab:


23:01:33.412: +++++ Plugin running.
23:01:33.562: Tried to access pin via an invalid ID P_FOVX (54)
23:01:33.562: Tried to access null node pin
23:01:33.562: Tried to access pin via an invalid ID P_FOVY (55)
23:01:33.563: Tried to access null node pin
23:01:33.563: Tried to access pin via an invalid ID P_KEEP_UPRIGHT (87)
23:01:33.563: Tried to access null node pin
23:01:33.563: Tried to access pin via an invalid ID P_STEREO_DIST_FALLOFF (225)
23:01:33.563: Tried to access null node pin
23:01:33.563: Tried to access pin via an invalid ID P_STEREO_CUTOFF_LATITUDE (226)
23:01:33.563: Tried to access null node pin
SiliconAya
Licensed Customer
Licensed Customer
 
Posts: 175
Joined: Tue Jul 30, 2013 12:00 pm
Location: Australia

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby toby_a » Thu Apr 20, 2023 8:45 pm

toby_a Thu Apr 20, 2023 8:45 pm
SiliconAya wrote:On start-up this is showing in the Octane Log under the system tab:


23:01:33.412: +++++ Plugin running.
23:01:33.562: Tried to access pin via an invalid ID P_FOVX (54)
23:01:33.562: Tried to access null node pin
23:01:33.562: Tried to access pin via an invalid ID P_FOVY (55)
23:01:33.563: Tried to access null node pin
23:01:33.563: Tried to access pin via an invalid ID P_KEEP_UPRIGHT (87)
23:01:33.563: Tried to access null node pin
23:01:33.563: Tried to access pin via an invalid ID P_STEREO_DIST_FALLOFF (225)
23:01:33.563: Tried to access null node pin
23:01:33.563: Tried to access pin via an invalid ID P_STEREO_CUTOFF_LATITUDE (226)
23:01:33.563: Tried to access null node pin


Thanks for pointing this out. Those are the pins that are present on the panoramic camera node but not on the thin-lens camera node. I'll see if I can easily avoid those messages.

Cheers,
Toby.
toby_a
OctaneRender Team
OctaneRender Team
 
Posts: 261
Joined: Tue May 10, 2022 11:59 pm

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby SiliconAya » Fri Apr 21, 2023 2:45 am

SiliconAya Fri Apr 21, 2023 2:45 am
The 'focus to selected object' camera focus mode seems to have stopped working, using it sets the camera to manual focus distance with a focal depth of 2.14 instead.

Oh and switching camera types seems to spit out those same log messages as above as well.
SiliconAya
Licensed Customer
Licensed Customer
 
Posts: 175
Joined: Tue Jul 30, 2013 12:00 pm
Location: Australia

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby toby_a » Fri Apr 21, 2023 3:21 am

toby_a Fri Apr 21, 2023 3:21 am
SiliconAya wrote:The 'focus to selected object' camera focus mode seems to have stopped working, using it sets the camera to manual focus distance with a focal depth of 2.14 instead.

Oh and switching camera types seems to spit out those same log messages as above as well.


"Focus to selected object" is supposed to set the camera to manual focal depth, but the calculation is wrong (it's 100 times too small!). I'll fix it in the next release.
toby_a
OctaneRender Team
OctaneRender Team
 
Posts: 261
Joined: Tue May 10, 2022 11:59 pm

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby Hun73rdk_1 » Thu Apr 27, 2023 8:02 pm

Hun73rdk_1 Thu Apr 27, 2023 8:02 pm
I get bluescreen with this build and i get cuda errors.

download/file.php?mode=view&id=90965

also with the shaders being in the scene list now it does not save with the scene if changed and does not save if you save daz matherials
Attachments
Capture.JPG
Join the Octane Daz Fan server for people that uses daz and octane https://discord.gg/wDzwC8tqAK
Hun73rdk_1
Licensed Customer
Licensed Customer
 
Posts: 115
Joined: Tue Mar 20, 2018 10:54 pm

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby toby_a » Thu Apr 27, 2023 9:19 pm

toby_a Thu Apr 27, 2023 9:19 pm
Hun73rdk_1 wrote:I get bluescreen with this build and i get cuda errors.

download/file.php?mode=view&id=90965

also with the shaders being in the scene list now it does not save with the scene if changed and does not save if you save daz matherials


Hi, thanks for testing!

The blue screen and CUDA errors are most unexpected (and shouldn't be caused by changes in the plugin). Just to confirm, are these problems with a scene that works without issue in the stable version of the plugin (2022.1.1_212)?

Can you say a bit more about what "if you save daz materials" means? Are you saving a subset of the scene?

Cheers,
Toby.
toby_a
OctaneRender Team
OctaneRender Team
 
Posts: 261
Joined: Tue May 10, 2022 11:59 pm

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby SiliconAya » Fri Apr 28, 2023 9:31 am

SiliconAya Fri Apr 28, 2023 9:31 am
I personally haven't had any issues with Octane materials saving in a scene (haven't tried a material preset though).

I have been having blue screens on and off most of this year though, with the errors of TDR Delay and PDC Watchdog mostly, but maybe others. At least some of them where caused by the recent (Feb? I think) Photoshop major version upgrade and bugs/compatibility issues in the nVidia studio driver, but that wasn't the only cause.
I've been upgrading to the latest nVidia studio drivers almost as soon as they've come out and while it's still happening every now and again, it's a lot better than a few a day I was getting sometimes.
However, after the Photoshop drivers bugs were fixed, a 100% of my blue screens have been when using Daz Studio and the plugin, with them mostly seeming to happen when the viewport hits 1000/1000 samples (whatever max samples is set to) and then trying to move the camera only to find the viewport render wont restart and after few seconds a blue screen happens.

I had been assuming it was a hardware fault on my side, but if others have been getting them maybe it isn't.
SiliconAya
Licensed Customer
Licensed Customer
 
Posts: 175
Joined: Tue Jul 30, 2013 12:00 pm
Location: Australia

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby Hun73rdk_1 » Fri Apr 28, 2023 11:26 am

Hun73rdk_1 Fri Apr 28, 2023 11:26 am
Seems like the "Stereo output type" is not getting saved when saving a scene
Join the Octane Daz Fan server for people that uses daz and octane https://discord.gg/wDzwC8tqAK
Hun73rdk_1
Licensed Customer
Licensed Customer
 
Posts: 115
Joined: Tue Mar 20, 2018 10:54 pm

Re: OctaneRender for DAZ Studio 2022.1.1 - 304 [TEST]

Postby Hun73rdk_1 » Fri Apr 28, 2023 11:28 am

Hun73rdk_1 Fri Apr 28, 2023 11:28 am
SiliconAya wrote:I personally haven't had any issues with Octane materials saving in a scene (haven't tried a material preset though).

I have been having blue screens on and off most of this year though, with the errors of TDR Delay and PDC Watchdog mostly, but maybe others. At least some of them where caused by the recent (Feb? I think) Photoshop major version upgrade and bugs/compatibility issues in the nVidia studio driver, but that wasn't the only cause.
I've been upgrading to the latest nVidia studio drivers almost as soon as they've come out and while it's still happening every now and again, it's a lot better than a few a day I was getting sometimes.
However, after the Photoshop drivers bugs were fixed, a 100% of my blue screens have been when using Daz Studio and the plugin, with them mostly seeming to happen when the viewport hits 1000/1000 samples (whatever max samples is set to) and then trying to move the camera only to find the viewport render wont restart and after few seconds a blue screen happens.

I had been assuming it was a hardware fault on my side, but if others have been getting them maybe it isn't.

yea i just got a new pc and it seems BSOD for really fast modern pcs is a norm for windows i have random once and almost never the same.
I had to use DDU for uninstalling my drivers to get back to rendering.
Join the Octane Daz Fan server for people that uses daz and octane https://discord.gg/wDzwC8tqAK
Hun73rdk_1
Licensed Customer
Licensed Customer
 
Posts: 115
Joined: Tue Mar 20, 2018 10:54 pm
Next

Return to DAZ Studio


Who is online

Users browsing this forum: No registered users and 34 guests

Sat Apr 27, 2024 12:09 pm [ UTC ]
cron