Hi Argon
Thank you so much for the help last time. I hate to nag you again, but I'm about really at my wit's end now. I spent days settings these up and getting them all to work with pretty much 100% compatibility in demulshooter, and now a couple days later for seemingly no reason, it's all just stopped working. Nothing seems to have changed, as in literally nothing. Just now when I open DemulShooter and set P1 and P2, and load games, nothing seems to happen. There's two corsshairs on the screen, and when I move one of the guns, one of the crosshairs goes to the bottom right of the screen, and then that's it. I assumed it might've been a driver issue or w/e with the guns, but it's not working when I try to set my real mouse or a gamepad either. Would you have any idea whatsoever? I've tried editing the config every which way and doing a reinstall of demulshooter, but it seems to all do nothing. There was a windows update, but it's impossible for me to roll back. Is there registry or appdata prefs I could try wiping as well do to a 'cleaner' reinstall? I'm about ready to reinstall windows and try from scratch but that's. jfc. I truly hope it doesn't come to that.
thanks for your time.
So I just tested it with some XInput controllers, and it works as intended as far as I can tell. Hooks into the program, and I can move the crosshair around the screen with my fightstick.... But it still doesn't work with my guns or actual mouse. The devices get registered in demulshooter, but the mouse seems to do nothing (can't even shoot), and when I move the guns the crosshair goes to bottom right of the screen and stays there. This behaviour doesn't occur with my mouse, it just doesn't respond at all. I'm guess this means it's probably a device manager/registry issue, and not a demulshooter issue? Only thing with that is they're still working perfectly in supermodel and mame - I think the issue must be related to demulshooter not reading the correct hareware IDs or something correctly? I really don't know. Is there a way I could manually input this information into config.ini and try that? I had a brief look around device manager and hardware IDs but it was hard to extrapolate, for example the config.ini uses syntax like so
HID#VID_0B9A&PID_016A&Col01#6&1f2cb574&3&0000#
with hashes, but the hashes seem to be slashes when I look in hardware IDs, is this correct? I also noticed something else. In Device Manager for my guns they read as having a REV_#001 etc. on them which doesn't show up in the config.ini, could this be related? If you need screenshots or more specific info, please let me know. I appreciate any help I can get from anyone ^^
I feel like there's meant to be a bigger difference between these device names maybe?
;Player1 Device configuration
P1Device = \\?\HID#VID_0B9A&PID_016A&Col01#6&1f2cb574&3&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
;Player2 Device configuration
P2Device = \\?\HID#VID_0B9A&PID_016A&Col01#7&1fd37798&2&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
At this point, it all just seems completely busted and random (not DemulShooter, I've seen that working 100% perfectly), Windows 10 I'm guessing, it ties back to pretty much what you said about user feedback on Windows 10. Now after finally removing all trace of my TopGun drivers (I think? who knows), I can't get the fight stick to work at all, and my mouse will work for the first 1 second of emulation then stop, BUT ON THE PLUS SIDE, my XInput steering wheel can now move on of the cursors perfectly across the screen left and right!!
I'm so sad
Last edit: As far as I can tell, it's just bugging out with the mouse for some reason. Can get XInput devices to work. But can't get mouses to work in any way. All devices work separately as player 1 not using raw input, and both guns work in supermodel and mame ;( I'm just..... so lost as to what could have caused this, I had them working ~72 hours ago
Here's my -v output, I spent some time in game trying to move the crosshairs and stuff around, same behaviour, they just get stuck in the bottom right of the screen (I think maybe they can "sometimes" move across the bottom of the screen, but even this isnt consistent)...
13:23:14.389060 : -------------------- Program Start ----------------------
13:23:14.717090 : P1 device = \\?\HID#VID_0B9A&PID_016A&Col01#6&1f2cb574&4&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
13:23:15.248912 : P1 device handle = 65597
13:23:15.670006 : P2 device = \\?\HID#VID_0B9A&PID_016A&Col01#7&1fd37798&3&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
13:23:15.747776 : P2 device handle = 65595
13:23:15.811314 : Cmdline arg 1 : -target=model2m
13:23:15.872464 : Cmdline arg 2 : -rom=vcop2
13:23:15.936419 : Cmdline arg 3 : -v
13:23:16.033564 : Waiting for Model2 vcop2 game to hook.....
13:23:16.592499 : Attached to Process emulator_multicpu.exe, ProcessHandle = 1312
13:23:16.752438 : emulator_multicpu.exe = 0x00400000
13:23:16.753942 : Calculated address 1 = 0x0793E020
13:23:17.756126 : Controls memory base address = 05079218
13:23:17.757282 : Memory Hack complete !
13:23:17.758435 : -
13:23:49.090877 : emulator_multicpu.exe closed
Welp I pulled an all-nighter and have been at this for like 20 hours straight or something now
I can't figure it out for the life of me. I've done everything I possibly can to restore the mice to default and reinstall them from scratch when I had them working, and nothing. Nothing nothing nothing. I'm installing windows 7 at the moment and am just going to see if I'm going to have too much drama migrating my registry, appdata and signed dlls from win 10 back to win 7, and will just use that if it works.
Is there any possibility, because I understand time is a beyond precious resource and you've already devoted so much to this - That you could release the source code to demulshooter (or if it already is you could point me in the direction) and I could try fiddling around with that? I'm not a programmer at all but I am a fast learner and I'm fairly confident there's nothing more I can do in device manager or registry at this point to change my situation.