- Posts: 7
- Joined: Fri Apr 03, 2020 9:07 am
- Real Name: Jørn Wulf
Sat Jan 16, 2021 12:39 pm
DR 17b6 Transform Nodes causes crash and freeze.
I hope that someone her can help or explain if I am doing something wrong that causes my issue, I am just a newbie.
When I upgraded from DR16 to DR17 did I start to experience some issues with the transform node in Fusion and it is only an issue in DR17.
When I first did see the issue was my thoughts that it will be solve in one of the next beta releases, but not.
I have now reached out to the support and I have been through many iterations to solve this issue, and the latest is that I have asked to take the issue to the next level as they do not have more to offer.
I have a very simple Fusion composition clip with some JPG’s moving from outside the frame into the frame while rotating and scaling.
When playing that clip in a loop and clicking between the transform nodes DR suddenly freezes and sometimes totally crashes.
I have replicated the issue using text nodes or background nodes to make sure it was not because of the JPG’s and the different in resolution of the images.
When clicking between the transform nodes does it seems like there is a short stop / hold in the play and it seems like it doesn’t recover from this “stops” when there have been a few. When doing the same on input or merge nodes do I not see this kind of “stops” so notable.
The support asked me to do a lot of stuff among them was the DDU.
https://www.guru3d.com/files-details/di ... nload.html
Did the new account / profile
https://support.microsoft.com/en-us/win ... e5e56fe234
To make sure that it wasn’t the RAID configuration causing the issue did I also try to run it all from just one drive (C)
It seems like it is the combination between the movement and the size in the same node what is causing the issue when clicking around between the transform nodes while playing the clip.
I have played around with this for a long time now and I have found out that it is more stable if I have one transform node for size and one transform node for the movement in serial.
No issues when clicking between the transform nodes afterwards while playing the clip I loop.
But for me it seems like an overkill to have one transform node for movement and one node for size as it should be possible to do it in one node.
I do know that I can do transform in the merge node as well, but have not done that here.
Also this is working just fine in DR16.
I don’t see this as a performance issue as I have a very powered workstation, and on my old workstation does this work fine and not consuming that much power (GPU).
Screen dump of the composition that have the issue. When using just one background is it the same as using multiple.
Here is a screen dump of the dual transform node in serial working fine. When using multiple text nodes is the same as using just one
This is the link to what I have showed the support when clicking between transform nodes.
This is the video I made for this “flying” JPG’s
My new workstation:
Windows 10 Pro 20H2
CPU: AMD Ryzen Threadripper 3970X 32-Core
64 Gb RAM 3600 Mhz
Graphic card: Nvidia GeForce RTX 3090 Studio driver version 456.71
Dual 4K monitor.
My disk are set up as follows:
C: Drive = one Samsung SSD 980 PRO NVMe M.2 500 Gb placed on the main board
L: Drive is just normal drive 3 TB for storage not used in DR
S: Drive is the scratch drive for DR two Samsung SSD 980 PRO NVMe M.2 1Tb placed on the main board in raid 0
M: Drive is the storage for all my video for DR it is 3 Samsung SSD 980 PRO NVMe M.2 1Tb placed on a ASUS HYPER M.2 X16 CARD Gen. 4 in RAID 0
My old workstation:
Windows 10 20H2
6 CPU / 12 threads i7-4930K 3.4 Ghz
64 Gb RAM
C: = Samsung 1Tb SSD 850 EVO
Storage drive a 3 Tb spinning drive as the one I have in my current workstation.
Graphic card Nvidia P2000 5 Gb
I hope that BMD will have some input here as well
Thanks in advance.
Br. Jørn Wulf
I hope that someone her can help or explain if I am doing something wrong that causes my issue, I am just a newbie.
When I upgraded from DR16 to DR17 did I start to experience some issues with the transform node in Fusion and it is only an issue in DR17.
When I first did see the issue was my thoughts that it will be solve in one of the next beta releases, but not.
I have now reached out to the support and I have been through many iterations to solve this issue, and the latest is that I have asked to take the issue to the next level as they do not have more to offer.
I have a very simple Fusion composition clip with some JPG’s moving from outside the frame into the frame while rotating and scaling.
When playing that clip in a loop and clicking between the transform nodes DR suddenly freezes and sometimes totally crashes.
I have replicated the issue using text nodes or background nodes to make sure it was not because of the JPG’s and the different in resolution of the images.
When clicking between the transform nodes does it seems like there is a short stop / hold in the play and it seems like it doesn’t recover from this “stops” when there have been a few. When doing the same on input or merge nodes do I not see this kind of “stops” so notable.
The support asked me to do a lot of stuff among them was the DDU.
https://www.guru3d.com/files-details/di ... nload.html
Did the new account / profile
https://support.microsoft.com/en-us/win ... e5e56fe234
To make sure that it wasn’t the RAID configuration causing the issue did I also try to run it all from just one drive (C)
It seems like it is the combination between the movement and the size in the same node what is causing the issue when clicking around between the transform nodes while playing the clip.
I have played around with this for a long time now and I have found out that it is more stable if I have one transform node for size and one transform node for the movement in serial.
No issues when clicking between the transform nodes afterwards while playing the clip I loop.
But for me it seems like an overkill to have one transform node for movement and one node for size as it should be possible to do it in one node.
I do know that I can do transform in the merge node as well, but have not done that here.
Also this is working just fine in DR16.
I don’t see this as a performance issue as I have a very powered workstation, and on my old workstation does this work fine and not consuming that much power (GPU).
Screen dump of the composition that have the issue. When using just one background is it the same as using multiple.
- Not working.JPG (54.54 KiB) Viewed 551 times
Here is a screen dump of the dual transform node in serial working fine. When using multiple text nodes is the same as using just one
- Working.JPG (122.05 KiB) Viewed 551 times
This is the link to what I have showed the support when clicking between transform nodes.
This is the video I made for this “flying” JPG’s
My new workstation:
Windows 10 Pro 20H2
CPU: AMD Ryzen Threadripper 3970X 32-Core
64 Gb RAM 3600 Mhz
Graphic card: Nvidia GeForce RTX 3090 Studio driver version 456.71
Dual 4K monitor.
My disk are set up as follows:
C: Drive = one Samsung SSD 980 PRO NVMe M.2 500 Gb placed on the main board
L: Drive is just normal drive 3 TB for storage not used in DR
S: Drive is the scratch drive for DR two Samsung SSD 980 PRO NVMe M.2 1Tb placed on the main board in raid 0
M: Drive is the storage for all my video for DR it is 3 Samsung SSD 980 PRO NVMe M.2 1Tb placed on a ASUS HYPER M.2 X16 CARD Gen. 4 in RAID 0
My old workstation:
Windows 10 20H2
6 CPU / 12 threads i7-4930K 3.4 Ghz
64 Gb RAM
C: = Samsung 1Tb SSD 850 EVO
Storage drive a 3 Tb spinning drive as the one I have in my current workstation.
Graphic card Nvidia P2000 5 Gb
I hope that BMD will have some input here as well
Thanks in advance.
Br. Jørn Wulf