Autodesk is going to end of life our T-Splines for Rhino plug-in on January 7th, 2017.
The T-Spines technology is now part of Fusion 360 .
Thanks,
Michael McCumber | Product Marketing Manger | Autodesk, Inc.
2 Likes
And the other shoe just dropped… 
That’s because the Rhino programmers are trying to develop a Sub-D technology alternative to the various plug-ins (including, precisely TSplines).
But as we know it will still take a long time …
A good move by Autodesk: clear for Rhino developing TSplines!
Rhino is lagging a little behind the competition. I think if something changes and you give a move will be an increasingly less used software: only the price is in his favor at the time!
Will that terminate existing licenses, or only end the sale of the plug-in?
// Rolf
Let’s hope not… I use it regularly.
I would expect that EOL for T-Splines would be the same as EOL for XP? Just no more patches or service upgrades so the T-Splines website would disappear as would the forum maybe…
I doubt you would buy a piece of software outright and then one day the vendor decides to terminate everyone’s access/use unless it was rented.
I wonder if they’ll have a fire sale and sell licenses for cheap in the run up? Might be worth investing for V5 and have it sat there for when you need it?
Andy
I doubt it… they’re clearly trying to get Rhino/T-Splines users over to Fusion, so why should they offer Rhino users a chance not to…?
The last release version of Dynamo also included “experimental T-Spline nodes” that can be optionally loaded, so it is being integrated into Dynamo and Dynamo for Revit.
Autodesk is going to end of life our T-Splines for Rhino plug-in on January 7th, 2017.
The T-Spines technology is now part of Fusion 360 .
You could see this coming from miles away, I think. For this precise reason we decided against using T-Splines, as the long-time support was not guaranteed after AD gobbled up T-Splines, Inc. Phew, I’m glad we dodged that one 
1 Like
No, it’s the other way around. McNeel saw this coming and started developing the Sub-D technology. Let’s just hope they put full focus on it for a 6.1 release instead of waiting for 7.0.
4 Likes
Has there ever been substantial functionality additions in point releases though? As I recall, in the past it has always been lab plug-ins until the next version.
Keep in mind that going forward there will always be a Rhino WIP available to current users. That is to say that Rhino 6 users will have access to Rhino WIP the same day Rhino 6 ships.
4 Likes
You could say the same for VSR Shape? A similar announcment for that can’t be far off. As I’ve said in previous discussions on here, I see this as the biggest barrier to many users moving to V6. How much functionality are you willing to leave behind (in the form of plugins that won’t work or won’t be supported in V6) before you start to think keeping the faith with Mcneel is too much of a sacrifice?
So let us hope that no Rhino update break the T-Spline connection.
But, isn’t Clayoo the same like T-Spline?
This is OT, but that’s true only for to those who organize their own licenses and have permission to install what ever software they like on their computers, and who are willing to sacrifice stability and to play with unfinished software during work hours. I don’t mean to be a party pooper, I just want you to have a realistic view on how many users that actually have access to in development tools. Do you have any numbers on how many V5 users that use V6 now? If so then I guess you can apply that same number for the future. Or maybe organize so the beta automatically works on the installed V6 license instead of operating with two licenses keys.
It has already been announced by mcneel that v5 C++ plugins, like tsplines, won’t work in v6. Plugin developers need to recompile their plugins, and probably have a lot of porting work to do to get their plugins to work with v6. I would be surprised to see a tsplines plugin for v6 given the OP announcement.
Bummer. 
1 Like
“Holo:
No, it’s the other way around. McNeel saw this coming and started developing the Sub-D technology. Let’s just hope they put full focus on it for a 6.1 release instead of waiting for 7.0.”
Absolutely, 
but even better would be to subtract 0.1 from that 6 
Regards to all,
Joao
True
After Rhino 1.1, no more decimal releases (for Windows), only SR’s
Unfortunately, many users of Rhino use the software in combination with VSR and TSplines (without these Rhino is really lacking: nothing SubD and no class-A instruments).
Purchase a license Rhino 6 to have as new Grasshopper do not think is a good strategy: will only be used by some architects and is not something indispensable. I would have given more attention to the segment “Surfaces”, modeling and editing, still a little lacking.
1 Like
I add: most users of Rhino would like to see better tools and more robust to generate surfaces, boolean, and fillet. The Sub-D will be a real big news!
If there were better tools in this direction, without having to rely on much more expensive modelers Rhino would sell many more licenses!
(It is a utopia, I know, but it’s also nice to dream!).
2 Likes