Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CX22 Resolution too high #70

Closed
thrust26 opened this issue Jan 11, 2017 · 6 comments
Closed

CX22 Resolution too high #70

thrust26 opened this issue Jan 11, 2017 · 6 comments
Assignees

Comments

@thrust26
Copy link
Member

@sa666666: Not specific to the new core.

The (unmodded) CX22/CX80 Trak-Ball delivers only half the resolution of e.g. an Atari or Amiga Mouse, a modded CX22/CX80 or other Trak-Balls modded for Atari Mouse mode.

http://atariage.com/forums/topic/243453-atari-2600-trak-ball-games/page-20#entry3668812
https://atariage.com/forums/topic/243453-atari-2600-trak-ball-games/page-20#entry3669256

BTW: There is no hyphen in CX22 or CX80. Also we should rename the controller option CX-22 Trakball into eg. CX22/CX80 Trakball and CX-80 Mouse into Atari Mouse or AtariMouse (like AmigaMouse). The current naming causes constant confusion. It results from an old wrong assumption that CX80 work like an Atari Mouse.

@sa666666
Copy link
Member

This will probably have to wait until after the 5.0 release, but it's good to have it recorded here.

sa666666 added a commit that referenced this issue Feb 12, 2017
own class, preparing for further work on issue #70.

The 3 classes are now named more appropriately, as mentioned in
issue #70.
@sa666666 sa666666 self-assigned this Feb 12, 2017
@sa666666
Copy link
Member

I think this is now fixed by 52d3bd9 and 5114a8e. More testing is required, but for now it seems to work with the ROMs from the above links.

@thrust26
Copy link
Member Author

Great!

When will there be a next pre-release?

@sa666666
Copy link
Member

@DirtyHairy mentioned wanting to get the automated testing done before we do pre5. So I await his answer.

@DirtyHairy
Copy link
Member

DirtyHairy commented Feb 26, 2017

@sa666666 I was indeed planning to do that before pre5, and I also wanted to do #93 before as I strongly suspect that this will fix #83 . However, my pace has slowed slighgly since new year, and this is unlikely change in the foreseeable future (we are currently planning a house 😏), so those two features could still be a few weeks away, and I see no harm whatsoever in releasing pre5 without them.

I'd just like to avoid people going through the effort of regression testing the whole VCS catalog against the next release as automated regression testing will catch most potential issues anyway 😄

@sa666666
Copy link
Member

In that case I will do a test release tomorrow after work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants