 | | Re: Spybot studies: seek a world object
|
|
(...) Or, then again, you might not. As with the vast majority of the ROM subroutines (and all the _Bead subroutines) this subroutine fiddles around with a global variable (via calls to EnterBead and ExitBead). In this case it happens to be global (...) (21 years ago, 10-Nov-03, to lugnet.robotics.spybotics)
|
| |
| | Re: Spybot studies: seek a world object
|
|
(...) Cool program. Keep up the great work! (...) You might be able to use PointToward_Bead without running into problems. __nolist void PointToward_Bead(const int& nTimes) { asm { 0xe3, &nTimes, 0x17, 81, 0x01, 1 }; } This ROM routine monitors an (...) (21 years ago, 10-Nov-03, to lugnet.robotics.spybotics)
|
| |
| | Spybot studies: seek a world object
|
|
/* beacon.nqc Uses World Relation Table to get a fix on and drive to another object. The object can be a Spybot, PC, or Spybot Controller. The program fixes on (i.e. drives to) the first object it finds. If that object disappears from the "radar", (...) (21 years ago, 10-Nov-03, to lugnet.robotics.spybotics)
|
| |
| | Re: Spybot studies: SetTxDirection() confusion
|
|
(...) How *does* the Spybot know the orientation (the ROM SDK calls it "aspect") of another Spybot? My (casual) observations indicate that all three emitters are on simultaneously and synchronously. How does the observing Spybot identify which one (...) (21 years ago, 8-Nov-03, to lugnet.robotics.spybotics)
|
| |
| | Re: Spybot Studies: display an 8-bit value
|
|
(...) In case anyone was wondering (yeah, sure :-), this line in my original post: lediDisplay = (x & 0x17) ((x & 8) * 4) ((x & 32) / 4) rearranges the bits so that the lower 6 bits can easily be read left to right (while looking at the bot from the (...) (21 years ago, 7-Nov-03, to lugnet.robotics.spybotics, FTX)
|
