Description
Dynamo version
2.0+
Operating system
N/A
What did you do?
Standard procedures that usually worked fine in prior versions (opening a large graph, modifying custom nodes, making changes to code blocks, etc.)
What did you expect to see?
A stable operating product, within the limits of what's possible. If something throws an exception, catch it, close down dynamo if you can if not -let it crash grcefully, BUT please do your best to keep Revit operational, finally provide sufficient info about the exception. I want to solve this issue, I'm expected to provide something useful, I really want to provide something useful, but I can't get anything!
What did you see instead?
Dynamo would crash and instantly take Revit down with it. There are no warning windows, there is no log information saved, there is nothing useful saved in the journal either because the whole things comes crashing down before anything can be reported.
Case in point, this is what happens when you try to work with a relatively large script in Dynamo 2.0:
https://www.youtube.com/watch?v=CR1X3vwUMpU&feature=youtu.be
(I suggest you speed the video through youtube, because of the long load times)
@kronz ,
While I accept the fact that we have to go with the flow and adapt to the changes, it appears to me that too many things in 2.0 tried to change too quickly at the same time. It feels to me like the crashes have skyrocketed (based on my personal usage experience and on what I see in the forum) and we've gotten little in return for it. I suspect your internal analytics would back this up as well if you compare the number of times dynamo is launched, with the number of times it's ended by conventional means. (because right now things crash before any report could be sent back)
While I and others understand that running Dynamo on top of Revit entails a lot difficulties and limitations, I'm pretty sure that the wider community out there doesn't. Revit users are still the biggest portion of all Dynamo users and you know very well that Revit is predominantly used in enterprise environments that design and produce costly products on tight deadlines. While you can certainly use it for your hobby project and try to push the limits and not care about the occasional crash, most people don't use it that way. And you don't need my reassurance to know that your end users' patience and support will quickly wane after they loose their unsaved progress and waste countless billable hours for the umpteenth time.
Right now the only way to figure out why things are going wrong, is to compile Dynamo Core & D4R from source and constantly run everything in VS Debug mode, with breakpoints placed everywhere. You can probably count the people who would be interested in doing all that(debug mode is both much slower and much more tedious), while at the same time trying to deliver on their everyday job, on the fingers of one's hand...
Instead I strongly believe that the team must re-prioritize and make a targeted effort and take a more proactive approach on the overall stability of Dynamo on top of Revit as soon as possible. Start by improving the existing reporting functionality for both D4R and Dynamo Core. You already have decent infrastructure for the average user to easily share their exception reports, but miss catching those exceptions in the first place... Once that is solved, the newly acquired information will be invaluable to further harden all aspects of the daily general usage of D4R.