Results 1 to 4 of 4

Thread: DP Mixer node - Bug

  1. #1
    Super Member kolby's Avatar
    Join Date
    Aug 2004
    Location
    CZ, EU
    Posts
    414

    DP Mixer node - Bug

    Hi, I found this bug in the DP Mixer node. It eats a lot of RAM while rendering.

    Steps to reproduce:
    Load or create any model into the 2019.1.5 layout.
    Open the Node Editor and add the Mixer node from DPFilter / Tools
    Open Windows Task Manager or anything to monitor memory usage.
    Enable VPR
    Connect the Mixer to the color input of the material.
    Memory usage increases rapidly (about 2 GB / s) until VPR rendering is complete. Then it stops.
    Any refresh of the VPR cause this again.
    The same is happening with F9.
    Clear Scene does not release the allocated memory.
    Additionally, draging the frame slider causes the layout to crash.

    Could anyone confirm this?
    System info: CPU: Ryzen 9 3950X RAM: 32GB DDR4/3200MHz MB: Asus Prime X570-P GFX: Asus GTX 750 Ti / 2GB OS: Win10, LW2019x64

  2. #2
    Member
    Join Date
    May 2006
    Location
    France
    Posts
    4,116
    Quote Originally Posted by kolby View Post
    ...Connect the Mixer to the color input of the material...
    DP Mixer node is part of DP Filter for Image filter node editor usage,
    I remember that I tried to limit issues for anyone using it in the Surface node editor,
    but there's probably other things to lock, also except its dedicated screen preview,
    it is not so much different from native one, so ignore it in this context.


    Denis.

  3. #3
    Member
    Join Date
    May 2006
    Location
    France
    Posts
    4,116
    Just in case, the memory leak of DPFilter Mixer node in Surfacing context
    has been fixed.

    Denis.

  4. #4
    Super Member kolby's Avatar
    Join Date
    Aug 2004
    Location
    CZ, EU
    Posts
    414
    Quote Originally Posted by dpont View Post
    DP Mixer node is part of DP Filter for Image filter node editor usage,
    I remember that I tried to limit issues for anyone using it in the Surface node editor,
    but there's probably other things to lock, also except its dedicated screen preview,
    it is not so much different from native one, so ignore it in this context.


    Denis.
    Oh, I didn't notice it was for the Image filter. I wanted to pick the native Mixer in the surface editor, but by mistake I chose this one.
    Thanks for explanation Denis.
    System info: CPU: Ryzen 9 3950X RAM: 32GB DDR4/3200MHz MB: Asus Prime X570-P GFX: Asus GTX 750 Ti / 2GB OS: Win10, LW2019x64

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
  •