I
looked into it long ago and yes, it is basically because Wacom pen events are
sent with lower priority than regular mouse events and therefore we don't get
them while playing back.
We seem to be affected because of the way we do playback and our
competitors who are not affected are probably using a simpler single-threaded
playback model. So, from our perspective the problem is most likely a Microsoft one. (but
it could be a Wacom driver issue)
However, because the problem only affects XSI (because of the way our
playback is implemented) we may have to ultimately try to work around this
issue. (no ETA or promises though - I'm just telling you the nature of the
problem)
For now I would suggest just setting up a keyboard hotkey to stop
playback.
--
Brent
Well thats the mystery...some Windows, Wacom thing. Basically I
think someone was saying your typical mouse is top of the processing stack but
the wacom is further down the chain. I couldn't for the life of me, tell
you what that means or to expand it any further. Perhaps someone from
Softimage can remind us of what the issue is? I just always thought it was
weird that ONLY XSI seems to have these Wacom issues. Haven't tested it in
awhile but I can't recall Max or Maya having stop playback issues with a Wacom.
Kris
On 6/29/07, Steven
Caron <carons(at)gmail.com>
wrote:
"know the whole stuck playback thing with Wacom is a non-XSI
issue"
who's is it?
On 6/29/07, Kris
Rivel < krisrivel(at)gmail.com>
wrote:
Is
this an issue beyond what Softimage can do I wonder? I know the whole
stuck playback thing with Wacom is a non-XSI issue so I wonder if this falls
into the same category. Can anyone from Softimage comment?
Kris
