by Baker » Tue Dec 22, 2009 9:44 am
More info:
1. The way Quake handles mouse input is by constantly re-centering the mouse pointer to the middle of the window. This isn't available to Flash. This places some limitations on how to handle input, but there is room for improvement. One thing that would help mouse movement is a higher sensitivity, as this prevents the mouse from leaving the window area as quickly. And possibly adding m_accel.
2. Full-screen mode in Flash disables the use of the keyboard. This is part of the security structure (as it is, only HTML indicating allowfullscreen=true even allows a Flash app to go full screen). Damn. The only use would be for viewing demos.
3. The Event activate and deactivate can detect focus. One possible optimization to reduce cpu usage might be to lower the frame rate or sleep more often when there is no focus. Or even some visible indicator that Quake doesn't have focus. If Quake doesn't have focus in Flash, it cannot receive keyboard input.
4. The combinations of ctrl + q and some other keys are problematic as they are browser shortcuts like "quit" which will exit the browser screen.
5. The config doesn't save session to session. Maybe a use of flash cookies could help fix this. The idea of save games seems a little out of reach.
Other thoughts:
a. The Flash page should use as large of a window as possible to maximize the surface area available.
b. Automatic reattach of mouse if pointer over middle of screen and previously attached.
c. volume should be lower as default (Flash seems overly loud?)
d. mouse sensitivity should be higher like 12 or 8 by default, helps mouse input.
e. Since config saving is not so easy, common sense alterations should be available?
f. Weapon switch default keys [ ]
g. See if can emulate mouse 2 or mouse wheel.
h. Anything to reduce cpu use if does not have focus. And some visible indicator.
i. Possibly make full screen available for demo watching.