I think that could we construct a group for developing a new ts? In my opinion, only rhinoceros can endow this tool a soul (because of great experience and openness). Anyway, if I had enough time, I would try to develop one and this experience will be a glory for me. Just personal perpective.
We’re working on SubD:
Just go buy T-Splines for Rhino rights from AutoDesk and recompile it to Rhino6. I’ll wait…
I can’t wait to have something to work with. I’ve tried everything else and don’t have the time to go learning other programs. I’m a bench jeweler. T-splines so far was the best of all of the plugins that were suggested to me. It was the most intuitive. But i’ll take anything even if I have to upgrade to Rhino6.
I updated to 6, but still do most of my work in 5 because of T-Splines. It’s a shame this beautiful addition to Rhino was let go. smh.
I think “let go” is an inaccurate characterization.
If you have followed strategic Autodesk company acquisitions, you might conclude this was a calculated move against a company they see as a competitor.
When you have a lot of money, you have more options.
Agreed. Same for VSR Shape Modeling. Buy it to kill it (after baking some dumbed-down subset of the code into house products). My characterization, “let go,” is a result of my perception of the level of kicking and screaming (or counter-offers) I heard from McNeel at the time (none), as well as my disappointment that some facility for backward compatibility of legacy and orphaned plug-ins wasn’t provided in Rhino 6. Surely if McNeel can write to RhinoScript, Python, C++, C#, Mono on Mac, etc, then McNeel can also provide a “thunk” like Microsoft did to run old RhinoCommon alongside new RhinoCommon, or some such equivalency. No?
I’m not one of the developers, but I’m around them a lot.
I recall that all of this was discussed at length internally.
The development path we’re following now is the result of those decisions and meetings.
As a privately held company, we do not have the immense resources Autodesk does. We don’t get to play in their sandbox.
Presumably no! Would not such require the blessing of the owner of said IP?
IMO, count your blessings you’re getting a natIve solution eventually. My gut tells me it’s going to be very Rhino-ish and awesome. How much time will elapse is the kicker…no clue.
That’s a cool idea David, but I bet that’s a ton of work. And probably not the best place for McNeel to put their limited resources on. Especially since the percentage of Rhino users that used/owned those tools is very very small.
It would be nice if from V7 an de onwards these l fact problems do not happen again. In theory of a current plugin can run in current Rhino it should also be able to run in ‘Rhino inside/cloud/virtualized’ so even if future SDKs make current stuff break, they should still be able to run in some sort of sandbox?
G
I would be one of the people in that very small subset of Rhino users that would benefit from McNeel putting Sub-d to priority number 1.
As a business owner I also realise that for McNeel to allocate a large part of their finite resources (money, engineers etc…) to focus on a small part of their customer base would be a bad decision.
You only had to look at the lack of posts on the old T-Splines forums to see that heavy Rhino/Sub-d users are a small subset…or the product is so good that no one had any issues using it.
2014 Sub-d for Rhino was first mentioned IIRC
2015 Dale Lear posted “If the state of the code is solid by the time Rhino 6 ships, it will be part of Rhino 6. Otherwise, it will remain in Rhino WIP until it is ready for commercial use.”
2017 T-splines plugin for Rhino no longer available
2018 Rhino 6 release without “Sub-d ready for commercial use”
2019 Still no sub-d plugin alternatives as good as t-splines IMO
I find that T-Splines with Rhino 5 does everything I need for now and I will stay there. I have so much more to learn in Rhino 5…but I also still use Photoshop CS5.
For those that can no longer purchase t-Splines and need it…I feel for them. Really your choice is to wait for who knows how many more years or head to Fusion 360.
cheers,
Sochin
Sochin, I was not implying that McNeel’s SubD development should be de-prioritize. I was referring to the effort of trying to make old plugins forward compatible (assuming it would be doable at all).
Of course developing SubDs is important. I’ve been working in SubDs for about 18 years now. I know how good and useful they are.
Also I know that a native SubD tool inside rhino will benefit probably 100X more users than any plugin. Also it’s not subject to acquisition or abandonment by developers.
BTW, we tried to work with Fusion 360. We really have. It’s a total [redacted]. So I guess we just have to keep working in Modo and Tsplines in V5 for a few more weeks/months/years.
G
SuperD Rhino plugin ($550) is similar to SubD, but mature: https://www.superdmodeling.com/
and SuperD | Food4Rhino
@andrew.nowicki Thanks for the heads up with that link in another thread as well Andrew but I had a look at it and some demo videos… and like @gustojunk wrote it looked very basic to me as well.
To give an example of what I mean by basic in comparison to t-splines…the symmetry feature in t-splines is something I use all the time.
^^^^this
One need only look at the T-Splines videos featuring Schuyler Greenawalt and his blog posts on betterlivingthroughcnc.com to know how powerful and useful T-Splines software is. There is no equivalent or replacement… 
@gustojunk Thanks for the feedback on Fusion 360. I have not tried it but only read @ec2638 comments about it being an alternative…and also an alternative for t-splines on the Mac.
Re the prioritisation of sub-d for McNeel…I could have worded my comments better. I used an exaggeration more as an affirmation of what you wrote rather than a challenge to it.
cheers,
Sochin
@davidjgall LOL nice to meet another T-Splines fanboy 
Wow…that post is from 2012.