Page 4 of 4 FirstFirst ... 234
Results 46 to 54 of 54

Thread: Node Item Motion plugin - slow eval

  1. #46
    What do I know? JBT27's Avatar
    Join Date
    Jan 2004
    Location
    Chester, England
    Posts
    2,250
    Quote Originally Posted by dpont View Post
    I can use Spline Map in node Item Motion node editor,
    without crashes here, but as I said before in this thread,
    it was written for Surfacing use, so when you try a node
    tree with a current surface node in other node editor you
    may have issues, since these node editor are clearly
    described as experimental, you are using them at your
    own risk, solving all cases is an enormous task,
    helping somebody with undetailled report, a pain.

    The author,
    Denis.
    My apologies if I came across as a potential or actual 'pain' - I didn't mean to. I know it's experimental, and I was just, err, experimenting - nothing serious, just trying stuff out

    If I can provide detailed reporting, I will. For now, what I did report is all there is - it crashed easily and consistently.

    Julian.
    LW 2015.3 Win 10 Pro 64bit

    http://www.take27.co.uk

  2. #47
    Member
    Join Date
    May 2006
    Location
    France
    Posts
    4,046
    Ok, I'm glad to know this is not serious.

    Denis.

  3. #48
    Lightwave junkie stevecullum's Avatar
    Join Date
    Jun 2005
    Location
    Reading UK
    Posts
    3,137
    Disabling the preview?

    No..just the set up of the nodes. I'll try cancelling the preview and see if it helps!
    i7 X3930/32GB/Quadro 4000

  4. #49
    Member
    Join Date
    May 2006
    Location
    France
    Posts
    4,046
    I don't think so, disabling preview is only for speed,
    crashes are caused by what you are evaluating,
    knowing that you will have immediate update in
    opengl windows, something like selecting a Null
    in a (Surface Map!) node for its own Item Motion
    instance is extremely dangerous, I get some
    success in my test above but it is a miracle...
    There are some other limitations I could not fix.

    Denis.

  5. #50
    A BUG PLANET. duke's Avatar
    Join Date
    Mar 2003
    Location
    Melbourne, Australia
    Posts
    708
    stevecullum try turning on/off Full Scene Param Evaluation - hit "o", and tick or untick FSPE down the bottom right.

  6. #51
    Lightwave junkie stevecullum's Avatar
    Join Date
    Jun 2005
    Location
    Reading UK
    Posts
    3,137
    Its already deselected duke, but thanks for the suggestion anyway.

    Edit..not tried it with it on tho!
    i7 X3930/32GB/Quadro 4000

  7. #52
    Member
    Join Date
    May 2006
    Location
    France
    Posts
    4,046
    Quote Originally Posted by duke View Post
    stevecullum try turning on/off Full Scene Param Evaluation - hit "o", and tick or untick FSPE down the bottom right.
    Good point,
    mine was "Lock Motion Key In Time",
    pressing "o" in GE.

    Denis.

  8. #53
    A BUG PLANET. duke's Avatar
    Join Date
    Mar 2003
    Location
    Melbourne, Australia
    Posts
    708
    Quote Originally Posted by dpont View Post
    Good point,
    mine was "Lock Motion Key In Time",
    pressing "o" in GE.

    Denis.
    I meant just General LW options, not in the Graph Editor. FSPE can cause trouble in some situations and works in others.

  9. #54
    Member
    Join Date
    May 2006
    Location
    France
    Posts
    4,046
    I understood what yo meant, my quote wasn't to deny,
    I replied to previous post about specific stability problems,
    Item Motion like GE make a full evaluation of motion path,
    not only for a NE preview, this causes crashes with
    nodes which need also a frame basis motion path
    evaluation.

    Denis.

Page 4 of 4 FirstFirst ... 234

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
  •