IIDX 18 gets stuck on boot when the BT5 monitor check is enabled.
Expected behavior
Should not happen, game boots.
Current behavior
Game gets stuck mostly on "GAME SYSTEM BOOTING..." but can also happen before that, e.g. first screen with "elapsed time" showing the value 2.
Detailed Description
Not a lot to add to the above.
Steps to reproduce
Add -p gfx.monitor_check=0 or -p gfx.monitor_check=59.95 to gamestart.bat and run it. Or, set the values in the iidxhook.conf file.
Run the the game.
You should not get through the boot process after a reasonable amount of time, i.e. 1-2 minutes, to reach the attract loop
Possible solution
Don't use BT5's monitor check with iidx 18 for now.
Context (Environment)
Bemanitools version(s) affected
5.33
Game(s) and version(s) affected
iid18
Other games pre iidx18 tested and no issues there, e.g. iidx10, iidx17
Log output
Checked the log but nothing relevant found.
Configuration files
Stock configuration + the changes mentioned above.
Command line arguments
See above.
APIs used
Default eamio and iidxio APIs.
OS version
Windows 10
## Summary
<!--- Provide a general summary of the issue in the Title above -->
IIDX 18 gets stuck on boot when the BT5 monitor check is enabled.
## Expected behavior
<!--- Tell us what should happen -->
Should not happen, game boots.
## Current behavior
<!--- Tell us what happens instead of the expected behavior -->
Game gets stuck mostly on "GAME SYSTEM BOOTING..." but can also happen before that, e.g. first screen with "elapsed time" showing the value 2.
## Detailed Description
<!--- Provide a detailed description of the issue. Include links to screenshots or videos if necessary -->
Not a lot to add to the above.
## Steps to reproduce
<!--- Provide a detailed step by step description how to reproduce this issue -->
1. Add `-p gfx.monitor_check=0` or `-p gfx.monitor_check=59.95` to `gamestart.bat` and run it. Or, set the values in the `iidxhook.conf` file.
2. Run the the game.
3. You should not get through the boot process after a reasonable amount of time, i.e. 1-2 minutes, to reach the attract loop
## Possible solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
Don't use BT5's monitor check with iidx 18 for now.
## Context (Environment)
### Bemanitools version(s) affected
* 5.33
### Game(s) and version(s) affected
* iid18
Other games pre iidx18 tested and no issues there, e.g. iidx10, iidx17
### Log output
Checked the log but nothing relevant found.
### Configuration files
Stock configuration + the changes mentioned above.
### Command line arguments
See above.
### APIs used
Default `eamio` and `iidxio` APIs.
### OS version
<!--- Provide the version of Windows you used with whatever update/build identifier -->
Windows 10
This was a problem with the old monitor check logic not working correctly on iidx18. Fixes included in the following PR: https://github.com/djhackersdev/bemanitools/pull/236
Version 5.44 also has this fixes included.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
IIDX 18 gets stuck on boot when the BT5 monitor check is enabled.
Expected behavior
Should not happen, game boots.
Current behavior
Game gets stuck mostly on "GAME SYSTEM BOOTING..." but can also happen before that, e.g. first screen with "elapsed time" showing the value 2.
Detailed Description
Not a lot to add to the above.
Steps to reproduce
-p gfx.monitor_check=0or-p gfx.monitor_check=59.95togamestart.batand run it. Or, set the values in theiidxhook.conffile.Possible solution
Don't use BT5's monitor check with iidx 18 for now.
Context (Environment)
Bemanitools version(s) affected
Game(s) and version(s) affected
Other games pre iidx18 tested and no issues there, e.g. iidx10, iidx17
Log output
Checked the log but nothing relevant found.
Configuration files
Stock configuration + the changes mentioned above.
Command line arguments
See above.
APIs used
Default
eamioandiidxioAPIs.OS version
Windows 10
In GitLab by @Radio on Nov 16, 2020, 12:29
Can confirm this also happens on Windows 7
This was a problem with the old monitor check logic not working correctly on iidx18. Fixes included in the following PR: https://github.com/djhackersdev/bemanitools/pull/236
Version 5.44 also has this fixes included.