Results 1 to 4 of 4

Thread: Lightwave 2018 openVDBnode extent to extent Crazy crashing.

  1. #1
    RETROGRADER prometheus's Avatar
    Join Date
    Aug 2003
    Location
    sweden stockholm
    Posts
    15,097

    Lightwave 2018 openVDBnode extent to extent Crazy crashing.

    Sigh...I do not know why the openVDB node extent sometimes craches lightwave 2018 ..without even bringing up a crash reporter, it just shuts lightwave instantly.

    trying out blender sims.

  2. #2
    Registered User dlvphoto's Avatar
    Join Date
    Feb 2018
    Location
    Atlanta, GA
    Posts
    30
    Quote Originally Posted by prometheus View Post
    Sigh...I do not know why the openVDB node extent sometimes craches lightwave 2018 ..without even bringing up a crash reporter, it just shuts lightwave instantly.

    trying out blender sims.
    What does your memory usage look like before and then during use of the node? I've had the OS kill Layout for memory over-utilization on my laptop (12GB ram, limited swap space) when it tried to allocate more than was physically available.

  3. #3
    RETROGRADER prometheus's Avatar
    Join Date
    Aug 2003
    Location
    sweden stockholm
    Posts
    15,097
    Quote Originally Posted by dlvphoto View Post
    What does your memory usage look like before and then during use of the node? I've had the OS kill Layout for memory over-utilization on my laptop (12GB ram, limited swap space) when it tried to allocate more than was physically available.
    Have to take note and check later, itīs not only VDB crashing either, it can happen tweaking just standard gradients in the openvd main panel as well..I am a bit tired of it now, and I am still trying the discovery version..which means every crash means creating it all from scratch again, not sure it is worth it and I may just as well keep it in blender..which almost never crashes, and it also gives better shading control directly with the principled volume shading.

    I do use the vpr, and that has often been crashing with other stuff as well, cycles in blender..not so much...so it leans over that I do not find it worth wrestling with these crashing issues I have had with 2015, and now with 2018.

  4. #4
    Registered User dlvphoto's Avatar
    Join Date
    Feb 2018
    Location
    Atlanta, GA
    Posts
    30
    I'd love to take a look at one of your VDB files that are causing the crash. I have so far found 2018 to be as stable or with the most recent 2018.0.6 patch more stable than I found 2015.3 to be. Both have been very stable with the exception of the memory issue I listed above which is something every OS will do to any misbehaving application.

    Scott

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •