Page 2 of 2 FirstFirst 12
Results 16 to 19 of 19

Thread: Rendering in 2019.1.4

  1. #16
    Quote Originally Posted by Nicolas Jordan View Post
    There was a bug back in 2018 that I submitted that caused crashes during rendering with GI. It happened when certain kinds of nodes like bump maps were fed through a nodal network a specific way. It took lots of work to narrow down that one. Just an example that these kinds of cashes can be caused by the most seemingly unlikely of things.
    I wouldn't mind at all sending NT the scene for testing and tracking down the bug (I've tried it on two PC's and they both crashed at some point), but their bug uploading system won't handle larger files.
    Tim Parsons
    Technical Designer
    Sauder Woodworking Co.

    http://www.sauder.com

  2. #17
    Registered User
    Join Date
    Jan 2005
    Location
    Colorado Springs
    Posts
    1,807
    If you're running Windows, you could download the DebugDiag tool, install it on your system, set it up to capture crashdumps for Layout, Modeler and Hub. The process crashdump(s) themselves are too big to upload, but when DebugDiag creates a dump it creates a much smaller TXT file containing the debug trace information including thread exceptions, call stacks, etc. Here's an example from a Modeler crash on my system:

    Modeler__PID__14944__Date__11_10_2019__Time_08_42_17PM__487__Log.txt

    which is only 32KB, while the associated crashdump is about 650MB. If someone at LWDG can interpret the TXT file exceptions, they may be able to do a diagnosis without the dump itself or the reproducer Scene file.

    The most current DebugDiag tool can be downloaded here:

    https://www.microsoft.com/en-us/down....aspx?id=58210

    but it only supports Windows 8 and above according to the System Requirements. The older version (which I run) which supports Windows 7 is here:

    https://www.microsoft.com/en-us/down....aspx?id=49924

    Good luck!
    mTp

  3. #18
    Quote Originally Posted by MonroePoteet View Post
    If you're running Windows, you could download the DebugDiag tool, install it on your system, set it up to capture crashdumps for Layout, Modeler and Hub. The process crashdump(s) themselves are too big to upload, but when DebugDiag creates a dump it creates a much smaller TXT file containing the debug trace information including thread exceptions, call stacks, etc. Here's an example from a Modeler crash on my system:

    Modeler__PID__14944__Date__11_10_2019__Time_08_42_17PM__487__Log.txt

    which is only 32KB, while the associated crashdump is about 650MB. If someone at LWDG can interpret the TXT file exceptions, they may be able to do a diagnosis without the dump itself or the reproducer Scene file.

    The most current DebugDiag tool can be downloaded here:

    https://www.microsoft.com/en-us/down....aspx?id=58210

    but it only supports Windows 8 and above according to the System Requirements. The older version (which I run) which supports Windows 7 is here:

    https://www.microsoft.com/en-us/down....aspx?id=49924

    Good luck!
    mTp
    Thanks so much for the info!
    Tim Parsons
    Technical Designer
    Sauder Woodworking Co.

    http://www.sauder.com

  4. #19
    Registered User
    Join Date
    Mar 2012
    Location
    Socal
    Posts
    428
    Make sure your fans are working correctly, of course. Make sure your ram timings are correct. That's about all I got.

Page 2 of 2 FirstFirst 12

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
  •