search

djhackersdev / bemanitools

Runs recent Konami arcade games and emulates various arcade hardware.
The Unlicense
87 stars 17 forks source link

[HV][BT5.33] Keypad not responding after full attract loop #72

Closed icex2 closed 1 year ago

icex2 commented 3 years ago

In GitLab by @phantomlan on Dec 21, 2020, 03:37

Summary

Keypad stops responding to any input after a full 1 or 2 loops of attract screen.

Expected behavior

Keypad should work at anytime.

Current behavior

At the moment, whenever game attract screen loops once or twice, the keypad stops responding to any input, trying to load a card or change SP/DP, difficulty, etc. in other menus also does not respond.

Detailed Description

I'm currently running a closed BPC setup (Minimal Win10 install, cleaned up, only required drivers, only IIDX27HV installed), it's running by itself 24/7 (autostarts by itself, closes by itself, no maintenance needed setup)

Steps to reproduce

1.Let the game runs once or twice through the whole attract loop

2.Keypad stops responding to any command, thus not allowing to login with card

Possible solution

Temporary solution - Going to Service Menu unlocks/resets keypad, thus when going back into game mode, it runs ok and allows to login, but the issue persists if it's idle(attract) again the same way.

Context (Environment)

Bemanitools version(s) affected

Bemanitools 5.33

Game(s) and version(s) affected

Beatmania IIDX 27 Heroic Verse (60hz/120hzHack with and without Omnimix tested)

Log output

I cannot provide log output as -Y command creates empty logfiles.

Configuration files

No changes to iidxhook-27.conf

Command line arguments

Default Stock supplied, added "-Y logfile.txt" for logfile with no output going in.

APIs used

Default Stock settings, no changes.

OS version

Win10 2004 (OS Build 19041.685)

Hardware specs

AMD Ryzen 2200g Running Stock

2x 2GB 3200MHz HyperX sticks for dual-channel memory

256GB Adata SSD (100GB System Partition and Rest is IIDX Partition)

icex2 commented 3 years ago

In GitLab by @xyen on Dec 21, 2020, 08:49

I've seen this happen before, and this happens on real cabs as well. Assuming that this locks up the PIN entry screen as well, and happens even more frequently when using the 120hz hack. I'm not sure if there's much we can do here, as it's the game's handling code that gets deadlocked, not ours.

This is the first time I've seen it occur without using real readers though.

icex2 commented 3 years ago

Just an additional note regarding log output: your avs-config.xml migth have set the log level to fatal. If you change that to misc, you should see very verbose output on both, the console and to the file if you have file output enabled using the -Y command line arg.

icex2 commented 2 years ago

In GitLab by @phantomlan on Dec 14, 2021, 11:59

On Bistrover the issue stopped existing, possible through windows updates etc. it fixed somehow, nevertheless the game responds to input properly.

icex2 commented 2 years ago

In GitLab by @xyen on Dec 14, 2021, 23:55

It actually still happens in Bistrover, just less often, I don't think it's an issue with the tools given that I've been seeing reports of it on actual cabs.