DSP Robotics Support

tester wrote:Is there a problem with ruby component between 304 and 306?

They've changed the init phase. Now init is executed after inputs/outputs are loaded. Maybe that causes problems in your schematics. What kind of error are you talking about?

Things like this. But also other error messages in other ruby boxes. When I click on input node - it reinitializes and resets the error, but after doing the export - error is back again.

It's a spooky thing. As if something was frozen "in the air" between inputs and outputs. I can reproduce it when copying faulty modules into new schematic, but it disappears completely (I think so) after connecting to fresh data node (but it isn't disappearing when I just pass through new data in old schematic).

i can confirm the same issues, but a after load trigger on the string in should solve it ..

in general some clearification would be helpful, it looks like that the persistance of the ins and outs isn't stable anymore?

Nubeat7 wrote:i can confirm the same issues, but a after load trigger on the string in should solve it ..

in general some clearification would be helpful, it looks like that the persistance of the ins and outs isn't stable anymore?

AfterLoad trigger may help, but watching how the thing behaves (errors after exporting application) - I'm not sure if in all cases. Maybe 1-time copying/refreshing/repasting modules would be better. I will try to isolate a unit, so that I can report it to Malc, because I'm not sure how problematic it may become in future versions of FS.

(btw, using AfterLoad would require some redesigns, to avoid wandering triggers where they are not welcome; on the other hand I remember I could crash FS just by copying some ruby modules that were stuck between S&H prims, so... no time for such experimentation right now, I'm late anyway).

I extracted few portions of the problem and reported to Malc.

Hello GANG !

Was wondering how 3.0.6 is playing for everyone ?

I've hesitated to upgrade till now, but would like to know how this version is doing.

Thanks

My ruby bug is fixed now.
Indexer bug is fixed too.

i thing it would be helpful to edit old bug reports with something like: " [solved with version 3.07]"... so its easy for new people to see if the bug (and any posted workarounds) are of interest...

Job for moderator perhaps, to mark posts in thread as "fixed"?

After about 12 Hours with 3.07, I found it UNSTABLE, removed it and gone back to 3.06

Problem: Selecting or dragging an item from toolbox crashes FS.

Details:
Item is varied...
sometimes very small : (1 button and small piece of ruby code)
sometimes big : (My "Painting Canvas" module)

First time was after a few hours use, I tried to drag a very small module called "Ruby Number'
from the toolbox. Ruby Number module is tiny..( a button and very small piece of ruby code)
FS crashed repeatedly .
Next problem came when the Ruby Number Module could not be deleted from the toolbox.
Any attempt to do so and crash.

Ok..so I go into App data, delete the module, back in FS create a new "Ruby Number" module,
toolbox it and keep working.

Now a few hours ago, i try to drag my Painting Canvas and get the same crash...
Tried several other modules...same crash...

No idea what's going on here...
Note:
I'm back at 3.06 now....these issues are not happening....