-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
p3io jubeats - Issues thread #92
Comments
In GitLab by @hayu on Jan 7, 2022, 08:52 I'm sorry for causing confusion by selecting the wrong word. I tested with P4IO PC and P3IO PC in cab with contactless reader.
I'm sorry I need to reconfirm the most important part. I'll test it again when I have time and catch the log. |
In GitLab by @hayu on Jan 7, 2022, 11:46 I just discovered that logs are not recorded from the time the copious game screen appears. maybe from 5.37. (edit) There was a card reader problem with the same symptoms on the knit. |
In GitLab by @mon on Jan 9, 2022, 15:25 @hayu Thank you very much for your clarification.
About the logs - if knit is anything like jb2008, it doesn't log much, and may also disable logging (jubeat is notoriously inefficient). There might be ways around it, but for now I hope you can try eamiotest.exe and see if it works. |
In GitLab by @hayu on Jan 9, 2022, 17:33
|
In GitLab by @hayu on Jan 10, 2022, 08:41 There is no problem using contactless reader in eamiotest. It scan well several times. |
In GitLab by @mon on Jan 10, 2022, 13:38 Thank you for the extra information - I will see what I can do. |
In GitLab by @expandbanana on Apr 3, 2022, 07:13 All 16 buttons go off on Copious with the magic box jbio at seemingly random intervals, but doesn't go into test/service. Can also hang the test menu sometimes when it happens while there. |
In GitLab by @mon on Apr 3, 2022, 14:29 Ok, some updates. Any code changes are in my jb-fixes branch, which is an upcoming MR.
|
In GitLab by @mon on Apr 3, 2022, 14:53 Yes - I wonder if eamio-icca itself has problems, instead of jbhook. |
In GitLab by @hayu on Apr 3, 2022, 15:11 Ok I'll try it soon. |
The symptoms I have observed with this issue so far in #89 point to an issue in the hooking backend, probably capnhook. The following does not back it up further, rather adds more mystery: pumptools's hook backend is based on capnhook and experiences the same issues. I do not know if these issues are connected. Considering that pumptools runs on Linux while bemanitools runs on Windows, it may be unlikely. However, the code on pumptools is based of capnhook and uses the same design and shares serveral platform independent data structures, e.g. list implementation. Maybe it helps to get an investigation started. I remember trying to debug this issue several times but have failed due to not being able to reproduce the issue locally and reliably. |
In GitLab by @hayu on May 5, 2022, 09:48 Sorry I'm late. I tested eamiotest, jubeat knit, copious, festo, SDVX IV, and V on Windows 10 x64 PC using eamio-icca. The wavepass reader works fine with eamiotest, festo, SDVX IV, and V. but knit and copious stop test version is +) Who should I ask for permission to |
Actually, I noticed just now that @mon has not merged his approved MR https://dev.s-ul.net/djhackers/bemanitools/-/merge_requests/109 yet. I can look into that later and push out another minor release.
Not having more data points on that, but that does sound like interaction with the aciodrv is slightly different on some games for different card types. You sound like you have some dev experience. Considering you have a setup to test and reproduce this, you could look into adding some simple debug prints/printf calls to several spots in the eamio-icca library. Build it, set logging to file, run the game and reproduce the issue. Get output for a working case, e.g. from festo, and a non working case, e.g. knit, and compare the two. Try to understand what's different in the output and where it gets stuck. With the good debug output, you might be able to understand what might be to expect next on the test where the game gets stuck. That insight might already give us some pointers what we need to further look into next. I hope this helps somewhat as I don't have a lot of time to spare for bemanitools right now. Otherwise, an actual live debug session might be a valuable thing to do. Let me know if you have any questions or ideas how I might support you.
Just open a MR once you got something you would like to get reviewed. There is @XYen and myself who can review less game specific things, which includes window mode support. For very game specific stuff for games we haven't worked on, it's usually good to also get @mon's perspective. Depending on our confidence we will make sure to loop in the right people. |
In GitLab by @hayu on May 6, 2022, 22:54 I also thought it strange that the MR of Mon would not be merged for a long time lol Shamefully, I have no previous dev experience, but I tried out as a wild man because of BEMANI. I will try the part you mentioned by myself and ask for help if there is a problem. and now I have confirmed that I have a new merge request button. Thanks! |
In GitLab by @hayu on May 23, 2022, 17:10 Is there anyone else who turns off before the game window pops up? All other versions are fine, but only from Windows 10 x64 PC |
FYI that the PR #236 includes potential fixes. The fixes are also included in the tagged release 5.44. Any testing feedback is welcome. |
In GitLab by @mon on Jan 6, 2022, 10:54
After releasing the p3io support for Jubeat, a number of issues have been reported. I'll be collating them here so I have a nice list of things to work on.
sidcode
instead of a hardcoded oneI will be adding to this list as things are reported, removing from it as I triage and resolve issues, and linking it to other people to submit their own issues as required.
The text was updated successfully, but these errors were encountered: