Is there a technical limitation that prevents supporting Workspaces on Mac?
Hi Pharris -
Do you mean Worksessions?
If so, according to RH-36512 there are 3 dependencies, two of which have not yet been resolved.
-wim
Apologies for āautocorrectā - yes Worksessionsā¦
Where can I see the dependencies? Currently only
SDK RhinoCommon: Worksession class needs work
is visible for me.
RH-49556 SDK RhinoCommon: Worksession class needs work
That actually depends on RH-36512, not the other way around.
But yes, I thought that all links would be shown and that one then gets a 404 when one tries to follow a private link. That doesnāt seem to be the case.
-wim
Iām not sure if this implies there is any active development towards supporting work sessions in OSX
The only thing I see that implies such is the release target of RH-36512 Worksessions not implemented
That was moved from āFutureā to ā9.0ā a month ago.
-wim
Ok, without getting in the weeds of the various Jiraās etc, from a customers point of view what is the plan wrt either WIP or Prod timeframe (or lack thereof)
Iām afraid that the only information that I have is what is in RH-36512.
It looks like there currently is an intention of getting this into 9.0. Apart from that, (1) that might change, and (2) nobody here knows when 9.0 will āhappenā.
-wim
Understood.. With the (changes in the) way OSX handles Auto-Saves, beyond any reasonable size model (>5G-ish), Worksessions seems to be (one of) the only ways of having a reasonable workflow.
1 Like
is there any update on Worksessions for Mac? Or in the interim/alternative, what advice does Mcneel have for Mac users who have no choice or no intention of moving to Windows, yet have to work on really big models. ?? This is really a fundamental issue.
I get the Mac users are seen a second class citizens, but this feature has been asked for, for literally years now,..
I may be misunderstandingā¦ But if you have enough RAM the size of the model shouldnāt be too much of an issue. ? These days MBP comes with 128gb and Studio Machine with double that.
Not withstanding of the need for WorkSessions for Mac.
Thread title revised to āWorksessions for OSXā.
If I have a really big model and I want the security of versioning/autosaving etc, worksessions lets me break a really big model into modules. as the worksession file is essentially a link to a number of modules Iām only saving the links and any content created. Saving now is very efficient as Iām not saving the modules just the top level content. Itās not a memory issues. Itās an interrupted workflow every time there is an āautosaveā..