> There's a Shockwave issue with more recent AMD
processors.
> This sounds similar to the symptoms your describing.
> The problem happens when the thread running shockwave
player
> in the browser switches from one processor to another.
This
> actually happens quite frequently on a dual core
system. The
> player gets the system time stamp at one frame, the
player's
> thread is switched to the different processor by the
OS, then
> on the next frame when it takes the time stamp again it
comes
> up with a completely invalid time since each core has
it's
> own clock and they aren't in sync.
This is really interesting, Gene. Does it affect *all*
time-related
functions (ticks, milliseconds), or just Director's internal
frame counter,
or only HW-accelerated 3D? If it affects the milliseconds,
that's a very
serious bug for anyone doing time-based code.
Danny
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
