>>> Please Read >>> Epic Has Abandoned this Project. New Repo in first comment

[dav01d]

UPDATE as of June 2024:
While Epic has abandoned the tool, JoshQuake is keeping it alive over at a fork: https://github.com/poly-hammer/BlenderTools

Scroll down for more discussion. This issue will be left open for Google/SEO history, as its one of the first things that comes up.

[violetbeamgames]

Seems like it :/

[vikista]

:(

[TactileVisions]

That'd be a pity

[hhzx]

Why？:(

[Xiarno]

Since the last version supported is Blender 3.6.0, which is an LTS version, it's possible that they are waiting for Blender 4.2 which is also an LTS version before releasing a new update to this addon.

The target for 4.2 LTS release is currently July 16th.
Source: https://projects.blender.org/blender/blender/milestone/19

[DanMcLaughlin]

Yes it's been discussed elsewhere, James left the company and there's nobody supporting this anymore. But the license was changed and we're now allowed to fork and develop it ourselves. What is needed is somebody to take the lead on that.

[Xiarno]

Yes it's been discussed elsewhere, James left the company and there's nobody supporting this anymore. But the license was changed and we're now allowed to fork and develop it ourselves. What is needed is somebody to take the lead on that.

Is that so? Well, if a fork get made that is usable and updated, would you mind linking it here please?

[DanMcLaughlin]

If you read my comment I said somebody needs to take the lead.

[Xiarno]

If you read my comment I said somebody needs to take the lead.

And if you read my comment, I said "if a fork get made", which is in the future, whenever that would be, if you could please link it here.

[DanMcLaughlin]

I'm trying to tell you I'm not taking control of this project and am unlikely to have any part of it, perhaps you could take the lead and find somebody who is willing to take responsibility on this.

[JoshQuake]

I'd love to do so to keep it alive, however I'm not skilled enough to do major fixes. I'd have to rely on others for most updates. However that being said I can do so and began implementing the pending pulls into my own fork.

If other contributors are okay with that, the fork is here https://github.com/JoshQuake/BlenderTools

[DanMcLaughlin]

That's great @JoshQuake! I think all we need is a maintainer who can

• Integrate all the pending and existing fixes, there are two are three already, the LOD regex error, the Blender 4.0 FBX update (older) and there might be one more
• Merge new fixes from the community
• Publish releases

However that link doesn't go anywhere, is the repo public? Are you able do these things and continue maintenance?

Edit: some URL parsing problems, if I go to your home page and view it from there looks like you already cut a release

[youthatninja]

Please keep it alive 🙏

[JoshQuake]

That's great @JoshQuake! I think all we need is a maintainer who can

• Integrate all the pending and existing fixes, there are two are three already, the LOD regex error, the Blender 4.0 FBX update (older) and there might be one more
• Merge new fixes from the community
• Publish releases

However that link doesn't go anywhere, is the repo public? Are you able do these things and continue maintenance?

Edit: some URL parsing problems, if I go to your home page and view it from there looks like you already cut a release

oops fixed link. Yeah I'm definitely down to do that. This tool is too useful to be abandoned.

[TactileVisions]

Thank you, @JoshQuake

[dav01d]

Awesome work @JoshQuake

In case people missed it, Josh is now running this project in a fork: https://github.com/JoshQuake/BlenderTools

[dav01d]

Closing thread for now, see above 👆

[dav01d]

Actually, I realize I should keep this issue open, incase google, or other visitors come by. It will be the very first thing people see. Apologies for the reopen, but its purely for guidance of future users :)

[youthatninja]

What about ue 2 rigify? Or it's included in the fork?

[JoshQuake]

What about ue 2 rigify? Or it's included in the fork?

It's included. As far as I'm aware it doesnt need an update yet as the checks pass.

[youthatninja]

What about ue 2 rigify? Or it's included in the fork?

It's included. As far as I'm aware it doesnt need an update yet as the checks pass.

Great. For the ue2rigify,
there are no unreal 5 mannequins presets. So metarig should be updated

[JoshQuake]

What about ue 2 rigify? Or it's included in the fork?

It's included. As far as I'm aware it doesnt need an update yet as the checks pass.

Great. For the ue2rigify, there are no unreal 5 mannequins presets. So metarig should be updated

okok. I shall take a look this weekend and see what I can do.

[jack-yao91]

Hi I am a little late to the conversation, but @JoshQuake thanks for stepping up and helping out with this project. I am a tool developer, and we have become very reliant on this addon being a part of our pipeline. Me and a co-worker had created our own fork here and integrated some of the PRs and stood up the CI/CD workflows for testing, docs, and creating releases.
https://github.com/poly-hammer/BlenderTools

Send to Unreal is passing all the tests in Blender 4.1, however UE to Rifigy is still failing some tests here. (which look like some changes to the rigify API)

Our primary interest in keeping this addon working and up to date, is so that users of our other tools can rely on the integrations we have made with send2ue.

Our org has a self-hosted runner pool we use for other repos that we were able to utilize for our BlenderTools fork, but maybe we could discuss a way to combine efforts? You have shown a great deal of ownership with project, so I definantly don't want to slow you down, but maybe we can figure out how to share some of our runners with you. I can follow up with some more details here.
JoshQuake#16

[Derjyn]

Okay. So which one do we utilize? It's confusing... The 2 repositories that are active, point fingers at each other:

https://github.com/JoshQuake/BlenderTools
https://github.com/poly-hammer/BlenderTools

Can the maintainers of those update their docs to reflect which is which, and we can get a final confirmation on which is the legitimate, active, end-all-be-all repo?

---

JoshQuake repo:

Poly-Hammer repo:

[JoshQuake]

Poly-Hammer is the new home. I will be archiving my fork when everything is migrated.

[Derjyn]

Poly-Hammer is the new home. I will be archiving my fork when everything is migrated.

Awesome! Thanks for the quick reply. I hit a bit of speedbump when working on internal documentation concerning production pipelines, and wasn't expecting the Epic side to go dead, and then got more confused when finding that you guys picked up the banner.

Thanks for all your hard work. I can get back to the joys of development docs 😏