Page 1 of 2 12 LastLast
Results 1 to 15 of 30

Thread: LW 2019 stability

  1. #1

    LW 2019 stability

    Hey everybody I've got a general question about how everybody's experience with 2019's stability has been. My team is getting Layout crashes on the weirdest things. Save image and poof LW disappears. Replace object - poof LW disappears. Save scene - poof LW disappears. When this happens we are not getting notice - it just poofs and LW disappears. I can't be repeated and it is so iffy so there is no sense making a report. Probably happens on average twice during an 8 hr day. Anybody else?
    Tim Parsons
    Technical Designer
    Sauder Woodworking Co.

    http://www.sauder.com

  2. #2
    Curmudgeon in Training Ma3rk's Avatar
    Join Date
    Mar 2003
    Location
    Near Beaverton, OR
    Posts
    1,618
    2019.3 has been quite stable for me & that's with a new system & new OS.

    This iss sounding like something else frankly. You say team, so everyone is having issues? Are you all networked with shared assets? Everything you've listed is I/O related.
    "Never be a cat in a cartoon. Never." Chief Wiggum

    The Big Apexx System:
    AMD RYZEN THREADRIPPER 2990WX Processor (3.00GHz)
    64GB DDR4-2666
    2x NVIDIA Quadro RTX 4000 8GB 32 Core (64 cores avail)

  3. #3
    Super Member Kryslin's Avatar
    Join Date
    Feb 2009
    Location
    Prescott, IA
    Posts
    1,565
    I've had some bizarre crashes, starting in 2018, and moving into 2019. Usually on closing, sometimes saving something. sometimes loading something. Most are not repeatable, I've tried.

    No strange network I/O set ups, just an SSD for boot and apps, and 4TB of RAID storage for data. I'm thinking about setting up a small NAS for data storage, or adding some more USB 3.0 ports and some USB external storage, though, and clearing some of my projects off to there...
    --------
    My Scripts for Lightwave
    Intel Core i7 960 @3.20 Ghz, 24 GB ram, EVGA 6GB GTX980Ti "Classified" driving 2 x HP LA2405.

  4. #4
    Super Member omichon's Avatar
    Join Date
    Jul 2003
    Location
    Bordeaux, FR
    Posts
    745
    It happens here too while creating a new folder from the File browser when defining a path for output images.
    I had this one at least 5 or 6 times, but randomly, so nothing to report unfortunately.
    www.oliviermichon.fr | 3D Animation, Motion Graphics and Broadcast Design.

  5. #5
    Registered User
    Join Date
    May 2012
    Location
    Virginia
    Posts
    508
    Probably a stupid question, but how up to date are the display drivers in your group?

    I've found that to be a serious issue with many different pieces of software in my dev group (although not Lightwave so much)... we update to a new version and suddenly we start getting weird crashes.

    Then the light bulb goes off and we get on IT to update the display drivers across the systems and everything starts running right again.

    If the crashes are at either end of a display driver update (no update or recently updated) that might be the culprit.

  6. #6
    pass:sword OFF's Avatar
    Join Date
    Feb 2003
    Location
    Russia
    Posts
    1,050
    I have another kind of problem - lw 2019.0.3 stops using my hotkey configuration, even many default hotkeys assigned (save, save as) stop working. Selection of more than one object stops working.

  7. #7
    Registered User
    Join Date
    May 2012
    Location
    Virginia
    Posts
    508
    Quote Originally Posted by OFF View Post
    I have another kind of problem - lw 2019.0.3 stops using my hotkey configuration, even many default hotkeys assigned (save, save as) stop working. Selection of more than one object stops working.
    Hey OFF... I see you posted on this issue in the General Support forum.

    Perhaps you should start a new topic thread here if you feel that your topic in General Support didn't get enough visibility.

    I would encourage you to include some system information in your thread as well; it may help to identify the issue.

  8. #8
    Quote Originally Posted by RPSchmidt View Post
    Probably a stupid question, but how up to date are the display drivers in your group?

    I've found that to be a serious issue with many different pieces of software in my dev group (although not Lightwave so much)... we update to a new version and suddenly we start getting weird crashes.

    Then the light bulb goes off and we get on IT to update the display drivers across the systems and everything starts running right again.

    If the crashes are at either end of a display driver update (no update or recently updated) that might be the culprit.
    I need to check the drivers just to make sure as we all have the same hardware. Today it went poof twice when I activated VPR (I use a short cut of F8).

    - - - Updated - - -

    Quote Originally Posted by Ma3rk View Post
    2019.3 has been quite stable for me & that's with a new system & new OS.

    This iss sounding like something else frankly. You say team, so everyone is having issues? Are you all networked with shared assets? Everything you've listed is I/O related.
    Yes - we work of a network, but today it went poof when I activated VPR which isn't I/O related.
    Tim Parsons
    Technical Designer
    Sauder Woodworking Co.

    http://www.sauder.com

  9. #9
    Super Member vncnt's Avatar
    Join Date
    Sep 2003
    Location
    Amsterdam
    Posts
    1,656
    Are you using Motionblur? If so, try again without.

  10. #10
    Quote Originally Posted by vncnt View Post
    Are you using Motionblur? If so, try again without.
    Not at all. We do product development so its just stills.
    Tim Parsons
    Technical Designer
    Sauder Woodworking Co.

    http://www.sauder.com

  11. #11
    ack ack Markc's Avatar
    Join Date
    Feb 2006
    Location
    England
    Posts
    1,452
    Quote Originally Posted by Tim Parsons View Post
    I need to check the drivers just to make sure as we all have the same hardware. Today it went poof twice when I activated VPR (I use a short cut of F8)
    When 2018 came out, if I opened an old 2015 scene VPR would crash LW.
    A new scene no problem.
    I havn’t tried the same thing with 2019.

    All seems pretty stable on 2019.0.3 with new assets.
    Mac Pro (2010) OSX 10.13 RX580 Pulse LW2019 LWCad 2018

  12. #12
    Quote Originally Posted by Markc View Post
    When 2018 came out, if I opened an old 2015 scene VPR would crash LW.
    A new scene no problem.
    I havn’t tried the same thing with 2019.

    All seems pretty stable on 2019.0.3 with new assets.
    Using all new assets. It just goes "poof" at the strangest times.
    Tim Parsons
    Technical Designer
    Sauder Woodworking Co.

    http://www.sauder.com

  13. #13
    Registered User MarkAH's Avatar
    Join Date
    Feb 2008
    Location
    Green Valley, AZ
    Posts
    66
    Sounds like un-caught exceptions. That can seem totally random even though it's happening in just a few places.
    It's totally frazelling figuring out what all exceptions should be handled.
    I can't imagine with LW being the mass of plug-ins it consists of.
    Tried to figure out just how much of all that stuff is now compiled into dll's by looking at the runtime.
    Just gets more confusing.

  14. #14
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    7,993
    Quote Originally Posted by Tim Parsons View Post
    Hey everybody I've got a general question about how everybody's experience with 2019's stability has been. My team is getting Layout crashes on the weirdest things. Save image and poof LW disappears. Replace object - poof LW disappears. Save scene - poof LW disappears. When this happens we are not getting notice - it just poofs and LW disappears. I can't be repeated and it is so iffy so there is no sense making a report. Probably happens on average twice during an 8 hr day. Anybody else?
    "Poof and disappear" without any warning or so, is a sign of
    1) out of CPU stack (infinite recursion)
    2) out of memory (which is easily visible because of heavy disk usage prior it, unless it's also connected with 1) issue..

    Perhaps one or couple assets like images that you are using are damaged, and LW I/O loader/saver is unable to handle it, which results in infinite loop/recursion, and voila..

    Hey everybody I've got a general question about how everybody's experience with 2019's stability has been.
    For me it was very stable so far. Don't remember any crash for months.
    But if you use some feature which is buggy, it can make entire app buggy, because of damaged memory (e.g. exceeding boundary of allocated memory or allocated array).
    After memory damage (not physically!), not buggy operations can start crashing in unexpected moments.
    These issues are the hardest to find, because of randomness of crash, which is not tied to what you actually used/clicked, but typically to freeing memory. e.g. replace asset (object, image, scene) requires freeing existing one, so if memory is damaged, freeing will crash..

    Damaged memory can lead to writing incorrect data to disk, and damaging the more assets even more..

    My team is getting Layout crashes on the weirdest things.
    How many licenses do you have?
    Send scene & assets to LW, and it will fixed, if these crashes are so repeatable..

  15. #15
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    7,993
    Quote Originally Posted by Tim Parsons View Post
    Yes - we work of a network, but today it went poof when I activated VPR which isn't I/O related.
    VPR is (perhaps) using recursion.
    On what asset you enabled it? Do you remember?
    Even orientation of object on viewport does matter.
    If it's reflective/refractive new rays are fired, at perhaps new recursion depth level..

    If object is damaged, it could lead to further crashes.

Page 1 of 2 12 LastLast

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
  •