1351 mode glitches

[TomCat666]

Hi Using latest version on c64 with 1351 mode turned on and using any multiplier I get occasional glitches in both directions. For 1 frame the mouse (or bat in arkanoid) would jump (delta would get some odd value) then in next frame it would jump back to the previous position (delta would get the negative same value). I tried with 3 monsters and it is the same.

[willyvmm]

I will lok into later. New driver for analogue mouse is on its way.

[willyvmm]

Please try the latest firmware: https://github.com/willyvmm/mouSTer/releases/tag/3.17.3377

[ziggystar12]

Testing now.

[ziggystar12]

Works peppy on Eye of the beholder.

Is the Amiga wheel option still retained in this version meaning both are supported with this firmware?

[ziggystar12]

Does not actually work correctly on GEOS, after further testing it appears it is moving to fast for GEOS. I thought it moved pretty quickly on Beholder and thought, this was nice! However, it makes the mouse jump all around the screen on GEOS unfortunately. So I think you just need to make the sensitivity a little less.

[radius75]

It may be related in part to #1 [3.17.3377] Also works fine in EoTB for me, but in Geos the pointer jumps chaotically across the screen.

Such a small summary of my tests: Joyride1.5 (tester for joy and mouse); 3.17.3377 OK, 3.16.2600 OK Joyport1&2 EoTB 3.17.3377 OK, 3.16.2600 OK Joyport2 Supremacy 3.17.3377 NOK, 3.16.2600 OK Joyport1 Cabal 3.17.3377 NOK, 3.16.2600 NOK Joyport2 Geos 3.17.3377 NOK, 3.16.2600 OK Joyport1

[ziggystar12]

Could be - but I noticed the mouse is a much faster on EOB then it was before. Even without Acel option.

[ziggystar12]

Also, firmware 2019 C1351 worked great in both EOB and GEOS

[willyvmm]

Try this Firmware: https://we.tl/t-NqNx1OknEs mouse is now slowed down. Also, the parameter in config (microstep=02) may be adjusted.

[ziggystar12]

This unfortunately seems to be worse for GEOS. Even with no dongle/mouse connected, the mouse jumps around the screen randomly. Also the build number appears to be the same 3377 so I'm not 100% sure it is the new firmware?

[TomCat666]

Hello. Thank you for this update! I have tested it now on my Ultimate64 and everything works: Joyride, EoTB, Supremacy (Excess), Geos (1.2, TopDesk, Wheels), Krakout 1351, Deja Vu (n0stalgia) all work fine. I had to slow it down a bit with microstep=03 otherwise it was jumping too much in some games - the overflow problem. Seems microstep 03 is good for me in the amiga mode too.

GREAT work ! :) Both cd32 and 1351 mouse working as they should.

[ziggystar12]

Hello. Thank you for this update! I have tested it now on my Ultimate64 and everything works: Joyride, EoTB, Supremacy (Excess), Geos (1.2, TopDesk, Wheels), Krakout 1351, Deja Vu (n0stalgia) all work fine. I had to slow it down a bit with microstep=03 otherwise it was jumping too much in some games - the overflow problem. Seems microstep 03 is good for me in the amiga mode too.

GREAT work ! :) Both cd32 and 1351 mouse working as they should.

What happens if you remove the usb mouse dongle on GEOS? Can you try GEOS 2.0? Also, here is a mouse driver to enable either port. https://commodore.software/downloads/download/662-geos-input-device-drivers/15900-port-2-drivers-v1-1-geos

[TomCat666]

What happens if you remove the usb mouse dongle on GEOS? Can you try GEOS 2.0? Also, here is a mouse driver to enable either port. https://commodore.software/downloads/download/662-geos-input-device-drivers/15900-port-2-drivers-v1-1-geos

I rather not remove anything from the control ports while my U64 is powered up. I did remove the usb mouse from mouster and nothing happend - mouse pointer stayed on the same position. I couldn't get these port 2 drivers to work (for some reason they don't even show up in the folder or input selector), but built-in 1351 and 1351(a) driver of 2.0 (d81) works fine with mouster latest fw...

[Jumpman64]

The actual MouSTer fw 3.17.3377 seems to run silky smooth. Tested so far: original 1351 driver, Arkanoid 2, GEOS (all port 1) and EotB (port 2) on Ultimate 64 with a wireless SilverCrest mouse (in 1000 dpi mode) and ,ini settings: mode=mouse type=c1351 microstep=8

[willyvmm]

The C1351 engine got merged all the best from 2600 build and the "new engine". Please try the latest build: https://github.com/willyvmm/mouSTer/releases/tag/3.17.3455

[ziggystar12]

So far so good on 1351!

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: willyvmm @.> Sent: Monday, February 6, 2023 2:28:56 PM To: willyvmm/mouSTer @.> Cc: ziggystar12 @.>; Comment @.> Subject: Re: [willyvmm/mouSTer] 1351 mode glitches (Issue #17)

The C1351 engine got merged all the best from 2600 build and the "new engine". Please try the latest build: https://github.com/willyvmm/mouSTer/releases/tag/3.17.3455

— Reply to this email directly, view it on GitHubhttps://github.com/willyvmm/mouSTer/issues/17#issuecomment-1419871611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF7ZZDH7I57GRBSIWIKIJRLWWF3KRANCNFSM5S3K3KZA. You are receiving this because you commented.Message ID: @.***>

[Retro-Nerd]

Yep, the C1351 works fine now. Tested all functions, via Joyride tool. Good job!

[vandabbin]

working great for me with most mice but when I use the a500mini themouse it will occasionaly freeze the pointer in place while the mouse is still moving in a direction and requires me to either lift the mouse up and put it down to get it to work again.

the mouse works fine with every other device i've used it on

[willyvmm]

@vandabbin Seems like it's not related to the mouSTer - rather to the connected device. A problem with the mouse has been reported to me before and exists only with "the mouse". I'm almost sure that the cause of the problem is the not fully compliant implementation of the USB STACK in the device. I know I push the USB HID interface to the limits (but not over the limits) to minimize latency. And this is the only device I know that is causing problems.

[JanNadziejowski]

Hello, The situation is like this. I uploaded FW 3.17.3475004. I checked the config, FW version and type (amigamm). I launched WB3.1 on RTG on Pistorm 030. Of course FreeWheel and micromys fired. Unfortunately, the roller does not work. I turned off the mouster, plugged it in again and downloaded the config. The config is 3.8.1743 FW. What can be played?

[vandabbin]

Ah I see, thanks for the info. Glad it's not the mouster then, too bad about 'the mouse' not working though it matches so nicely haha!

[willyvmm]

@JanNadziejowski That's the point. The update process is too complicated and too restricted. Remove everything from the mouSTer folder, and put the Firmware Only.

Btw. Wrong thread.

[JanNadziejowski]

Ok. Willy, sorry. I'll try again and post in the right thread haha :P

[willyvmm]

Confirmed: https://github.com/willyvmm/mouSTer/issues/17#issuecomment-1421334659