Oh, and another thing - the other way of course to map an absolute input to a mouse is as you describe by doing it in a finite box.
This doesn't really work either - how many bits for the joystick input?
I am guessing about 65k positions possible.
What is the actual level of granularity you have? Probably a lot less - I doubt you could hit each and every one of those points, even with an unsprung stick.
So you would probably want at least a 10x10 block of input points per pixel that the mouse cursor could rest over.
Yeah, may work for lower resolutions, but for big monitors or multi-monitor, it would be useless. This is why mouse DPIs had to go up, because screen resolutions were going up but mouse mats weren't getting any bigger Sure it went to ridiculous levels, but you get my point.
4
Anyone Tried Saitek X-65F With Mwo
Started by Midnight Camel, Oct 06 2013 06:13 AM
21 replies to this topic
#21
Posted 12 October 2013 - 08:38 AM
#22
Posted 28 October 2014 - 02:20 PM
As a long time online MW pilot back to MW2. As a long time online flier with FalconBMS and Janes F18.
I find it disappointing that I cannot use my x65 well with MWO. It worked fine in previous versions of MW. So what's changed? Using a mouse kills the immersion IMHO.
BTW where is the TrackIR support, speaking of immersion...?
I find it disappointing that I cannot use my x65 well with MWO. It worked fine in previous versions of MW. So what's changed? Using a mouse kills the immersion IMHO.
BTW where is the TrackIR support, speaking of immersion...?
Edited by Bramage, 28 October 2014 - 02:21 PM.
4 user(s) are reading this topic
0 members, 4 guests, 0 anonymous users