-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
ace_interact_menu_consolidateSingleChild
Setting prevents insertion of USB Drives
#414
Comments
Maybe #406 could fix this, I'll check it out if I find the time. |
Interesting. I will have a look into it. |
Issue is also present in #406. It occurs at private _condition =
{
params ["_target", "_player", "_params"];
(_params select 0) params ["_index", "_name", "_rel_pos", "_rot_yaw", "_rot_pitch", "_rot_roll"];
private _occupiedList = _target getVariable "AE3_USB_Interfaces_occupied";
isNull (_occupiedList select _index);
}; Apparently when |
Got it. Basically, when [[1,"USB1",[-0.19,-0.028,-0.145],90,0,180]] However, when ["Item_FlashDisk_AE3_ID_1",[1,"USB1",[-0.19,-0.028,-0.145],90,0,180]] I guess that's just an ACE quirk, will investigate further. Because of this, params ["_target", "_player", "_params"];
(_params select 0) params ["_index", "_name", "_rel_pos", "_rot_yaw", "_rot_pitch", "_rot_roll"];
private _occupiedList = _target getVariable "AE3_USB_Interfaces_occupied";
isNull (_occupiedList select _index); I found a fix, basically checking if the first element of |
Indeed, child params are used with parent condition code. Please check if it's fixed with acemod/ACE3#9946. |
Can confirm that your PR fixes this issue, many thanks 👍🏻 |
This has now been fixed publicly by ACE v3.17.1. |
When the "ACE Interaction Menu" setting called "Consolidate single child actions" (
ace_interact_menu_consolidateSingleChild
) is enabled, the following error occurs when trying to plug in a USB Drive.As a result, the USB Drive can not be plugged in unless the setting is disabled.
The ACE Interaction interface also somewhat bugs itself and remains in view despite releasing
⊞ Win
, requiring going back to a previous node to unstick it, though that is probably just the way Ace reacts to an interaction's exception.The text was updated successfully, but these errors were encountered: