| Main > Lightguns |
| QMamehook - The Cross-platform MAMEHOOKER-compatible alternative for PCLightguns |
| << < (3/7) > >> |
| bandicoot:
if you want to test LEDWIZ here's a open source code https://github.com/cithraidt/lwcloneu2 and for compile it this post can help https://www.ukvac.com/forum/threads/custom-arduino-firmware-lwcloneu2.56901/ ;) |
| ThatOneSeong:
Again, I don't have an LEDWiz to even test with, lol. Also the driver code in that repo only has source code for a Windows library, which aside from inherently not being cross-platform (no Linux support) is also way outside of my wheelhouse (of frankly limited knowledge). Again, though, I'm accepting PRs if anyone wants to try. ;) Pushed another update out tonight; aside from some code plumbing, it includes contingencies for Flycast (standalone) and its out-of-spec outputs behavior. Shouldn't affect people using frontends for the most part, but still. Aaaaaaaaaaaaaaaand yet ANOTHER update! Turns out that Flycast's implem revealed some weaknesses in the older design of the socket reading mechanism, so this version should make outputs ever so slightly more consistent in most cases (and mainly fixes Flycast, or other games with weird simultaneous outputs). To get around a QT bug on Windows, this does mean the Windows binary now checks the socket every 1ms to accommodate for that platform having a random timeout issue. But even on my old i5 6500U laptop, the difference in idle usage was imperceptible, and should only effect the slowest of slow embedded-class 64-bit machines. Still, should be noted. It was either that, or have the connection erroneously dropping out and having PTSD panic attacks from my MAMEHOOKER on GUN4ALL saga... |
| baritonomarchetto:
--- Quote from: bandicoot on February 27, 2024, 01:22:46 pm ---i'm curious to test your alternative , cause with mamehooker and two positionnal gun , when i shoot at the same time it's seem lost sometime, the part of code you see is not complete , but with this i can manage Qmamehook and my solenoid , there's not joystick code in this example ^^ but it's just for me to test recoil on solenoid ;) --- End quote --- This is more likely related to the very specific charge/discharge timing of your gun solenoid vs emulating game's oroginal hardware. Add to this USB latency and, voilą, you lose some message. |
| ThatOneSeong:
I can't speak for all (gun/feedback) systems obviously, but I don't think it's the USB latency that's a factor (at worst, it should just delay messages, not lose them outright). Self-promotion aside, I know it's not an issue with GUN4ALL for instance. The problem seems to be MAME itself sometimes loses very quick channel update messages if done in rapid succession. It should be important to note that MAME does in fact do some concatenation of simultaneous messages, which QMamehook has to account for - you notice this most in games with a BEVY of different LED outputs working in tandem with one or two recoil channels, e.g. timecris, or games with rapid recoil mechanisms, e.g. term2/revx. I've done all I could to ensure all messages received are split and processed sequentially, but nothing can be helped by the source itself neglecting some of those events. |
| argonlefou:
I've updated DemulShooter with Network outputs supports. No official release yet, as I still have to clean some things before. but I'm attaching a version for you to test. Just go in DemulShooter_GUI and enable Network outputs in the outputs tab It should behave similar than MAME (at least it's what a network sniffer shows) I encountered some bugs with your app though: if I run it when DemulShooter is already running and already has hooked the game, QMamehook mix all arriving string into the rom name. Looks like OK if QMameHook connects before DemulShooter hooks the game |
| Navigation |
| Message Index |
| Next page |
| Previous page |