- Posts: 432
- Joined: Tue Apr 14, 2020 12:40 am
- Real Name: Wesley McDermott
Tue May 25, 2021 6:23 am
Is it plausible that very long accumulated node names in DR Fusion can lead to crashes?
I had built a branch that involved about 70 merges, each of which had an image and two translate nodes to form the foreground input. I was copy/pasting the most recent translate node pair to form new ones (it was convenient, as the edits to the scale and positions dynamics were incremental). Fusion built up default node names (appending _1 each time), and I didn't care so the strings got quite long.
Around the 71s, when I would connect the image, things were fine... until I attempted to drag the start/end positions of a translate node's position trajectory - then DR would disappear (crash, process gone). I would reload, try deleting the source input and reconnecting... same behavior. Tried deleting the translate nodes and recopying... same behavior.
Finally, I renamed the translate nodes (tr2 and tr2b)... and then I was able to drag the dynamic position path as expected, without crashing.
If the node names are truly the root of the issue, then it would be nice for DR to handle that gracefully when copy/pasting a node - generate a new short name (or prevent me with a note that I can't paste as the generated name is too long).
I had built a branch that involved about 70 merges, each of which had an image and two translate nodes to form the foreground input. I was copy/pasting the most recent translate node pair to form new ones (it was convenient, as the edits to the scale and positions dynamics were incremental). Fusion built up default node names (appending _1 each time), and I didn't care so the strings got quite long.
Around the 71s, when I would connect the image, things were fine... until I attempted to drag the start/end positions of a translate node's position trajectory - then DR would disappear (crash, process gone). I would reload, try deleting the source input and reconnecting... same behavior. Tried deleting the translate nodes and recopying... same behavior.
Finally, I renamed the translate nodes (tr2 and tr2b)... and then I was able to drag the dynamic position path as expected, without crashing.
If the node names are truly the root of the issue, then it would be nice for DR to handle that gracefully when copy/pasting a node - generate a new short name (or prevent me with a note that I can't paste as the generated name is too long).
PC Win 11 Pro, 64GB ram; NVidia 572.83; dual monitor; RTX 3080 (10GB); auto/CUDA processing mode; SSD cache, separate SSD for data; Davinci Studio