If HID lights are mapped in Bemanitools config for DDR, they will not light up during gameplay.
Expected behavior
If a light is mapped to an HID light, the HID light should turn on and off to correspond to the expected pattern.
Current behavior
Lights will not turn on to correspond to the expected pattern. Nothing lights up when it should.
Steps to reproduce
1.Ensure that a controller with HID lighting is plugged in (For example, an Arcin IIDX controller with LED lights)
2.Open up Bemanitools config and select the Lights tab
3.Configure any number of in-game lights to map to the HID lights on the controller
4.Open DDR Ace and begin a game. Navigate to the IO Check > Lamp Check menu option in the service menu.
5.Attempt to illuminate all lights
6.The lights should turn on, but nothing lights up. Same issue during gameplay or when trying to cycle through individual lights in the lamp check.
Possible solution
This should work, since Spicetools maps to HID lights properly. It's possible that things are not mapped properly in Bemanitools?
Context (Environment)
Bemanitools version(s) affected
*5.29
Game(s) and version(s) affected
DDR Ace
OS version
Windows 10
In GitLab by @Androopy on Feb 25, 2020, 24:04
## Summary
If HID lights are mapped in Bemanitools config for DDR, they will not light up during gameplay.
## Expected behavior
If a light is mapped to an HID light, the HID light should turn on and off to correspond to the expected pattern.
## Current behavior
Lights will not turn on to correspond to the expected pattern. Nothing lights up when it should.
## Steps to reproduce
1.Ensure that a controller with HID lighting is plugged in (For example, an Arcin IIDX controller with LED lights)
2.Open up Bemanitools config and select the Lights tab
3.Configure any number of in-game lights to map to the HID lights on the controller
4.Open DDR Ace and begin a game. Navigate to the IO Check > Lamp Check menu option in the service menu.
5.Attempt to illuminate all lights
6.The lights should turn on, but nothing lights up. Same issue during gameplay or when trying to cycle through individual lights in the lamp check.
## Possible solution
This should work, since Spicetools maps to HID lights properly. It's possible that things are not mapped properly in Bemanitools?
## Context (Environment)
### Bemanitools version(s) affected
*5.29
### Game(s) and version(s) affected
* DDR Ace
### OS version
Windows 10
Trying to map any other lights will result in the "Game Light" column remaining blank.
No lights work except P2 Marquee Top Light and P2 Marquee Bottom
P2 Marquee Bottom and P2 Marquee Top seem to light up, corresponding to P1 arrow lights. So, they "work" but not really.
Keep in mind, this is using Bemanitools 4, so unsure how relevant this is.
In GitLab by @Androopy on Feb 27, 2020, 05:10
Yes, you can in 2014, but with some exceptions:
1. You can only map the following buttons:
* P1 Menu Lights
* P1 Marquee Bottom
* Bass Neons
* P2 Menu Lights
* P2 Marquee Top Light
* P2 Marquee Bottom
2. Trying to map any other lights will result in the "Game Light" column remaining blank.
3. No lights work except P2 Marquee Top Light and P2 Marquee Bottom
3. P2 Marquee Bottom and P2 Marquee Top seem to light up, corresponding to P1 arrow lights. So, they "work" but not really.
Keep in mind, this is using Bemanitools 4, so unsure how relevant this is.
As an update (Thanks, pandemic) I poked around in the code and I've figured it out. Light mappings for spotlights are different for HD cabs. Might be able to make a PR once I can figure out how to check for cab type and map accordingly.
In GitLab by @Androopy on Mar 18, 2020, 05:33
As an update (Thanks, pandemic) I poked around in the code and I've figured it out. Light mappings for spotlights are different for HD cabs. Might be able to make a PR once I can figure out how to check for cab type and map accordingly.
Nice find, the cab type should be accessible by p3io_ddr_get_cab_type if you're working inside of p3io.c.
Or if I'm mistaken, and it's actually based on cab model and not monitor type, std_getenv (#include "imports/avs.h") should allow you to poll various envvars including /env/profile/soft_id_code.
In GitLab by @xyen on Mar 18, 2020, 17:58
Nice find, the cab type should be accessible by `p3io_ddr_get_cab_type` if you're working inside of p3io.c.
Or if I'm mistaken, and it's actually based on cab model and not monitor type, `std_getenv` (`#include "imports/avs.h"`) should allow you to poll various envvars including `/env/profile/soft_id_code`.
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.
In GitLab by @Androopy on Feb 25, 2020, 24:04
Summary
If HID lights are mapped in Bemanitools config for DDR, they will not light up during gameplay.
Expected behavior
If a light is mapped to an HID light, the HID light should turn on and off to correspond to the expected pattern.
Current behavior
Lights will not turn on to correspond to the expected pattern. Nothing lights up when it should.
Steps to reproduce
1.Ensure that a controller with HID lighting is plugged in (For example, an Arcin IIDX controller with LED lights)
2.Open up Bemanitools config and select the Lights tab
3.Configure any number of in-game lights to map to the HID lights on the controller
4.Open DDR Ace and begin a game. Navigate to the IO Check > Lamp Check menu option in the service menu.
5.Attempt to illuminate all lights
6.The lights should turn on, but nothing lights up. Same issue during gameplay or when trying to cycle through individual lights in the lamp check.
Possible solution
This should work, since Spicetools maps to HID lights properly. It's possible that things are not mapped properly in Bemanitools?
Context (Environment)
Bemanitools version(s) affected
*5.29
Game(s) and version(s) affected
OS version
Windows 10
In GitLab by @xyen on Feb 25, 2020, 23:13
Do they work in 2014?
In GitLab by @Androopy on Feb 27, 2020, 05:10
Yes, you can in 2014, but with some exceptions:
Keep in mind, this is using Bemanitools 4, so unsure how relevant this is.
In GitLab by @Androopy on Mar 18, 2020, 05:33
As an update (Thanks, pandemic) I poked around in the code and I've figured it out. Light mappings for spotlights are different for HD cabs. Might be able to make a PR once I can figure out how to check for cab type and map accordingly.
In GitLab by @xyen on Mar 18, 2020, 17:58
Nice find, the cab type should be accessible by
p3io_ddr_get_cab_typeif you're working inside of p3io.c.Or if I'm mistaken, and it's actually based on cab model and not monitor type,
std_getenv(#include "imports/avs.h") should allow you to poll various envvars including/env/profile/soft_id_code.In GitLab by @xyen on Jun 29, 2020, 21:35
Should be fixed now upstream.
In GitLab by @xyen on Jun 29, 2020, 21:35
closed