yes behavior editor. I was aware that you have them while doing mr. But I
assume that behavior is somehow contacted during the rendering, and it's
probably only two different frontends on the same program.
It simply means that seems to be their standard error message if something
pointer is missing.
I told you about the broken xsi while doing the tutorial just to reassure
you it might be the software and not you.
The access violations went away one time on reload.
I also had in the beginning occasions where the keyboard focus was lost
and in the HKSMs the message tree was lost. No idea why? Went away on
restart. This at least provides a hint that the pointer handling might be
a bit individualistic in Behavior.
On the other hand maybe a node or bone or actor might be missing.
Nils
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
