Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • linuxmce linuxmce
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 255
    • Issues 255
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • linuxmce
  • linuxmcelinuxmce
  • Issues
  • #2066

Closed
Open
Created Feb 12, 2014 by Thom Cherryhomes@tschak909Maintainer

Implement Controller Types for Game Player

Certain game systems need a concept of different controller types, especially because different configuration files may be needed to properly implement them.

e.g.

If an Atari 2600 game is selected that requires paddles, then:

(1) MESS's configuration should be altered to turn on paddles (2) depending on which joysticks are attached and active, alter the configuration files for the emulator, so that they come up in an optimal stage (for example: real Atari Paddle controllers attached via the 2600-daptor II need joystick dead zone set to 0.0, and joystick saturation set to 1.0, in order to work properly without any dead spots.

Assignee
Assign to
Time tracking