-
Notifications
You must be signed in to change notification settings - Fork 44
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 3 Misc Items wrong location in arsenal #64
Comments
Fireman linked me this acemod/ACE3#5673 the problem is that i can't find InventoryItem_Base_F in antistasi to replace with CBA_MiscItem_ItemInfo as the issue suggest... |
I've found this link: |
The ACE_items are on the wrong position because since ACE changed from mine detecting system > CBA_miscItem (for good reasons). But because of that the initializing of the arsenal is partly fucked. We need to figure out how the arsenal recognize the ACE items again and put them into the misc item section. This is the mainreason why the ACE items are not showing up when you start a new campaign. I think because we need to call the items on a different way. My guess would be that the trouble is in the: fn_detectACE.sqf |
Somehow ACE misc items are categorized as
rpt
fn_JNA_classifyItem.sqf classifies That classification is interpreted to The Arsenal data structure shows that items indeed are in that bipod category
imho that's the obvious bug from ACE items configuration, whether we adapt to it or wait for the fix. |
Is related to #60 |
I think it's related to how CBA handles now an old ace 3 misc item class: |
The case, when new items are delivered via AirDrop (with ACE misc items), was not covered by previous fix. PR pending |
also, when looking at rifle attatchments, arsenal displays medical stuff instead of bipods etc. |
All ACE misc items are missing from Misc tab. Instead they are located in Bipod tab for every weapon and cannot be retrieved that way.
ACE version 3.11.0.1
Tested on antistasi 1.7.16C and 1.7.16D(with updated ACE detection), with Jeroen arsenal on
The text was updated successfully, but these errors were encountered: