http://robowiki.net/w/index.php?title=Thread:User_talk:Tkiesel/DeBroglie_dev_Notebook/calling_execute()_every_tick/reply&feed=atom&action=historyThread:User talk:Tkiesel/DeBroglie dev Notebook/calling execute() every tick/reply - Revision history2024-03-29T12:32:32ZRevision history for this page on the wikiMediaWiki 1.34.1http://robowiki.net/w/index.php?title=Thread:User_talk:Tkiesel/DeBroglie_dev_Notebook/calling_execute()_every_tick/reply&diff=25027&oldid=prevTkiesel: Reply to calling execute() every tick2012-06-17T20:16:57Z<p>Reply to <a href="/wiki/Thread:User_talk:Tkiesel/DeBroglie_dev_Notebook/calling_execute()_every_tick" title="Thread:User talk:Tkiesel/DeBroglie dev Notebook/calling execute() every tick">calling execute() every tick</a></p>
<p><b>New page</b></p><div>That execute() was just an instance of me trying to stop the do-nothing-this-round bug. When deBroglie does nothing on a round, the radar isn't spinning.. despite the infinite radar spin in run().. yet onSkippedTurn is still never triggered.<br />
<br />
<br />
I don't have any calls to execute(). Everything is in onScannedRobot()<br />
<br />
Question: in a 1v1 match, can onScannedRobot trigger more than once? That right there might be a source of some of my problems.<br />
<br />
deBroglie's structure would allow a movement(), gun(), execute() loop in run().. and just update the Universe object in onScannedRobot. I think some of my bullet/wave code would need tweaking because the gun and movement might be operating on a one-tick-old Universe.. but I think that can be dealt with.</div>Tkiesel