We'll poke around on this a little and see if we can figure something out. It may be something associated with the minimum_timestep variable and your interval setting. I'm not seeing the exact same behavior, but it is stopping/locking on me (the simulation isn't actually locked though, per se). Hello Zachariah, This is definitely an interesting problem. It is not a very good example, but should demonstrate.
Attached is an extremely simple runtime class that reads/sets values between itself.
The runtime interface is a bit of a kludge and meant for simple manipulations - doing object interfaces is quite a PITA.
If you're getting into something complicated enough that you are pushing properties back and forth, doing it as a source-code manipulation/addition is much easier/stable. Hello Rahman, I think your best solution is to not use a runtime class.
