[X] My issue is not on the issue tracker or in a pull request already (go search for it and dig around a little bit!)
[X] This bug is reproducible
Natron version
Natron 2.4.3 Release
Operating system
MS Windows 10 21H2
System specs
32GB RAM
AMD Ryzen 3700X
AMD 6600 XT
Did you install Natron using the official installer?
[X] Yes, I used the official installer
[ ] No, I installed from a binary archive
[ ] No, I compiled Natron from sources
[ ] No, I installed Natron via another method
Custom installation path
No response
What were you trying to do?
Execute a Write node. It ends-up writing image to the request path and to the path of another Write node present in the script, therefore overwriting a different file.
What did you expect to happen? What happened instead?
Only the selected Write node is rendered when user presses the Render button.
Step-by-step reproduction instructions
Create a couple of Write nodes that originate from the same source.
Execute one of them
Observe that from time to time Natron overwrites files you haven't asked to render.
Additional details
The issue can be reproduced on Linux.
It might be linked to the problem where content of the output is not what is displayed in the Viewer. Latter can be usually fixed via Ctrl+Shift+K and restart of the app.
Make sure to follow our issue report guidelines
Natron version
Natron 2.4.3 Release
Operating system
MS Windows 10 21H2
System specs
32GB RAM AMD Ryzen 3700X AMD 6600 XT
Did you install Natron using the official installer?
Custom installation path
No response
What were you trying to do?
Execute a Write node. It ends-up writing image to the request path and to the path of another Write node present in the script, therefore overwriting a different file.
What did you expect to happen? What happened instead?
Only the selected Write node is rendered when user presses the Render button.
Step-by-step reproduction instructions
Additional details
The issue can be reproduced on Linux. It might be linked to the problem where content of the output is not what is displayed in the Viewer. Latter can be usually fixed via Ctrl+Shift+K and restart of the app.