For the past 12 years I have been using Rhino for Windows on the Mac using Parallels. Currently using R5. For the last 6 years I have been using T-splines and have a large library of t-splines models.
My now 11-12 year old 15inch Mac Book Pro is end of life. I have purchased a new M2 Pro MBP but I can no longer run my virtual Windows file containing R5 and t-splines on the M2 chip in emulation.
If I upgrade my R5 Windows copy to the latest Mac Rhino can I convert my t-spline files to sub-d from the rhino 5 files? All the t-splines models in those R5 Windows files will be in smooth mode. Do they need to be in box mode to convert to Rhino subD?
Anybody else been down this path or got advice/tips?
Thank you. Looks like I am going to have to buy another old Intel Mac to run my Rhino 5 and t-splines in emulation on for a bit longerā¦or go through every file I have and change every t-splines object to box mode.
Just started playing with the Rhino Mac 90 day trialā¦this is going to take some getting used to. Thanks again for the reply.
For anyone wanting to move their tSpline models to Rhino 7 this is the Alias I am using in Rhino 5 to toggle every tSpline object in the file to Smooth āoffā before opening the file in Rhino 7 so they remain SubD.
Seems to work but if I have missed something please let me know.
!-Layer On * Enter _NoEcho _-Layer _Unlock * _Enter _UnLock _Show -_SelTSplines _tsSmoothToggle _Save
Maybe someone will find it useful if they get to this thread.
cheers,
Sochin
I wonder if a possible batch file could be written to do this on a complete archive of rhino files.
Open rhino file
See if it contains a Tspline object
Change Tspline to box mode
Save a copy of the file in same directory with _box added to name
Repeat on all 3dm files found in the selected folder/sub folders
I would for sure like to do this before something happens to my Tsplines copy as there is many years of work that could not be maintained if Tsplines objects are ālostā.
Thinking about it, this might be possible to run from GH python, as that will stay in itās current state even if the Rhino doc is changed.
Could really just be a series of Rhino command line inputs over a list of rhino file names.
My issue might be disk space, as this approach will bump my usage thru the roof. Might take a number of hours to complete tooā¦
Cheers
DK
Ps, MUST be done, I was even thinking about this before this thread came up, Iāve got SO MUCH previous work in Tsplines files that are a single point of failure away from being not recoverable to a clean, editable state.
@kiteboardshaper I am the same. Got caught with Clayoo before I moved to Tsplines. Would hate to lose all that work. Making my way through the files a bit everyday and making sure I run that Alias before I close any file I still work on in R5.
That said very grateful that McNeel committed to SubD and that it is now developed enough for me to use.
@theoutside I watched the video that I have viewed in the past ā¦I think it just reaffirms what I already thought being that if you either import or open a tSpline object in R7 it needs to be in box mode as a tSpline or mesh to remain SubD?
If that is the caseā¦ to secure my tSplines work in R5, given the day may come where I no longer have R5 running with tSplines installedā¦I need to make sure all my tSplines objects are saved in box mode in the R5 files. Do I have that right?
@theoutside thanks for the tip re clean up. When you refer to the different maths are you in particular referring to a tSpline? If so I may be in luck as I avoided using tSpline faces as they seemed to create more issues for me than solutions.
Im the same on the use of actual Tsplines in my Tspline models, almost never did.
I actually described my Tspline/SubD workflow to others as more like āAuto Polysurface Managementā. Where I mostly try to create pretty logical nurbs patch layouts, and just use Tsplines/SubD to take care of the tangency between the connected patches.
