I was just wondering if you knew the difference between the regular opertion call in an ACS and the "Direct" version, example:<br><br>CmdPolyWait<br>CmdPolyWaitDirect<br><br>Specifically I just want to know exactly what the "Direct" one means, since apparently the "wait" functions are the only ones who bother with 'em... and they change only in what looks like the matter of getting a parameter?<br><br><br>Also, when you define a new built-in, must the "native" defines in "builtins.vc" go in order?  <br><br>I.E. if I had a new to-be built-in function called "Func", and I add it after say "TagFinished"...<br><br>static void PF_TagFinished(void)<br>{<br>...<br>}<br><br>static void PF_Func(void)<br>{<br>...<br>}<br><br>...<br><br>builtin_info_t BuiltinInfo[] =<br>{<br>...<br><br>  _(TagFinished)<br>  _(Func)<br><br>...<br><br>}<br><br><br>Would that require the order of (in builtins.vc):<br><br>(all prior function definitions)<br><br>native void TagFinished(int tag);<br>native void Func(whatever); // New one NOW<br><br>(all later function definitions)<br><br><br>... for it to be properly addressed?

I can't tell you anything about the direct versions of commands. I will check it out some days later (I'm too busy now).<br><br>No, builtins are identified by name, order doesn't matter.

OK, about those Direct versions of ACS functions. They really differ in a way they are getting the arguments, direct versions gets them directly from code which is faster than pushing/calculating them and then poping.

Okay, makes sense, but my main question is, when are they used?  What even causes them to be called over their standard counterparts?  Why does it seem they're only really included in the "wait" script commands?

In ACS you specify them with const keyword like this:<br><br>delay(const: 35);<br>

Ah.  Thanks then.