DSP Robotics Support

Remember, that new release may reset state of some primitives, and this may affect some ruby modules as well. This is why you have the "afterload" primitive.

Its so weird. my projects crash even when changing presets...

kortezzzz wrote:Its so weird. my projects crash even when changing presets..

Have you got a specific example schematic that we can try? Also, what Windows are you using?

Have you got a specific example schematic that we can try? Also, what Windows are you using?

Using windows 7, 64bit. Everything worked just fine on the previous release.
Just sent it to your PM box, Trog.

Thanks!

kortezzzz wrote:Just sent it to your PM box, Trog.

Got it - let you know ASAP if it crashes here on XP.

This update pretty much confirms the direction of Flowstone....teaching robotics...

tested my 3 latest projects, with the new version and everything works perfectly (lot of ruby stuff inside).
not only this - the file size of the exported dll is much less then the old dll's - about 1/3 smaller!

just my first small tests with exporting them as they were...

kortezzzz wrote:Using windows 7, 64bit. Everything worked just fine on the previous release.
Just sent it to your PM box, Trog.

Confirmed - same on XP for both synths. Everything's works fine until changing presets, then instant crash every time.
Weirdly though, only audio seems to crash (PM recompile options make no difference) - animated GUI and FS workspace mouse response continue to function while the Windows crash report is on screen. FS doesn't actually shut down until you click for Windows to force the application to close.
Definitely one for DSPr to investigate.

Why not release the beta has made public?
Why there are no demo available?
How soon will now resolved this bug, as the DSPR always does everything quietly and in secret?

BUT,

<<Once again, few people have the privilege to participate in the beta,
discussions on what to implement or not,
and take the merits after,
but others have praised a long time for a few things needed
and have never been taken into account,
this is pure discrimination, not business strategy ....>>

sorry for my harsh words, do not get me wrong,
I always appreciate the hard work of DSPR (only Malc, or who?)
so thanks for the update,
but I hope, in the future we can have a better service,
considering the money we pay for the update.

@Tronic:
I agree with you that the update periods of DSPR are quite long, and it looks like it takes forever to get a problem fixed. But that isn't really the case. When you have a bug and you report it to Malc with details and a stripped down to the minimum schematic (so he can reproduce the problem), you'll get a fix for it within 2 weeks. Malc is really responsive in that case.
I don't think public betas for updates are a good idea, because they are just unstable releases titled as "beta". Might make sense for a new major product, but not for updates. But I would like to see more regular "tiny" updates instead of big updates every now and then. But I can understand the developer, it can take more time to do the documentation/setup/upload/announcements than the actual code update.

few people have the privilege to participate in the beta, discussions on what to implement or not

The betas that we get from DSPR are just fixes for problems that we reported, or sometimes requests for testing very specific features that we might find interesting. We have not much influence on what get's implemented. Trust me, if that would be the case, you would see more audio features (eg. Trog and me are not that interested robotics/school stuff). DSPR has their own roadmap, oriented at the most promising market (I'm ok with that, it keeps the product alive).

What feature would you like to see in an FS update (not upgrade) ?