Loading...
> >

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

24567…26

Comments

  • barbultbarbult Posts: 24,240

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

  • no__nameno__name Posts: 88
    edited November 2020
    Richard Haseltine said:
    dim_sh_ecd463260f said:

    I wrote earlier here on the forum, https://www.daz3d.com/forums/discussion/comment/6139332/#Comment_6139332

    wrote in support. I was waiting for the new version to be released, but the Iray Plain Node was never fixed. Shame on you, Daz. 

    Your duplicate posts have been removed.

    An Iray render crash is almost certainly going to requier a fix from nVidia, not Daz. For that to happen they need a basic set of steps to trigger the crash - Daz QA has not been able to get the crash to happen, and therefore has nothing to pass to nVidia. If you can give simple steps that reliably trigger the crash, or a scene file that causes the crash on load and render, then please make sure support has those details.

    https://www.daz3d.com/forums/discussion/comment/6205951/#Comment_6205951
    https://www.daz3d.com/forums/discussion/comment/6203211/#Comment_6203211
    https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691
    https://www.daz3d.com/forums/discussion/comment/6140197/#Comment_6140197
    https://www.daz3d.com/forums/discussion/comment/6140312/#Comment_6140312
    https://www.daz3d.com/forums/discussion/comment/6140342/#Comment_6140342
    https://www.daz3d.com/forums/discussion/comment/6139067/#Comment_6139067
    https://www.daz3d.com/forums/discussion/comment/6139457/#Comment_6139457
    https://www.daz3d.com/forums/discussion/comment/6139637/#Comment_6139637
    https://www.daz3d.com/forums/discussion/comment/6139712/#Comment_6139712
    https://www.daz3d.com/forums/discussion/comment/6139737/#Comment_6139737
    https://www.daz3d.com/forums/discussion/comment/6139787/#Comment_6139787
    https://www.daz3d.com/forums/discussion/comment/6139982/#Comment_6139982

    All these post talk about the same crash with Iray section plane. And how to reproduce it. I could keep going.

    I send message to Daz QA, 15th October, with all the step to reproduce it. No answer so far.

    We're 11th November, 4.14.0.8, problem is still not even acknowledged. indecision

    Post edited by no__name on
  • Richard HaseltineRichard Haseltine Posts: 100,778
    capitanharlock80 said:
    Richard Haseltine said:
    dim_sh_ecd463260f said:

    I wrote earlier here on the forum, https://www.daz3d.com/forums/discussion/comment/6139332/#Comment_6139332

    wrote in support. I was waiting for the new version to be released, but the Iray Plain Node was never fixed. Shame on you, Daz. 

    Your duplicate posts have been removed.

    An Iray render crash is almost certainly going to requier a fix from nVidia, not Daz. For that to happen they need a basic set of steps to trigger the crash - Daz QA has not been able to get the crash to happen, and therefore has nothing to pass to nVidia. If you can give simple steps that reliably trigger the crash, or a scene file that causes the crash on load and render, then please make sure support has those details.

    In case it could be useful (and I hope it will be, it's really a big problem for those of us who use Iray planes), here are the simple steps to follow to reproduce the problem:

    https://www.daz3d.com/forums/discussion/comment/6205951/#Comment_6205951

     

    As a curiosity, commenting that when testing the 4.12.2.60 beta to be able to use the RTX 3090, everything seemed to work fine, I was able to render 159 frames of an animation at night (from a total of 420); but from there on I've had that problem.
    To clear up any doubt that some change in the system could have caused that, today I've done the test with a clean installation of W10, just installing the latest Nvidia driver, Daz 4.14, and the essential G8 pack... the result is the same, it still gives the same error :-/

     

    no__name said:
    Richard Haseltine said:
    dim_sh_ecd463260f said:

    I wrote earlier here on the forum, https://www.daz3d.com/forums/discussion/comment/6139332/#Comment_6139332

    wrote in support. I was waiting for the new version to be released, but the Iray Plain Node was never fixed. Shame on you, Daz. 

    Your duplicate posts have been removed.

    An Iray render crash is almost certainly going to requier a fix from nVidia, not Daz. For that to happen they need a basic set of steps to trigger the crash - Daz QA has not been able to get the crash to happen, and therefore has nothing to pass to nVidia. If you can give simple steps that reliably trigger the crash, or a scene file that causes the crash on load and render, then please make sure support has those details.

    https://www.daz3d.com/forums/discussion/comment/6205951/#Comment_6205951
    https://www.daz3d.com/forums/discussion/comment/6203211/#Comment_6203211
    https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691
    https://www.daz3d.com/forums/discussion/comment/6140197/#Comment_6140197
    https://www.daz3d.com/forums/discussion/comment/6140312/#Comment_6140312
    https://www.daz3d.com/forums/discussion/comment/6140342/#Comment_6140342
    https://www.daz3d.com/forums/discussion/comment/6139067/#Comment_6139067
    https://www.daz3d.com/forums/discussion/comment/6139457/#Comment_6139457
    https://www.daz3d.com/forums/discussion/comment/6139637/#Comment_6139637
    https://www.daz3d.com/forums/discussion/comment/6139712/#Comment_6139712
    https://www.daz3d.com/forums/discussion/comment/6139737/#Comment_6139737
    https://www.daz3d.com/forums/discussion/comment/6139787/#Comment_6139787
    https://www.daz3d.com/forums/discussion/comment/6139982/#Comment_6139982

    All these post talk about the same crash with Iray section plane. And how to reproduce it. I could keep going.

    I send message to Daz QA, 15th October, with all the step to reproduce it. No answer so far.

    We're 11th November, 4.14.0.8, problem is still not even acknowledged. indecision

    Yes, the issue has been reproted - but daz can't reproduce it, it seems to vary by system or by some other factor and until they have a reliable and repeatable way to show the issue they can't expect nVidia to look into it.

  • L'AdairL'Adair Posts: 9,479
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

  • Saxa -- SDSaxa -- SD Posts: 872
    jbowler said:
    The second, the new problem, is that Daz never exits, or at least not for "many hours"; I let it sit there for 12 on one occasion.

    Official position is that users are supposed to wait for shutdown. Once waited as long as 5 minutes and still wasn't clearing out memory.

    So, Personally I have a batch file i click on desktop that force-closes DS.  Basically just task-kill in batch format for quicker use. After probably a year of this on various DS versions with many long day sessions, still have zero ill effects.  My usage is probaly near the high-end, and still it's been fine for me.  However should anything negative happen, I know I am on my own.  ie. unsupported which is why many follow official position and wait for close.

    Looking in Regular Release DocJellyBean wrote it's being investigated.

  • no__nameno__name Posts: 88
    edited November 2020
    Richard Haseltine said:
     

    Yes, the issue has been reproted - but daz can't reproduce it, it seems to vary by system or by some other factor and until they have a reliable and repeatable way to show the issue they can't expect nVidia to look into it.

    Thanks for answering, I just hope devs know there is some problem here (could reproduce it on two different machines at work tho).

    If I update Daz by mistake, I lose around ~800 scenes, as I rely heavily on section plane for various reasons.  Can't also upgrade my system with a 3xxx card as I would be forced to update.

    Make things a bit spicy for me lol.

    Post edited by no__name on
  • barbultbarbult Posts: 24,240
    L'Adair said:
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

    Yes, that is a better question. Do you think we will get an answer?

  • Saxa -- SDSaxa -- SD Posts: 872
    no__name said:
    Richard Haseltine said:
     

    Yes, the issue has been reproted - but daz can't reproduce it, it seems to vary by system or by some other factor and until they have a reliable and repeatable way to show the issue they can't expect nVidia to look into it.

    Thanks for answering, I just hope devs know there is some problem here (could reproduce it on two different machines at work tho).

    If I update Daz by mistake, I lose around ~800 scenes, as I really heavily on section plane for various reasons.  Can't also upgrade my system with a 3xxx card as I would be forced to update.

    Make things a bit spicy for me lol.

    There are situations where your PC software environment may not be working exactly as DAZ's systems.  Case in point, probably 6 months ago a user was having OpenCL issues.  Daz support told them couldn't reproduce.  User asked for help in forums and in the end their registry had a toggle value that was interfering, and with a modifying of  said entry OpenCL worked fine.  So many users with different PC systems and Win10 doing "inconsistent updates" from time to time on some users machines is probably not helping either.  Only so much Daz support can do and know.

  • Saxa -- SDSaxa -- SD Posts: 872
    barbult said:
    L'Adair said:
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

    Yes, that is a better question. Do you think we will get an answer?

    Going to make an educated guess having worked alot with IT.

    The safest route from DAZ's perspective is to to restore the whole menus to vanilla each time with that command, so there is no conflicts left behind or lingering effects, just in case.  Or something close to that.  Is it possible to make this work with user content? Maybe.  Problem is if there is any overlap, there could be unforseen conflicts.  So, this is likely the safest route.

    That is just a guess though, not having poked through everything.  So whatev this is worth.

     

  • barbultbarbult Posts: 24,240
    Saxa -- SD said:
    barbult said:
    L'Adair said:
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

    Yes, that is a better question. Do you think we will get an answer?

    Going to make an educated guess having worked alot with IT.

    The safest route from DAZ's perspective is to to restore the whole menus to vanilla each time with that command, so there is no conflicts left behind or lingering effects, just in case.  Or something close to that.  Is it possible to make this work with user content? Maybe.  Problem is if there is any overlap, there could be unforseen conflicts.  So, this is likely the safest route.

    That is just a guess though, not having poked through everything.  So whatev this is worth.

     

    I thought the specific point of the "merge" in the "update and merge" name was to prevent wiping out custom menus. A lot of work goes into setting up custom menus. Deleting them without warning is pretty harsh.

  • Richard HaseltineRichard Haseltine Posts: 100,778
    L'Adair said:
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

    It will do its best to preserve any customisations (or rather to add them back in after updating). I don't generally have custom actions on the Scripts menu, but the process does seem to do a good job or maintaining them in place for the most part.

  • jbowlerjbowler Posts: 794
    jbowler said:

    Daz never exits, or at least not for "many hours"; I let it sit there for 12 on one occasion. 

    Since I now have the same .exe exiting in one case and not the other I should be able to track the problem down; it pretty much has to be a plug-ini (but not Octane in my case) which is failing to exit after the relevant (app close down, AppExit) signal.

    Nope; no cigar, I'm going to have to stick with my wife's horrible Menthol Marlboros (M&Ms).  I have disabled every single plugin, that includes the Iray and 3Delight ones so my Beta is back to "OpenGL multipass" rendering.  Despite this the exit still hangs and, apparently, it is waiting on a whole load of Iray threads; 16 (magic number) threads inside libneuray.dll of which one, one very specific one (I don't have symbols so I can't assert this) is always the guilty party.

    I suspect the beta has debugging options enabled which actually detect a problem but, rather that doing something good like crashing, just hang.  I haven't tracked down one of the DLLs in the list yet; ig9icd64.dll, so that might be a culprit.  Everything else seems plausible, even the boost DLLs, yuck; there are three of them, they are all stuck in the Microsoft C library, which suggests a dynamically loaded DLL, which might correspond to a plug-in yet they are all disabled...

  • Saxa -- SDSaxa -- SD Posts: 872

    Would seem a clarification from Daz programmers how this update/merge should work would be kinda helpful.  Interesting to hear there is some kind of preservation intended, but with 2 longtime savvy users both having issues, seems a bit more info is needed to help.

    Have only updated/merged menus once myself over the last 2 years plus, but not before a total backup of my customizations.  As it was, all was fine after update/merge for what I had customized.

  • NathNath Posts: 2,798
    Richard Haseltine said:
    L'Adair said:
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

    It will do its best to preserve any customisations (or rather to add them back in after updating). I don't generally have custom actions on the Scripts menu, but the process does seem to do a good job or maintaining them in place for the most part.

    Except for the three out of five it removed here.

  • Dolce SaitoDolce Saito Posts: 192
    edited November 2020
    Richard Haseltine said:
    L'Adair said:
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

    It will do its best to preserve any customisations (or rather to add them back in after updating). I don't generally have custom actions on the Scripts menu, but the process does seem to do a good job or maintaining them in place for the most part.

    I had 3 submenus with a few custom actions underneath them. Everything is gone except only one submenu with one custom action underneath it. Neither I have any idea why others are gone, nor why the one left was the "chosen one". In any case, it was disturbing.

    Post edited by Dolce Saito on
  • PerttiAPerttiA Posts: 10,024
    edited November 2020
    Saxa -- SD said:
    no__name said:
    Richard Haseltine said:
     

    Yes, the issue has been reproted - but daz can't reproduce it, it seems to vary by system or by some other factor and until they have a reliable and repeatable way to show the issue they can't expect nVidia to look into it.

    Thanks for answering, I just hope devs know there is some problem here (could reproduce it on two different machines at work tho).

    If I update Daz by mistake, I lose around ~800 scenes, as I really heavily on section plane for various reasons.  Can't also upgrade my system with a 3xxx card as I would be forced to update.

    Make things a bit spicy for me lol.

    There are situations where your PC software environment may not be working exactly as DAZ's systems.  Case in point, probably 6 months ago a user was having OpenCL issues.  Daz support told them couldn't reproduce.  User asked for help in forums and in the end their registry had a toggle value that was interfering, and with a modifying of  said entry OpenCL worked fine.  So many users with different PC systems and Win10 doing "inconsistent updates" from time to time on some users machines is probably not helping either.  Only so much Daz support can do and know.

    Sometimes the difference may even be something as trivial as the country of residence - I once had a case where a manufacturer in northern america built the exact system with all the same software and drivers that I was using and they still couldn't reproduce the problem (serious), after which I started figuring out, what had they done differently...

    Post edited by PerttiA on
  • cain-xcain-x Posts: 186

    Seems that point lights do not cast shadows no matter if its deep shadow map or raytraced. Is this intended or a known defect?

    Will there be lights that allow softer shadows for filament? Right now all lights are hard shadows.

    Also the play/pause which I set to spacebar is very finicky and does not always stop the playback of the timeline.

    +1 on emissives question.

  • no__nameno__name Posts: 88
    Saxa -- SD said:
    no__name said:
    Richard Haseltine said:
     

    Yes, the issue has been reproted - but daz can't reproduce it, it seems to vary by system or by some other factor and until they have a reliable and repeatable way to show the issue they can't expect nVidia to look into it.

    Thanks for answering, I just hope devs know there is some problem here (could reproduce it on two different machines at work tho).

    If I update Daz by mistake, I lose around ~800 scenes, as I really heavily on section plane for various reasons.  Can't also upgrade my system with a 3xxx card as I would be forced to update.

    Make things a bit spicy for me lol.

    There are situations where your PC software environment may not be working exactly as DAZ's systems.  Case in point, probably 6 months ago a user was having OpenCL issues.  Daz support told them couldn't reproduce.  User asked for help in forums and in the end their registry had a toggle value that was interfering, and with a modifying of  said entry OpenCL worked fine.  So many users with different PC systems and Win10 doing "inconsistent updates" from time to time on some users machines is probably not helping either.  Only so much Daz support can do and know.

    Daz support didn't even bother to answer, not sure they even read lol. And it's too widespread to be just a single PC problem (not sure if I can link another forum).

    "can't reproduce", here on another machine with an old 1060 :

    2020-11-12 14:59:12.217 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 16.66% of image converged2020-11-12 14:59:12.326 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00253 iterations after 204.325s.2020-11-12 14:59:33.382 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00281 iterations after 225.391s.2020-11-12 14:59:55.741 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Tail kernel failed after 0.004s2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): an illegal memory access was encountered (while launching CUDA renderer in <internal>:705)2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Failed to launch renderer2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Device failed while rendering2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : All available GPUs failed.2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: Fallback to CPU not allowed.

     

  • Richard HaseltineRichard Haseltine Posts: 100,778
    felix_nukem said:
    Richard Haseltine said:
    L'Adair said:
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

    It will do its best to preserve any customisations (or rather to add them back in after updating). I don't generally have custom actions on the Scripts menu, but the process does seem to do a good job or maintaining them in place for the most part.

    I had 3 submenus with a few custom actions underneath them. Everything is gone except only one submenu with one custom action underneath it. Neither I have any idea why others are gone, nor why the one left was the "chosen one". In any case, it was disturbing.

    I can't test this very well as I haven't added much customisation since having to do a system reinstall a couple of moths back, but what should happen (and did seem to happen for me, at least since an update long ago) is that DS will note the differences from the defaults, replace the menus with the new defaults (the Update part), and then add back the customisations (the Merge part). The actual custom actions should be firmly fixed in the Custom tree on the left of Window>Workspace>Customise.

  • NathNath Posts: 2,798
    Richard Haseltine said:
    felix_nukem said:
    Richard Haseltine said:
    L'Adair said:
    barbult said:

    Update and Merge Menus removed everything from my Scripts menu and my Bookmarks menu.Why is such a destructive thing recommended?

    Good to know. And I agree, that shouldn't happen. My question isn't why it's recommended, though. My question is why does this action do anything to our saved, custom menus in the first place?

    It will do its best to preserve any customisations (or rather to add them back in after updating). I don't generally have custom actions on the Scripts menu, but the process does seem to do a good job or maintaining them in place for the most part.

    I had 3 submenus with a few custom actions underneath them. Everything is gone except only one submenu with one custom action underneath it. Neither I have any idea why others are gone, nor why the one left was the "chosen one". In any case, it was disturbing.

    I can't test this very well as I haven't added much customisation since having to do a system reinstall a couple of moths back, but what should happen (and did seem to happen for me, at least since an update long ago) is that DS will note the differences from the defaults, replace the menus with the new defaults (the Update part), and then add back the customisations (the Merge part). The actual custom actions should be firmly fixed in the Custom tree on the left of Window>Workspace>Customise.

    They are in the custom tree, but not in the dropdown, and refuse to show up there (yes, the paths are correct) - but at least that helps in redoing all of them, even if some then announce that they already exist, but only the new one turns up in the dropdown, even if there are now two in the Custom tree window.

  • Richard HaseltineRichard Haseltine Posts: 100,778
    jbowler said:
    jbowler said:

    Daz never exits, or at least not for "many hours"; I let it sit there for 12 on one occasion. 

    Since I now have the same .exe exiting in one case and not the other I should be able to track the problem down; it pretty much has to be a plug-ini (but not Octane in my case) which is failing to exit after the relevant (app close down, AppExit) signal.

    Nope; no cigar, I'm going to have to stick with my wife's horrible Menthol Marlboros (M&Ms).  I have disabled every single plugin, that includes the Iray and 3Delight ones so my Beta is back to "OpenGL multipass" rendering.  Despite this the exit still hangs and, apparently, it is waiting on a whole load of Iray threads; 16 (magic number) threads inside libneuray.dll of which one, one very specific one (I don't have symbols so I can't assert this) is always the guilty party.

    I suspect the beta has debugging options enabled which actually detect a problem but, rather that doing something good like crashing, just hang.  I haven't tracked down one of the DLLs in the list yet; ig9icd64.dll, so that might be a culprit.  Everything else seems plausible, even the boost DLLs, yuck; there are three of them, they are all stuck in the Microsoft C library, which suggests a dynamically loaded DLL, which might correspond to a plug-in yet they are all disabled...

    Thank you, I am told that the incorrect loading of libneuray and dependencies has been confirmed and fixed, though it is unlikely to resolve the shutdown issues as those are in the Qt thread pool and Iray is not built with Qt.

  • jbowlerjbowler Posts: 794
    edited November 2020
    Richard Haseltine said:

    I am told that the incorrect loading of libneuray and dependencies has been confirmed and fixed, though it is unlikely to resolve the shutdown issues as those are in the Qt thread pool and Iray is not built with Qt.

    I suspected libneuray and the cuda libraries for that matter were some other bug.  I've finally found a work-round and, maybe, a fix.  I de-installed the beta (where I have the problem), deinstalling all the dependent products (GoZ, measure metrcs, photoshop bridge and Postgres) as well and reverting those the general release.  I then removed (actually renamed) the AppData folder for the beta and then reinstalled the beta (and all the dependencies, which automatically de-install the general versioons).

    At this point I have normal behavior on open/immediate close; the DAZStudio task sits there for a short time with a non-zero CPU% (about half a CPU) then exits cleanly.  I'm now guessing there is some configuration file issue.  Since my work round deletes all my script entries (as well as actually turning all the plug-ins back on) I'll try restoriing some of the configuration using the old files.

    UPDATE: I could both fix and unfix the problem by deleting/restoring C:\Users\my user name\AppData\Roaming\DAZ 3D\Studio4 Public Build\layout.dsx  Deleting it restores the window layout to the default and DAZStudio exits just fine.  If anyone wants to test this I suggest just renaming layout.dsx temporarily to layout.dsx.saved, if you uses -instanceName # then the file actually exists in the instance AppData directory.

    UPDATE 2: In my case I fixed the problem in layout.dsx by deleting the <Pane> element with Class="DzAuxViewportPane"; I've appended the problem element below but it looks well formed to me.  At this point I figured I wasn't getting paid enough to keep debugging it so I just copied my general release layout.dsx into the public beta; I prefer having a UI which is the same in both anyway.

      <Pane Class="DzAuxViewportPane">
       <Setting Type="String" Key="ActiveCamera">PerspectiveView</Setting>
       <Setting Type="Bool" Key="AxesOn">no</Setting>
       <Setting Type="Bool" Key="AspectOn">yes</Setting>
       <Setting Type="Bool" Key="ThirdsGuideOn">no</Setting>
       <Setting Type="Bool" Key="PoseToolOn">no</Setting>
       <Setting Type="Int" Key="ToolBarMode">1</Setting>
       <Setting Type="Int" Key="FloorStyle">1</Setting>
       <Setting Type="Int" Key="ShadeStyle">7</Setting>
       <Setting Type="Bool" Key="CubeShown">no</Setting>
       <Setting Type="Bool" Key="AutoHideViewOptions">yes</Setting>
       <Setting Type="Bool" Key="AutoHideViewControls">yes</Setting>
       <Setting Type="Bool" Key="ShowToolbar">yes</Setting>
      </Pane>

    Post edited by jbowler on
  • fixmypcmikefixmypcmike Posts: 19,583
    jbowler said:
     

    UPDATE: I could both fix and unfix the problem by deleting/restoring C:\Users\my user name\AppData\Roaming\DAZ 3D\Studio4 Public Build\layout.dsx  Deleting it restores the window layout to the default and DAZStudio exits just fine.  If anyone wants to test this I suggest just renaming layout.dsx temporarily to layout.dsx.saved, if you uses -instanceName # then the file actually exists in the instance AppData directory.

    I can confirm this -- I've had DS never closing for several versions.  Renaming layout.dsx allows it to close.

  • capitanharlock80capitanharlock80 Posts: 36
    no__name said:
    Saxa -- SD said:
    no__name said:
    Richard Haseltine said:
     

    Yes, the issue has been reproted - but daz can't reproduce it, it seems to vary by system or by some other factor and until they have a reliable and repeatable way to show the issue they can't expect nVidia to look into it.

    Thanks for answering, I just hope devs know there is some problem here (could reproduce it on two different machines at work tho).

    If I update Daz by mistake, I lose around ~800 scenes, as I really heavily on section plane for various reasons.  Can't also upgrade my system with a 3xxx card as I would be forced to update.

    Make things a bit spicy for me lol.

    There are situations where your PC software environment may not be working exactly as DAZ's systems.  Case in point, probably 6 months ago a user was having OpenCL issues.  Daz support told them couldn't reproduce.  User asked for help in forums and in the end their registry had a toggle value that was interfering, and with a modifying of  said entry OpenCL worked fine.  So many users with different PC systems and Win10 doing "inconsistent updates" from time to time on some users machines is probably not helping either.  Only so much Daz support can do and know.

    Daz support didn't even bother to answer, not sure they even read lol. And it's too widespread to be just a single PC problem (not sure if I can link another forum).

    "can't reproduce", here on another machine with an old 1060 :

    2020-11-12 14:59:12.217 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 16.66% of image converged2020-11-12 14:59:12.326 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00253 iterations after 204.325s.2020-11-12 14:59:33.382 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00281 iterations after 225.391s.2020-11-12 14:59:55.741 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Tail kernel failed after 0.004s2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): an illegal memory access was encountered (while launching CUDA renderer in &lt;internal&gt;:705)2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Failed to launch renderer2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Device failed while rendering2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : All available GPUs failed.2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: Fallback to CPU not allowed.

     

    Solution here:

    https://www.daz3d.com/forums/discussion/comment/6213281/#Comment_6213281

  • TBorNotTBorNot Posts: 369
    amandainjapan said:

    I am also having the  "never exiting, ever, just sitting there on exacty the same active private working memory amount and CPU usage" bug, but this is new for me in this beta.

    To fix this on my Mac, I log out of connect before exiting Daz3D.  For me, the long timeout is a network hang.

     

     

  • no__nameno__name Posts: 88
    capitanharlock80 said:
    no__name said:
    Saxa -- SD said:
    no__name said:
    Richard Haseltine said:
     

    Yes, the issue has been reproted - but daz can't reproduce it, it seems to vary by system or by some other factor and until they have a reliable and repeatable way to show the issue they can't expect nVidia to look into it.

    Thanks for answering, I just hope devs know there is some problem here (could reproduce it on two different machines at work tho).

    If I update Daz by mistake, I lose around ~800 scenes, as I really heavily on section plane for various reasons.  Can't also upgrade my system with a 3xxx card as I would be forced to update.

    Make things a bit spicy for me lol.

    There are situations where your PC software environment may not be working exactly as DAZ's systems.  Case in point, probably 6 months ago a user was having OpenCL issues.  Daz support told them couldn't reproduce.  User asked for help in forums and in the end their registry had a toggle value that was interfering, and with a modifying of  said entry OpenCL worked fine.  So many users with different PC systems and Win10 doing "inconsistent updates" from time to time on some users machines is probably not helping either.  Only so much Daz support can do and know.

    Daz support didn't even bother to answer, not sure they even read lol. And it's too widespread to be just a single PC problem (not sure if I can link another forum).

    "can't reproduce", here on another machine with an old 1060 :

    2020-11-12 14:59:12.217 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: 16.66% of image converged2020-11-12 14:59:12.326 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00253 iterations after 204.325s.2020-11-12 14:59:33.382 Iray [INFO] - IRAY:RENDER ::   1.0   IRAY   rend progr: Received update to 00281 iterations after 225.391s.2020-11-12 14:59:55.741 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Tail kernel failed after 0.004s2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): an illegal memory access was encountered (while launching CUDA renderer in &lt;internal&gt;:705)2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Failed to launch renderer2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: CUDA device 1 (GeForce GTX 1060 3GB): Device failed while rendering2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - IRAY:RENDER ::   1.4   IRAY   rend warn : All available GPUs failed.2020-11-12 14:59:55.756 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [ERROR] - IRAY:RENDER ::   1.4   IRAY   rend error: Fallback to CPU not allowed.

     

    Solution here:

    https://www.daz3d.com/forums/discussion/comment/6213281/#Comment_6213281

    Seems to work \o/, Thank you!

  • jackdot-_2f631de5d3jackdot-_2f631de5d3 Posts: 7
    edited November 2020

    I wonder if anyone can help. I've download this new version of Daz and the Invidia Studio drivers to match,

    The software crashes randomly, see the error below, this can happen during an Iray render, using Iray in the viewpoint, working perhaps too quickly for Daz.

    My hardware is decent and all checked out - Nvidia RTX 2080 Super, AMD Ryzen 9 3900X 12- Core Processor etc

    Does anyone else recognise this problem ,,, when you try to log the problem with Daz it say the page is unavailable.

    As previous people have written then Daz really need to stabilise Studio or give better hints and tips to their users.

     

    DAZStudio.exe caused ACCESS_VIOLATION in module 'C:Daz 3d\Applicatios\64-bit\DAZ 3D\DAZStudio4Public Build\libs\iray\libiray.dll

     

     

    Post edited by jackdot-_2f631de5d3 on
  • mcorrmcorr Posts: 1,084
    edited November 2020

    I don't see a beta in my DIM .... has it been removed, or is there a different link to it?

    EDIT: not in DIM, but it's in the product library

    Post edited by mcorr on
  • mcorrmcorr Posts: 1,084

    Different problem: the link in my product library is not a manual download, it kicks over to DIM, but in DIM there is no way of telling if DAZ 4.14 is the BETA or GR? Can somebody help me sort this?

  • DoctorJellybeanDoctorJellybean Posts: 8,463
    mcorr said:

    Different problem: the link in my product library is not a manual download, it kicks over to DIM, but in DIM there is no way of telling if DAZ 4.14 is the BETA or GR? Can somebody help me sort this?

    The Public Beta will be labelled as such. If you see a Daz Studio 4.14 without labels, then it is the GR.

Sign In or Register to comment.