I am observing something completely bizarre. The game, Armored Core 2 on PCSX2, is receiving inputs that do not exist in my script, according to a keyboard event viewer. The attached file only shows the keyboard event log after event 80 due to limitations of the website. The game is behaving as if random single Ss are sent during the random length sequence of Ds. The loop is structured so that only one S is sent and it always happens before the Ds and Space are sent. How is this possible?
I simulated the overall macro myself by hitting S, D a couple times, Space, then repeat in the hopes that this was some weird glitch with the game. The game acts normally and does not receive ghost inputs if a human is sending inputs.
I would send a PDF containing the keyboard event log, but I can't attach PDFs.
I simulated the overall macro myself by hitting S, D a couple times, Space, then repeat in the hopes that this was some weird glitch with the game. The game acts normally and does not receive ghost inputs if a human is sending inputs.
I would send a PDF containing the keyboard event log, but I can't attach PDFs.
CODE:
SendMode "Event"
F12::Suspend
;Create random build
F1::{
setKeyDelay 140, 30
;Select Head
Send "{space}"
sleep 900
rand := Random(1, 12)
Send "{d " rand "}"
Send "{space}"
;Select everything else
Loop 13 {
Send "{s}"
rand := Random(1, 7)
Send "{d " rand "}"
Send "{space}"
}
;Return to start
Send "{shift}"
}Statistics: Posted by Starker — Today, 17:24