We try to keep changes to the serialization to a minimum, but some times we have to do it. It is not just because we want to make our customer’s life bitter, it simply needs to be done to fix a bug or introduce a feature. Things like that happen day to day, and planning ahead is not always able to detect such things.
Mind that we also offer subscription pricing model which will always give you the latest version for free… the upgrade only takes a minute
Very good points. I always update the app and all plug-ins FIRST, then trouble-shoot SECOND, and only THIRD will I post to a forum or support for help.
Why? They always ask immediately if you’re running the latest version! Plus, same-version updates are free and fast.
Once again, the last thing I would have ever thought about is that a 3 months difference upgrade would have made such a big difference from rendering, to not rendering at all our work. So, I apologise if my dinosaur mind didn’t even remotely think about that and I focused more on the trouble-shoot phase first, to complete my deadline. To me it is like saying that I should be worried that I have to hurry up with a Rhino update, which is 3 months old, because it makes such a difference that it doesn’t model things at all. I understand that the subscription model is what some companies want to all the users to go for, however, considering that the non-subscription option is still available, not every computer in a network maybe updated to the very last non-critical update (I thought that critical updates are defined by the initial numbers and not the last after any comma, but I was evidently completely wrong).