-
Notifications
You must be signed in to change notification settings - Fork 739
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
CSW - Minor fixes for CSW + RHS Compats #7497
Conversation
Why would static weapons appear in the arsenal? |
There is no reason to do this. Just use the external filepath. Tbh, for legal reasons, these commits should be rebased. |
Isn't the whole point of What is the point of the weapon and tripod bags if you can't equip them from the arsenal. Maybe I've completely misunderstood the purpose of the module.
When equipped, you get an error when looking in the inventory (ex.
I'll point them to the generic icons in |
No, use the RHS paths. If they changed them, adjust the paths. Obviously you have to start RHS to start these components. |
addons/csw/CfgWeapons.hpp
Outdated
@@ -148,6 +145,9 @@ class CfgWeapons { | |||
model = QPATHTOEF(apl,ACE_CSW_Bag.p3d); | |||
modes[] = {}; | |||
picture = QPATHTOF(UI\StaticAT_Icon.paa); | |||
magazines[] = { | |||
"Titan_AT" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does make them be able to load the magazines, doesn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if you have it (the weapon bag) equipped, you can drag a mag to it, but nothing happens.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's terrible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a Titan/Spike AT, i guess its pretty obvious what kind of mag you need for it, but adding compatible mags to the array is the only way to know what ammo you need for the weapon. Otherwise you have to scroll through the "All Magazines" list and pray you pick up the right one.
We can remove them, but the convenience of having the compatible mags listed under Magazines maybe outweighs the fact you can "placebo load" the weapon with them ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe consider adding custom properties for magwells and magazine classes. Content of these properties could be read by ACE Arsenal and shown on the magazine list.
I did, of course. With the RHS paths, the icon/picture shows up in the arsenal ok, but when you exit and look in your inventory, the error pops up and the launcher slot is blank. |
Does the picture error happen in the release version of ACE? |
I don't understand what |
Yepp, just tested with SW versions ACE + USAF/AFRF/GREF + compats: Equipped a
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Correct, did a boo boo there. Looked at the wrong classes. The actual static weapons that has a corresponding vehicle for them have 65535. Will remove those declarations. |
Most of the requested changes done now. Added a Image now shows in player inventory without any errors .... |
Without ACE CSW static weapons are available as backpack variants, I see no reason to not have launcher slot variants in it too. Otherwise to get launcher slot variants you would need to assemble backpack versions and disassemble them via CSW to get them. Ideally you would have backpack versions in arsenal when CSW is disabled and opposite if enabled. |
RHS will rip your ass up and potentially cause issues for us if you do that. So no no no no no.
yes. Definitely. Please do that, right now the RHS icons are still in history. Should be fine if we just squash&merge at the end though, if author doesn't want to fix it. |
Would you like me to remove the mag. defs. and just keep the other fixes, or just rebase as is ? |
@Whigital I would say remove the mag defs for right now. I'll take a look at ACE Arsenal to try and find a way to have compatible magazines show up if you have the launcher equipped, but being able to drag magazines into the launcher slot is hacky and I just don't like it |
9e99dae
to
0b4a38d
Compare
There we go, squashed, baked and magazines gone. |
Can you explain why: class MuzzleSlot {
iconScale = 0.1;
}; works? Why list iconScale at all? |
Basically just to trick the engine into using the weapon picture instead of looking for alternatives based on slots: https://community.bistudio.com/wiki/Arma_3_Weapon_Config_Guidelines#Inventory_icons_overlay_method
From what i could gather, the picture error is based on the engine looking for a picture with Can add the other slots and use an empty picture for them if it makes more sense. |
It wouldn't make more sense to add the other entries, however, I think this warrants a comment in the source code. |
Maybe add a macro for that class (
|
Not sure about macro. It would be enough if the first occurance in the config is commented. I'd chose a better comment though, i.e.:
FAKE_MUZZLE_SLOT is a poor name, imo. One should use the self documenting possibilities when chosing a macro name. I.e. FIX_INVENTORY_ICON; |
When merged this pull request will:
ace_csw
:ace_compat_rhs_usf3
/ace_compat_rhs_afrf3
/ace_compat_rhs_gref3
:WeaponSlotsInfo
to get rid of error picture error when opening inventory.rhs_SPG9_INS
instead ofrhsgref_ins_SPG9
forace_compat_rhs_afrf3_spg9_carry
.ACE_CSW
inheritance onace_compat_rhs_afrf3_spg9m_carry
.