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

AI can't fire mortars when ammo handling is enabled #6173

Open
Cyruz143 opened this issue Mar 1, 2018 · 9 comments
Open

AI can't fire mortars when ammo handling is enabled #6173

Cyruz143 opened this issue Mar 1, 2018 · 9 comments
Assignees
Milestone

Comments

@Cyruz143
Copy link
Contributor

Cyruz143 commented Mar 1, 2018

Arma 3 Version: 1.80 (stable)
CBA Version: 3.6.0 (stable)
ACE3 Version: 3.12.1 (stable)

Mods:

- CBA_A3
- ace

Description:

  • In the CBA settings having force force ace_mk6mortar_useAmmoHandling = true; breaks AI using mortars.

Steps to reproduce:

test_mortar_fnc = {
    params ["_unit","_target"]
    private _mortar = vehicle _unit;

    if (_target inRangeOfArtillery [[_unit], "8Rnd_82mm_Mo_shells"] ) then {
        _mortar setVehicleAmmoDef 1;
        _mortar setVehicleAmmo 1;
        _unit doArtilleryFire [_target, "8Rnd_82mm_Mo_shells", 3];
        diag_log format ["MORTARS -- %1 firing at %2", _unit, _target];
        systemChat format ["MORTARS -- %1 firing at %2", _unit, _target];
        uiSleep 15;
    } else {
        diag_log format ["MORTARS -- %2 out of range of %1", _unit, _target];
        systemChat format ["MORTARS -- %2 out of range of %1", _unit, _target];
        uiSleep 15;
    };
};

[mortarGunner, getMarkerPos "testTarget"] spawn test_mortar_fnc;

Drop that in init.sqf, place a vanilla unit named mortarGunner on a vanilla mortar and put a marker down called testTarget.

Where did the issue occur?

  • Editor (Singleplayer)

CBA Settings:

Was previously set to force force ace_mk6mortar_useAmmoHandling = true;

RPT log file:

  • Doesn't log anything other than the logging I've provided in the test function.

Workaround

  • Changed CBA setting to force ace_mk6mortar_useAmmoHandling = true; and in the mission file itself I created a cba_settings.sqf with force ace_mk6mortar_useAmmoHandling = false;. Although this means players can't use the feature when AI need to use mortars so it's not great.
@MisterHLunaticwraith
Copy link

Same issue is true for disable artillery computer.

@stale
Copy link

stale bot commented Nov 18, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale label Nov 18, 2018
@dedmen
Copy link
Contributor

dedmen commented Nov 18, 2018

Still an issue? I think there was once a PR to fix this? Not sure.
If it's still a thing it should be labeled as bug.

@Tanin69
Copy link

Tanin69 commented Dec 8, 2018

Issue still occurs with Arma 1.88 and ACE 3.12.5. Didn't find any workaround

@Cyruz143
Copy link
Contributor Author

Cyruz143 commented Dec 10, 2018

Issue still occurs with Arma 1.88 and ACE 3.12.5. Didn't find any workaround

The workaround is in my initial report but means it's either you have manual ammo handling or the AI can fire mortars, but not both.

@Tanin69
Copy link

Tanin69 commented Dec 10, 2018

I saw your workaround Cyruz143. But, as you wrote, it doesn't work if you want to use manual handling AND AI mortar...

@genjonakasone
Copy link

Any progress on that? It's really annoying to be unable to turn that off. force ace_mk6mortar_useAmmoHandling = false just doesn't work.

@Spiretail
Copy link

Any progress on this again? This still completely breaks AmmoHandling if you are just using it in PvE missions and want Mk6 like mortars to work for the AI, quite frustrating this is nearly 5 years old now too.

@LinkIsGrim
Copy link
Contributor

LinkIsGrim commented Jul 13, 2023

Partially addressed by #9258. Full fix in #9238.

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

No branches or pull requests

10 participants