Pocket Quake mouse support ?

[SonicSilicon]

I finally got around to purchasing a PocketPC 2002 (worth, the wait, in my opinion.)
Mine has USB hosting which means that I can plug USB devices into it and use them (if there's a WinCE driver.)
I already got a keyboard working with it (since there's a built in driver) and seems to have mouse support, too, just not with the GUI.
So, Dan, any way to add mouse support to Pocket Quake/Quake II?

[R0B]

[SonicSilicon]

I have a Cassiopeia E-200.
NEC's MobilePro P300 also has USB hosting abilities (and I think CompUSA has them on sale for about $300 US this week.)

[R0B]

I have an e200 also, but don't you think that requiring a mouse takes away from the portability of it all.

[SonicSilicon]

Take away from portability? Nah!
Check this out :
I should have been a bit broader and said pointing device instead of mouse.

[Dan East]

Pocket Quake should work fine with a mouse as-is, assuming drivers are available and the Pocket PC OS recognizes it.

Dan East

[SonicSilicon]

I guess there isn't a driver buil in, then.
I assumed there was since the one I plugged in lit up and the E-200 didn't complain.

Time to hunt for a driver.

[R0B]

Good luck. And if you find some, post links.

[Dan East]

I've thought a bit on this, and took another look at the PQ sources. You will be able to use a mouse, but it won't be perfectly suited for control. The mouse button will not fire, but will trigger onscreen controls, or mlook if the mouse was in the mlook area when the button was pressed. When the mouse button is released mlook will stop. It would be very straightforward to add true support for mice, but I will wait until someone actually gets the hardware / drivers going with the OS first.

Dan East

[Robotbeat]

Why wait?

And also, when you say straight-forward, do you mean not difficult or do you mean quick? (or both?)

[Matt Keys]

The E-200 comes with built in support for most usb mice.

[SonicSilicon]

[RwGast]

[Dan East]

Okay, first off, you need to turn off the auto-yaw rate. That was a custom var I added so that when the stylus reaches the edge of the display the view would start automatically rotating. Add the following line to autoexec.cfg to disable:
in_autoyawrate 0

The sensitivity is cranked up for stylus input. There is an additional multiplier I use to get the sensitivity where it needs to be for the stylus, so that will negatively affect mouse input. Also, when a mouse is used on PC games, the mouse cursor is constantly re-centered. Windows CE does not provide the ability to set the cursor position, so I don't know what the solution would be. The problem is that over time you will end up working the mouse cursor further and further in a specific direction. Eventually the OS will not allow it to go any further in that direction (I don't know if CE will even allow it to go beyond 0-239 on the X axis or not).

Dan East

[RwGast]

Wouldnt it be pretty easy to edit the source to allow a console command to turn off the custom multiplier?