OctaneRender 3 for DAZ Studio [TEST and STABLE] [OBSOLETE]

[face_off]

Hi Paul. Maybe it is a jnown issue, but I am still having problems with geocrafted props on G3F. The genital prop is not smoothley connected to the body in renders. It looks detached.

It's not a issue I have seen before. I would suggest restarting DAZStudio and trying again - to make sure it's not a glitch with just that session.

Paul

[Masterstroke]

o.k. it is a displacement map. Hard to tame that beast

[rajib]

Hi Paul,

I have create the DAZ instances not rendering in Octane Viewport issue. Please take a look at viewtopic.php?f=44&t=55646. I have given the steps and added a scene file in that thread. I think it is not reading the individual instance's position and rendering all instances at one place hence making it appear that there is only 1 instance.

I think it is the same issue because of which UltraScatter instances do not render in the Octane Viewport unless you break the group. But breaking groups with tens of thousands of instances is not possible in any case.

I am using DAZ 4.9.2.70 and Octane Plugin 3.4.4.28.

Regards,
Rajib

[rajib]

Hi Paul,

I get a crash each and every time I click the '...' next to any image node. This had been present for me in every version of the Octane 3.x plugin. Is there a way to reset this ? e.g. clear old favorite folders it may have, etc ? I have lost a fair bit of my work by accidentally clicking on the '...' to change the texture map of a material many times now.

Regards,
Rajib

[rajib]

Hi Paul,

Another issue. Some props and accessories load in the wrong way in Octane Viewport. Have had this in all versions of the 3.x plugin.

In DAZ Viewport the bag is hung from the right shoulder and is at the left side. This is the correct orientation. But in the Octane window it appears in the reverse way.

DAZ Viewport - Correct

Octane Viewport - Wrong

Can you please take a look at this ? I am not sure if I save the scene can you read it as you might not have the same props in your Content Library. The bag in the scene comes in 2 forms - one left to right (original) and one right to left (mirrored). Both load properly in the DAZ Viewport. But in the Octane Viewport both result in the left to right (original) orientation. It makes me believe whatever 'transpose' has been applied to the bag is being read by the DAZ Viewport correctly but not being read by the Octane Plugin correctly. Reloading / Rebuilding does not correct it.

Regards,
Rajib

[rajib]

Hi Paul,

One more issue. If you keep switch between scenes using the "File->Open / Open Recent" menu, sooner or later the Octane Viewport will stop loading and reload / rebuild does not help. If the scene had an daylight environment with a sky map, only the sky map will load but nothing else. In the System tab it shows:

02:48:01.518: +++++ Plugin running.
02:48:53.039: Node type 20 is either unknown, a linker or incompatible to dynamic pin '_2' (type PT_OBJECTLAYER) of node 'sphere' (NT_GEO_MESH, 000000007696D5E0)
02:48:53.361: Node type 20 is either unknown, a linker or incompatible to dynamic pin '_2' (type PT_OBJECTLAYER) of node 'sphere' (NT_GEO_MESH, 000000007696D5E0)

I was just testing with 2 scenes files. One had Cube instances (the one I attached for the instances problem) and another had just one sphere. I load one of them and then clicked the open menu item to load the other. The octane viewport had the running orange bar and nothing loaded. Sometimes it would happen the first time. Somethings it took a couple of switching between the scenes to recreate the issue. But each time it had a similar error in the log.

Regards,
Rajib

[face_off]

I get a crash each and every time I click the '...' next to any image node. This had been present for me in every version of the Octane 3.x plugin. Is there a way to reset this ? e.g. clear old favorite folders it may have, etc ? I have lost a fair bit of my work by accidentally clicking on the '...' to change the texture map of a material many times now.

There are one or two other users who are experiencing this issue and it has proven hard to track down (and I cannot reproduce the crash). There appears to be a setting in DAZStudio which is triggering it. So my theory is that the DAZStudio settings need to be cleared - but unsure which ones. If you truly want to resolve the issue, and you have a high level of technical expertise, may I suggest doing the following, and after each one, test if DAZStudio is still crashing, so you can tell me exactly which one resolved the issue. Keep in mind, doing the following is going to reset any custom settings you have in DAZStudio.

1) Reset the interface to the default settings, choose Edit > Reset to Defaults from the DAZStudio menu.

2) You can try deleting C:\Users\[username]\AppData\Roaming\DAZ 3D and then reinstall DAZStudio (make a backup copy of this folder first)

3) Delete all the keys (one by one, testing if the crash occurs after each delete) in HKEY_CURRENT_USER/Software/Daz/Studio4 in your registry. You would need to be extremely cautious doing this, and would potentially break DAZStudio. Do this at your own risk.

4) Try deleting (make a backup copy first) C:\ProgramData\DAZ 3D\Studio4\dazstudio.dat (may potentially break DAZStudio and require a reinstall)

5) You could also try deleting C:\Users\[username]\OctaneRender\Data\* however you will loose all your presets (make a backup copy of this folder first)

6) If the above doesn't work, delete all of C:\Users\[username]\OctaneRender and reinstall the plugin (make a backup copy of this folder first)

Sorry I get offer more help on this issue - without being able to reproduce it, it's almost impossible for me to fix.

Paul

[rajib]

I get a crash each and every time I click the '...' next to any image node. This had been present for me in every version of the Octane 3.x plugin. Is there a way to reset this ? e.g. clear old favorite folders it may have, etc ? I have lost a fair bit of my work by accidentally clicking on the '...' to change the texture map of a material many times now.

There are one or two other users who are experiencing this issue and it has proven hard to track down (and I cannot reproduce the crash). There appears to be a setting in DAZStudio which is triggering it.

Paul, will try what you mentioned and get back.

What about the other issues specially the one related to the instancing ? Can that be taken on priority ? I have already given you the steps to reproduce it even without UltraScatter. If that is resolved it will allow us to do a lot more in DAZ / Octane plugin.

[rajib]

I get a crash each and every time I click the '...' next to any image node. This had been present for me in every version of the Octane 3.x plugin. Is there a way to reset this ? e.g. clear old favorite folders it may have, etc ? I have lost a fair bit of my work by accidentally clicking on the '...' to change the texture map of a material many times now.

There are one or two other users who are experiencing this issue and it has proven hard to track down (and I cannot reproduce the crash). There appears to be a setting in DAZStudio which is triggering it.

Paul, will try what you mentioned and get back.

What about the other issues specially the one related to the instancing ? Can that be taken on priority ? I have already given you the steps to reproduce it even without UltraScatter. If that is resolved it will allow us to do a lot more in DAZ / Octane plugin.

Paul, I have resolved this for myself. Basically issue seems to be with a list of files that may have been loaded in a image browser before and for which the file paths may no longer be valid.

I opened Windows Registry (Regedit.exe) and went to the following key : HKEY_CURRENT_USER\SOFTWARE\DAZ\Studio4\OctaneRender
I then deleted all entries named ImageBrowserLast_NN Where NN are running numbers. e.g. one will see ImageBrowserLast_1,ImageBrowserLast_2,ImageBrowserLast_3... in the right side panel of the RegEdit application.
Do not delete anything else otherwise things might just get worse.

Then I relaunched DAZ and was able to open the image browser without any issue. No crash.

To fix this issue within the Image Browser code of the Octane plugin, you may want to validate the file paths and ignore those that to not exists. You can use a Windows API like :
HANDLE CreateFile(...) with OPEN_EXISTING flag with the path read from the ImageBrowserLast_NN entry. All you would be checking for is if the return value is INVALID_HANDLE_VALUE. If it returns that then the path is wrong and can be skipped and the registry entry for that automatically deleted. If you are using standard C, then you can try fopen in read mode the path to test the files existence. If that fails, skip the entry and automatically delete the corresponding entry. DO note there may be entries like "DazContent:/Runtime/Textures/DimensionTheory/iRadiance/SkiesOfIradiance" where you will need to replace the DazContent: with the actual Daz Content path before calling either of the APIs. You can also use equivalent Qt APIs if available to validate the path.

Potentially the Octane Plugin can do this once when it is loaded - check and delete the invalid entries. That way the image browser will always open without crashing.

Hope this helps.

[face_off]

I opened Windows Registry (Regedit.exe) and went to the following key : HKEY_CURRENT_USER\SOFTWARE\DAZ\Studio4\OctaneRender
I then deleted all entries named ImageBrowserLast_NN Where NN are running numbers. e.g. one will see ImageBrowserLast_1,ImageBrowserLast_2,ImageBrowserLast_3... in the right side panel of the RegEdit application.
Do not delete anything else otherwise things might just get worse.

Then I relaunched DAZ and was able to open the image browser without any issue. No crash.

To fix this issue within the Image Browser code of the Octane plugin, you may want to validate the file paths and ignore those that to not exists. You can use a Windows API like :
HANDLE CreateFile(...) with OPEN_EXISTING flag with the path read from the ImageBrowserLast_NN entry. All you would be checking for is if the return value is INVALID_HANDLE_VALUE. If it returns that then the path is wrong and can be skipped and the registry entry for that automatically deleted. If you are using standard C, then you can try fopen in read mode the path to test the files existence. If that fails, skip the entry and automatically delete the corresponding entry. DO note there may be entries like "DazContent:/Runtime/Textures/DimensionTheory/iRadiance/SkiesOfIradiance" where you will need to replace the DazContent: with the actual Daz Content path before calling either of the APIs. You can also use equivalent Qt APIs if available to validate the path.

Awesome! Thank you so much for this. I tried added invalid folder names into ImageBrowserLast_1, and DAZStudio still did not crash for me. Regardless, I will post this fix to the FAQ.

I could modify the plugin to validate the paths before using them in the ImageBrowser, however without being able to reproduce the crash, it would be hard to tell if that fix actually works or not.

I will look at your other issues in the next few days.

Paul