Author Topic: Pause or reset of "Play" simulation  (Read 2862 times)

Wall-E

  • Robots in Architecture Members
  • Forum User
  • *
  • Posts: 194
    • View Profile
Pause or reset of "Play" simulation
« on: April 17, 2016, 01:59:51 PM »
Hi !

It seems to me that the "Play" simulation feature becomes impossible to pause or reset in certain circumstances.
In simulations with many waypoints, this "locking" seems to occur quite often.

I guess I should always save my definition before running "Play" so that I can just crash Rhino and restart, but is it possible to give the user more control over this ?

Cheers,

Johannes @ Robots in Architecture

  • Lead Developer
  • Administrator
  • Forum User
  • *****
  • Posts: 952
    • View Profile
    • Robots in Architecture
Re: Pause or reset of "Play" simulation
« Reply #1 on: April 17, 2016, 05:44:13 PM »
Hello,

By default, the Play component tries to automatically adapt itself to the computation time of the entire solution, but if you set a custom refresh it will try to enforce that, no matter how much performance it takes.

I'll look into making it more reliable, however it seems to be quite an underlying problem with Grasshopper, as its internal Timer component comes with a widget that operates outside Grasshopper to avoid these problems. Maybe I can integrate something like that...

Best,
Johannes

Wall-E

  • Robots in Architecture Members
  • Forum User
  • *
  • Posts: 194
    • View Profile
Re: Pause or reset of "Play" simulation
« Reply #2 on: April 17, 2016, 09:58:41 PM »
Hi Johannes, I had no custom refresh value set.
Sometimes, it works very well though, even on tough stuff, but other times, user interaction (even rotation, pan and zoom in Rhino) becomes ineffective.

Cheers,

Johannes @ Robots in Architecture

  • Lead Developer
  • Administrator
  • Forum User
  • *****
  • Posts: 952
    • View Profile
    • Robots in Architecture
Re: Pause or reset of "Play" simulation
« Reply #3 on: April 18, 2016, 06:48:43 AM »
Hmmm... This could happen when Rhino has to draw large amounts of geometry, i.e. when the drawing time is significant in relation to the computation time.
As I said, I'll look into it, but it's not an ideal situation to start with.

Best,
Johannes