I’m just installing to test locally before uploading a new version to the extensions website.
What’s in question is the fact that I localy have a higher version but Blender still tells me there’s an update.
I’m just installing to test locally before uploading a new version to the extensions website.
What’s in question is the fact that I localy have a higher version but Blender still tells me there’s an update.
Would it be possible to add sorting by install time, sorting by name to the plugins and extensions in blender?
Hi, I wanted to ask if it was possible to upload an add-on for Blender to the extensions website, this allows users a bridge between Blender and a commercial application that is Plasticity 3D. The add-on is open source with the MIT license.
Here on GitHub the add-on link.
Thank you.
@PaoloFurani You would have to ask the authors of the addon to submit it to the site.
Thanks for quick reply, the author’s concern is that he is not sure if uploading add-ons for commercial programs is allowed, so that was why I was asking, but I assume from your reply that is not a problem with this add-on with MIT license.
They can submit the addon which will go into a review process. If it somehow is not eligible then it won’t be accepted. I believe the extensions team is working on a document to list the requirements of an eligible extension and will release it soon.
A bridge wouldn’t be accepted since it depends on an external software. Basic I/O would be accepted though.
That said the extension author can still self-host a repository so users can benefit from updates from within Blender.
This would be a nice feature to have for sure, but it is not planned. But any contributions on that direction would be mostly welcome.
So what about UVPackmaster? Or the various Daz importers, or game engine exporters? What about the Mixamo bridge, or the Audio2Face integration for NVIDIA Omniverse? Are all of these not eligible?
I’m not familiar with all of these. But if they depend on an external software, then they are not eligible.
From the terms of service:
(At least) six of the corporate sponsors listed on fund.blender.org have add-ons that act as bridges to their software. How have representatives of those companies responded to the news that their add-ons are no longer supported in Blender? I’m curious how this will be affecting their funding of Blender going forward.
Hi Joseph,
I honestly have no idea, so far I haven’t heard any complains from any of these groups. (if any corporate sponsor wants to share any concern, feel free to reach out to your liason/pont of contact directly).
I would expect them to be very pleased though. Not only their add-ons are still supported, but now their users can even get their add-on updates from within Blender.
That’s just not true. Their addon isn’t going anywhere, it will still work. It might just not be hosted on extensions.blender.org. That’s all
How would a bridge addon get an update, if a bridge addon isn’t accepted to be hosted in the official blender listing?
@dfelinto aready explainded it just a few posts above:
I see that Rigify and Node Wrangler are marked as orphan. What does it mean in the context of the distribution platform? Should they be not distributed on this platform if orphan means not maintained anymore?
Rigify has been chosen to become an official/native add-on. I don’t know about Node Wrangler, however.
Node Wrangler is in a bit of a middle ground at the moment. It should still be there as it’s full self, but parts are or will be moved into Blender as base code.
So from that point of view, the ‘old’ Node Wrangler is orphaned and will slowly die out.
As already stated, Rigify is now full core addon and will ship as part of the base Blender download (in effect, nothing has changed for Rigify and any time it may have been on the Extensions Platform is now just a history blip).
“Orphan” mainly shows up if:
Alternatively it shows up if you install from Disk and choose to install in a remote tepository that it doesn’t really contain this extension. You have to go out of your way to do it, but it is possible.
In your particular case it probably happened because you installed them during the alpha/beta period of 4.2, before they were moved back into Blender.
That makes sense, I was not aware of the changes. I will try your steps and report back as a feedback. Thanks