MovieSandbox Puppet Implementation
From Moviesandbox
| Line 9: | Line 9: | ||
<br> | <br> | ||
| - | <h3>What is done when?<h3> | + | <h3>What is done when?</h3> |
The ''event ReceivedBinary(...)'' function in MSBPuppetUdpControl takes care of incoming data. It can either store it in variables inherited from its superclass (like joyXAxis, etc...) or create its own variables. When creating variables, keep in mind that you will need a Cast when dealing with them in MSBPuppetControl!<br><br> | The ''event ReceivedBinary(...)'' function in MSBPuppetUdpControl takes care of incoming data. It can either store it in variables inherited from its superclass (like joyXAxis, etc...) or create its own variables. When creating variables, keep in mind that you will need a Cast when dealing with them in MSBPuppetControl!<br><br> | ||
Revision as of 18:16, 26 October 2006
Explanation of Puppet implementation for MSB
Every Character (Pawn) has a PawnInputControl that gets Spawned when creating the Pawn -> in the appropriate Button.
In case of the GATech Puppet, the Spawning Button would be MSBCreatPuppet.uc in the MSBMenuButtons Package.
The PawnControl that we create here is called MSBPuppetControl (in the MSBCode Package).
As a Link to the outside world, every PawnControl gets a udpLink and a reference to the Mouse, where all the native unreal input is being processed.
For now, all we need is the udpLink, which in our case (cause we're special) is a MSBPuppetUdpLink ( in the MSBCode Package).
What is done when?
The event ReceivedBinary(...) function in MSBPuppetUdpControl takes care of incoming data. It can either store it in variables inherited from its superclass (like joyXAxis, etc...) or create its own variables. When creating variables, keep in mind that you will need a Cast when dealing with them in MSBPuppetControl!
MSBPuppetControl creates its own udpLink in the initUdp() function. Actual code can get executed in Tick(). The Pawn is referenced through the myPawn variable defined in the SuperClass.
