The F1 issue is fixed in the newest pre. Thanks for that.
Separately, and this isn't specific to the new prerelease, it looks like some keys aren't having their value reset to 0 after being pressed. That is, gfx.getchar(26161)
if F1 is pressed and 0
if it isn't, but keys like ~ (ASCII # 96) or § (ASCII # 167) continue returning 1
after being released.
Test script here: https://dl.dropboxusercontent.com/u/...%20checker.lua
Once you press a key, it'll check that key's status on every loop. The second column should go back to false
, but not every key does.