richard-broadhurst


The idea is to have the mouse position in the window / "screen" scaled 0..&FFFF be the values returned by the first two A2D channels with the two mouse buttons...

A further option may be to support AMX style mice, but this is tricky, as the input is basically X+=1, X-=1, Y+=1 or Y-=1 which is OK if the mouse...

If possible, two joystick support would be good, but even if only one is possible, supporting both fire buttons would be good.

Looks like browsers now have good joystick support https://gamepad-tester.com/ although it looks like it might only be xinput drivers on windows.

I was wondering if anyone had been working on this and if there this would be supportable on "interface = shugart", possibly with an FF.CFG option or would the jumper...

I have this locally and would suggest that you add the option to the write breakpoint to only break when the value changes.

Does XInput still only support the 360 controller, if so, maybe DirectInput might be better as it supports all joysticks inc the 360 (apart from mapping the triggers together) AFAIK,...

Thanks for the update - I did say it had been a long time. I have just checked and my 360 controller is using the default driver and the analogue...

I've added an if (m_DD2) to the else in BeebWin::UpdateSmoothingwhich seems to have solved the immediate issue. void BeebWin::UpdateSmoothing(void) { DDSURFACEDESC ddsd; HRESULT ddrval; if (m_DisplayRenderer == IDM_DISPDX9) { if...