| Main > Lightguns |
| DemulShooter (Dual light gun on DEMUL, Model2, Dolphin, Silent Hill, etc...) |
| << < (17/727) > >> |
| argonlefou:
--- Quote from: burn_654 on June 19, 2016, 07:49:28 am ---Ok so I tried the new version with the TopGunCon setup and it works perfectly for Demul as expected. :applaud: However I'm not having luck with model2. I launched demulshooter with the -target=model2 -rom=vcop -v arguments as well as -rom=hotd. I'm getting no shot position updating from the guns/recognized shots are only occuring in one spot of the screen (this behavior seems to be the same as if demulshooter isn't running.) I can't get to my log right now but I'll retrieve it later - but I seem to recall a couple repeat statements of 'Couldn't read from XXXXXX' which was a hex address. It was the same address showing for running Demulshooter for Virtua Cop and House of the Dead. I'm running model2 1.1a from the nebula homepage on windows xp 32bit. Any thoughts? I'll get the log for you when I get home. --- End quote --- I'll wait for your log before saying something, I prefer not to say anything wrong based on a guess :-) |
| ArcadeBliss:
--- Quote from: argonlefou on June 15, 2016, 04:45:02 pm --- --- Quote from: ArcadeBliss on June 03, 2016, 09:16:28 pm ---Not intending to hijack your thread, but can anyone PM me the 1.6 firmware of the AimTrack? I flashed the wrong version and it is stuck in update mode looking for the correct firmware. Thanks --- End quote --- Do you have an "old type" or "newer type" of Aimtrak ? (you can see both here : https://www.ultimarc.com/recoil.html) If you have old version, I'll send you the latest firmware If not, you can mail Andy directly, he usually answers. That's how I got my firmwares --- End quote --- thanks I have the old version and the link to the firmware on that page is dead. I contacted Andy and was helped within hours. Sent from my Nexus 6P using Tapatalk |
| burn_654:
--- Quote from: argonlefou on June 19, 2016, 03:08:13 pm ---I'll wait for your log before saying something, I prefer not to say anything wrong based on a guess :-) --- End quote --- Of course! Here's what I'm seeing: --- Quote from: vcop debug ---7:02 PM : -------------------- Program Start ---------------------- 7:02 PM : Conf read OK 7:02 PM : P1 device = \??\HID#Vid_0b9a&Pid_016a&Col01#6&28ddcf26&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 7:02 PM : P1 device handle = 65613 7:02 PM : P2 device = \??\HID#Vid_0b9a&Pid_016a&Col01#6&16241e81&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 7:02 PM : P2 device handle = 65611 7:02 PM : Cmdline arg 1 : -target=model2 7:02 PM : Cmdline arg 2 : -rom=vcop 7:02 PM : Cmdline arg 3 : -v 7:02 PM : Waiting for Model2 vcop game to hook..... 7:02 PM : Cannot read memory at address 0x0018FB14 7:02 PM : Cannot read memory at address 0x0018FB14 7:02 PM : Cannot read memory at address 0x0018FB14 7:02 PM : Cannot read memory at address 0x0018FB14 --- End quote --- The 'Cannot read memory' lines continue until the next 'program start' entry. Here's House of the Dead model2: --- Quote from: hotd debug ---7:04 PM : -------------------- Program Start ---------------------- 7:04 PM : Conf read OK 7:04 PM : P1 device = \??\HID#Vid_0b9a&Pid_016a&Col01#6&28ddcf26&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 7:04 PM : P1 device handle = 65613 7:04 PM : P2 device = \??\HID#Vid_0b9a&Pid_016a&Col01#6&16241e81&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 7:04 PM : P2 device handle = 65611 7:04 PM : Cmdline arg 1 : -target=model2 7:04 PM : Cmdline arg 2 : -rom=hotd 7:04 PM : Cmdline arg 3 : -v 7:04 PM : Waiting for Model2 hotd game to hook..... 7:04 PM : Cannot read memory at address 0x0018FB14 7:04 PM : Cannot read memory at address 0x0018FB14 7:04 PM : Cannot read memory at address 0x0018FB14 7:04 PM : Cannot read memory at address 0x0018FB14 7:04 PM : Cannot read memory at address 0x0018FB14 --- End quote --- And finally for reference here is a successful working hook with Demul 0.57 on my system. --- Quote from: demul hotd2 debug ---7:08 PM : -------------------- Program Start ---------------------- 7:08 PM : Conf read OK 7:08 PM : P1 device = \??\HID#Vid_0b9a&Pid_016a&Col01#6&28ddcf26&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 7:08 PM : P1 device handle = 65613 7:08 PM : P2 device = \??\HID#Vid_0b9a&Pid_016a&Col01#6&16241e81&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd} 7:08 PM : P2 device handle = 65611 7:08 PM : Cmdline arg 1 : -target=demul057 7:08 PM : Cmdline arg 2 : -rom=hotd2 7:08 PM : Cmdline arg 3 : -v 7:08 PM : Waiting for naomigame to hook..... 7:09 PM : Attached to Process demul.exe, ProcessHandle = 1612 7:09 PM : Demul.exe = 0x00400000, padDemul.dll = 0x0FB00000 7:09 PM : Memory Hack complete ! 7:10 PM : demul.exe closed 7:11 PM : --- End quote --- It seems like it's having trouble recognizing something to inject the hook/can't get access to the memory address? |
| argonlefou:
Yes, this is a fixed address pointing to the Input structure in memory (buttons, etc...) It simply equals "0" untill a game is loaded, but I never ran into the case where the address is not accessible ! Sorry I was a bit late to answer you but I had to wait until today, so that I can access an old Windows Xp computer to test : I can reproduce this behavior only with windows XP, so confirming my initial guess. I still have to investigate further, it may be caused because winXP uses a different (and older) version of DirectX than the latest win7 or ++, and maybe this address is specific to DX11 or DX10....i'm working on it but it will be slow as I have limited acces to this old computer ! |
| argonlefou:
--- Quote from: burn_654 on June 20, 2016, 05:34:04 pm ---... --- End quote --- Hi burn_654 ! I may have found why. Can you test the exe I've joined here below in this post ? Just overwrite the old one, that's all ! I'll wait to have a confirmed working version for this issue before I release a full 3.1 update with a new readme (as I added support for a game or two) |
| Navigation |
| Message Index |
| Next page |
| Previous page |