Home Website Youtube GitHub

Tutorial for Building Custom Modules in Shifter?

Hi Miquel,

Firstly, I want to thank you for such an awesome tool as it is vital for making my project a reality.
I’ve purchased all the tutorials from Gumroad and appreciate them very much as they have helped me a ton.

I want to push my rigs a bit further and I realize that scripting is a necessary aspect of the mGear environment. I am wondering if, like the previous tutorials on Gumroad, you would be willing to make a series on how to make custom modules for Shifter? I’d be more than happy to pay for such a series if you consider it.

Thanks!

Also, just as a side note, I think it would be a great idea if mGear had a discord server so we can ask questions and share progress in real-time with those in the community. I would like to think that it would be beneficial for everyone involved.

A tutorial would be nice. In the meantime, what I did and what I recommend is to take some existing components, copy them into a custom component directory, rename them, and then edit them. It’s a good first step and you’ll learn the basic flow of how they work from guide to built rig.

That said, I didn’t get very far, and I still couldn’t write one from scratch. I rely more on post python scripts.

1 Like

I share the same sentiment with Chris. While more documentation would be amazing, that documentation can come not only from Miquel and the team but from any user that decides to experiment with this. You might find several threads regarding this subject, where folks share their modules (that might end up in the main branch). I’ve been adding some features to our mGear-based rig using Python modules on top of an already built rig rather than extending the Shifter modules. At some point I would like to look into it.

Regarding the Discord server, and please note that this is just an opinion, I’m strongly opposed to it as a way of managing data. Mainly to avoid fragmentation of information. The beauty of the forum is that is a gold mine, the information is very well organized and it’s relatively easy finding if someone had the same issues/questions you have. Finding information in a place like Slack/Discord is, compared to a forum, a nightmare in my opinion.

In addition to that, I found the team and the community to be very responsive and in a very timely manner here in the forum. A chat format enables a sense of ‘urgency’, both from the person that asks the question and those who might jump to answer it. I assume everyone here is more or less busy with their day to day job, so to me it is far from an ideal format. Someone explains it really well here:

I am aware this is a bit of confirmation bias self-exercise, and while I’m not an active part of the mGear development team nor the forum, I’ve seen several communities ‘die’ because moving to other platforms where the real time interaction is favored. Good for solving individual problems, bad for letting users be aware of those, hence the same basic questions being repeated over and over and over. Facebook Groups, I’m looking at you :slight_smile:

Sorry for the rant!

4 Likes

I agree with Iker, I’m against the idea of moving to chat, or splitting the community by having both. I’m on another forum where there is a Discord community. The forum is luckily still vibrant, but there is a ton of activity in the Discord, and it all gets lost in the noise. They needs bots just to answer questions that people keep asking over and over. It’s fun to hang out sometimes, but it isn’t good for building a store of knowledge.

(You certainly are. You’re one of the most active this year, you’ve given good tips and unearthed good bugs!)

4 Likes

I agree with Chris, I think the best way is to copy one component and edit them.

Maybe this video can help you to start.