Main > Main Forum

Train simulator controller project

Pages: << < (2/3) > >>

shinyknight:

Wow, that's interesting....never imagined to see that technique applied to a controller other than a mouse :)

The issue thou, is that you still need to assign it....if it is not seen as button press signal (which is done by the mapping software on the USB chip on the device, the one that does translation of the actions into HID codes), the program will simply ignore it. That's a great solution if I could assign the mouse to either axis of the train (acc or brake), but it accept only keyboard input sadly.

The KAde looks really interesting; the HW is not different from an Arduino (uses the same Atmel Mega chip), but the software seems able to map anything natively, independently from the application that runs below...maybe it could fool the simulator to believe that the analog input received by the pots is in fact a key press; with a specific repeat and delay rate....gotta check into this a bit more.

Giving a try now to joy2key :) And yes....I would love to put my hands on one of those thruster controls :P I was even looking at abandoned factories, to grab those handles from discarded electric panels :)

PL1:


--- Quote from: shinyknight on February 23, 2014, 08:17:09 pm ---The issue thou, is that you still need to assign it....if it is not seen as button press signal (which is done by the mapping software on the USB chip on the device, the one that does translation of the actions into HID codes), the program will simply ignore it. That's a great solution if I could assign the mouse to either axis of the train (acc or brake), but it accept only keyboard input sadly.

--- End quote ---
Sorry, wasn't clear on this earlier.

I think Jon might be able to modify the KADE firmware so that it would output one keystroke per optical transition instead of moving the mouse cursor one pixel.

What say you, Jon?  Is it theoretically possible?


--- Quote from: shinyknight on February 23, 2014, 08:17:09 pm ---I would love to put my hands on one of those thruster controls :P I was even looking at abandoned factories, to grab those handles from discarded electric panels :)

--- End quote ---
Dezbaz fabbed that controller from scratch as documented in his outstanding Converting Asteroids to Lunar Lander thread on KLOV.   :notworthy:


Scott

sharpfork:


--- Quote ---modify the KADE firmware so that it would output one keystroke per optical transition instead of moving the mouse cursor one pixel
--- End quote ---

I bet $25 Degenatrons could do that in his sleep.

degenatrons:


--- Quote from: PL1 on February 23, 2014, 10:45:45 pm ---
--- Quote from: shinyknight on February 23, 2014, 08:17:09 pm ---The issue thou, is that you still need to assign it....if it is not seen as button press signal (which is done by the mapping software on the USB chip on the device, the one that does translation of the actions into HID codes), the program will simply ignore it. That's a great solution if I could assign the mouse to either axis of the train (acc or brake), but it accept only keyboard input sadly.

--- End quote ---
Sorry, wasn't clear on this earlier.

I think Jon might be able to modify the KADE firmware so that it would output one keystroke per optical transition instead of moving the mouse cursor one pixel.

What say you, Jon?  Is it theoretically possible?


--- Quote from: shinyknight on February 23, 2014, 08:17:09 pm ---I would love to put my hands on one of those thruster controls :P I was even looking at abandoned factories, to grab those handles from discarded electric panels :)

--- End quote ---
Dezbaz fabbed that controller from scratch as documented in his outstanding Converting Asteroids to Lunar Lander thread on KLOV.   :notworthy:


Scott

--- End quote ---

Hey Scott,  sure it's possible.  I've done this already with analog signals for a composite version of KADE which we're calling KADE multiHID (supports simultaneous emulation of keyboard+mouse+joystick).
Looking at the optical encoding part now, to bring in native support for Trackballs and Spinners.   Could also read in PS/2 from legacy devices if that would be useful.
Will post more info when I make progress.

Jon


PL1:

Thanks for the confirmation, Jon.

I'm guessing that for his application, he'd want gears, an encoder wheel and an Atari steering optic PCB, but I'm just spitballing on those parts.

Are you interested in this approach, Shinyknight?


Scott

Pages: << < (2/3) > >>

Go to full version