I’m stumped – the Keyboard sensor and the Always sensor in 2.49 do not seem to honor the setLogicTicRate setting identically. I have two scripts, one connected to an Always sensor where I set GameLogic.setLogicTicRate(20.), and the other connected to a Keyboard sensor. I’d like both scripts to operate at 20Hz, but the Keyboard sensor seems to race past the Always sensor at roughly 2x to 3x speed.
Here’s a little more detail. Both scripts have socket connections to an external C++ program. The Always sockets are blocking and the Keyboard socket is non-blocking. If I setLogicTicRate to 60Hz, the Keyboard script sends data precisely when key is pressed and all is good. But, if I setLogicTicRate to 20Hz, the Keyboard sensor samples and cues up all of my keyboard inputs at about 40Hz to 60Hz. I’d much prefer a TicRate of 20Hz if I can resolve this issue, because 20Hz is real world speed for this C++ program.
Thanks,
Doug