Crashes on TBB.DLL when loading scenes

Since the last update I'm getting a new crash on the file TBB.DLL about "skinning" something. The crash seems to happen more often if I'm in a big scene with many props and I load another scene before closing that. This means I can't use my Batch Render utility when reaching those parts.

I see in the details of the DLL file that is "Intel Thread Building Block library" but I got a Ryzen CPU form AMD.

There's a way to avoid this crash?

Comments

  • Is that a Daz Studio plug-in? If so, which one?

  • ImagoImago Posts: 5,140

    Richard Haseltine said:

    Is that a Daz Studio plug-in? If so, which one?

    No, it's a DAZ Studio's internal component as I can see. You cna find it in the main folder, along with the DAZ.exe file. As I said it's called TBB.DLL.

    Until now even the biggest and most crowded scenes never gave me issues.

  • crosswindcrosswind Posts: 6,831

    Have you had the plugin of Fluido II (or Fluido) installed ?

  • ImagoImago Posts: 5,140

    crosswind said:

    Have you had the plugin of Fluido II (or Fluido) installed ?

    Yes I have them but I just found out the real source of the crash: Mesh Grabber.

    For some reason now DAZ Studio brutally crashes if there's any prop modified with Mesh Grabber, probably because some of the altered props got instances. The crashes stopped when I baked the changes in the prop to morphs.

    I guess now the software doesn't like the props altered with Mesh Grabber to be instanced.

  • crosswindcrosswind Posts: 6,831

    Right ~ it shoud be instances issue as you said. I have MeshGrabber installed but found no crash as I didn't have any case of instances with MG. However, I was also trouble-shooting with some crashes resulting from plugins... headache.

  • ImagoImago Posts: 5,140

    crosswind said:

    Right ~ it shoud be instances issue as you said.

    I can confirm that, when you have multiple instances of a prop with some "unbaked to morph" changes in it, DAZ Studio crashes when loading the scene containing them. The solution is to bake the changes to morph.

    Probably it's the amount too, I had many of them in those scenes.

  • Imago said:

    crosswind said:

    Right ~ it shoud be instances issue as you said.

    I can confirm that, when you have multiple instances of a prop with some "unbaked to morph" changes in it, DAZ Studio crashes when loading the scene containing them. The solution is to bake the changes to morph.

    Probably it's the amount too, I had many of them in those scenes.

    Any morph, or a Mesh Grabber modifier in particular?

  • ImagoImago Posts: 5,140

    Only the changes made with Mesh Grabber and NOT baked to morph using the internal converter.

    I'll explain better:

    You have a cube with 10 divisions, make 50 instances and save the scene. Then load another scene and, with that scene loaded, reload the Cube scene. All works fine.

    In the Cube scene, make a slight change on the main prop using the Mesh Grabber, let's say you pull one or two polygons. All the instances reacts to the change. Now, save the scene and load another scene. With the second scene loaded reload the Cube scene. DAZ Studio crashes.

    Reload the Cube scene on a new DAZ run. It loads fine. Now in the Mesh Grabber pane, convert the changes you made to the cube to morph. Save the scene and then load another scene. With the scene loaded, reload again the cube scene. It loads correctly now.

  • crosswindcrosswind Posts: 6,831
    edited September 27

    Imago said:

    Only the changes made with Mesh Grabber and NOT baked to morph using the internal converter.

    I'll explain better:

    You have a cube with 10 divisions, make 50 instances and save the scene. Then load another scene and, with that scene loaded, reload the Cube scene. All works fine.

    In the Cube scene, make a slight change on the main prop using the Mesh Grabber, let's say you pull one or two polygons. All the instances reacts to the change. Now, save the scene and load another scene. With the second scene loaded reload the Cube scene. DAZ Studio crashes.

    Reload the Cube scene on a new DAZ run. It loads fine. Now in the Mesh Grabber pane, convert the changes you made to the cube to morph. Save the scene and then load another scene. With the scene loaded, reload again the cube scene. It loads correctly now.

    What is the version of DS that you're using in which such issue occurred... General Release 4.22.0.19 ?

    I couldn't reproduce the issue with General Release 4.22.0.16 and latest Public Build 4.22.1.221.

    Post edited by crosswind on
  • ImagoImago Posts: 5,140

    crosswind said:

    What is the version of DS that you're using in which such issue occurred... General Release 4.22.0.19 ?

    I couldn't reproduce the issue with General Release 4.22.0.16 and latest Public Build 4.22.1.221.

    I get the crash in 4.22.0.19.

  • crosswindcrosswind Posts: 6,831

    Imago said:

    crosswind said:

    What is the version of DS that you're using in which such issue occurred... General Release 4.22.0.19 ?

    I couldn't reproduce the issue with General Release 4.22.0.16 and latest Public Build 4.22.1.221.

    I get the crash in 4.22.0.19.

    Got it ~ So the issue seems specific to 4.22.0.19 ~ This version has mostly updated Daz Connect funtions, I decided not to upgrade as I have the latest Public Build. If you have latest Public Build installed, try with it... see if you can reproduce the issue.

  • The issue is prsumably the way Mesh Grabber serialises its modifiers, rather than DS per se

  • ImagoImago Posts: 5,140

    Richard Haseltine said:

    The issue is prsumably the way Mesh Grabber serialises its modifiers, rather than DS per se

    Still, It's something that needs to be fixed.

  • ImagoImago Posts: 5,140

    crosswind said:

    Got it ~ So the issue seems specific to 4.22.0.19 ~ This version has mostly updated Daz Connect funtions, I decided not to upgrade as I have the latest Public Build. If you have latest Public Build installed, try with it... see if you can reproduce the issue.

    Just tried, it seems to not happen in the beta. I hope it will be the same in the "final" release.

Sign In or Register to comment.