Daz Studio Pro BETA - version 4.22.1.136! (*UPDATED*)

jbowler

jbowler said:

How do I define the color mapping for "Object ID"?

I don't know if this is a 4.22.1 bug or something I don't understand but it is similar to the problem with convergence maps (they always come out 0, even though they are TIFFs, not PNGs.)

It's a 4.22.1.41 documentation bug.  Here's the relevant snippet from the change log:

• Added support for controlling “Object ID” when NVIDIA Iray is the active renderer

  • If a DzColorProperty (user) property named “Object ID”, with the property group path of “Display/Rendering/Iray” is added to a node with geometry, the value of this property is used to control the color of that object in the “Object ID” canvas

So the property has to be added by hand, the "Create Advanced Iray Not Properties" script will create it.  However it is not called "Object ID" - that's the bug - it's called "Iray Object ID", even though it is in the .../Iray property group.  This is not something anyone would discover by accident; I spent a few hours trying to guess what it was (since spelling errors seem to be common in the documentation) before trying the script.  I guess I should have tried that first but the property is useful independent of Iray (like Material ID).  E.g. an Object ID canvas can be rendered corresponding to a Filament render and it's probably going to be close enough.

It's not necessary for the render to converge for either of the "Material ID" or the "Object ID" canvases; "Render Settings/Progressive Rendering/Max Samples" can be set to 1 and the result is, so far as I can see, exactly the same as if it's set to 20,000.

The use of color mapping is somewhat odd given than a name (of an object) isn't a color and that objects (DzObject) have simple 1D numerical IDs but the level of indirection (the mapping) has some potential uses.

Richard Haseltine

jbowler said:

jbowler said:

How do I define the color mapping for "Object ID"?

I don't know if this is a 4.22.1 bug or something I don't understand but it is similar to the problem with convergence maps (they always come out 0, even though they are TIFFs, not PNGs.)

It's a 4.22.1.41 documentation bug.  Here's the relevant snippet from the change log:

• Added support for controlling “Object ID” when NVIDIA Iray is the active renderer

  • If a DzColorProperty (user) property named “Object ID”, with the property group path of “Display/Rendering/Iray” is added to a node with geometry, the value of this property is used to control the color of that object in the “Object ID” canvas

So the property has to be added by hand, the "Create Advanced Iray Not Properties" script will create it.  However it is not called "Object ID" - that's the bug - it's called "Iray Object ID", even though it is in the .../Iray property group.  This is not something anyone would discover by accident; I spent a few hours trying to guess what it was (since spelling errors seem to be common in the documentation) before trying the script.  I guess I should have tried that first but the property is useful independent of Iray (like Material ID).  E.g. an Object ID canvas can be rendered corresponding to a Filament render and it's probably going to be close enough.

It's not necessary for the render to converge for either of the "Material ID" or the "Object ID" canvases; "Render Settings/Progressive Rendering/Max Samples" can be set to 1 and the result is, so far as I can see, exactly the same as if it's set to 20,000.

The use of color mapping is somewhat odd given than a name (of an object) isn't a color and that objects (DzObject) have simple 1D numerical IDs but the level of indirection (the mapping) has some potential uses.

I can't say I have noticed a lot of errors in the change logs or othe documentation (and I am geenrally better at spotting others' than at catching my own - such as "Create Advanced Iray Not Properties" above :) ).

It is a specifically Iray property, however, not something that affects or is used by Filament.

DzObject isn't related to ObjectID - the latter is a colour, so it iss et by a colour property.

barbult

Richard, did you overlook the actual error? The change log says the property is "Object ID", but it is implemented as "Iray Object ID". Jbowler is saying that if someone creates a property named Object ID, as stated in the change log, it does not work.

Dolce Saito

Richard Haseltine said:

When you first use a morph, or bend a joint that triggers a corrective morph, the morph deltas (the shape change) have to be loaded from disc. Also, every time you make a change DS has to trace through the links to and from the changed bone/shape to look for links that may be affected by the change and so need updating.

Hi Richard;

Thanks for the knowledge. I already knew most of this. But I would like to point to the problem that "it happens all the time". So, not when first used.

Yesterday, I did something very drastic. Deleted almost all of my content, started by first uninstalling all connect items from the studio itself. And moved everything to the content directory by reinstalling everything from DIM. While doing this, at certain point I barely had any 3rd party plug-ins, only had genesis 3/8 and a few vanilla morphs give or take. Also my ssd drive was almost %90 empty. At this point, I opened a genesis figure, did the same test. UI froze again.

Unfortunately, I couldn't be able to identify root cause yet. However, this only occurs in Daz studio and during character movement.

Richard Haseltine

barbult said:

Richard, did you overlook the actual error? The change log says the property is "Object ID", but it is implemented as "Iray Object ID". Jbowler is saying that if someone creates a property named Object ID, as stated in the change log, it does not work.

Yes, and it has been corrected (I was aware that the author had seen the posts reporting the slip).

barbult

Richard Haseltine said:

barbult said:

Richard, did you overlook the actual error? The change log says the property is "Object ID", but it is implemented as "Iray Object ID". Jbowler is saying that if someone creates a property named Object ID, as stated in the change log, it does not work.

Yes, and it has been corrected (I was aware that the author had seen the posts reporting the slip).

Great 

HatB

I recently purchased at 18T External hard drive so I could have everything except the program on it.

I installed all my purchased iterms using DIM but when I go into the program some are listed as installed but the majority are only listed as available.

When I try to use some that are listed as installed, I get a message that it is not available so I uninstall it within the program and reinstall,

When I try to load an item of clothing by double clicking, I wind up having to drag it onto the character. Changing the material is guess and guess again--drag and drop, select and click, in viewport or scene choice--and it may or not work at all.

HELP!! This is very frustrating and I have been using it for years without this kind of problem.

DoctorJellybean

HatB said:

I recently purchased at 18T External hard drive so I could have everything except the program on it.

I installed all my purchased iterms using DIM but when I go into the program some are listed as installed but the majority are only listed as available.

When I try to use some that are listed as installed, I get a message that it is not available so I uninstall it within the program and reinstall,

When I try to load an item of clothing by double clicking, I wind up having to drag it onto the character. Changing the material is guess and guess again--drag and drop, select and click, in viewport or scene choice--and it may or not work at all.

HELP!! This is very frustrating and I have been using it for years without this kind of problem.

Is the content on the extrenal drive mapped in Content Directory Manager?

HatB

DoctorJellybean said:

HatB said:

I recently purchased at 18T External hard drive so I could have everything except the program on it.

I installed all my purchased iterms using DIM but when I go into the program some are listed as installed but the majority are only listed as available.

When I try to use some that are listed as installed, I get a message that it is not available so I uninstall it within the program and reinstall,

When I try to load an item of clothing by double clicking, I wind up having to drag it onto the character. Changing the material is guess and guess again--drag and drop, select and click, in viewport or scene choice--and it may or not work at all.

HELP!! This is very frustrating and I have been using it for years without this kind of problem.

Is the content on the extrenal drive mapped in Content Directory Manager?

Yes. I just went and checked.

 

HatB

My problem with the PRO version and not the Beta. Everything was working fine until the last install.

Richard Haseltine

Installing an update doesn't change settings. You can transfer the beta version's content directory settings to the General Release using http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/file_io/save_mapped_paths/start in the beta and then running the script it creates in the General Release.

Stretch65

I've tried Filment draw style and the scene is completely black.  I've already created a Filament Draw Options node, and tried adjusting a few parameters but still all black.  Is there something I'm missing?

jbowler

A couple more bugs in the new canvas handling; these were in .99 and are still in .110

The render window doesn't update if the active canvas is swapped until the next update of the (an?) actual render canvas.  E.g. if I swap from the render canvas (called "Beauty" for some reason) to any(?) other the change only happens with the redraw of the render canvas.  This is true even if the current canvas is not the render canvas, e.g. if I swap between "Distance" (ray length) and "Object ID".

After the render has finished I can't swap between the canvases; I'm stuck on whichever I was eyeballing last.  This forces me to save the whole shebang and view the darned things with gwenview or gimp as appropriate; a lot of work to work out if I really wanted to fill my disk up with the result!

Richard Haseltine

jbowler said:

A couple more bugs in the new canvas handling; these were in .99 and are still in .110

The render window doesn't update if the active canvas is swapped until the next update of the (an?) actual render canvas.  E.g. if I swap from the render canvas (called "Beauty" for some reason) to any(?) other the change only happens with the redraw of the render canvas.  This is true even if the current canvas is not the render canvas, e.g. if I swap between "Distance" (ray length) and "Object ID".

After the render has finished I can't swap between the canvases; I'm stuck on whichever I was eyeballing last.  This forces me to save the whole shebang and view the darned things with gwenview or gimp as appropriate; a lot of work to work out if I really wanted to fill my disk up with the result!

As far as I can recall these are not new.

It's called a beauty canvas because that is the standard term for a render of everything, rather than the specialised renders of the other canvas types

Dolce Saito

Dolce Saito said:

Richard Haseltine said:

When you first use a morph, or bend a joint that triggers a corrective morph, the morph deltas (the shape change) have to be loaded from disc. Also, every time you make a change DS has to trace through the links to and from the changed bone/shape to look for links that may be affected by the change and so need updating.

Hi Richard;

Thanks for the knowledge. I already knew most of this. But I would like to point to the problem that "it happens all the time". So, not when first used.

Yesterday, I did something very drastic. Deleted almost all of my content, started by first uninstalling all connect items from the studio itself. And moved everything to the content directory by reinstalling everything from DIM. While doing this, at certain point I barely had any 3rd party plug-ins, only had genesis 3/8 and a few vanilla morphs give or take. Also my ssd drive was almost %90 empty. At this point, I opened a genesis figure, did the same test. UI froze again.

Unfortunately, I couldn't be able to identify root cause yet. However, this only occurs in Daz studio and during character movement.

I identified the source of the problem after 2 full days of trial-error. It is a bios setting, which decides to slightly overclock the cache sram frequency when the system is under heavy load for raptor lake processors (13900ks). Daz Studio is very sensitive to the system's state, so it was the only application for me that got destabilized with this setting. I disabled it and after that no more UI freezes on viewport.

jbowler

Richard Haseltine said:

As far as I can recall these are not new.

Neither your nor I could swap the active render window canvas until the change was made to the render window.  The render window locking up is, indeed, older but it affected scrolling of the window (and was very very annoying) which is why my update interval is set to 120s; it's probably a side effect of that that I can't swap the canvas in the render window for quite a long time.  Can I swap the render update interval from the render window?

"Beauty Canvas" gets me loads of hits on Google so maybe there is something I don't know; I wish to learn so I will check them out, thankyou.

cain-x

Stretch65 said:

I've tried Filment draw style and the scene is completely black.  I've already created a Filament Draw Options node, and tried adjusting a few parameters but still all black.  Is there something I'm missing?

Same. I assume there is more work to be done to make a proper Filament shader. I am excited that it is being worked on.

I am curious if this effort is being done resolve the issues Filament has had since it was introduced and implement new features to make it somewhat on par with Iray (i.e. transparency, emissives, etc..). Being able to access the full capabilities of Filament would be a huge boon. Understanding the roadmap will help folks like myself make better decisions for the future.

Richard Haseltine

cain-x said:

Stretch65 said:

I've tried Filment draw style and the scene is completely black.  I've already created a Filament Draw Options node, and tried adjusting a few parameters but still all black.  Is there something I'm missing?

Same. I assume there is more work to be done to make a proper Filament shader. I am excited that it is being worked on.

I am curious if this effort is being done resolve the issues Filament has had since it was introduced and implement new features to make it somewhat on par with Iray (i.e. transparency, emissives, etc..). Being able to access the full capabilities of Filament would be a huge boon. Understanding the roadmap will help folks like myself make better decisions for the future.

All I can suggest is watching the change log, Daz doesn't usually pre-announce things.

Sevrin

Tried to update to the 1.110 version of the beta, and the download kept failing. Updating everything else worked fine, and it's not a disk space issue.

johndoe_36eb90b0

Sevrin said:

Tried to update to the 1.110 version of the beta, and the download kept failing. Updating everything else worked fine, and it's not a disk space issue.

Check the downloads folder, there might be a partially downloaded zip file. If there is, delete it and launch DIM again then retry.

f7eer

DS 4.22.1.110 bug: When rendering, "Save" in the render window is no longer grayed-out. I hit it by mistake, and it generated an error in the progress dialog, but nothing in the regular log. The error was inconsequential, and when the render was done, I hit Save, and it saved the render with no errors. This button used to be properly grayed out, and this is the first time I noticed it wasn't grayed out.

johndoe_36eb90b0

f7eer said:

DS 4.22.1.110 bug: When rendering, "Save" in the render window is no longer grayed-out. I hit it by mistake, and it generated an error in the progress dialog, but nothing in the regular log. The error was inconsequential, and when the render was done, I hit Save, and it saved the render with no errors. This button used to be properly grayed out, and this is the first time I noticed it wasn't grayed out.

I have seen this before, sometimes the button gets enabled before render is fully finished.

Elor

I have a problem with 'Daz Studio 4.22.110' and 'Iray Server 2023.1.4 (18 Mar 2024)', a problem that doesn't happen with 'Daz 4.21.0.5'. I used the same scene with both versions.

The error message is not really helpful:

"Unkown error preparing snapshot render."

I opened the log file and initially, I thought that the problem was my computer forcefuly closing the connection, but it does too when I'm using Daz 4.21.0.5 and the main difference between the two logs files is the line related to the error:

[WARNING] :: /src/pluginsource/DzIrayRender/dzirayrenderer.cpp(2863): Unkown error preparing snapshot render.

Is it a known problem ?

Richard Haseltine

The unknown error may be related to an issue fixed in 4.22.1.112 http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_22_1_112

barbult

The changes to Save Modified Assets looks interesting. I haven't tried it yet.

Richard Haseltine

Richard Haseltine said:

The unknown error may be related to an issue fixed in 4.22.1.112 http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_22_1_112

This fix is now available in the new Public Build (beta)

Richard Haseltine

barbult said:

The changes to Save Modified Assets looks interesting. I haven't tried it yet.

Yes, it will greatly simplify dealing with things that should not have non-zero default values as there will now be a way to avoid overwriting things that should have non-zero default values..

Elor

Richard Haseltine said:

The unknown error may be related to an issue fixed in 4.22.1.112 http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_22_1_112

After updating to 4.22.1.112, sending a scene to Iray Server is working: no more unknow error at the end

Thank you and thank to the dev team

johndoe_36eb90b0

Is it just me or is .123 version not showing scene loading progress dialog anymore?

barbult

In 4.22.1.123 PB, Autofit of G8 dForce hair to G9 now works for me. Is that an improvement I missed somewhere along the line? Or was I just lucky today that the few I tried worked. The dForce hair used to end up rotated incorrectly when autofit to G9. I did Saul Hair (AprilYSH), Speakeasy Hair (Chevybabe25) and Summer Sports Hair (Nirvana).