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

nemesis10

So..  I broke something.... i have a mac and have remained at High Sierra so I could continue using my Nvidia card.  I decided to try the beta and lose the Nvidia acceleration and keep my standard Daz Studio 4.12 with Nvidia acceleration.  After installation, beta works great with the slow CPU rendering while regular installation renders fast and great but Smart Content and autofit no longer works.... Any ideas?

RayDAnt

barbult said:

gerster said:

RayDAnt said:

gerster said:

I still think that DAZ should automatically open a new instance, if the main instance is still running.
There's an issue that you can't start DAZ again, after you closed it, until the DAZ task is finishd with clean up, which can take a while after closing a complex scene.

At the same time, this serves as a very straightforward way to alert the user that a previous instance has not yet shut down. Which in turn can lead to major usability problems (eg. not being able to work on/render scenes in a new instance up to the max capacity of system/GPU ram due to the previous instance holding on to things) whose true cause is otherwise very easy to overlook.

I think not starting without any warning is the most worse solution. It will confuse users, which don't know the background of the behavoir if DAZ ist just not starting.

The best thing would be if DAZ would show a warning and offers an option in the settings that can be opted-in and automatically starts a new instance, for more advanced users.

I agree that just not starting with no warning is very confusing.

Confusing, perhaps, but still better (in terms of user-experience) than how it was before.

 

 

gerster said:

RayDAnt said:

gerster said:

I still think that DAZ should automatically open a new instance, if the main instance is still running.
There's an issue that you can't start DAZ again, after you closed it, until the DAZ task is finishd with clean up, which can take a while after closing a complex scene.

At the same time, this serves as a very straightforward way to alert the user that a previous instance has not yet shut down. Which in turn can lead to major usability problems (eg. not being able to work on/render scenes in a new instance up to the max capacity of system/GPU ram due to the previous instance holding on to things) whose true cause is otherwise very easy to overlook.

I think not starting without any warning is the most worse solution. It will confuse users, which don't know the background of the behavoir if DAZ ist just not starting.

The best thing would be if DAZ would show a warning

That would make the most sense. Feature request it here. Just type "N/A" in the Order Number field, select "Tech Support Issue" for Sales Ticket Tracker, and "UI Issues in Daz Studio" for Tech Ticket Tracker.

 

gerster said:

and offers an option in the settings that can be opted-in and automatically starts a new instance, for more advanced users.

They already did. Just append " -instanceName #" to the Target field in the properties box of your desktop shortcut to Daz Studio Beta. Now you can have as many simultaneous instances as you want.

mikmod

Richard Haseltine said:

prixat said:

Playing with the new Matte Fog on 4.12.1.115.

Does anyone else get the swapped Blue and Green colour channels?

Red is correct and gives red fog.

This is a bug and has been fixed.

I'd like to ask - will Nvidia fix a bug, where I can't use hardware Iray rendering anymore due to illegal instruction exception as soon as I click render or use preview Iray render? I'm using RTX 2080 and Skylake-X processor on Windows 7 and this OS doesn't support AVX-512 instruction set, which I think is the issue. Stable 4.12 works fine, but next updated 4.12 versions won't as long as Iray crashes on combo Skylake-X CPUs+Win7. Ah, CPU rendering on both versions also runs fine. I reported this on the Zendesk, but for now there's no answer. I believe there will not be, since we have this pandemic situation and Iray is totally on Nvidia's field.

Maybe there's environment variable for that, like this one for OpenCV libraries AVX-512 issue? 

OPENCV_IPP=AVX2

Zilvergrafix

Dunno if the sofware is asking for directives or if suggest my thinking about this:

barbult

DAZ_Rawb asked that feedback on the beta be posted here. I've submitted several bug reports on DS 4.12.1.109 and 4.12.1.115 which I don't think have been fixed yet. 

Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder
Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded
Request #328589 View Control Shift+K doesn't work after DS Beta update
Request #328270 Render Settings Record Range input bug in DS 4.12.1.109
Request #328711 Color of Spotlight changes when timeline keyframe is moved or copy/pasted

 

Hurdy3D

RayDAnt said:

and offers an option in the settings that can be opted-in and automatically starts a new instance, for more advanced users.

They already did. Just append " -instanceName #" to the Target field in the properties box of your desktop shortcut to Daz Studio Beta. Now you can have as many simultaneous instances as you want.

No that's not the same.

The solution you described has some disadvantages.

1) It's not helping with Mans Friday Render Queue

2) we need two DAZ icons, to start. One for the main instance and one for the numbered instances, which makes using DAZ more complicate.

nicstt

I use instances all the time, so not sure what folks are bothered about; sure Studio can be slow getting rid of itself (sometimes very) but eventually even if it's a lurker it only uses a couple hundre K bytes, which is less than when it starts up for me. I will eventually kill em off if i get a few building up.

I use the main icon to start Studio; I have link to a batch script for the instances. the [1, 2, 3, 4.. etc] tells me what it is.

RayDAnt

gerster said:

RayDAnt said:

and offers an option in the settings that can be opted-in and automatically starts a new instance, for more advanced users.

They already did. Just append " -instanceName #" to the Target field in the properties box of your desktop shortcut to Daz Studio Beta. Now you can have as many simultaneous instances as you want.

No that's not the same.

The solution you described has some disadvantages.

1) It's not helping with Mans Friday Render Queue

To be fair, Render Queue is an addon to Daz Studio - not the other way around. If Daz ends up going with this mechanism (or something very like it - remember this is Beta software we're talking about) in the next final release the onus would be on ManFriday to change/update the plugin to maintain compatiblity.

 

gerster said:

2) we need two DAZ icons, to start. One for the main instance and one for the numbered instances, which makes using DAZ more complicate.

Yes. But if advanced Daz Studio users are the target demographic of this featureset (a point you yourself made here earlier that I wholeheartedly agree with)  added complication in exchange for greater control over app behavior is a non-issue.

I'm not saying that things should be made needlessly complex. But they also shouldn't be artificially simplified. Doing complex things with computer software generally requires having an advanced level of understanding into how those things are done.

barbult

Another bug report

Request #328938 Some keyframes are not displayed in DS 4.1.12.115 Timeline when a saved file is reopened

MeneerWolfman

While the last two beta's have been a vast, vast improvement over the previous ones, this last beta has been giving me some odd issues.

I had been working on a scene for a while, switching in and out Iray preview. Made some changes, hit the aux viewport tab whic had the iray preview view and got a super quick pop-up that said something to the extent of "target invalid" and then daz crashed. And not in a way that would let me record why it crashed.

A scene I'm currently working on is doing fine except the last two times I've gone to render the scene, I get a windows Memory error message about being low on memory and asking to close Daz. I tell it to cancel and the error message goes away, but I'm a bit concerned because I have 48gb of memory. Of which currently, with this image rendering, is only at 74% physical memory. While Daz is sucking up a crapton of memory (25.5gb), I still have 12gb free according to Windows. What would be causing this?

marble

barbult said:

Another bug report

Request #328938 Some keyframes are not displayed in DS 4.1.12.115 Timeline when a saved file is reopened

Is that related to the problem I highlighted in this post: https://www.daz3d.com/forums/discussion/comment/5553146/#Comment_5553146 ; ?

Reminder: Save animation, re-open, some parts of the animation are reset to either zero or static parameter values. I experienced this with attachments (hair) and with store-bought morphs (Zev0, etc.).

EDIT - sorry that link doesn't seem to take me to the correct post so here's what I wrote:

I've just noticed a problem with saving a short animation using the new timeline (I'm on this latest 4.12.1.109 beta). 

I created an animation and rendered it, saved the scene and quit DAZ Studio. The render came out as expected but I noticed things I wanted to tweak so I re-loaded the scene and moved a hand and one leg. Then I rendered again but the finished animation had changed form the original. Some animated body parts and attachments (hair, for example) which had animated movement were now static. I'm trying to narrow it down but it seems to be a problem with attachments and with some morphs such as Zev0's Glute Control - I had animated some squish effects whuch were all cleared upon reload.

Does any of this make sense? Would it help to animate with KeyMate/GraphMate instead?

BTW: I have the Key Creation Scope set to "Node". I don't understand the options, however.

 

 

barbult

marble said:

barbult said:

Another bug report

Request #328938 Some keyframes are not displayed in DS 4.1.12.115 Timeline when a saved file is reopened

Is that related to the problem I highlighted in this post: https://www.daz3d.com/forums/discussion/comment/5553146/#Comment_5553146 ; ?

Reminder: Save animation, re-open, some parts of the animation are reset to either zero or static parameter values. I experienced this with attachments (hair) and with store-bought morphs (Zev0, etc.).

EDIT - sorry that link doesn't seem to take me to the correct post so here's what I wrote:

I've just noticed a problem with saving a short animation using the new timeline (I'm on this latest 4.12.1.109 beta). 

I created an animation and rendered it, saved the scene and quit DAZ Studio. The render came out as expected but I noticed things I wanted to tweak so I re-loaded the scene and moved a hand and one leg. Then I rendered again but the finished animation had changed form the original. Some animated body parts and attachments (hair, for example) which had animated movement were now static. I'm trying to narrow it down but it seems to be a problem with attachments and with some morphs such as Zev0's Glute Control - I had animated some squish effects whuch were all cleared upon reload.

Does any of this make sense? Would it help to animate with KeyMate/GraphMate instead?

BTW: I have the Key Creation Scope set to "Node". I don't understand the options, however.

 

 

No, I don't think so. In my case, the reloaded scene had all the animation that it had before. Playing the timeline looked correct, but some the keyframes were not visible in the Timeline. The invisible keyframes were operating, but not visible. TRSOAH was set, so I believe all keyframes should have been visible. I had to toggle the "O" in TRSOAH OFF and ON again to get the invisible keyframes to show up.

However, I have seen strange symptoms similar to what you described. In my case, I had a scene that animated G8F from her base shape to another dialed character shape in a later keyframe. The animation played correctly. After saving and reloading the scene, the dialed shape was in frame 0 instead of later in the animation sequence. There was no change of shape as I ran the animation. I can repeated the failure scenario with that scene (i.e. I can change it to set frame 0 back to base G8F and set the dialed shape later, save the scene and reload it and see the same problem.) But I don't understand it well enough to create a simple scene that reliably demonstrates the problem, so I haven't reported it.

marble

barbult said:

marble said:

barbult said:

Another bug report

Request #328938 Some keyframes are not displayed in DS 4.1.12.115 Timeline when a saved file is reopened

Is that related to the problem I highlighted in this post: https://www.daz3d.com/forums/discussion/comment/5553146/#Comment_5553146 ; ?

Reminder: Save animation, re-open, some parts of the animation are reset to either zero or static parameter values. I experienced this with attachments (hair) and with store-bought morphs (Zev0, etc.).

EDIT - sorry that link doesn't seem to take me to the correct post so here's what I wrote:

I've just noticed a problem with saving a short animation using the new timeline (I'm on this latest 4.12.1.109 beta). 

I created an animation and rendered it, saved the scene and quit DAZ Studio. The render came out as expected but I noticed things I wanted to tweak so I re-loaded the scene and moved a hand and one leg. Then I rendered again but the finished animation had changed form the original. Some animated body parts and attachments (hair, for example) which had animated movement were now static. I'm trying to narrow it down but it seems to be a problem with attachments and with some morphs such as Zev0's Glute Control - I had animated some squish effects whuch were all cleared upon reload.

Does any of this make sense? Would it help to animate with KeyMate/GraphMate instead?

BTW: I have the Key Creation Scope set to "Node". I don't understand the options, however.

 

 

No, I don't think so. In my case, the reloaded scene had all the animation that it had before. Playing the timeline looked correct, but some the keyframes were not visible in the Timeline. The invisible keyframes were operating, but not visible. TRSOAH was set, so I believe all keyframes should have been visible. I had to toggle the "O" in TRSOAH OFF and ON again to get the invisible keyframes to show up.

However, I have seen strange symptoms similar to what you described. In my case, I had a scene that animated G8F from her base shape to another dialed character shape in a later keyframe. The animation played correctly. After saving and reloading the scene, the dialed shape was in frame 0 instead of later in the animation sequence. There was no change of shape as I ran the animation. I can repeated the failure scenario with that scene (i.e. I can change it to set frame 0 back to base G8F and set the dialed shape later, save the scene and reload it and see the same problem.) But I don't understand it well enough to create a simple scene that reliably demonstrates the problem, so I haven't reported it.

Unfortunately I'm not confident enough with animation to log a tech support report. I know they will ask me things that will lose me in the technicalities. I've attempted two animations with the new timeline and both have been changed on re-load. Also, the new graph editor seems to be half-finished - I can't use the pan and zoom controls to see the waveforms so I went back to using GraphMate. I wish someone there would just keep an eye on this thread.

barbult

marble said:

barbult said:

marble said:

barbult said:

Another bug report

Request #328938 Some keyframes are not displayed in DS 4.1.12.115 Timeline when a saved file is reopened

Is that related to the problem I highlighted in this post: https://www.daz3d.com/forums/discussion/comment/5553146/#Comment_5553146 ; ?

Reminder: Save animation, re-open, some parts of the animation are reset to either zero or static parameter values. I experienced this with attachments (hair) and with store-bought morphs (Zev0, etc.).

EDIT - sorry that link doesn't seem to take me to the correct post so here's what I wrote:

I've just noticed a problem with saving a short animation using the new timeline (I'm on this latest 4.12.1.109 beta). 

I created an animation and rendered it, saved the scene and quit DAZ Studio. The render came out as expected but I noticed things I wanted to tweak so I re-loaded the scene and moved a hand and one leg. Then I rendered again but the finished animation had changed form the original. Some animated body parts and attachments (hair, for example) which had animated movement were now static. I'm trying to narrow it down but it seems to be a problem with attachments and with some morphs such as Zev0's Glute Control - I had animated some squish effects whuch were all cleared upon reload.

Does any of this make sense? Would it help to animate with KeyMate/GraphMate instead?

BTW: I have the Key Creation Scope set to "Node". I don't understand the options, however.

 

 

No, I don't think so. In my case, the reloaded scene had all the animation that it had before. Playing the timeline looked correct, but some the keyframes were not visible in the Timeline. The invisible keyframes were operating, but not visible. TRSOAH was set, so I believe all keyframes should have been visible. I had to toggle the "O" in TRSOAH OFF and ON again to get the invisible keyframes to show up.

However, I have seen strange symptoms similar to what you described. In my case, I had a scene that animated G8F from her base shape to another dialed character shape in a later keyframe. The animation played correctly. After saving and reloading the scene, the dialed shape was in frame 0 instead of later in the animation sequence. There was no change of shape as I ran the animation. I can repeated the failure scenario with that scene (i.e. I can change it to set frame 0 back to base G8F and set the dialed shape later, save the scene and reload it and see the same problem.) But I don't understand it well enough to create a simple scene that reliably demonstrates the problem, so I haven't reported it.

Unfortunately I'm not confident enough with animation to log a tech support report. I know they will ask me things that will lose me in the technicalities. I've attempted two animations with the new timeline and both have been changed on re-load. Also, the new graph editor seems to be half-finished - I can't use the pan and zoom controls to see the waveforms so I went back to using GraphMate. I wish someone there would just keep an eye on this thread.

I know what you mean. I don't even know how to find the graph editor.

Richard Haseltine

barbult said:

marble said:

barbult said:

marble said:

barbult said:

Another bug report

Request #328938 Some keyframes are not displayed in DS 4.1.12.115 Timeline when a saved file is reopened

Is that related to the problem I highlighted in this post: https://www.daz3d.com/forums/discussion/comment/5553146/#Comment_5553146 ; ?

Reminder: Save animation, re-open, some parts of the animation are reset to either zero or static parameter values. I experienced this with attachments (hair) and with store-bought morphs (Zev0, etc.).

EDIT - sorry that link doesn't seem to take me to the correct post so here's what I wrote:

I've just noticed a problem with saving a short animation using the new timeline (I'm on this latest 4.12.1.109 beta). 

I created an animation and rendered it, saved the scene and quit DAZ Studio. The render came out as expected but I noticed things I wanted to tweak so I re-loaded the scene and moved a hand and one leg. Then I rendered again but the finished animation had changed form the original. Some animated body parts and attachments (hair, for example) which had animated movement were now static. I'm trying to narrow it down but it seems to be a problem with attachments and with some morphs such as Zev0's Glute Control - I had animated some squish effects whuch were all cleared upon reload.

Does any of this make sense? Would it help to animate with KeyMate/GraphMate instead?

BTW: I have the Key Creation Scope set to "Node". I don't understand the options, however.

 

 

No, I don't think so. In my case, the reloaded scene had all the animation that it had before. Playing the timeline looked correct, but some the keyframes were not visible in the Timeline. The invisible keyframes were operating, but not visible. TRSOAH was set, so I believe all keyframes should have been visible. I had to toggle the "O" in TRSOAH OFF and ON again to get the invisible keyframes to show up.

However, I have seen strange symptoms similar to what you described. In my case, I had a scene that animated G8F from her base shape to another dialed character shape in a later keyframe. The animation played correctly. After saving and reloading the scene, the dialed shape was in frame 0 instead of later in the animation sequence. There was no change of shape as I ran the animation. I can repeated the failure scenario with that scene (i.e. I can change it to set frame 0 back to base G8F and set the dialed shape later, save the scene and reload it and see the same problem.) But I don't understand it well enough to create a simple scene that reliably demonstrates the problem, so I haven't reported it.

Unfortunately I'm not confident enough with animation to log a tech support report. I know they will ask me things that will lose me in the technicalities. I've attempted two animations with the new timeline and both have been changed on re-load. Also, the new graph editor seems to be half-finished - I can't use the pan and zoom controls to see the waveforms so I went back to using GraphMate. I wish someone there would just keep an eye on this thread.

I know what you mean. I don't even know how to find the graph editor.

It's probably collapsed under the Dope Sheet in the Timleine - click the show/hide button mid-way along the collapsed divider bar at the bottom of the pane.

Richard Haseltine

barbult said:

DAZ_Rawb asked that feedback on the beta be posted here. I've submitted several bug reports on DS 4.12.1.109 and 4.12.1.115 which I don't think have been fixed yet. 

Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

This is a known issue, I think it was reported

barbult said:

Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

Again, this is not a new issue in tis beta

barbult said:

Request #328589 View Control Shift+K doesn't work after DS Beta update

Shift K seems to correctly switch WASD navigation on/off. It's an application setting, not a file/document setting. Check your shortcuts in Window>Workspace>Customise.

barbult said:

Request #328270 Render Settings Record Range input bug in DS 4.12.1.109
Request #328711 Color of Spotlight changes when timeline keyframe is moved or copy/pasted

 

 

barbult

Richard Haseltine said:

barbult said:

DAZ_Rawb asked that feedback on the beta be posted here. I've submitted several bug reports on DS 4.12.1.109 and 4.12.1.115 which I don't think have been fixed yet. 

Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

This is a known issue, I think it was reported

barbult said:

Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

Again, this is not a new issue in tis beta

barbult said:

Request #328589 View Control Shift+K doesn't work after DS Beta update

Shift K seems to correctly switch WASD navigation on/off. It's an application setting, not a file/document setting. Check your shortcuts in Window>Workspace>Customise.

barbult said:

Request #328270 Render Settings Record Range input bug in DS 4.12.1.109
Request #328711 Color of Spotlight changes when timeline keyframe is moved or copy/pasted

 

 

Thanks for taking time to read and reply. Here is some more info.

RE: Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

Yes, I know it is a known issue. I reported it here in the forum. You said that Rob said it was a bug, You said I should report it in case Rob didn't get a chance to log it. So I wrote the help request about the "known problem". I linked that forum discussion in my help request.

RE: Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

It may not be new in this Beta, but that is where I ran into it. I did not go back and check every previous build to see when it first occurred. Who cares. It is still in the latest available build, so it is still a problem that needs fixing. There is no list of known bugs for users to refer to. How could I know if it was previously reported?

RE: Request #328589 View Control Shift+K doesn't work after DS Beta update

Every time I restart Daz Studio DS 4.12.1.115 (and it happened in 109, too)  WASD navigation is turned on, even though I turned it off in the previous session. Looking at my shortcuts (F3) shows that Shift+K is defined as the shortcut for View Control. But Shift+K does nothing. If I go to F3 and click Accept, Shift+K works again, until the next time I start DS. This info is in the  help request. If it works differently for you, maybe something else is conflicting for me.

Richard Haseltine

barbult said:

Richard Haseltine said:

barbult said:

DAZ_Rawb asked that feedback on the beta be posted here. I've submitted several bug reports on DS 4.12.1.109 and 4.12.1.115 which I don't think have been fixed yet. 

Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

This is a known issue, I think it was reported

barbult said:

Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

Again, this is not a new issue in tis beta

barbult said:

Request #328589 View Control Shift+K doesn't work after DS Beta update

Shift K seems to correctly switch WASD navigation on/off. It's an application setting, not a file/document setting. Check your shortcuts in Window>Workspace>Customise.

barbult said:

Request #328270 Render Settings Record Range input bug in DS 4.12.1.109
Request #328711 Color of Spotlight changes when timeline keyframe is moved or copy/pasted

 

 

Thanks for taking time to read and reply. Here is some more info.

RE: Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

Yes, I know it is a known issue. I reported it here in the forum. You said that Rob said it was a bug, You said I should report it in case Rob didn't get a chance to log it. So I wrote the help request about the "known problem". I linked that forum discussion in my help request.

RE: Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

It may not be new in this Beta, but that is where I ran into it. I did not go back and check every previous build to see when it first occurred. Who cares. It is still in the latest available build, so it is still a problem that needs fixing. There is no list of known bugs for users to refer to. How could I know if it was previously reported?

RE: Request #328589 View Control Shift+K doesn't work after DS Beta update

Every time I restart Daz Studio DS 4.12.1.115 (and it happened in 109, too)  WASD navigation is turned on, even though I turned it off in the previous session. Looking at my shortcuts (F3) shows that Shift+K is defined as the shortcut for View Control. But Shift+K does nothing. If I go to F3 and click Accept, Shift+K works again, until the next time I start DS. This info is in the  help request. If it works differently for you, maybe something else is conflicting for me.

Are other changes to the UI and application settings persisting between sessions, just not the keboard navigation?

barbult

Richard Haseltine said:

barbult said:

Richard Haseltine said:

barbult said:

DAZ_Rawb asked that feedback on the beta be posted here. I've submitted several bug reports on DS 4.12.1.109 and 4.12.1.115 which I don't think have been fixed yet. 

Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

This is a known issue, I think it was reported

barbult said:

Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

Again, this is not a new issue in tis beta

barbult said:

Request #328589 View Control Shift+K doesn't work after DS Beta update

Shift K seems to correctly switch WASD navigation on/off. It's an application setting, not a file/document setting. Check your shortcuts in Window>Workspace>Customise.

barbult said:

Request #328270 Render Settings Record Range input bug in DS 4.12.1.109
Request #328711 Color of Spotlight changes when timeline keyframe is moved or copy/pasted

 

 

Thanks for taking time to read and reply. Here is some more info.

RE: Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

Yes, I know it is a known issue. I reported it here in the forum. You said that Rob said it was a bug, You said I should report it in case Rob didn't get a chance to log it. So I wrote the help request about the "known problem". I linked that forum discussion in my help request.

RE: Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

It may not be new in this Beta, but that is where I ran into it. I did not go back and check every previous build to see when it first occurred. Who cares. It is still in the latest available build, so it is still a problem that needs fixing. There is no list of known bugs for users to refer to. How could I know if it was previously reported?

RE: Request #328589 View Control Shift+K doesn't work after DS Beta update

Every time I restart Daz Studio DS 4.12.1.115 (and it happened in 109, too)  WASD navigation is turned on, even though I turned it off in the previous session. Looking at my shortcuts (F3) shows that Shift+K is defined as the shortcut for View Control. But Shift+K does nothing. If I go to F3 and click Accept, Shift+K works again, until the next time I start DS. This info is in the  help request. If it works differently for you, maybe something else is conflicting for me.

Are other changes to the UI and application settings persisting between sessions, just not the keboard navigation?

I haven't noticed any other shortcut keys not working after I restart DS. It remembers things like what was displayed in the Content Library and displays that again when I restart. It remembers what layout to use. Is there anything specific I should check?

Richard Haseltine

barbult said:

Richard Haseltine said:

barbult said:

Richard Haseltine said:

barbult said:

DAZ_Rawb asked that feedback on the beta be posted here. I've submitted several bug reports on DS 4.12.1.109 and 4.12.1.115 which I don't think have been fixed yet. 

Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

This is a known issue, I think it was reported

barbult said:

Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

Again, this is not a new issue in tis beta

barbult said:

Request #328589 View Control Shift+K doesn't work after DS Beta update

Shift K seems to correctly switch WASD navigation on/off. It's an application setting, not a file/document setting. Check your shortcuts in Window>Workspace>Customise.

barbult said:

Request #328270 Render Settings Record Range input bug in DS 4.12.1.109
Request #328711 Color of Spotlight changes when timeline keyframe is moved or copy/pasted

 

 

Thanks for taking time to read and reply. Here is some more info.

RE: Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

Yes, I know it is a known issue. I reported it here in the forum. You said that Rob said it was a bug, You said I should report it in case Rob didn't get a chance to log it. So I wrote the help request about the "known problem". I linked that forum discussion in my help request.

RE: Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

It may not be new in this Beta, but that is where I ran into it. I did not go back and check every previous build to see when it first occurred. Who cares. It is still in the latest available build, so it is still a problem that needs fixing. There is no list of known bugs for users to refer to. How could I know if it was previously reported?

RE: Request #328589 View Control Shift+K doesn't work after DS Beta update

Every time I restart Daz Studio DS 4.12.1.115 (and it happened in 109, too)  WASD navigation is turned on, even though I turned it off in the previous session. Looking at my shortcuts (F3) shows that Shift+K is defined as the shortcut for View Control. But Shift+K does nothing. If I go to F3 and click Accept, Shift+K works again, until the next time I start DS. This info is in the  help request. If it works differently for you, maybe something else is conflicting for me.

Are other changes to the UI and application settings persisting between sessions, just not the keboard navigation?

I haven't noticed any other shortcut keys not working after I restart DS. It remembers things like what was displayed in the Content Library and displays that again when I restart. It remembers what layout to use. Is there anything specific I should check?

You could try deliberately making some changes and see if they stick - failing to recall a chnaged (corrected) shortcut does sound like a problem writing the updated file, unless some custom utility or rare script that is running on launch is changing them

MeneerWolfman

The Oso shader pack 1 shader product. This product no longer works in the current beta. This product works fine in the current public general release.

DoctorJellybean

MeneerWolfman said:

The Oso shader pack 1 shader product. This product no longer works in the current beta. This product works fine in the current public general release.

What isn't working for you? I've just given it a quick spin and it appears to work.

MeneerWolfman

DoctorJellybean said:

MeneerWolfman said:

The Oso shader pack 1 shader product. This product no longer works in the current beta. This product works fine in the current public general release.

What isn't working for you? I've just given it a quick spin and it appears to work.

I get nothing but the base diffuse color. Newest Iray Driver, Titan RTX. Works fine in the general release.

barbult

Richard Haseltine said:

barbult said:

Richard Haseltine said:

barbult said:

Richard Haseltine said:

barbult said:

DAZ_Rawb asked that feedback on the beta be posted here. I've submitted several bug reports on DS 4.12.1.109 and 4.12.1.115 which I don't think have been fixed yet. 

Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

This is a known issue, I think it was reported

barbult said:

Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

Again, this is not a new issue in tis beta

barbult said:

Request #328589 View Control Shift+K doesn't work after DS Beta update

Shift K seems to correctly switch WASD navigation on/off. It's an application setting, not a file/document setting. Check your shortcuts in Window>Workspace>Customise.

barbult said:

Request #328270 Render Settings Record Range input bug in DS 4.12.1.109
Request #328711 Color of Spotlight changes when timeline keyframe is moved or copy/pasted

 

 

Thanks for taking time to read and reply. Here is some more info.

RE: Request #324394 DS 4.12 shows plus sign when dragging asset into Daz Connect virtual folder

Yes, I know it is a known issue. I reported it here in the forum. You said that Rob said it was a bug, You said I should report it in case Rob didn't get a chance to log it. So I wrote the help request about the "known problem". I linked that forum discussion in my help request.

RE: Request #328365 Render Settings "Series Base" is not restored when a saved scene is reloaded

It may not be new in this Beta, but that is where I ran into it. I did not go back and check every previous build to see when it first occurred. Who cares. It is still in the latest available build, so it is still a problem that needs fixing. There is no list of known bugs for users to refer to. How could I know if it was previously reported?

RE: Request #328589 View Control Shift+K doesn't work after DS Beta update

Every time I restart Daz Studio DS 4.12.1.115 (and it happened in 109, too)  WASD navigation is turned on, even though I turned it off in the previous session. Looking at my shortcuts (F3) shows that Shift+K is defined as the shortcut for View Control. But Shift+K does nothing. If I go to F3 and click Accept, Shift+K works again, until the next time I start DS. This info is in the  help request. If it works differently for you, maybe something else is conflicting for me.

Are other changes to the UI and application settings persisting between sessions, just not the keboard navigation?

I haven't noticed any other shortcut keys not working after I restart DS. It remembers things like what was displayed in the Content Library and displays that again when I restart. It remembers what layout to use. Is there anything specific I should check?

You could try deliberately making some changes and see if they stick - failing to recall a chnaged (corrected) shortcut does sound like a problem writing the updated file, unless some custom utility or rare script that is running on launch is changing them

I added a keyboard shortcut Shift+? to one of my custom actions. I closed DS and reopened it and that shortcut is recognized. Shift+K is still not recognized.

Edit to add: I have never installed the released 4.12.0.86. I still have the last 4.11 release version. Shift+K works fine in 4.11.

barbult

There is nothing in the 4.12.beta highlights thread for either of the last two versions (4.12.1.115 and 4.12.1.117).

RayDAnt

barbult said:

There is nothing in the 4.12.beta highlights thread for either of the last two versions (4.12.1.115 and 4.12.1.117).

See the full changelog - updates have been coming fast and heavy lately (most likely with fewer staff around, given the current world situation.)

barbult

RayDAnt said:

barbult said:

There is nothing in the 4.12.beta highlights thread for either of the last two versions (4.12.1.115 and 4.12.1.117).

See the full changelog - updates have been coming fast and heavy lately (most likely with fewer staff around, given the current world situation.)

The Highlights thread is usually tailored more toward user understanding than the techno-speak of the change log. So I was hoping for continued support of that thread. I'm sure you are right that they are working fast and furious to get a new release (non-Beta) out.

DoctorJellybean

MeneerWolfman said:

DoctorJellybean said:

MeneerWolfman said:

The Oso shader pack 1 shader product. This product no longer works in the current beta. This product works fine in the current public general release.

What isn't working for you? I've just given it a quick spin and it appears to work.

I get nothing but the base diffuse color. Newest Iray Driver, Titan RTX. Works fine in the general release.

Not even when it renders?

MeneerWolfman

DoctorJellybean said:

MeneerWolfman said:

DoctorJellybean said:

MeneerWolfman said:

The Oso shader pack 1 shader product. This product no longer works in the current beta. This product works fine in the current public general release.

What isn't working for you? I've just given it a quick spin and it appears to work.

I get nothing but the base diffuse color. Newest Iray Driver, Titan RTX. Works fine in the general release.

Not even when it renders?

Affirmative :-/

Richard Haseltine

barbult said:

RayDAnt said:

barbult said:

There is nothing in the 4.12.beta highlights thread for either of the last two versions (4.12.1.115 and 4.12.1.117).

See the full changelog - updates have been coming fast and heavy lately (most likely with fewer staff around, given the current world situation.)

The Highlights thread is usually tailored more toward user understanding than the techno-speak of the change log. So I was hoping for continued support of that thread. I'm sure you are right that they are working fast and furious to get a new release (non-Beta) out.

Lots of updates does mean Rob has been busy, so I'm afraid the updates to those psots have fallen by the wayside (at least for now).