Tip for reducing Flowstone Crashes... maybe?

[Spogg]

Hi all

I don't know if it's me or my PC but I've found that when my schematics start to get big I get frequent crashes:

"Flowstone has stopped working".

I've noticed that the thing that mostly seems to initiate a crash is when I add/remove/modify an input or output at a high level in the schematic and especially with Mono inputs/outputs. My computer desk has been thumped MANY times and I'm not sure it'll take much more punishment!

I've found a way to get around this (apart from very frequently Saving As). If I deselect the Audio out on the ASIO or Direct Sound Prim, then make my changes and then re-select the audio it doesn't crash (not yet anyway). My thought is that this is to do with the dynamic re-compiling and timing issues in FS but what do I know?

I'd be interested to know if this is an issue for others and whether my "tip" works for others and is useful...

Cheers

Spogg

[Spogg]

Well, as I write this, 1557 folk have viewed my tip but exactly zero replies! Come on guys, just say what you think!

I've also found out something else. Always, if I load a 2nd schematic to maybe look at a previous idea or copy a module, when I close the 2nd schematic the main (original) one makes no sound.
I found that if I de-select the audio driver in the output prim, then re-select it, it springs back to life and I no longer need to close FS and re-open it to get sound from the main project.

I hope this helps speed up your workflow a bit and I'd simply love to know!

Cheers

Spogg