Cannot reach maximum pitch under mouse control.

[Cody]

I am about to commit a fix, which is essentially making the sensitivity dependent on the game view's resolution. It now works for me on Windows in both windowed and full screen mode. Once committed, I would really appreciate some testing both from other Windows users and our Linux people, to be sure that nothing is broken (in which case will revert immediately).

Is that for mouse only, or 'stick as well? Will it be be in tomorrow's nightly (if terrastorage is back up... it's been down here for a couple of days).

[another_commander]

I think it's going to be mouse only. Unfortunately, I do not have a joystick handy to test. The fix should be on r4639 or later.

[Capt. Murphy]

Nice one another_commander. I'll be sure to test.

e2a - I've just dug out a cheap game controller I bought a while ago (£5 from Ebay jobby), but could never get on with - too used to fly by mouse from other games - confirmed it works fine pre this fix (no problems with pitch/roll - )so will also check that nothings changed.

[Micha]

Seems to work just as before under Linux - not being a mouse-commander I can't really tell whether or not there are subtle differences (keyboard for me).

[Gimi]

Just compiled 4640.

Have tested with my:
Logitech Rumblepad 2. (Didn't work before)
Logitech Attack 3 joystick (Worked before)
Logitech Anywhare MX mouse (didn't work before)
Keys (Worked)

Status now is:
Logitech Rumblepad 2 with Logitech driver 5.9.129.0. (Doesn't work)
Logitech Attack 3 joystick with Logitech driver 5.9.129.0 ((Doesn't work))
Logitech Anywhare MX mouse with Logitech driver 5.33.10.0 (Works)
Keys (Works)

Oh, I have changed mouse since I last tested this with a mouse. Also, I have reinstalled my computer since doing any testing with this at all.

I'm running Windows 7 Professional 64 bit and Logitech profiler 5.10.127. I don't use profiler to set up my controllers though, I use Oolite.

Edit: Running at resolution 1920 x 1080

[CaptSolo]

Docking on the C64 was indeed a pig - I had an Atari 2600 stick (because I could spin it round and shoot from view port) and I remember in the end I just learned to fly basically flat out when the rotation was at a certain angle - knowing I'd go almost straight in. Which is why I smile a rueful/knowing smile with all the pilots now who say docking is too hard (dons Monty Python flat cap)

I played C64 Elite and docking was easy using the keyboard for flight control. The game had a damping toggle accessible from the pause game function. With damping turned off the ship would maintain whatever roll the ship was put in and so it was no problem matching the stations rotation. One still had to line up correctly and there was no nav beacon to assist in that regard.

[Capt. Murphy]

Well terrastorage.ath.cx still seems to be down so no nightly build (also tried http://nightly.oolite.org/windows/oolit ... .win32.exe - doesn't exist - the last nightly build seems to be http://nightly.oolite.org/windows/oolit ... .win32.exe ) and can't download the development environment to compile and test.

[Eric Walch]

This issue has been touched upon before, and I think the conclusion was that this is related to the drivers and calibration software in Windows and not to the Oolite code. For some joysticks the maximum flex will change with calibration and wear and tear of the potentiometers. I play Oolite at full HD (1920-1080 on desktop) or (1920-1200 on laptop) and I still see this problem on my mouse and game controller. Anyway, if it can be fixed, nothing is better.
-----
Just compiled 4640.

Have tested with my:
Logitech Rumblepad 2. (Didn't work before)
Logitech Attack 3 joystick (Worked before)
Logitech Anywhare MX mouse (didn't work before)
Keys (Worked)

Status now is:
Logitech Rumblepad 2 with Logitech driver 5.9.129.0. (Doesn't work)
Logitech Attack 3 joystick with Logitech driver 5.9.129.0 ((Doesn't work))
Logitech Anywhare MX mouse with Logitech driver 5.33.10.0 (Works)
Keys (Works)

Oh, I have changed mouse since I last tested this with a mouse. Also, I have reinstalled my computer since doing any testing with this at all.

I'm running Windows 7 Professional 64 bit and Logitech profiler 5.10.127. I don't use profiler to set up my controllers though, I use Oolite.

Edit: Running at resolution 1920 x 1080

As far as I see the code is the joystick fully separated handled and we are only addressing the mouse here.
The complain was for full screen mode. (Just checking if we are testing the same thing: mouse-controll in full screen). Or exists the problem also in windowed mode?

I myself never could fly by mouse. I already have problems to point my nose in the general direction of the station. i always keep overshooting strongly and have to keep an eye on the dials to check they are near the centre. In combat that is a problem as I need my eyes on the opponent. Also a problem with the standard hud is that there is no line on the dial for the neutral position. You just have to guess if one dial is centered.
Yesterday I briefly configured my mouse with a second button. Than it becomes easy to stop rolling with a right-click. But back to my normal mouse setup it became impossible again.

(I use a magic mouse where the whole surface is pressure sensitive. So, in the theory could the software define an unlimited number of buttons on its surface )

[maaarcooose]

Just picked up this thread, but I remember using an old Voltmace joystick on my BBC for Elite.

http://acorn.chriswhy.co.uk/8bit_Upgrad ... lta14.html

The control on them was superb and you could match rotation flawlessly.

!m!

[Eric Walch]

Just picked up this thread, but I remember using an old Voltmace joystick on my BBC for Elite.

http://acorn.chriswhy.co.uk/8bit_Upgrad ... lta14.html

The control on them was superb and you could match rotation flawlessly.

!m!

from the old C64 I only remember joystick flight. Maybe keyboard didn't exist of was very problematic. I also remember that Elite was the reason I bought a new joystick. With that new one became dogfighting much easier. Although both were just binary joysticks with 4 micro-switches.

[Cody]

I cannot get a nightly build for testing as terrastorage is still down!

[another_commander]

Nightly r4640 for Windows uploaded temporarily to my box account and available here: http://www.box.net/shared/nz0xzbv3fcnnp1xh4yj1

[Cody]

Thanks, Admiral... grabbed it!

[Cody]

Disclaimer: I'd never used the mouse for flight control before today.

Win XP Pro x32 SP3 1280x1024 in fullscreen mode.

Oolite 1.75.3: the mouse works, the 'stick doesn't.
Trunk r4640: the mouse works, the 'stick doesn't.

[Gimi]

As far as I see the code is the joystick fully separated handled and we are only addressing the mouse here.
The complain was for full screen mode. (Just checking if we are testing the same thing: mouse-controll in full screen). Or exists the problem also in windowed mode?

I did all my testing in full screen mode. I can do windowed mode tonight when I get home.
But as you see further up, mouse now works. I don't consider this a big issue, and possibly almost a feature. A forced misjump should require "fiddling" with the ships "engine" and "buttons".