Re: A Rendering for Behaviour Question

Date : Tue, 12 Jul 2005 13:14:12 +0200
To : <XSI(at)Softimage.COM>
From : "Sandy Sutherland" <sandy(at)refinery.co.za>
Subject : Re: A Rendering for Behaviour Question
Hmm - I have a Model of a Cow - I have used the Behaviour Toolbar to
generate a Behaviour actor - using the box option, I then transferred a
skill across - a walk cycle - OK so far, did my sim using this actor - cool
sort of, then when I generate render data and try and render it having
generated the render data using the cow that I created the actor from - I
get the access error - so after some digging around in the docs, I find that
you can generate a render version using the toolbar - to ensure
compatibilty - Aha - sorts out my problem I think, must be this - so I
created a Render version - then created render data, did the sim again, try
to render with the new ultra compatible render cow - same error - start to
scream!!!  Don't know what could be missing - it is always after the
enveloping message in the cmd window!

Thanks for you help

Sandy

----------------------------------------------------------
Sandy Sutherland  Digital Doodeller - TD
The Refinery (Cape)  http://www.refinery.co.za
mailto:sandy(at)refinery.co.za
(P) (+27 21) 480 3132  (F) (+27 21) 480 3101
----------------------------------------------------------

----- Original Message -----
From: "Nils Koesters" <nils(at)mcs.st-and.ac.uk>
To: <XSI(at)Softimage.COM>
Sent: Tuesday, July 12, 2005 12:51 PM
Subject: Re: A Rendering for Behaviour Question


> 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

---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.