| Main > Software Forum |
| CoinDrop v1.3 Released - Now you can insert coins from your front-end! |
| << < (21/27) > >> |
| headkaze:
Some people are misinterpreting how CoinDrop works, since version 1.1 it has changed. This is a message I got from someone, as you will note you have to press start to drop a coin. Also, it will not carry over credits once you have inserted them within a game. Perhaps I could add the feature that if you quit a game before using all your credits I could add this to the CoinDrop credit total - but for now, just don't drop in credits in a game unless you want to use them. --- Quote ---How I thought it worked: -> enter a coin from frontend -> start game -> game would come up with 1 credit showing How it does works: -> enter coin from frontend -> start game -> game shows 0 credits -> pressing 1 or 2 player start enters coins and starts game --- End quote --- |
| headkaze:
Version 1.3. Okay, now you can carry over credits you insert in Mame but do not play. Eg. If your in a game, you insert a coin, you can exit, select another game, and use the coin in that game instead. |
| loadman:
--- Quote ---Actually, you can still get a copy, you just have to message me in this forum with a link to your project page and I will give you a password and url to download. --- End quote --- Thanks I got it. With MAME 32 it worked perfectly. With MaLa it didn't work at all until I applied the tip from SWINDUS of renaming a .dll file. After that within the MaLa FE I could add credits (by the sound). But when I launch 1942 it didn't work and to make things worse game controls were very sluggish. As instructed I used the test version as well. It had the same results: As requested below is a list of windows that came up: -'Dihook checking process x 2 windows (when 1st launched coindrop) -'Dihook checking process x 1 window |
| headkaze:
Ok, I don't know what exactly is happening here, but you are not getting the critical messages. The following should occur... The messages I am looking for are: - "DIHook Checking Process" (should appear a few times) - "MAME Found" Now you launch 1942 from Mame32 - "DirectInputCreateA Trapped" (if you don't get this message it's not using DirectInput) - "MAME: 1942 (set 1) [1942]" - "Ready Status OK" If you don't get the "DirectInputCreateA Trapped" message then it's not finding DirectInput. This is the method I use to intercept and inject keys into Mame. Ok, I've just updated CoinDrop again, this time it also intercepts the Unicode version of DI called DirectInputCreateW. Try this out and if you still don't get the message that DirectInputCreate is being trapped then DI is not being used on your system. I breifly looked at the Mame source and it looks like it has a backup method of reading input using GetAsyncKeyState. Perhaps this is what is happening here. Anyway try the new version and get back to me. Appreciate your help, thanks. |
| loadman:
Hello again, |
| Navigation |
| Message Index |
| Next page |
| Previous page |