@Daxel and @Greenlaw, no, I do think I do understand what 'Flexi bind points' and 'Flexi bind layer' does and I don't confuse the two. Unless there's even more crazy stuff going on. I thought we were already past that station. The issue I (think I) WAS having here (at least that is my conclusion after all of this and by your help and I thought we concluded that by now) is that there was already a 'Flexi bind points' active on SELECTED Body bones on the body mesh (manually set). And it should just prevent to have influence by other bones on that layer because why would we even want that if we already bound it with another method? At least that's what I would say is the most (and only tbh) logical thing. But STILL I needed to also 'Flexi-bind Layer' THE SAME body bones to THE SAME body mesh, ONLY to avoid the unwanted default 'global' binding behaviour (we never want). Which is just completely illogical to me as now there are TWO (!!) binding methods set on the SAME bones and the SAME layers(' points) **if taking the features literally by description**, ONLY to prevent a third 'global' method, which also happens to be flexi point binding, but with some mesh generated automatically and controlled by ALL bones. That's just nuts to me and doesn't make any logical sense to me.
Greenlaw wrote: ↑Wed Aug 16, 2023 2:41 pm
I looked at the recent video, and it appears you haven't applied
Use Selected Bone For Flexi-binding because the bones are not highlighting as you select each layer.
Yes, and that would make complete sense to me in what I consider normal logic; because these bones are already Point Binded. By Daxels post I understood that it's even weirder than I thought it would be and that we even need to use 'flexi-layer binding' those bones only to prevent issues from happening, while these were already point binded.
Let me be clear; I'm learning how Moho currently works and spent already days on the binding alone basically. Which to me tbh is nuts for such a simple thing. And looking at many posts here about this I'm clearly not the only one. Hense, there's even a video explaining the pitt falls... (Thanks for that btw McCoy, just watched it). This all just shouldn't be necesary if just 1 thing would be different: No default global binding. Because it makes all logic in reverse and that's never a good thing. That's what I mean by making things overly complicated and confusing.
I am willing to understand how the current system works and try hard, but I'm really hoping somebody from Lost Marble reads along and will clean up some things in the next version and make it logical in the next version, because again; the stacked design choices made over the years make things overly complicated, confusing and time consuming now. Both to learn and to use. And I noticed I'm not the only one thinking that and haven't see nobody calling 1 benefit of the overly complicated implementation of the techniques.
Let's be honest, I think this would be way more logical and easy to understand for everybody, both beginners as well as advanced users:
1 - No binding by default. None. No binding. Fresh start. CLear logic; we don't bind, so nothing is bound. No more inversed logic. Makes complete sense to me and stops all other confusion, time consuming corrections, weeks of learning Moho binding, and overly complex stuff immediately. I think this alone is solving all issues for 80% if not way more already. This would, for one, make a word like 'RESET' also way more clear and trustworthy because it really resets something to NONE. It would also directly prevent all the weird influences by other bones etc. we didn't want in the first place. To me it just doesn't make any sense to keep struggling about what things to turn OFF first to stop the weird influences. We should only have to worry about our OWN bindings and just start from zero. Also for beginners than it's way easy to understand new software, because everybody understands that you have to do something to make it do something and all following steps are just logic actions with no influence on something we didn't want in the first place.
2 - Note by 1: This would also make sure that 'Use selected Bones for FLexi binding' does exactly what it says. Because there is no such thing as a confusing 'global'/ default binding no more.
3 - See 1
4 - See 1
5 - See 1
6 - See 1
7 - Clear and consistant, clearly distinctable, terminalogy used everywhere in UI and documentation that actually tells what it does (no terms like 'rigging' that are vague and nobody knows what it exactly means)
8 - Make things 'checkable': some clear UI stuff to actually see what is being bound to what and with what method so things are less of a black box and easier to learn (although this is way less important when: see 1)
9 - Not 100% sure about this one, because it can perhaps have advanced use cases, but at this point I think it would make sense and prevent issues;
only allow either Point binding or Layer binding per layer.
10 - Indepth explanation in the manual about what the binding techniques are and what exactly they do, when to use which etc. ('this is automatically creating a mesh underwater' etc. things like that so we get to understand them). Because new users just don't have all the knowledge of how things were in the old version of Moho and than this whole thing is just one big black box. Which is sad, because I think it's not that hard to explain this, if at least done as: see 1.
I completely understand that when software gets more features software can get bloated and confusing and older users just adapt and don't complain, because they knew the (perhaps already confusing, but less functions) past. But sometimes you just need to step back, be honest and look with fresh eyes and this is clearly one of those things that just aren't intuitive and even very counter intuitive. And it shouldn't be that hard to fix this: just remove the initial binding that nobody uses anyways and is inversing all normal logic (which is even more confusing with the used terms that sometimes are just wrong). Everybody understands the logic that when you don't do nothing, nothing is bound. If you inverse that logic (and not consistantly), like now, you mess up with peoples brains and it makes everything way harder.
It's very complex and counterintuitive now to need to do everything inversed (but not consistantly) from the basic logic the world works with and to get rid of default behaviours first. Defaults that obviously no real user even uses so doesn't serve nobody and is only making things hard to use and understand.
This is no hating whatsoever, this is being honest and straight and not talking around it, like when with friends, to hopefully make somebody reading along to make Moho easier to use and get in the future. Because I like to use Moho for years to come and take it seriously, hope that new users don't have to go through all of this and really hope that Moho gains way more popularity and gets more users. Because these struggles to learn and use such a pretty basic thing in software just shouldn't be there IMO.
Thanks everybody for all the time to help me understand this. Really appreciated!! I'm going to see now if I can change my documentation on this to make it understandable for myself and if everything is completely clear the way it works now (I think I do) so I don't encounter these pitt falls next time.