search

OrkestraOnline / Orkestra_Online

Orkestra Online is a cloud based platform for deploying, documenting and securing DynamoBIM and Grasshopper content.
https://www.orkestra.online
40 stars 2 forks source link

Revit Crashes when running second graph #6

Closed Kranzy closed 4 years ago

Kranzy commented 4 years ago

Describe the bug After running a graph, when running the next graph (manually) Revit closes without warning.

To Reproduce Steps to reproduce the behavior:

  1. Go to Orkestra tab
  2. Click on Workspace dropdown menu and select first graph to run.
  3. First graph completes successfully
  4. Click on Workspace dropdown menu and select second graph (using same packages)
  5. We see dynamo window open and close and then after that Revit closes/crashes

Expected behavior Being able to run graphs one after another without crashes

Observed behavior After running a graph, when running the next graph (manually) Revit closes without warning.

Desktop (please complete the following information):

In Which context did it happen : Orkestra Revit Addin

MostafaElAyoubi commented 4 years ago

Thanks for the detailed report! Just to be sure : this happens when you play definitions through online QuickAccesses that are grouped as a drop down button. Is that correct?

Kranzy commented 4 years ago

That seems to be correct. I ran multiple graphs one after the other from the dockable pane with no issues.

MostafaElAyoubi commented 4 years ago

@Kranzy this issue should now be less of a problem with v.0.1.7 : QuickAccess buttons behave the same as the dockable pane. They only trigger a reset of the package environment when needed. Let me know when you have had a chance to try it! Have ane awesome day.

Kranzy commented 4 years ago

@Kranzy this issue should now be less of a problem with v.0.1.7 : QuickAccess buttons behave the same as the dockable pane. They only trigger a reset of the package environment when needed. Let me know when you have had a chance to try it! Have ane awesome day.

Seems to be much better. Seemed to have less of an issue when removing some packages from the folder that wasnt required so not sure if that was the fix, or the update as well. Either way I'll close it now and can re-open if need be.