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

Illidanstorm

Sevrin said:

Sevrin said:

DoctorJellybean said:

@Sevrin: Did it render using the GPU or CPU?

GPU

dim_sh_ecd463260f said:

@Sevrin: Do you have the latest public build version?

Yup.  Current beta.

I doublechecked.  The renders fell back to CPU.

I had CPU deselected, but somehow CPU fallback got enabled, which I didn't normally have.

When I tried to render one of the scenes again with CPU fallback disabled., the render was blank.  When I enabled Iray preview, all I got was a endless loop with no preview appearing.  So yeah, Iray Section nodes won't render on GPU.  I've not used them in my scenes in a long time, but for people who do, this is obviously a big problem.

It seems like this is a bug for rtx gpus that everyone has 

MEC4D

All GPUs  a big bug for all users . 

Illidanstorm said:

Sevrin said:

Sevrin said:

DoctorJellybean said:

 

It seems like this is a bug for rtx gpus that everyone has 

 

Serene Night

I'm using the new beta. My GPU is RTX 2080 Super. I render the first scene perfectly. Super fast even. Then subsequent scenes are all blank. if I reboot, it renders one scene well, then back to rendering blanks. Very strange.

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

DoctorJellybean

Serene Night said:

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

Are you sure it isn't just running in the background? Check in Task Manager.

MEC4D

I rendered sequences this morning with figures with no issue on GPUs , check the LOG files , something may trigger the GPU error as happened with the section pane this morning , 2 issues the same error behavior , definitely a bug 

Serene Night said:

I'm using the new beta. My GPU is RTX 2080 Super. I render the first scene perfectly. Super fast even. Then subsequent scenes are all blank. if I reboot, it renders one scene well, then back to rendering blanks. Very strange.

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

 

Serene Night

DoctorJellybean said:

Serene Night said:

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

Are you sure it isn't just running in the background? Check in Task Manager.

No, there is nothing running at all. I can launch other versions of DAZ studio, such as 4.11 without difficulty, but 4.12 beta will not start again. It is acting like something is running still, but it does not have anythign showing in the finder.

 

If instead of quitting studio when I want to restart it, I CTRL alt Delete and force it to quit, it then reloads properly. So, I do think something runs in the background, even though finder says otherwise.

Serene Night

MEC4D said:

I rendered sequences this morning with figures with no issue on GPUs , check the LOG files , something may trigger the GPU error as happened with the section pane this morning , 2 issues the same error behavior , definitely a bug 

Serene Night said:

I'm using the new beta. My GPU is RTX 2080 Super. I render the first scene perfectly. Super fast even. Then subsequent scenes are all blank. if I reboot, it renders one scene well, then back to rendering blanks. Very strange.

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

 

I do use section panes quite a bit. So that may be an issue.

MEC4D

That's the bug ! I guess we need to wait for the fix now

Serene Night said:

MEC4D said:

I rendered sequences this morning with figures with no issue on GPUs , check the LOG files , something may trigger the GPU error as happened with the section pane this morning , 2 issues the same error behavior , definitely a bug 

Serene Night said:

I'm using the new beta. My GPU is RTX 2080 Super. I render the first scene perfectly. Super fast even. Then subsequent scenes are all blank. if I reboot, it renders one scene well, then back to rendering blanks. Very strange.

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

 

I do use section panes quite a bit. So that may be an issue.

 

L'Adair

Serene Night said:

DoctorJellybean said:

Serene Night said:

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

Are you sure it isn't just running in the background? Check in Task Manager.

No, there is nothing running at all. I can launch other versions of DAZ studio, such as 4.11 without difficulty, but 4.12 beta will not start again. It is acting like something is running still, but it does not have anythign showing in the finder.

 

If instead of quitting studio when I want to restart it, I CTRL alt Delete and force it to quit, it then reloads properly. So, I do think something runs in the background, even though finder says otherwise.

I've noticed that once you close DS 4.12, in Win10 anyway, the entry in Task Manager for Daz Studio on the Processes tab, (default sort, by Name,) moves from "Apps" at the top to "Background Processes" further down the tab until the shutdown is complete. Basically, the shutdown background process should take about the same length of time as the program takes to remove the current scene if you open a "New" file, (probably a little longer because it's also saving the "state" of your menus and tabs, etc.)

I used to use End Task to stop DS when it kept going and going, but I discovered that caused some of my docked panes to relocate! I now only use End Task when DS locks up.

Serene Night

L'Adair said:

Serene Night said:

DoctorJellybean said:

Serene Night said:

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

Are you sure it isn't just running in the background? Check in Task Manager.

No, there is nothing running at all. I can launch other versions of DAZ studio, such as 4.11 without difficulty, but 4.12 beta will not start again. It is acting like something is running still, but it does not have anythign showing in the finder.

 

If instead of quitting studio when I want to restart it, I CTRL alt Delete and force it to quit, it then reloads properly. So, I do think something runs in the background, even though finder says otherwise.

I've noticed that once you close DS 4.12, in Win10 anyway, the entry in Task Manager for Daz Studio on the Processes tab, (default sort, by Name,) moves from "Apps" at the top to "Background Processes" further down the tab until the shutdown is complete. Basically, the shutdown background process should take about the same length of time as the program takes to remove the current scene if you open a "New" file, (probably a little longer because it's also saving the "state" of your menus and tabs, etc.)

I used to use End Task to stop DS when it kept going and going, but I discovered that caused some of my docked panes to relocate! I now only use End Task when DS locks up.

Thanks. Yes, it does appear to be there...No longer under apps... But it really is not closing. It just hangs out there.

How strange.

 

amandainjapan

((thanks all, it's fixed now))

marble

L'Adair said:

Serene Night said:

DoctorJellybean said:

Serene Night said:

Also, if I close the beta, it will not let me reopen it. I have to reboot in order to get the beta to launch.

Are you sure it isn't just running in the background? Check in Task Manager.

No, there is nothing running at all. I can launch other versions of DAZ studio, such as 4.11 without difficulty, but 4.12 beta will not start again. It is acting like something is running still, but it does not have anythign showing in the finder.

 

If instead of quitting studio when I want to restart it, I CTRL alt Delete and force it to quit, it then reloads properly. So, I do think something runs in the background, even though finder says otherwise.

 

I used to use End Task to stop DS when it kept going and going, but I discovered that caused some of my docked panes to relocate! I now only use End Task when DS locks up.

Oh so it is not just my docked panes that have a mind of their own. For me, they rearrange themselves and I have to drag them back to the order I want them. This has nothing to do with End Task though as I have not been using that recently.

amandainjapan

oh, that is so good to know, I was also having the panes moving around.

L'Adair

KInda, sorta, off topic… Cath mentioned something in passing about making sure the Render Engine is set to Iray and not Viewport a day or two ago. I thought, "What!?" so I went looking, and sure enough, where it use to say "OpenGL" it now says "Viewport". I don't know what version brought us that change, but I suspect it was the same version that made Filament available. (Because, as far as I can see, that's the only way to actually render an image with Filament. Currently, of course.) But I'm getting sidetracked.

I tested this new "Viewport" as render engine, and found it does render your viewport to a separate window, regardless of what Draw Mode I tried. (I did not try all of them…) I admit, I got a bit excited. It's always bothered me that I can view the scene in Cartoon Shaded, but had to jump through numerous hoops, including purchasing separate products, in order to render in that style. But now I can. Thank you, Daz.

To test this out, I used my render, Tea Time, and ultimately created a toon version of the image, (both are currently linked in my signature.) Mostly it worked "out of the box." There is an issue if an object has any opacity, either less than 100% or a transmap. Where the opacity exists, the rendered image, (in the render window, not the viewport,) is also transparent. For example, eyelashes. Where the lashes should be, the image is transparent. The opacity of zero works correctly for the mesh, It's only where the opacity is greater than zero that the image has the same opacity.

Knowing that now, I think it would have been much easier to create a scene specifically to use as a toon rather than converting this particular image to use the Cartoon Shaded mode.

Not sure if the opacity issue deserves a bug report, though.

MEC4D

First of all you need Filament in the viewport to be able to render out bigger render of the Filament, other way you will get OpenGL render only as it was there for so long I guess you never tried it before .

I have no issue with opacity map, it render exactly as I see it in the viewport , no matter what draw mode I use .

If you use cartoon shader preview the setting of cutoutpacity not really matter, as long there is an proper alpha map , assuming you using Iray shader for that , other viewport modes than Filament and Iray was made for 3DL shaders so it render as OpenGL as it was before.

Use 3DL shaders for the cartoon mode preview as Iray shader not really works with it at full  , however if you use opacity map it works, it only need to be black and white without middle gray colors for a true alpha, if the eyelashes alpha is not completely white on black it will not works . the proper cutout opacity values are 0 or 1 and nothing between it, that why it is called Cutout , opacity on materials don't excist in PBR iray shader

same when you render refractions like glass etc.. it need to have something behind it like a prop or Enviorment as it will not render in a vacuum space and not in Filament

looks below, cartoon viewport and cutout alpha map ( Iray shader as I was too lazy to change it to 3DL ) and Filament render out and the rest works fine , can you show image to see the problem you have ? 

 

L'Adair said:

KInda, sorta, off topic… Cath mentioned something in passing about making sure the Render Engine is set to Iray and not Viewport a day or two ago. I thought, "What!?" so I went looking, and sure enough, where it use to say "OpenGL" it now says "Viewport". I don't know what version brought us that change, but I suspect it was the same version that made Filament available. (Because, as far as I can see, that's the only way to actually render an image with Filament. Currently, of course.) But I'm getting sidetracked.

I tested this new "Viewport" as render engine, and found it does render your viewport to a separate window, regardless of what Draw Mode I tried. (I did not try all of them…) I admit, I got a bit excited. It's always bothered me that I can view the scene in Cartoon Shaded, but had to jump through numerous hoops, including purchasing separate products, in order to render in that style. But now I can. Thank you, Daz.

To test this out, I used my render, Tea Time, and ultimately created a toon version of the image, (both are currently linked in my signature.) Mostly it worked "out of the box." There is an issue if an object has any opacity, either less than 100% or a transmap. Where the opacity exists, the rendered image, (in the render window, not the viewport,) is also transparent. For example, eyelashes. Where the lashes should be, the image is transparent. The opacity of zero works correctly for the mesh, It's only where the opacity is greater than zero that the image has the same opacity.

Knowing that now, I think it would have been much easier to create a scene specifically to use as a toon rather than converting this particular image to use the Cartoon Shaded mode.

Not sure if the opacity issue deserves a bug report, though.

 

L'Adair

MEC4D said:

First of all you need Filament in the viewport to be able to render out bigger render of the Filament, other way you will get OpenGL render only as it was there for so long I guess you never tried it before .

I have no issue with opacity map, it render exactly as I see it in the viewport , no matter what draw mode I use .

If you use cartoon shader preview the setting of cutoutpacity not really matter, as long there is an proper alpha map , assuming you using Iray shader for that , other viewport modes than Filament and Iray was made for 3DL shaders so it render as OpenGL as it was before.

Use 3DL shaders for the cartoon mode preview as Iray shader not really works with it at full  , however if you use opacity map it works, it only need to be black and white without middle gray colors for a true alpha, if the eyelashes alpha is not completely white on black it will not works . the proper cutout opacity values are 0 or 1 and nothing between it, that why it is called Cutout , opacity on materials don't excist in PBR iray shader

same when you render refractions like glass etc.. it need to have something behind it like a prop or Enviorment as it will not render in a vacuum space and not in Filament

looks below, cartoon viewport and cutout alpha map ( Iray shader as I was too lazy to change it to 3DL ) and Filament render out and the rest works fine , can you show image to see the problem you have ?

This falls under the category of, "Well, that's embarassing!"

I remember searching the forums with Google, looking for a way to render the "Cartoon Shaded" version of the Viewport draw. I found post after post where other people asking the same question were told they need PwToon or ToonyCam Pro. Not once did I see a response that said, "just set your render engine to OpenGL in the Render Settings."

And now that Daz has renamed the setting "Viewport", I "discovered" I can now render Cartoon Shaded. Only now you're telling me, that option has been available to me all along… This underscores why a manual would be really useful. (Even though I understand perfectly why a manual for a "moving target" is just not feasible.)

As always, thank you for your help. Hugs.

 

DustRider

Same issue here, going straight to CPU on a scene that would render with CPU in the previous version (3 sectional planes). I upgraded to the latest version hoping it fixed the problem I was having with a render dropping to CPU about 60% done, but now it won't render with GPU at all, GPU rendering works fine with the stable build.

MEC4D

I wish I came across your question early , I use it for so long, mostly for rendering wire frames and color swabs , you never too old to learn something new !  

L'Adair said:

MEC4D said:

 

This falls under the category of, "Well, that's embarassing!"

I remember searching the forums with Google, looking for a way to render the "Cartoon Shaded" version of the Viewport draw. I found post after post where other people asking the same question were told they need PwToon or ToonyCam Pro. Not once did I see a response that said, "just set your render engine to OpenGL in the Render Settings."

And now that Daz has renamed the setting "Viewport", I "discovered" I can now render Cartoon Shaded. Only now you're telling me, that option has been available to me all along… This underscores why a manual would be really useful. (Even though I understand perfectly why a manual for a "moving target" is just not feasible.)

As always, thank you for your help. Hugs.

 

 

takezo_3001

.

MEC4D said:

I wish I came across your question early , I use it for so long, mostly for rendering wire frames and color swabs , you never too old to learn something new !  

This is the very creed that I live by!

The best thing about being proven wrong is that you learn how to be right at the same time!

Dolce Saito

A few notes by my side:

- For every beta release, filament is getting brighter and brighter. Like a nuke dropped near the scene. :)

- Repeating: Filament is too transparent on surfaces with cutout opacity mapping available. It doesn't take mapping image into account (to a degree). It just makes the surface overly transparent.

- Filament is too sharp/bumpy.

- I don't know why, but every time I change exposure in draw settings when filament is the engine also changes the exposure in renders settings (for iray). I have to manually tune it back.

- I didn't know exactly how that happened, but I went crazy once that "tone mapping" section just didn't appear in draw settings for filament. I didn't know what made it disappear or what made it appear much later on (after restarting studio).

- I will wrong myself: "Copy-pasting tcb keyframes didn't corrupt animation and freeze daz studio anymore...". They still do. Randomly, but when it happens it is too late. The unsaved animation is gone. This will be a trouble if there are dforce animated data in your scene. Because, it is pain to save and wait 2-3 minutes (more or less depending on animation length) after every step to avoid losing data to freezing.

 

Also a workaround; My cpu fallback is off. In case you were able to render one frame but went out of memory somehow (due to low light etc), your cuda device decides to disable itself without reporting it. Go back to texture shaded mode. Then go to the iray advanced settings -> untick and re-enable your cuda device. Surprise! (No need to shut down and re-open everything). Works every time for me.

Moviehawk

.60 just crashed on me - no error messages in log file, just went bye-bye. 

Not that difficult a scene, well within memory limits.

Can't use it if I can't trust it. Bummer - it was actually saving timeline data/morphs properly - was hoping to start using for animations - but not ready for prime time yet.

. 

 

Richard Haseltine

Moviehawk said:

.60 just crashed on me - no error messages in log file, just went bye-bye. 

Not that difficult a scene, well within memory limits.

Can't use it if I can't trust it. Bummer - it was actually saving timeline data/morphs properly - was hoping to start using for animations - but not ready for prime time yet.

Was it rendering? What Drawstyle was in use for the Viewport?

barbult

I submitted a help request (Request #351148) about tool icon problems with the Strand-Based Hair Editor in DS 4.12.2.60,  and Customer Service suggested that I post the problem here. (I already posted about it in the Strand-Based Hair Editor thread and the problem was confirmed by 3Diva.) The problem is that the tool icons on the Style tab are incorrect and do not represent what the tool does. It looks like there is a completely wrong set of tool icons on the top row and then the rest of the tool icons are pushed down to lower rows, with some tool icons completely missing.

Correct tools in 4.12.1.117

Incorrect tools in DS 4.12.2.60

Moviehawk

.60 just crashed on me - no error messages in log file, just went bye-bye. 

Richard Haseltine said:

Moviehawk said:

Not that difficult a scene, well within memory limits.

Can't use it if I can't trust it. Bummer - it was actually saving timeline data/morphs properly - was hoping to start using for animations - but not ready for prime time yet.

Was it rendering? What Drawstyle was in use for the Viewport?

Iray.

I keep shooting myself in the foot - I installed  .60 on my backup machine, it crashed, I uninstalled - now on my older versions of Studio the CPU option for dforce is gone. Dforce won't function with my Intel HD Graphics 630. Anyone know how to reinstall/reset dforce to the CPU???

I keep having serious issues with this new beta messing up previous installations. Still having screen-freezes on my main system running older versions of Studio - that worked great until trying the beta.

There must be some common/shared files that are being updated with the beta that conflict with older versions of Studio.

Is there an easy way to wipe studio completely from my system - and just start over? Or just a recommended procedure?

(I would need install files for .87 - the only version safe to do animations with)

Thanks

 

DoctorJellybean

@barbult: it looks like the style files got their wires crossed. You can try 2 things:

Uninstall, reboot and reinstall or with DS closed (verified in task manager), manually delete the style files and reinstall. If the files cannot be manually deleted, then something could be preventing the updated files from being dropped by the installer as they might be "locked".

barbult

DoctorJellybean said:

@barbult: it looks like the style files got their wires crossed. You can try 2 things:

Uninstall, reboot and reinstall or with DS closed (verified in task manager), manually delete the style files and reinstall. If the files cannot be manually deleted, then something could be preventing the updated files from being dropped by the installer as they might be "locked".

I use a custom workspace with all the options saved as custom. Does that affect this? Is there an "update and merge" for style files?

DoctorJellybean

barbult said:

DoctorJellybean said:

@barbult: it looks like the style files got their wires crossed. You can try 2 things:

Uninstall, reboot and reinstall or with DS closed (verified in task manager), manually delete the style files and reinstall. If the files cannot be manually deleted, then something could be preventing the updated files from being dropped by the installer as they might be "locked".

I use a custom workspace with all the options saved as custom. Does that affect this? Is there an "update and merge" for style files?

Did you move\manipulate any *style files in \resources\style? There is no update and merge for style files, and the custom workspace shouldn't affect it. I have a custom workspace and the Strand Hair Based Editor appears fine for me.

barbult

DoctorJellybean said:

barbult said:

DoctorJellybean said:

@barbult: it looks like the style files got their wires crossed. You can try 2 things:

Uninstall, reboot and reinstall or with DS closed (verified in task manager), manually delete the style files and reinstall. If the files cannot be manually deleted, then something could be preventing the updated files from being dropped by the installer as they might be "locked".

I use a custom workspace with all the options saved as custom. Does that affect this? Is there an "update and merge" for style files?

Did you move\manipulate any *style files in \resources\style? There is no update and merge for style files, and the custom workspace shouldn't affect it. I have a custom workspace and the Strand Hair Based Editor appears fine for me.

I'm not sure, so I switched to City Limits workspace and Darkside style, but I still have the problem of the wrong tool icons.

Edit: then I tried the Main Street style and closed DS 4.12.2.60 and restarted it. I still have the problem with the Strand-Based Hair Editor tool icons.

evacyn

Not sure if this was discussed, but is GenX not supported in the current beta version? I've installed it several times and it works fine in the full 4.12 release but the current beta doesn't show the GenX window.

Richard Haseltine

evacyn said:

Not sure if this was discussed, but is GenX not supported in the current beta version? I've installed it several times and it works fine in the full 4.12 release but the current beta doesn't show the GenX window.

Was it working in betas before? Some plug-ins don't.