You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
1.43 made auto generated bones use the current bone default with null as its name, where before it always defaulted to non dynamic eg. 0 mass
To Reproduce
Find a xml that has a bone default and then add weights to a mesh for a new bone it will fall off the body since it will now have a mass > 0
Expected behavior
This may be desired behavior but it hasn't been discussed to my knowledge. Personally I think all auto generated bones should be 0 mass as it was pre-1.43
Desktop (please complete the following information):
Windows 10
FSMP
Installed version: 1.6.640
CUDA: No_CUDA
AVX: AVX2
Required files
Don't have a log with it occuring since i fixed it on my setup(in XML) configs.zip
The text was updated successfully, but these errors were encountered:
Describe the bug
1.43 made auto generated bones use the current bone default with null as its name, where before it always defaulted to non dynamic eg. 0 mass
To Reproduce
Find a xml that has a bone default and then add weights to a mesh for a new bone it will fall off the body since it will now have a mass > 0
Expected behavior
This may be desired behavior but it hasn't been discussed to my knowledge. Personally I think all auto generated bones should be 0 mass as it was pre-1.43
Desktop (please complete the following information):
Windows 10
FSMP
Required files
Don't have a log with it occuring since i fixed it on my setup(in XML)
configs.zip
The text was updated successfully, but these errors were encountered: