We have an official transition date for our Next-Gen connectors: June 1st.
What does this mean?
Next-Gen connectors will officially become the default. We strongly encourage you to switch over.
Legacy connectors will be available, but will no longer receive feature requests or bug fixes.
Tutorials for legacy connectors will be unlisted.
You’ve probably received an email about this transition from us, but if you missed it then please read the migration guide we’ve put together with all the FAQs for what this means
If you don’t already know what you can do with Next-Gen, check out our supported use cases and workflows:
so does that mean anyone on mac wont be able to work cross platform with windows users/models per this line?
Models published with Next-Gen (default) are incompatible with models published with legacy connectors and vice versa.
and tutorials will be unlisted meaning new mac users wont be able to find help?
it seems bizzare that the app designed solely for interop between apps suddenly stops supporting an entire platform.. one that is working fine today will be broken in 2 weeks…
Well, I personally would not expect a perfect bug free Mac + even Blender release, at that same date … but I am happy if they already got all their new exciting v3 features together at that date.
But of course will be looking forward to see the release of my personal minority OS and App Connectors when they are also ready.
@eee, as Claire mentioned already here - you can still use Legacy Mac connectors in the Legacy environment. We are not shutting down anything. This just means we won’t maintain them to put more resources on Next-Gen development. On the other hand this doesn’t mean we won’t have Mac support with Next Gen. It’s just a balance between resources and priorities right now.
i appreciate that they will “still work” - but from what i can tell they wont work with models published from windows computers. so they are no longer interoperable with 95% of models.
also, can you provide a list of connectors that are <5% usage so we can prepare for other services you will deprecate if that is the focus.
OMG
I really I would have thought it may be about a Revit vs Rest 60 : 40 and Windows vs Mac of 80 : 20 in AEC …
WTH
Regarding those frightening sub 5 % only , I wonder - and am happy that there is even “any” Mac Connector, not even thinking of any Blender on Mac Connectors :))
And I really love the V3 features I have read so far.
i appreciate that they will “still work” - but from what i can tell they wont work with models published from windows computers.
They will still work with legacy Windows connectors!
If cross-platform is critical for you, then you and your collaborators should continue to stay on the legacy connectors, until we have more signals to prioritize Mac-support for Next Gen
BTW: Not promising about timing, but we have been thinking of providing steps to enable the Blender next-gen connector on Mac by some copy-pasting till we enable it properly with our deploy channels. We do not want to block people if they do not mind setting it up themselves. (Same for SketchUp, Rhino is quite hard with this way). Would it work for you @zoomer since I know your desire from the beginning
It has been a best effort to support them in both directions. You can get geometries from next gen to v2 but might loose render materials and blocks since we extract them differently in next gen. It is a breaking change in our object model for performance, data footprint, and many other reasons.
I will keep you posted once we have it. cc @dogukan
That is great to know.
So far I thought v2 and v3 uploads would be completely incompatible.
No problem in my case of course. When I get access to v3 I’ll test v3.
Later v2’s to v2 inside (or IFC to) Blender was already cool and promising, but I am so much looking forward to Materials and such …