Free Allegiance Forums

My mistake, updated the file, please download again and it should work fine.

and so it does.

So the problem is that the game cursor is acting like it's following the primary cursor around?

I've encountered this on various other games, and it makes the controls infuriating. VSync seems to be a culprit much of the time.

Spunkmeyer wrote:QUOTE (Spunkmeyer @ Feb 13 2012, 10:18 AM) Please try this, it re-enables Vsync settings and you can turn it off (should be off by default now that I think about it)

http://dl.dropbox.com/u/21458077/AllegianceVsyncOff.zip

I've seen a definite improvement, so I think it fixes the problem.

(It will connect to the beta lobby, you can run it directly)

Zomg so much better! One thing I noticed though is that it breaks #76. But that's fixable without the forced Vsync.

TurkeyXIII wrote:QUOTE (TurkeyXIII @ Feb 13 2012, 03:49 AM) Zomg so much better! One thing I noticed though is that it breaks #76. But that's fixable without the forced Vsync.

What are you seeing in game exactly? My mouse throttle is fine (if a little more sensitive but it's a non-issue) but I haven't got my joystick working yet. Imago's previous hack to limit to 60 updates/sec completely breaks it, so we can't use that.

Anyone else having issues with this build (the exe linked above) with mouse wheel or joystick throttle sensitivity?

EDIT: Just tested my joystick/throttle, no issues.

I don't use a joystick. I have keys mapped to increase/decrease throttle, but they adjust it so fast that even a slight tap brings it to full. I think the point (or one of the points) of capping the framerate was so the controls would only update the throttle at known intervals, so the rates for increasing/decreasing throttle (and zoom - zooming in/out has the same issue) would be constant.

I think the more suitable way to do it would be to measure the time since the last throttle update and adjust the throttle proportionally.

Fixed the throttle key problem I believe.

DonKarnage wrote:QUOTE (DonKarnage @ Feb 13 2012, 04:17 AM) So the problem is that the game cursor is acting like it's following the primary cursor around?

I've encountered this on various other games, and it makes the controls infuriating. VSync seems to be a culprit much of the time.

"Didn't I metnion that Windows SVN>6 (ergo: "Windows 7") has a different handling with the velocity of its mice..." "--Another brilliant."

Don't you dare blame me for this mouse screw up. I was the first one to notice it and reported it all over TRAC when everyone else cried that "everything was fine".

Windows is supposed to control mouse sensitivity and speed. The mouse speed is applied to a series of curves to deliver sub pixelation at slow speeds for extreme accuracy and accelerates beyond a 1 to 1 ratio when the mouse is moved quickly. These curves were extensively researched by MS when implemented into windows operating system (research pointer ballistics). All of those curves are applied when you have the "Enhanced Pointer Precision" enabled in mouse settings within windows control panel. When the "Enhanced Pointer Precision" is unchecked, you have a perfect 1 to 1 ratio between the mouse movement and the pointer speed on your screen.

If you use other software to override windows pointer speed control, then that software dictates your speed and curves for any given mouse movement.

That pointer speed control in R6 should be removed completely and windows mouse settings within control panel should be managing pointer movement. R5 broke this relationship completely. If you adjust your mouse speed in windows then launch Allegiance (R5), you will see that your mouse speed is not applied. It worked properly in all versions of Allegiance UNTIL R5 broke it and is now also screwed up in R6.

Jimmy is correct in that widows versions XP and Vista, had applied inproper math to calculate pointer movement. When screen refresh rates were changed in those versions the mouse behaved differently when instead a change in screen resolution should have made the mouse behave differently, not refresh rate. This was fixed in windows 7.