Daz Studio BETA - version 4.23.1.27!

gram

Dolce Saito said:

Richard Haseltine said:

Dolce Saito said:

Is it reported somewhere or am I the only one with undo stack issues? The undo stack looses track on what is happening in the scene frequently. I don't know if these are repeatable or just happening randomly, but with a long timeline, I created a key somewhere, then mistakenly moved a camera on another frame, hit ctrl+z, then the key was deleted instead of latest camera movement. The put it in simple terms; there was no "camera movement" in the undo stack. Just an example. But all undo stack had was the created key. All limb movements, all camera movements, character poses are lost in the undo stack. Good that I saved the scene prior.

Camera or view? By design the Perspective (and other) view is not tracked for undo - and is not remembered between sessions.

Camera. I don't know why or when bug decides to trigger, but when it does, undo stack stops registering random inputs on characters/objects. It sometimes does it after creating a keyframe on character in junction with a recent camera movement (actual camera object).

Oh yes, this happens to me relatively often. Just out of blue some actions/changes in the scene are not registered into the undo stack. Like posing a character on viewport - not in undo out of sudden. And then you do some other change and then it is in undo again.

I have no idea what triggers it, only thing I can think of is that it usually happens if i've worked with daz for a longer time.

barbult

I've had many more "fatal error and must close" crashes and "Not Responding" freezes with 4.23.1.27 than any previous recent beta. It usually happens after I have been working in the Viewport for a long time or using the timeline for dForce simulation. The longer I work, the slower it gets and the more likely it is to crash. I can't point to a repeatable scenario, but it is so frequent with this beta, that I felt I should mention it. I am on Windows 10, 32 GB RAM and RTX 3080 GPU.

tombraider4ever

Edit, nevermind I found it .

Does someone know where the settings is to convert old ghostligt to work in the beta? I had saved converted ghostlights from the latest versions but they don't work.

crosswind

barbult said:

I've had many more "fatal error and must close" crashes and "Not Responding" freezes with 4.23.1.27 than any previous recent beta. It usually happens after I have been working in the Viewport for a long time or using the timeline for dForce simulation. The longer I work, the slower it gets and the more likely it is to crash. I can't point to a repeatable scenario, but it is so frequent with this beta, that I felt I should mention it. I am on Windows 10, 32 GB RAM and RTX 3080 GPU.

I've not experienced crash yet with 4.23.1.27 on my side but I've been experiencing its performance turning lower and lower with long time's use, especially in Viewport.  With Win11, 128GB RAM, 4090, I still have to use Purge Memory script to improve the performance in Viewport from time to time.

I think it's a long standing issue that DS has bad RAM management now thing's getting worse in PB.

Imago

barbult said:

I've had many more "fatal error and must close" crashes and "Not Responding" freezes with 4.23.1.27 than any previous recent beta. It usually happens after I have been working in the Viewport for a long time or using the timeline for dForce simulation. The longer I work, the slower it gets and the more likely it is to crash. I can't point to a repeatable scenario, but it is so frequent with this beta, that I felt I should mention it. I am on Windows 10, 32 GB RAM and RTX 3080 GPU.

Just tried working a bit longer with the latest beta to see if I get the same and I can confirm that, after a while I'm working on the scenes, DAZ Studio starts slowing down and freezing randomly.

The freezing/slowing down happens more often if I move a prop or change a value, so it could be somewhat related to the Undo Stack that keeps registering Perspective View movements and ignores camers/prop/model's changes.

But it stopped crashing on complex scenes load. It's something.

barbult

There was recently an update to the G9 Dev Tools, but an error I reported almost two years ago has never been fixed. That help request was probably never reported to the developers, because customer service never responded to my ticket. Sure, they are behind, but TWO YEARS? When it gets to 3 years old, they just silently close it and mark it solved. What a crummy way to treat customers. But anyway, here is the error report I submitted:

crosswind

barbult said:

There was recently an update to the G9 Dev Tools, but an error I reported almost two years ago has never been fixed. That help request was probably never reported to the developers, because customer service never responded to my ticket. Sure, they are behind, but TWO YEARS? When it gets to 3 years old, they just silently close it and mark it solved. What a crummy way to treat customers. But anyway, here is the error report I submitted:

That file name has never been corrected in the script. Each time I had to modify it after updating G9 starter essentials ......

barbult

crosswind said:

barbult said:

There was recently an update to the G9 Dev Tools, but an error I reported almost two years ago has never been fixed. That help request was probably never reported to the developers, because customer service never responded to my ticket. Sure, they are behind, but TWO YEARS? When it gets to 3 years old, they just silently close it and mark it solved. What a crummy way to treat customers. But anyway, here is the error report I submitted:

That file name has never been corrected in the script. Each time I had to modify it after updating G9 starter essentials ......

Yup, me too.

Richard Haseltine

barbult said:

crosswind said:

barbult said:

There was recently an update to the G9 Dev Tools, but an error I reported almost two years ago has never been fixed. That help request was probably never reported to the developers, because customer service never responded to my ticket. Sure, they are behind, but TWO YEARS? When it gets to 3 years old, they just silently close it and mark it solved. What a crummy way to treat customers. But anyway, here is the error report I submitted:

That file name has never been corrected in the script. Each time I had to modify it after updating G9 starter essentials ......

Yup, me too.

Not, however, a Daz Studio issue - it is a content issue that needs to be handled by the content QA team.

Richard Haseltine

barbult said:

I've had many more "fatal error and must close" crashes and "Not Responding" freezes with 4.23.1.27 than any previous recent beta. It usually happens after I have been working in the Viewport for a long time or using the timeline for dForce simulation. The longer I work, the slower it gets and the more likely it is to crash. I can't point to a repeatable scenario, but it is so frequent with this beta, that I felt I should mention it. I am on Windows 10, 32 GB RAM and RTX 3080 GPU.

Although a search of http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log for Viewport does turn up a few hits, none of them has any relation to anything that would impact performance. With this kind of issue the first thing to do is check that it is not a third-party plug-in causing prob lems, by disabling them all and then seeing (to the extent that you can work) if the issue is resolved.

barbult

Richard Haseltine said:

barbult said:

crosswind said:

barbult said:

There was recently an update to the G9 Dev Tools, but an error I reported almost two years ago has never been fixed. That help request was probably never reported to the developers, because customer service never responded to my ticket. Sure, they are behind, but TWO YEARS? When it gets to 3 years old, they just silently close it and mark it solved. What a crummy way to treat customers. But anyway, here is the error report I submitted:

That file name has never been corrected in the script. Each time I had to modify it after updating G9 starter essentials ......

Yup, me too.

Not, however, a Daz Studio issue - it is a content issue that needs to be handled by the content QA team.

Oh, OK. How can I get QA team's attention on this problem? Submitting a help request didn't work.

Richard Haseltine

barbult said:

Richard Haseltine said:

barbult said:

crosswind said:

barbult said:

There was recently an update to the G9 Dev Tools, but an error I reported almost two years ago has never been fixed. That help request was probably never reported to the developers, because customer service never responded to my ticket. Sure, they are behind, but TWO YEARS? When it gets to 3 years old, they just silently close it and mark it solved. What a crummy way to treat customers. But anyway, here is the error report I submitted:

That file name has never been corrected in the script. Each time I had to modify it after updating G9 starter essentials ......

Yup, me too.

Not, however, a Daz Studio issue - it is a content issue that needs to be handled by the content QA team.

Oh, OK. How can I get QA team's attention on this problem? Submitting a help request didn't work.

Sorry, I don't have a better solution.

barbult

I just did a spot render of an UltraScenery2 scene, and the spot render got "stuck" in the viewport. No amount of clicking in the viewport would clear the spot render. I even tried clicking with a few different tools selected. The cursor was an arrow, but there was a blue circle spinning around it. Daz Studio was still responding to other things, though. I could save my scene with V3D Super Save. I could click in the Scene pane and move items into an existing group. Finally I changed the draw style with the drop down menu and that cleared the spot render. I had successfully done spot renders in this scene several times before this problem occurred. I had no problem clicking in the viewport to clear those previous spot renders.

Richard Haseltine

barbult said:

I just did a spot render of an UltraScenery2 scene, and the spot render got "stuck" in the viewport. No amount of clicking in the viewport would clear the spot render. I even tried clicking with a few different tools selected. The cursor was an arrow, but there was a blue circle spinning around it. Daz Studio was still responding to other things, though. I could save my scene with V3D Super Save. I could click in the Scene pane and move items into an existing group. Finally I changed the draw style with the drop down menu and that cleared the spot render. I had successfully done spot renders in this scene several times before this problem occurred. I had no problem clicking in the viewport to clear those previous spot renders.

It is beginning to sound as if theer may be issues with the GPU drivers.

gram

Richard Haseltine said:

gram said:

Richard Haseltine said:

Via script it can, I think (cetainly most are, I haven't tried DoF though).

See http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/elements/post_load_view_proxy_create/start (which I frequently, but not always, forget to mention)

This actually seems to work, even DoF is there. 

I must say i am a bit confused with the purpose of these proxy nodes - what is the general use case behind them?

They allow the creation of remote-control nodes, items in the scene that can be used to control properties on other item(s) (ERC links work only within an item if they are to be saved) and they can also do thinks like making material properties (not animatable in themselves) aniamtable by linking them to regular, aniamtable node properties.

 

After some time the proxy camera works quite well, i noticed one small bug. When i create the proxy it has all the camera properties (Focal length, Dof, Focal distance) - but when I reload the scene the proxy node no longer has these extra parameters. I have to re-create it.

Of course this is very simple, but thought to note. Maybe there is similar issue with other types than just cameras.

The other potential use cases are also relatively interesting, have to try them out some day.

barbult

Richard Haseltine said:

barbult said:

I just did a spot render of an UltraScenery2 scene, and the spot render got "stuck" in the viewport. No amount of clicking in the viewport would clear the spot render. I even tried clicking with a few different tools selected. The cursor was an arrow, but there was a blue circle spinning around it. Daz Studio was still responding to other things, though. I could save my scene with V3D Super Save. I could click in the Scene pane and move items into an existing group. Finally I changed the draw style with the drop down menu and that cleared the spot render. I had successfully done spot renders in this scene several times before this problem occurred. I had no problem clicking in the viewport to clear those previous spot renders.

It is beginning to sound as if theer may be issues with the GPU drivers.

I haven't updated NVIDIA graphics drivers. I'm using 560.94, which I've had for several Daz Studio beta builds now (over many months). As I understand it, Iray hasn't been updated, so I think this graphics driver should still be working OK. Right???

Richard Haseltine

barbult said:

Richard Haseltine said:

barbult said:

I just did a spot render of an UltraScenery2 scene, and the spot render got "stuck" in the viewport. No amount of clicking in the viewport would clear the spot render. I even tried clicking with a few different tools selected. The cursor was an arrow, but there was a blue circle spinning around it. Daz Studio was still responding to other things, though. I could save my scene with V3D Super Save. I could click in the Scene pane and move items into an existing group. Finally I changed the draw style with the drop down menu and that cleared the spot render. I had successfully done spot renders in this scene several times before this problem occurred. I had no problem clicking in the viewport to clear those previous spot renders.

It is beginning to sound as if theer may be issues with the GPU drivers.

I haven't updated NVIDIA graphics drivers. I'm using 560.94, which I've had for several Daz Studio beta builds now (over many months). As I understand it, Iray hasn't been updated, so I think this graphics driver should still be working OK. Right???

It does seem odd, but it may be worth  a clean reinstall - things like this are GPU-related, and it is possible that something else might damage the driver. Of course it is also possible that the GPU might have developed hardware issues, which would be even worse.