Crash reporting sounds great!
But will this work when Natron just disappears ?
I am working on a project for the next few weeks for which I will use Natron a lot.
(Still checking if I can send you a project, but its a hell lot of files…).
Especially the crashes when DiskCashing or Rendering are important to fix.
Also willing to donate and to promote Natron, the rendering speed is just amazing on a Threadripper
(coming from BMD Fusion, its soooo slow and the support is s***, figured out that Natron does not need a 3d workspace at all, we have Blender and the two work great together…).
The current implementation will not work without a server. I’m working on a local crash system.
It might be easier to get the crash reporting working. I got the server side working already and I have tested reporting on Linux and Windows (I don’t think we can enable on Mac anymore?). We need to enable building of the crash reporter again, update server url and collect symbol files.
Note that this is a bit hackish as the build system created a broken CrashReporter (does not detect Natron-bin crashes), so you will need to apply a “patch”.
Great!
Just installed your version and forced Natron to crash while simply importing a .jpg file into a read node (I think messed up the words read and write in crash report).