Saitek Cyborg USB stick config grief.

Hi.

I'm having some problems configuring my Saitek Cyborg usb joystick for use with WinUAE 1.5.3 the game I'm using to test it with is Knights Of The Sky. I have calibrated the joystick in Windows first.

The game only recognises joystick input from port 2, and mouse input on port 1 is required to get past the opening credits, therefore I have to test using mouse in port 1 and joystick in port 2, otherwise I would test with only the joystick in an effort to eliminate the possibility of conflicting configurations.

In the game it is possible to switch between using digital and analog joystick input. Using compatibility mode on the WinUAE input tab the joystick works in digital mode, although it is sensitive to the point of unusability.

Switching to Configuration #1 I've set the hat switch controls to <none> and mapped the X Axis, Y Axis and fire buttons to Joystick 2. In this configuration the joystick still works in digital mode but I find that adjusting the digital or analog joy-mouse speed has no effect on joystick sensitivity at all, I've tried values between 0-300. Adjusting the joystick dead zone does however have the expected effect.

Remapping the X Axis and Y Axis Input Sources to Joy 2 Horizontal (Analog) and Joy 2 Vertical (Analog) respectively and selecting to use the analog joystick in game results in a continual full scale deflection to the right in game (the plane yaws hard right while taxing and flips over to the right if you attempt to take off). Moving the joystick full left centers the input (the plane taxis straight). Again tweaking either joy-mouse speed has no effect.

I've tested with Birds Of Prey and the behaviour is identical except in this case the full scale deflection is to the left. I've also tried it with the mouse disabled just in case its input was overriding the joystick. I've searched through this forum to check whether anyone else already had the same problem but haven't found anything else like it.

I've tried everything I can think of and I'm stumped. Has anyone else had this problem or does anyone have any idea what else I might try? The rest of this post is the bootlog and log of a session using the analog configuration in Knights of the Sky.

Brilliant emulator though. I'm very impressed. Played a dozen games on it over the last few days without a single hitch apart from this joystick configuration, which is a bummer cos it's really the old flight sims I like.

WinUAEBootLog.txt:

WinUAE 1.5.3 (2008.11.09) (5.1 Service Pack 2 [2]) 32-bit 6.F0B 4
(c) 1995-2001 Bernd Schmidt   - Core UAE concept and implementation.
(c) 1998-2008 Toni Wilen      - Win32 port, core code updates.
(c) 1996-2001 Brian King      - Win32 port, Picasso96 RTG, and GUI.
(c) 1996-1999 Mathias Ortmann - Win32 port and bsdsocket support.
(c) 2000-2001 Bernd Meyer     - JIT engine.
(c) 2000-2005 Bernd Roesch    - MIDI input, many fixes.
Press F12 to show the Settings Dialog (GUI), Alt-F4 to quit.
End+F1 changes floppy 0, End+F2 changes floppy 1, etc.
EXE: 'C:\Program Files\WinUAE\', DATA: 'C:\Program Files\WinUAE\'
params:
CLOCKFREQ: QPF 2400.02MHz (9.38MHz, DIV=256)
Max hardware surface size: 8192x8192
DriverCaps: 94c27be3 606afe70 00000290 12ad54e1 00000000 00000000
DDCAPS_BLT, DDCAPS_BLTQUEUE, DDCAPS_BLTFOURCC, DDCAPS_BLTCOLORFILL, DDCAPS_BLTSTRETCH, DDCAPS_CANBLTSYSMEM, DDCAPS_COLORKEY, DDCAPS_OVERLAY, DDCAPS_3D,DDCAPS_READSCANLINE, DDCAPS2_CANRENDERWINDOWED, DDCAPS2_NOPAGELOCKREQUIRED, DDCAPS2_FLIPNOVSYNC, DDCAPS2_FLIPINTERVAL, DDCAPS2_NONLOCALVIDMEM, DDCAPS2_NONLOCALVIDMEMCAPS, DDCAPS2_WIDESURFACES, DDCKEYCAPS_SRCBLT
HELCaps   : f4c08241 00000001 00000200 0003fce3 00000000 00000347
DDCAPS_BLT, DDCAPS_BLTCOLORFILL, DDCAPS_BLTSTRETCH, DDCAPS_CANBLTSYSMEM, DDCAPS_CANCLIP, DDCAPS_CANCLIPSTRETCHED, DDCAPS_COLORKEY, DDCAPS_3D, DDCAPS_PALETTE, DDCAPS2_CERTIFIED, DDCKEYCAPS_SRCBLT
Enumerating display devices.. 
'Primary Display Driver' 'display' NULL
Sorting devices and modes..
Desktop: W=1680 H=1050 B=32. CXVS=1680 CYVS=1050
0: 640x480, 8-bit (60,75,70,72)
1: 640x480, 16-bit (60,70,72,75)
2: 640x480, 32-bit (60,70,72,75)
3: 720x480, 8-bit (60)
4: 720x480, 16-bit (60)
5: 720x480, 32-bit (60)
6: 720x576, 8-bit (60)
7: 720x576, 16-bit (60)
8: 720x576, 32-bit (60)
9: 800x600, 8-bit (60,70,72,75,56)
10: 800x600, 16-bit (60,70,72,75,56)
11: 800x600, 32-bit (60,70,72,75,56)
12: 848x480, 8-bit (60,70,72,75)
13: 848x480, 16-bit (60,70,72,75)
14: 848x480, 32-bit (60,70,72,75)
15: 960x600, 8-bit (60,70,72,75)
16: 960x600, 16-bit (60,70,72,75)
17: 960x600, 32-bit (60,70,72,75)
18: 1024x768, 8-bit (60,70,72,75)
19: 1024x768, 16-bit (60,70,72,75)
20: 1024x768, 32-bit (60,70,72,75)
21: 1152x864, 8-bit (60,70,72,75)
22: 1152x864, 16-bit (60,70,72,75)
23: 1152x864, 32-bit (60,70,72,75)
24: 1280x720, 8-bit (60,70,72,75)
25: 1280x720, 16-bit (60,70,72,75)
26: 1280x720, 32-bit (60,70,72,75)
27: 1280x768, 8-bit (60,70,72,75)
28: 1280x768, 16-bit (60,70,72,75)
29: 1280x768, 32-bit (60,70,72,75)
30: 1280x800, 8-bit (60,70,72,75)
31: 1280x800, 16-bit (60,70,72,75)
32: 1280x800, 32-bit (60,70,72,75)
33: 1280x960, 8-bit (60,70,72,75)
34: 1280x960, 16-bit (60,70,72,75)
35: 1280x960, 32-bit (60,70,72,75)
36: 1280x1024, 8-bit (60,70,72,75)
37: 1280x1024, 16-bit (60,70,72,75)
38: 1280x1024, 32-bit (60,70,72,75)
39: 1360x768, 8-bit (60,70,72,75)
40: 1360x768, 16-bit (60,70,72,75)
41: 1360x768, 32-bit (60,70,72,75)
42: 1440x900, 8-bit (60,70,72,75)
43: 1440x900, 16-bit (60,70,72,75)
44: 1440x900, 32-bit (60,70,72,75)
45: 1600x900, 8-bit (60,70,72,75)
46: 1600x900, 16-bit (60,70,72,75)
47: 1600x900, 32-bit (60,70,72,75)
48: 1680x1050, 8-bit (60,59)
49: 1680x1050, 16-bit (60,59)
50: 1680x1050, 32-bit (60,59)
'Primary Display Driver (1680*1050)', 51 display modes (enabled)
Display buffer mode = 1
Enumerating DirectSound devices..
Enumeration end
0:DS: Primary Sound Driver
1:DS: Realtek HD Audio output
Enumerating recording devices:
0:DS: Primary Sound Capture Driver
1:DS: Realtek HD Audio Input
2:DS: Realtek HD Digital input
done
CW: No Catweasel detected
PARAPORT: no ParaPort.dll, direct parallel port emulation disabled
IPC: Named Pipe '\\.\pipe\WinUAE' open
IPC: waiting for connections
Serial port enumeration..
SERPORT: 'Communications Port (COM1)' = 'COM1' = '\\?\acpi#pnp0501#1#{86e0d1e0-8089-11d0-9ce4-08003e301f73}'
Serial port enumeration end
DirectInput enumeration.. Keyboards..
I=6F1D2B61-D5A0-11CF-BFC7444553540000 P=6F1D2B61-D5A0-11CF-BFC7444553540000
'Keyboard' 'Keyboard' 00000413 [Keyboard]
DirectInput enumeration.. Pointing devices..
I=6F1D2B60-D5A0-11CF-BFC7444553540000 P=6F1D2B60-D5A0-11CF-BFC7444553540000
'Mouse' 'Mouse' 00000112 [Mouse]
DirectInput enumeration.. Game controllers..
I=E646D3D0-F90F-11DD-8001444553540000 P=046406A3-0000-0000-0000504944564944
'Saitek Cyborg USB Stick' 'Saitek Cyborg USB Stick' 00010214 [Game controller]
RawInput enumeration..
RAWINPUT: found 5 devices
00010047 mouse: '\??\HID#Vid_093a&Pid_2510#6&382880af&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}'
id=256 buttons=3 hw=0 rate=0
Windowsmouse initialization..
Catweasel joymouse initialization..
end
Saitek Cyborg USB Stick (PGUID=046406A3-0000-0000-0000504944564944):
00 000 'X Axis' (-99,0)
04 004 'Y Axis' (-98,0)
08 008 'Z Axis' (-97,0)
14 020 'Z Rotation' (-87,0)
20 032 'Hat Switch (1)' (-69,1)
20 032 'Hat Switch (2)' (-69,2)
Saitek Cyborg USB Stick (PGUID=046406A3-0000-0000-0000504944564944):
30 048 'Button 0' (48,-1)
31 049 'Button 1' (49,-1)
32 050 'Button 2' (50,-1)
33 051 'Button 3' (51,-1)
34 052 'Button 4' (52,-1)
35 053 'Button 5' (53,-1)
36 054 'Button 6' (54,-1)
37 055 'Button 7' (55,-1)
38 056 'Button 8' (56,-1)
39 057 'Button 9' (57,-1)
3A 058 'Button 10' (58,-1)
3B 059 'Button 11' (59,-1)
00 000 'X Axis [-]' (1000,-1)
00 000 'X Axis [+]' (1001,-1)
04 004 'Y Axis [-]' (1008,-1)
04 004 'Y Axis [+]' (1009,-1)
08 008 'Z Axis [-]' (1016,-1)
08 008 'Z Axis [+]' (1017,-1)
14 020 'Z Rotation [-]' (1040,-1)
14 020 'Z Rotation [+]' (1041,-1)
20 032 'Hat Switch (1) [-]' (1066,-1)
20 032 'Hat Switch (1) [+]' (1067,-1)
20 032 'Hat Switch (2) [-]' (1068,-1)
20 032 'Hat Switch (2) [+]' (1069,-1)
Mouse * (PGUID=6F1D2B60-D5A0-11CF-BFC7444553540000):
00 000 'X-axis' (-99,0)
04 004 'Y-axis' (-98,0)
08 008 'Wheel' (-97,0)
Mouse * (PGUID=6F1D2B60-D5A0-11CF-BFC7444553540000):
0C 012 'Button 0' (12,-1)
0D 013 'Button 1' (13,-1)
0E 014 'Button 2' (14,-1)
08 008 'Wheel [-]' (1016,-1)
08 008 'Wheel [+]' (1017,-1)
Keyboard * (PGUID=6F1D2B61-D5A0-11CF-BFC7444553540000):
01 001 'ESC' (0,-1)
02 002 '1' (0,-1)
03 003 '2' (0,-1)
04 004 '3' (0,-1)
05 005 '4' (0,-1)
06 006 '5' (0,-1)
07 007 '6' (0,-1)
08 008 '7' (0,-1)
09 009 '8' (0,-1)
0A 010 '9' (0,-1)
0B 011 '0' (0,-1)
0C 012 '-' (0,-1)
0D 013 '=' (0,-1)
0E 014 'BACKSPACE' (0,-1)
0F 015 'TAB' (0,-1)
10 016 'Q' (0,-1)
11 017 'W' (0,-1)
12 018 'E' (0,-1)
13 019 'R' (0,-1)
14 020 'T' (0,-1)
15 021 'Y' (0,-1)
16 022 'U' (0,-1)
17 023 'I' (0,-1)
18 024 'O' (0,-1)
19 025 'P' (0,-1)
1A 026 '[' (0,-1)
1B 027 ']' (0,-1)
1C 028 'ENTER' (0,-1)
1D 029 'CTRL' (0,-1)
1E 030 'A' (0,-1)
1F 031 'S' (0,-1)
20 032 'D' (0,-1)
21 033 'F' (0,-1)
22 034 'G' (0,-1)
23 035 'H' (0,-1)
24 036 'J' (0,-1)
25 037 'K' (0,-1)
26 038 'L' (0,-1)
27 039 ';' (0,-1)
28 040 ''' (0,-1)
29 041 '`' (0,-1)
2A 042 'SHIFT' (0,-1)
2B 043 '#' (0,-1)
2C 044 'Z' (0,-1)
2D 045 'X' (0,-1)
2E 046 'C' (0,-1)
2F 047 'V' (0,-1)
30 048 'B' (0,-1)
31 049 'N' (0,-1)
32 050 'M' (0,-1)
33 051 ',' (0,-1)
34 052 '.' (0,-1)
35 053 '/' (0,-1)
36 054 'RIGHT SHIFT' (0,-1)
37 055 '*' (0,-1)
38 056 'ALT' (0,-1)
39 057 'SPACE' (0,-1)
3A 058 'CAPSLOCK' (0,-1)
3B 059 'F1' (0,-1)
3C 060 'F2' (0,-1)
3D 061 'F3' (0,-1)
3E 062 'F4' (0,-1)
3F 063 'F5' (0,-1)
40 064 'F6' (0,-1)
41 065 'F7' (0,-1)
42 066 'F8' (0,-1)
43 067 'F9' (0,-1)
44 068 'F10' (0,-1)
45 069 'Num Lock' (0,-1)
46 070 'SCROLL LOCK' (0,-1)
47 071 'NUM 7' (0,-1)
48 072 'NUM 8' (0,-1)
49 073 'NUM 9' (0,-1)
4A 074 '-' (0,-1)
4B 075 'NUM 4' (0,-1)
4C 076 'NUM 5' (0,-1)
4D 077 'NUM 6' (0,-1)
4E 078 '+' (0,-1)
4F 079 'NUM 1' (0,-1)
50 080 'NUM 2' (0,-1)
51 081 'NUM 3' (0,-1)
52 082 'NUM 0' (0,-1)
53 083 'NUM DECIMAL' (0,-1)
56 086 '\' (0,-1)
57 087 'F11' (0,-1)
58 088 'F12' (0,-1)
90 144 'Prev Track' (0,-1)
99 153 'Next Track' (0,-1)
9C 156 'NUM ENTER' (0,-1)
9D 157 'Right Ctrl' (0,-1)
A0 160 'Mute' (0,-1)
A1 161 'Calculator' (0,-1)
A2 162 'Play/Pause' (0,-1)
A4 164 'Media Stop' (0,-1)
AE 174 'Volume -' (0,-1)
B0 176 'Volume +' (0,-1)
B2 178 'Web/Home' (0,-1)
B5 181 'NUM DIVIDE' (0,-1)
B7 183 'Prnt Scrn' (0,-1)
B8 184 'RIGHT ALT' (0,-1)
C5 197 'Pause' (0,-1)
C7 199 'HOME' (0,-1)
C8 200 'UP' (0,-1)
C9 201 'PGUP' (0,-1)
CB 203 'LEFT' (0,-1)
CD 205 'RIGHT' (0,-1)
CF 207 'END' (0,-1)
D0 208 'DOWN' (0,-1)
D1 209 'PGDOWN' (0,-1)
D2 210 'INSERT' (0,-1)
D3 211 'DELETE' (0,-1)
DB 219 'Left Windows' (0,-1)
DC 220 'Right Windows' (0,-1)
DD 221 'Application' (0,-1)
DE 222 'Power' (0,-1)
DF 223 'Sleep' (0,-1)
E3 227 'Wake' (0,-1)
E5 229 'Search' (0,-1)
E6 230 'Favorites' (0,-1)
E7 231 'Refresh' (0,-1)
E8 232 'Web Stop' (0,-1)
E9 233 'Forward' (0,-1)
EA 234 'Back' (0,-1)
EB 235 'My Computer' (0,-1)
EC 236 'Mail' (0,-1)
ED 237 'Media' (0,-1)
Max Z3FastRAM 1536M. Total physical RAM 3582M
GetWriteWatch() test ok
load config '.\Configurations\default.uae':0
load failed
failed to load config '.\Configurations\default.uae'
LCD: Logitech LCD system not detected
Entering GUI idle loop
load config '.\Configurations\A500.uae':0
*: C:\Program Files\WinUAE\Amiga Kickstart Roms - Complete - TOSEC v0.04\KS-ROMs\Kickstart v1.3 rev 34.5 (1987)(Commodore)(A500-A1000-A2000-CDTV).rom:262144 = KS ROM v1.3 (A500,A1000,A2000) rev 34.5 (256k) [315093-02]
CRC32=C4F0F55F SHA1=891E9A547772FE0C6C19B610BAF8BC4EA7FCB785
Log (enabled): 'C:\Program Files\WinUAE\winuaelog.txt'

WinUAELog.txt:

2009-03-10 15:25:58
58-703: WinUAE 1.5.3 (2008.11.09) (5.1 Service Pack 2 [2]) 32-bit 6.F0B 4
(c) 1995-2001 Bernd Schmidt   - Core UAE concept and implementation.
(c) 1998-2008 Toni Wilen      - Win32 port, core code updates.
(c) 1996-2001 Brian King      - Win32 port, Picasso96 RTG, and GUI.
(c) 1996-1999 Mathias Ortmann - Win32 port and bsdsocket support.
(c) 2000-2001 Bernd Meyer     - JIT engine.
(c) 2000-2005 Bernd Roesch    - MIDI input, many fixes.
Press F12 to show the Settings Dialog (GUI), Alt-F4 to quit.
End+F1 changes floppy 0, End+F2 changes floppy 1, etc.
58-703: EXE: 'C:\Program Files\WinUAE\', DATA: 'C:\Program Files\WinUAE\'
58-703: NATMEM: Our special area: 0x04950000-0x05950000 (01000000 16M)
58-703: shmget of size 65536 (64k) for rtarea
58-703: VirtualAlloc 00F00000 - 00F10000 10000 (64k) ok
58-703: uaegfx.card magic code: 00F00FA0-00F010DE ABI=00000000
58-703: shmget of size 65536 (64k) for filesys
58-703: shmget of size 524288 (512k) for kick
58-703: VirtualAlloc 00F80000 - 01000020 80020 (512k) ok
58-703: Entered action_replay_load ()
58-703: shmget of size 1048576 (1024k) for chip
58-703: VirtualAlloc 00000000 - 00100020 100020 (1024k) ok
58-703: shmget of size 1048576 (1024k) for bogo
58-703: VirtualAlloc 00C00000 - 00D00020 100020 (1024k) ok
58-718: No disk in drive 0.
58-718: Building CPU table for configuration: 68000 prefetch 24-bit
58-734: 1885 CPU functions
58-734: Building CPU, 44316 opcodes (0 1 1)
58-734: CPU=68000, FPU=0, JIT=0.
58-734: CPUID level=10, Family=6, Model=15, Mask=11, Vendor=GenuineIntel [0]
58-734: JIT: Setting signal handler
58-734: JIT: Building Compiler function table
58-734: JIT: Supposedly 42101 compileable opcodes!
58-734: DirectDraw GUID=NULL
58-734: W=1680 H=1050 B=32 CT=9
58-750: winuae_active(0)
58-781: Created 720x568x32 (0018A8A0) surface in DefaultRAM (1)
58-796: Created 48x48x32 (0018A710) surface in DefaultRAM (1) hardware colorkey
58-796: Created 48x48x32 (00176938) surface in DefaultRAM (1)
58-796: DDRAW: primary surface 0018A6C0, secondary 0018A8A0 (720x568x32)
58-796: set_ddraw: 720x568@32-bytes
58-796: Reset at 00000000
58-796: 00000000    2048K/4 =     512K Chip memory
58-796: 00200000    8192K/0 =    8192K <none>
58-796: 00A00000    2048K/0 =    2048K CIA
58-796: 00C00000    1024K/1 =    1024K Slow memory
58-796: 00D00000     512K/0 =     512K Custom chipset
58-796: 00D80000     256K/0 =     256K <none>
58-796: 00DC0000      64K/0 =      64K Battery backed up clock (none)
58-796: 00DD0000      64K/0 =      64K <none>
58-796: 00DE0000     128K/0 =     128K Custom chipset
58-796: 00E00000     512K/2 =     256K Kickstart ROM (C4F0F55F)
58-796: =KS ROM v1.3 (A500,A1000,A2000) rev 34.5 (256k) [315093-02]
58-796: 00E80000      64K/0 =      64K Autoconfig
58-796: 00E90000     960K/0 =     960K <none>
58-796: 00F80000     512K/2 =     256K Kickstart ROM (C4F0F55F)
58-796: =KS ROM v1.3 (A500,A1000,A2000) rev 34.5 (256k) [315093-02]
58-812: BEAMCON0 0000 -> 0020
58-812: PAL mode, V=50Hz H=15600Hz (227x312)
58-812: hardreset, memory cleared
58-828: SOUND: 00140004 1:00000000 2:00000000 4:00000033 4:00000603 4:00000107 6:0000003F 6:0000060F 
58-828: SOUND: 00000000,CH=2,FREQ=44100 'Realtek HD Audio output' buffer 16384 (65536), dist 4096
58-875: SOUND: 879 = (882 - 3)
58-875: SOUND: bs=128 w=10240 max=16384 tof=21845 tuf=29127
2009-03-10 15:26:00
00-421 [78 066x213]: Illegal instruction: 4e7b at 00FC0564 -> 00FC0582
00-421 [78 052x270]: SERIAL: period=372, baud=9600, hsyncs=16, bits=8, PC=fc2234
2009-03-10 15:26:01
01-500 [132 000x000]: PAL mode, V=57Hz H=15561Hz (227x273)
01-515 [133 000x000]: PAL mode, V=50Hz H=15600Hz (227x312)
2009-03-10 15:26:05
05-421 [325 000x000]: winuae_inactive(0)
2009-03-10 15:26:09
09-296 [325 000x000]: winuae_active(0)
09-296: SOUND: 0 = (1323 - 1323)
09-296: SOUND: bs=128 w=10240 max=16384 tof=21845 tuf=29127
2009-03-10 15:26:20
20-109 [537 172x001]: Byte put to custom register DFF0A9 PC=00C1C516
20-109 [537 030x003]: Byte put to custom register DFF0A9 PC=00C1CD20
20-109 [537 059x006]: Byte put to custom register DFF0D9 PC=00C1C516
20-109 [537 144x007]: Byte put to custom register DFF0D9 PC=00C1CD20
20-250 [544 108x002]: Byte put to custom register DFF0B9 PC=00C1C516
20-250 [544 193x003]: Byte put to custom register DFF0B9 PC=00C1CD20
20-250 [544 223x004]: Byte put to custom register DFF0C9 PC=00C1C4F2
20-390 [551 071x003]: Byte put to custom register DFF0C9 PC=00C1C4F2
20-390 [551 171x004]: Byte put to custom register DFF0C9 PC=00C1CD20
20-531 [558 077x003]: Byte put to custom register DFF0C9 PC=00C1C4F2
2009-03-10 15:27:13
13-109 [3178 000x000]: winuae_inactive(0)
2009-03-10 15:27:15
15-093 [3178 000x000]: winuae_active(0)
15-109: SOUND: 0 = (882 - 882)
15-109: SOUND: bs=128 w=10240 max=16384 tof=21845 tuf=29127
2009-03-10 15:28:58
58-437 [5148 000x165]: KB: reset warning triggered
58-437 [5148 000x165]: KB: sent reset warning code (phase=1)
58-437 [5148 000x167]: KB: reset warning second phase..
58-437 [5148 000x167]: KB: sent reset warning code (phase=2)
58-437 [5148 000x168]: KB: reset warning SP = output
58-437 [5148 000x170]: KB: reset warning end by software. reset.
58-468 [5149 000x000]: Reset at 00C4CD12
58-468 [5149 000x000]: 00000000    2048K/4 =     512K Chip memory
58-468 [5149 000x000]: 00200000    8192K/0 =    8192K <none>
58-468 [5149 000x000]: 00A00000    2048K/0 =    2048K CIA
58-468 [5149 000x000]: 00C00000    1024K/1 =    1024K Slow memory
58-468 [5149 000x000]: 00D00000     512K/0 =     512K Custom chipset
58-468 [5149 000x000]: 00D80000     256K/0 =     256K <none>
58-468 [5149 000x000]: 00DC0000      64K/0 =      64K Battery backed up clock (RF5C01A)
58-468 [5149 000x000]: 00DD0000      64K/0 =      64K <none>
58-468 [5149 000x000]: 00DE0000     128K/0 =     128K Custom chipset
58-468 [5149 000x000]: 00E00000     512K/2 =     256K Kickstart ROM (C4F0F55F)
58-468 [5149 000x000]: =KS ROM v1.3 (A500,A1000,A2000) rev 34.5 (256k) [315093-02]
58-468 [5149 000x000]: 00E80000      64K/0 =      64K Autoconfig
58-468 [5149 000x000]: 00E90000     960K/0 =     960K <none>
58-468 [5149 000x000]: 00F80000     512K/2 =     256K Kickstart ROM (C4F0F55F)
58-468 [5149 000x000]: =KS ROM v1.3 (A500,A1000,A2000) rev 34.5 (256k) [315093-02]
58-468 [5149 000x000]: PAL mode, V=50Hz H=15600Hz (227x312)
58-703 [5160 110x298]: Illegal instruction: 4e7b at 00FC0564 -> 00FC0582
2009-03-10 15:28:59
59-781 [5214 000x000]: PAL mode, V=57Hz H=15561Hz (227x273)
59-812 [5215 000x000]: PAL mode, V=50Hz H=15600Hz (227x312)
2009-03-10 15:29:03
03-031 [5375 000x000]: winuae_inactive(0)
2009-03-10 15:29:11
11-062 [5375 000x000]: winuae_active(0)
11-078: SOUND: 0 = (1323 - 1323)
11-078: SOUND: bs=128 w=10240 max=16384 tof=21845 tuf=29127
11-109: winuae_inactive(0)
11-109: SOUND: DirectSound driver freed

[Toni Wilen]

There is no analog joystick calibration screen in neither game?

Neither of these games has built in calibration facilities. I didn't think there were many Amiga games that did have built in joystick calibration support and most of the early analog sticks used hardware calibration, (ie physical sliders on the joystick which you used to trim it).

I wouldn't have thought in game calibration was necessary as looking at the logs WinUAE appears to be capturing the joystick input from DirectInput in which case the Windows calibration should be in effect, unless perhaps WinUAE is using raw input from the device instead.

Is there some way to enable trace logging for the input subsystem?

[Toni Wilen]

Originally Posted by Neutrino

Neither of these games has built in calibration facilities. I didn't think there were many Amiga games that did have built in joystick calibration support and most of the early analog sticks used hardware calibration, (ie physical sliders on the joystick which you used to trim it).

I wouldn't have thought in game calibration was necessary as looking at the logs WinUAE appears to be capturing the joystick input from DirectInput in which case the Windows calibration should be in effect, unless perhaps WinUAE is using raw input from the device instead.

Of course calibration (even in emulation) is needed because different games expect different range and zero position.. (if they don't have calibration screens)

You can experiment with input.analog_joystick_multiplier configuration entry(not available in GUI, edit config file manually)

input.analog_joystick_multiplier set to 20 (can try up to 50) apparently works better, at least with some games.

Is there some way to enable trace logging for the input subsystem?

Won't help in this case.

I have the joystick axes configured pretty well now, the value of 20 you provided worked well, thanks very much. I'm still not in a happy place though because I've discovered a few other problems.

Mapping the input target 'Joy 2 Fire/Mouse2 Left Button (0x00)' to any joystick button does not work (ie the fire button does not fire) if the X and Y joystick axes are mapped to their respective analog inputs, whereas it does fire if the X and Y axes are mapped to the non-analog inputs.

Mapping the input target 'Joy2 2nd Button/Mouse2 Right Button (0x01)' to any joystick button kills the Y axis and causes the plane to dive uncontrollably at the ground. This was the main cause of my earlier problems, it was only after leaving this unassigned that changing the analog_joystick_multiplier was of benefit.

That's in Knights Of The Sky, but I'm seeing the same problem with the fire button not working with an analog joystick in Red Baron too, and in both cases switching to the WinUAE gui mid flight and switching the joystick axes mapping to non-analog causes the fire button to start working straightaway.

I've tried that with an A500 and A4000 configuration with both games. If someone else has these games and can either reproduce my issues and/or discover a working configuration that would be appreciated, but for now I can't think of anything else to do.

After getting the axes working I also tested it in Birds Of Prey and there the axes and fire buttons all work perfectly so I know it isn't a joystick problem, plus I use this joystick for PC games all the time.

[Toni Wilen]

Originally Posted by Neutrino

I have the joystick axes configured pretty well now, the value of 20 you provided worked well, thanks very much. I'm still not in a happy place though because I've discovered a few other problems.

I guess 20 will be good default in future versions. Thanks for testing.

ADDED: could you do some more testing? Try for example 15 and 25. If 15 works better than 25, decrease 20 (increase if 25 was "better") by one or two and try again (14 and 24 if new multiplier is 19) and so on until you find value that is exactly middle. (both -5 and +5 values work equally but opposite)

Mapping the input target 'Joy 2 Fire/Mouse2 Left Button (0x00)' to any joystick button does not work (ie the fire button does not fire) if the X and Y joystick axes are mapped to their respective analog inputs, whereas it does fire if the X and Y axes are mapped to the non-analog inputs.

Mapping the input target 'Joy2 2nd Button/Mouse2 Right Button (0x01)' to any joystick button kills the Y axis and causes the plane to dive uncontrollably at the ground. This was the main cause of my earlier problems, it was only after leaving this unassigned that changing the analog_joystick_multiplier was of benefit.

It works as designed

Analog joystick buttons are used for analog direction!
Analog joystick buttons are connected to digital joystick left and right directions..

(someday there will be separate digital and analog joystick select box in winuae joystick panel)

I've done the testing you requested and discovered that coming lower than 20 the joysticks responsiveness improves even more. I tested using Knights Of The Sky by loading a training mission and then timing how long it takes to taxi in a complete a 360 degree turn in either direction at a fixed speed measured against a point on the horizon.

joystick_multiplier        Left Turn        Right Turn
13                            17s                >60s
14                            17s                29s
15                            24s                15s
16                            34s                13s
17                            34s                11s

As you can see I hit the sweet spot at 15 but with the joystick still more responsive to the right. So then I left the analog_joystick_multiplier set to 15 and played with the offset value, -1 turned out to be fine.

joystick_offset            Left Turn        Right Turn
-1                            18s                15s
-2                            14s                21s
-3                            11s                42s
-5                            10s                >60s

So the joystick is now perfectly calibrated.

I thought about what you said here:

Originally Posted by Toni Wilen

Analog joystick buttons are used for analog direction!
Analog joystick buttons are connected to digital joystick left and right directions..

So I connected input source 'Button 0' to 'Joy2 Left (0x01) and input source 'Button 1' to 'Joy2 Right (0x02)' and now the fire buttons work too. So I'm all sorted for Knights Of The Sky

With the joystick set up like this I retested Birds Of Prey. It doesn't recognise the fire button connected to the X axis like this. It's no trouble to make a separate config for each game but I assume both games would work on a real Amiga with an analog stick and neither game has a joystick config panel. So I suspect that the technique used by WinUAE to interface analog joysticks doesn't quite match up to the way some programs expect it to work. I'm just guessing though.

At any rate I'm happy and thanks for all your help, I've learned more about joysticks that I ever thought I would.

[Toni Wilen]

Nearly forgot to update default values in next WinUAE version.. Will be in next beta

Also it includes Gameports-panel analog joystick setup, no need to use input panel anymore (and more..)