Hey, not entirely sure if this thread is still active, considering the last post was 3 weeks ago, but I wouldn't want to be a rule breaker, so I figured I'd ask here anyway.
I'm building a fun little script, unfortunately I will not be producing source code beyond what is necessary for you to answer my questions nor be explaining what it is until I'm done, it's a surprise!
My questions for now are: (Note A isn't entirely LUA script related, but it is related to my script)
A) Is there any way to permanently turn off ghosts, rather than to have to add a hook that would turn them off at the start of each turn? I ask because I need every ounce of performance I can get, and with opt fixedframerate 0 I get around 300fps with ghosts on and around 1400 fps with ghosts off, (A rather dramatic difference.) and I don't want to sacrifice the usability of my script for other users. If not, what kind of command would I put in the hook to turn ghosts off? something like a call to opt ghosts 0? I don't know the command name.
B) Is there a command I can call or a good way to force the turn to progress? Again this is for time saving / performance reasons.
C) The distance between (and direction to) player x's head and player y's joints (all of them) (and visa versa) and the momentum of player y's joints (and visa versa) need to be calculated, can you give me some tips on how to get this information? I understand trigonometry, and I've done mathematics mechanics at higher level education, so I don't need you to do all the math for me, I'm just having trouble getting the data I need.
I should mention I have read the various LUA tutorials by blam and jok, as well as the wiki page, so if any of these questions should have been answered by those feel free to be patronising / condescending, I'll understand.
[EDIT]
In relation to question C; unless there is world position data for the tori-models (it looks like it's drawn from the position of the camera, correct?) Then I figure we can place the camera onto the default head tracking cam positions and measure locations relevant to the camera like that? Not ideal but it could work.
Last edited by Vox; May 26, 2011 at 11:39 AM.