Hello

1. Is there a simple way to replace a painted strength map for many bones by a new map? If not, there should be.

Now I have to Duplicate Paint the old map, Select Bones for the original map, Remove the original map, and Attach Bones to the replacement map. Is there a better workflow?

2. Another glitch: The Skin Editor values (Weight Min, Falloff, Bone Max) are lost when I detach a skin. So I have to enter the same values again and again when I detach/bind the same skin—really annoying. The skin should retain these values.

3. On the other hand, the strength maps survive when I detach a skin. The bones of the detached skin retain their map reference, which now points to a map on an unbound skin. This state seems to make Animator unstable. I get a lot of crashes in this situation, whenever I rename any object in the scene. The crash is always caused by
DFWDialogEffector::InterfaceBoneStrengthListRename().
The same operation usually works when I restart Animator.

Animator 7, OSX 10.4.11, iMac G5.

Hi, atlantis23

Your 3 points are very different ("full spectrum” ). Ok, step by step

atlantis23 - 16 August 2008 07:15 AM

1. Is there a simple way to replace a painted strength map for many bones by a new map? If not, there should be.

Now I have to Duplicate Paint the old map, Select Bones for the original map, Remove the original map, and Attach Bones to the replacement map. Is there a better workflow?

Don’t know, it’s “application design”, not a programming yet.  If there are ideas - let’s consider them together.

atlantis23 - 16 August 2008 07:15 AM

2. Another glitch: The Skin Editor values (Weight Min, Falloff, Bone Max) are lost when I detach a skin. So I have to enter the same values again and again when I detach/bind the same skin—really annoying. The skin should retain these values.

Let’s formulate like: “skin dialog default values should be auto-adjusted to latest opened skin”. Right? Then let’s ask EITG permission (because it’s a changing of functionality, although a little) and then - change it.

atlantis23 - 16 August 2008 07:15 AM

3. On the other hand, the strength maps survive when I detach a skin. The bones of the detached skin retain their map reference, which now points to a map on an unbound skin. This state seems to make Animator unstable. I get a lot of crashes in this situation, whenever I rename any object in the scene. The crash is always caused by
DFWDialogEffector::InterfaceBoneStrengthListRename().
The same operation usually works when I restart Animator.

Animator 7, OSX 10.4.11, iMac G5.

It looks like direct bug that should be fixed. But we need a bug prj - please prepare such small one and write few phrases what we need to do to get a crash

Hi Igors,

Thanks for the fast reply.

Ad 2: I understand why the data is dropped, and maybe there’s a good reason to do so. But there’s maybe a simple way to keep the values.

Ad 3: I’m trying hard to find a reliable crash sequence on a simple project. The other project crashed 10 out of 10 times, the minimal example only crashes sometimes. Always at InterfaceBoneStrengthListRename(), though.

Hi, atlantis23

atlantis23 - 16 August 2008 02:32 PM

Ad 2: I understand why the data is dropped, and maybe there’s a good reason to do so. But there’s maybe a simple way to keep the values.

No probs for such kind of changes. All we need = refer to “users asked this”. Can we?

atlantis23 - 16 August 2008 02:32 PM

Ad 3: I’m trying hard to find a reliable crash sequence on a simple project. The other project crashed 10 out of 10 times, the minimal example only crashes sometimes. Always at InterfaceBoneStrengthListRename(), though.

Ok, please archive crashReport and give us a link to it. Maybe it’s possible to fix prob with crash info only (of course, maybe not).

Hi Igors,

No more crashes today, unfortunately . Here’s the latest crash report I saved:
http://www.atlantis23.com/crash_report_08_15.zip

I had many crashes with that project on August 15th, and some more crashes with a minimal project on August 16th. Always when renaming a group/effector in the project window. The crash reports always looked the same to me. Everything works well now. If it happens again, I will send you the affected project. Thanks for your support, anyway.