You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arma 3 Version:1.70 (stable) CBA Version:3.3.1 (stable / dev + commit hash) ACE3 Version:3.9.1 (stable / dev + commit hash)
Mods:
Doesn't matter
Description:
Fuel hose is too short/not changeable via config option. Same thing with Rearm function.
Steps to reproduce:
Walk off with fuel nozzle, wait for too long message to occur
Where did the issue occur?
Everywhere
As noted in Slack, Fuel Hose length is statically set and not a problem normally, is becoming serious issue on with new Jets DLC due to limited size of carrier and size of the Jets.
Similar but not as serious problem is rearm distance.
Resolution:
It would be nice to allow this to be set globally. Wishlist would be set per vehicle/static object. Easy fix but not as satisfying would be ACE just change it from 12 to something like 30-40.
This was noted in Slack #Help channel that others were experiencing similar issues.
The text was updated successfully, but these errors were encountered:
Arma 3 Version:
1.70
(stable)CBA Version:
3.3.1
(stable / dev + commit hash)ACE3 Version:
3.9.1
(stable / dev + commit hash)Mods:
Doesn't matter
Description:
Fuel hose is too short/not changeable via config option. Same thing with Rearm function.
Steps to reproduce:
Walk off with fuel nozzle, wait for too long message to occur
Where did the issue occur?
Everywhere
As noted in Slack, Fuel Hose length is statically set and not a problem normally, is becoming serious issue on with new Jets DLC due to limited size of carrier and size of the Jets.
Similar but not as serious problem is rearm distance.
Resolution:
It would be nice to allow this to be set globally. Wishlist would be set per vehicle/static object. Easy fix but not as satisfying would be ACE just change it from 12 to something like 30-40.
This was noted in Slack #Help channel that others were experiencing similar issues.
The text was updated successfully, but these errors were encountered: