Skip to content
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

RHS Jerry Can WATER issues #8710

Closed
Rockfrog opened this issue Nov 28, 2021 · 3 comments · Fixed by #8717
Closed

RHS Jerry Can WATER issues #8710

Rockfrog opened this issue Nov 28, 2021 · 3 comments · Fixed by #8717
Labels

Comments

@Rockfrog
Copy link

Rockfrog commented Nov 28, 2021

Mods (complete and add to the following information):

  • Arma 3: 2.06.148470
  • CBA: 3.15.6.211004
  • ACE3: 3.14.1.65
  • RHS: United States Forces: 0.5.6
  • ACE Compat - RHS USAF: 3.14.1

Description:

  • rhsusf_props_ScepterMWC_OD (RHS WATER jerry can OLIVE)
  • rhsusf_props_ScepterMWC_D (RHS WATER jerry can TAN)

How to carry items is unclear/misleading (regular drag/carry options do not appear), interactions are not consistent.

WITHOUT CHANGING item ACE Options in Eden:

  1. Items are not pre-configured as 20L water holding items unlike other hydration devices (water bottles etc)
  2. In order to carry RHS Water Jerry cans: ACE Interactions > Refuel > Take Fuel Nozzle ... is very confusing for grunts, not even Marines drink fuel :)
  3. Cannot select any ACE water interactions

CHANGING item ACE Options in Eden to Water Supply 20:

  1. ACE Refuel & Water interactions now overlayed on one another, requiring lots of mousing over to try and get the right interaction to pop depending on need to carry items (take fuel nozzle...), or utilise ACE water interactions.

Steps to reproduce:

  1. Launch Arma with only CBA, ACE3, RHS USAF, ACE Compat RHS USAF
  2. Create a new mission, place a unit and a Things>Tool>Jerry Can (Water)
  3. Load mission
  4. Interact with Jerry Can Water

Expected behavior:

  1. Items should be pre-configured as 20L water devices without editting (as other water devices)
  2. Carrying or dragging devices should be more logically accessed and named/titled
  3. Carrying & water use interactions should not overlay in the same 'space'

Where did the issue occur?

  • Dedicated / Self-Hosted Multiplayer / Singleplayer / Editor (Singleplayer) / Editor (Multiplayer)

Screenshots:
Stock items are not pre-configured water supply devices:
107410_20211128141101_1

Carry devices is confusing/misleading:
107410_20211128141029_1

Adding 20L water:
107410_20211128141112_1

ACE fuel device and ACE water device interactions overlaying on one another:
107410_20211128141135_1

Repetitively mousing on and off can eventually get you to the Water Source options:
107410_20211128141144_1

Repetitively mousing on and off can eventually get you to the "carrying" options (take fuel nozzle):
107410_20211128141152_1

@Drofseh
Copy link
Contributor

Drofseh commented Nov 28, 2021

I'd recommend not adding fuel and water to the same jerry can (-1 fuel is infinite fuel iirc).
This does say water on the side though, so should probably have the fuel removed in the compat.

@Rockfrog
Copy link
Author

Rockfrog commented Nov 29, 2021

I did not add both fuel and water to the same can, unsure how you came to that conclusion?

-1 is disabled, -10 is infinite, for both fuel or water, per my screenies above. At least according to the tooltip.....

By default both fuel and water jerry cans are set to -1 disabled in both categories, however... the fuel jerry cans clearly have fuel in them, despite having a -1 disabled value. You just can't check the fuel remaining, it's like they're fuel items with fuel but apparently without fuel.

@Drofseh
Copy link
Contributor

Drofseh commented Nov 29, 2021

Oh my mistake, I was thinking that -1 was both infinite and accidentally the default for that object.
Either way, the fuel actions will need to be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants