| Main > Lightguns |
| MAME direct input & GlovePIE |
| (1/2) > >> |
| zatarra76:
Hello! This is my first topic, please be kind :notworthy: I'm using a Wiimote as a lightgun and with GlovePIE I wrote a script to map all buttons as keyboard keys and IR pointer as mouse. (About this, I don't know why all people keep using in their scripts PPJoy to do that, Windows 10 must be always in test mode and calibrating is so difficult...) However, my script works perfectly with an old NONAG - DIRECT INPUT version of MAME 0.174 but fails to work on a new version like MAMEARCADE64 0.224. In the new version I modified the ini file of the game with: keyboard provider dinput mouse provider dinput The first one works (Wiimote buttons are correctly translated into keyboard keys and MAME maps them). The second doesn't work (I can see the GlovePIE script is working because I see the mouse pointer/arrow moving, but the crosshair cursor is not following it). The crosshair only follow the mouse if I use the real mouse, with the Wiimote only the arrow moves (I'm not an expert but it seems like MAME is not detecting the mouse direct input). Is there a way to force direct input to new versions of MAME? I read somewhere that with old versions there was some tool to make a personal build of MAME forcing NO NAG and Direct input, I'm wondering if there is something similar for new versions. I believed that new versions don't need this hack but maybe I'm wrong. In the worst case I will set my Hyperspin to launch only shooting games with an old MAME build, but I wish I could do everything with the same emulator/version. Just to give you all information, the Wiimote is connected to the PC with a Dolphin bar in mode 4. Thanks in advance for your help! :) |
| Howard_Casto:
You can't simulate the cursor within mame.... simulate a joystick instead |
| zatarra76:
Thanks for the reply. I don't want to contradict you, but not only it is possible, I've already done it in an old Direct Input forced build of MAME (MAMEUIFX64 NoNag Direct input 0.174), I'm only asking if I can do it also in a newer version. To simulate a joystick as you suggest I have to use PPJoy and to use it Windows 10 must be always in test mode. Over than that I tried many scripts I found on the internet that uses joystick simulation and no one seems to be line of sight accurate, if I want something so imprecise I can use the Dolphin bar in mode 2 and software like Touchmote (I already tried it and the result is quite a mess). With the script I wrote using some basic math and the cursor coordinates I can hit the small leaf falling in Point Blank 8) An alternative solution could be working with Mouse.DirectInput, but translating from simple coordinates to increasing/decreasing mikeys will be kind of tricky. |
| Foxhole:
Try changing lightgun provider instead of mouse, to either dinput or win32. |
| zatarra76:
I have never tried win32 as a value for providers :dunno I think I should try it for mouse provider first and then with lightgun if it doesn't work. In the meanwhile I was searching on the internet a simple way to convert pixels to mouse mickeys, but it's not that simple :banghead: I hope I will find a solution using cursor 8) |
| Navigation |
| Message Index |
| Next page |