DSP Robotics Support

No we are talking about the same things, but you are not correct with the premise that you can always load newer schematics with older version.
Yes you can load some newer schematics with some older versions. But you can only do that as long as the schematic only contains stuff that wasn't affected by newer versions. So, you might have noticed from the changelog of 3.0.9b1 that this version changed quite a lot. However you can still load some schematics from 3.0.9b1 with 3.0.1 as long as the schematic contains stuff that wasn't touched. For example:


The version handling in the beta version hasn't changed (see changelog), what has changed is we store a lot more informations in the schematic now, that older versions just don't understand. eg. we store the bookmarks inside each editor in the schematics, so when you use an editor (Ruby/DSP/ASM/Multiline String) and save it, the schematic won't be compatible with older versions anymore. BTW:


Same goes for almost all stream components as they support data types (=double streams) and eg. int / double arrays in assembler that older version just don't know.

Ok, now I understand. It would be just as it was before, but there are way too many changes (which is a good thing ) to make it seem so effortlessly than prior to 3.0.9

For the progressing of Flowstone that's a low price to pay. Still I hope people will give examples made in older versions until the transition to 3.0.9 is made.

tulamide and i mean a modul dropped out of the toolbox - not loading a hole schematic...

as i mentioned before: even an empty v309b1 modul dropped out of the toolbox kills FS <= v3081

After 1st retest i got this in FS v3081(not showing the component icon):


Then i checked v306-3081: here none of the new beta modules showed up in the toolbox...
=> ..."modules.dat" was recreated
In v309b1 all new beta modules shows up again - so problem seams to be only a temporary one... so i shut up!

Tronic wrote:I would like to take the opportunity to discuss the Client and Server primitives,
which seem to have problems to send buffer larger than 256 bytes,
and also the Client have problems with port binding, it does not receive any data,
with various external servers I have tested.

So if there was the possibility to set the receiving port on the Client primitive,
instead of always having a random port, it would be better,

while for the Server primitive, it should be able to set its own IP,
and also be able to set the max buffer output byte for both primitive.

News on this?

I often find myself in the situation of working with multiple ethernet cards,
so it would be useful to specify the IP address with which to have the connection,
without this possibility, it occasional connects to any ethernet card, based on how it is configured in the system,
for example, preferred almost always the one with static IP, but this is not guaranteed if multiple adapters are configured with static or dynamic IP.

Here's an issue found in the display of single streams, which in some cases are being incorrectly represented on screen by double stream icons (see the red arrows):

yep, that's already fixed

tulamide wrote:
For the progressing of Flowstone that's a low price to pay. Still I hope people will give examples made in older versions until the transition to 3.0.9 is made.

Could a stupid old Vulcan please get clarification:

Anything made with 3.08.1 or earlier FS versions that uses any type of code modules won't work in 3.09?
If so, what about current Prims?
Also, will any of the old Synthmaker stuff I'm currently filtering and testing at the moment still work in 3.09?
I've found a lot of good stuff that works so far and it would be a shame if I'm basically wasting my time!

Cheers

Spogg

Can u fix this bugg then mybe i can relax a bit.

viewtopic.php?f=3&t=2902

and prob many others to who making synths.

Spogg wrote:

tulamide wrote:
For the progressing of Flowstone that's a low price to pay. Still I hope people will give examples made in older versions until the transition to 3.0.9 is made.

Could a stupid old Vulcan please get clarification:

Anything made with 3.08.1 or earlier FS versions that uses any type of code modules won't work in 3.09?
If so, what about current Prims?
Also, will any of the old Synthmaker stuff I'm currently filtering and testing at the moment still work in 3.09?
I've found a lot of good stuff that works so far and it would be a shame if I'm basically wasting my time!

Cheers

Spogg

We need to wait for a statement from MyCo, but the former discussion was about compatibility the other way around (new to old). Of course, with the new assembler prim I'm also not sure if it will work flawlessly, since some code was changed (although not its functionality). The other improvements shouldn't affect older prims when imported.

New FS versions are always backward compatible, so you can always load older FS versions schematics. But once you save the schematics in newer FS versions you might not be able to load them in older FS version. It's like it always was. Nothing has changed there.