PCEngineFans.com - The PC Engine and TurboGrafx-16 Community Forum
NEC PC-Engine/SuperGrafx => PC Engine/SuperGrafx Discussion => Topic started by: wolfman on May 15, 2014, 06:55:14 AM
-
Has anybody ever tried modding a mouse to use it instead of a controller? Since there are so few games for mouse available I thought it might be cool to have it for some adventures at least...
-
Be nice for Loom.
-
Has anybody ever tried modding a mouse to use it instead of a controller? Since there are so few games for mouse available I thought it might be cool to have it for some adventures at least...
Not sure what you mean here... the PCE mouse uses an entirely different way of communicating what it's doing than a controller.... and that protocol involves some deliberate delays when reading the controller port.
Do you mean something along the lines of taking any mouse, getting some way of identifying whether movement is up/down/let/right, and encoding that signal into the PCE in the same format as a HuPad would ? That would be interesting, but I'm not sure how one would identify movement so easily (or set sensitivity).
-
It would be cool to have something like the XNA wrapper does: have something to tell where's the XY position of the mouse relative to the position from the previous read. Then translate it to controller inputs somehow.
-
Interesting technical project for someone perhaps, but too few games where it'd be useful I think to seriously justify doing it.
-
Not worth the chore, and the movements/mouse control wouldn't be what you expect.
-
I'd be more interested in seeing it done for click games, like Loom, Dungeon Master, ect..
-
Do you mean something along the lines of taking any mouse, getting some way of identifying whether movement is up/down/let/right, and encoding that signal into the PCE in the same format as a HuPad would ? That would be interesting, but I'm not sure how one would identify movement so easily (or set sensitivity).
I am not thinking of any mouse, but of a PCE mouse. I thought it might be possible connecting the pad electronics to the h/v IR sensors and click buttons...no? Like throwing away mouse electronics and replacing it with a pad circuit?
Since the two wheels inside a mouse are basically nothing else than temporary switches (signal/no signal) shouldn´t it be like tapping the direction button(s) very fast, depending on the movement speed of the mouse itself?
Not possible? Stupid idea? Too complicated?