Mass-closing resolved issues not updated in 10 days.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

Mass-closing resolved issues not updated in 10 days.

This is in Arma since OA:

http://www.bistudio.com/english/company/developers-blog/85-breaking-the-32-bit-barrier

Closing as fixed. For new issues create new tickets, as directed above.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

This might not be for japa, if it's a config error.

Mass closing resolved tickets from last month.

Problem is that you don't pay attention, build 110387 is not released yet, current is 110339.

Marking resolved then, feedback still possible.

Dupe of #9688.

Mass closing resolved tickets from last month.

Mass closing resolved tickets from last month.

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

Mass closing resolved tickets from last month.

Dupe of #4020.

Mass closing resolved issues not updated since November.

Mass closing resolved issues not updated since November.

mepwaygame, is this in stable or dev build?

For me in dev build it seems to be more reliable.

As soon the UAV reached the waypoint you set, you'll be able to control it fully. I believe the only problem is, that you cannot cancel the waypoint.

It should probably cancel the waypoint too, as soon you take control of the UAV.

How is it as of today?

Peter, actually since Steam the data changes (such as config) should be applied immediately.

Hence, if something is broken, we need to have it looked at asap.

But are we sure that it is broken in the game and not simply a class rename which needs to be corrected in the addon/missions?

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved tickets from last month.

Mass-closing resolved issues not updated in 10 days.

Marking resolved as per update.

Mass closing resolved tickets from last month.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Added additional info.

Since it's upon releasing controls, there is not much a key binding can do.

Mass closing resolved tickets from last month.

Mass closing resolved tickets from last month.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved tickets from last month.

Mass closing resolved issues not updated since November.

Mass-closing resolved issues not updated in 10 days.

I believe you should be able to "pick up" the terminals from dead units by recent script fixes now.

EDIT: If it's still bugged please make a new ticket!

Mass-closing resolved issues not updated in 10 days.

Mass-close of resolved tickets not updated in last two weeks.

Mass-close of resolved tickets not updated in last two weeks.

Mass closing resolved issues not updated since November.

Mass closing resolved issues not updated since November.

Mass closing resolved tickets from last month.

Now it's clear to me, thanks.

I wonder if such a mission/setup is a valid use case for aerial vehicles of any type; I can't think of any valid reason to have those UAVs starting 100 m apart, heading towards eachother, at the beginning of the mission.

Same issue exists with any type of aircraft, btw.

Cheers.

Marking resolved. Please protest if the issue still exists.

I think this should be resolved too, in dev build. Please confirm.

Caused by #12128?

Mass-closing resolved issues not updated in 10 days.

Fixed, as far I tested.

Mass closing resolved tickets from last month.

Mass-closing resolved issues not updated in 10 days.

Mass closing resolved issues not updated since November.

Mass-close of resolved tickets not updated in last two weeks.

Mass closing resolved issues not updated since November.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Solved?

Mass-closing resolved issues not updated in 10 days.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass-closing resolved issues not updated in 10 days.

Excellent

Fixed?

Mass closing resolved issues not updated since November.

Mass closing resolved tickets from last month.

Mass closing resolved tickets from last month.

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.

Mass closing resolved tickets from last month.

Closing in favor of the assigned ticket.

Thanks!

Two things:

• Can you check on latest development build (you specified stable build in the ticket)?
• *removed, should read the entire ticket before commenting*

What you guys really want is dynamic destruction. I believe there is no "patchwork" style for a damage model you would expect.

This already happens, depending on the velocity of the crash.

Looks like I read only what I thought. Apologies.

Which would, on the other hand, remove the ability to choose directly which ammo type you wish to load.

But it would be a small step toward #10726.

EDIT: Since a reload of different ammo type is connected with a reload animation, it's probably not such a good idea, needing to cycle through different ammo types by hitting e.g. Ctrl-R multiple times.

Let's say this is a dupe of #8233 (or a part of it).

I think this is a dupe with #8799. Unless it's a complaint about the new flinch animations (which are to be corrected anyway, according to dev branch CL).

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Mass-closing resolved issues updated only last year - assuming fixed correctly.

Cheers!

Sorry, I should have been clear, that this ticket is about multiplayer.

I'll attach a repro mission.

EDIT: Mission file attached, repro works for me in SP and MP.

If this is not the true skill of the AI, then it would be interesting to know how to visualize it - else we have no chance of knowing what the effective skill is.

It's neither a feature request nor a bug, but it's worthwhile.

Not sure if it's supposed to be category "Feature Ticket" rather, but it's a bit of both.

Mass-close of resolved tickets not updated in last two weeks.

No crash for me here.

Reopening, the other ticket pertains to GL flares, there is illumination.

http://forums.bistudio.com - what plutoto74 said.

Mass closing resolved tickets from last month.

Do you realize, as of with vanilla, magazines are not discarded unless really empty? So if you do tactical reloads all the time, there be no magazines discarded.

And with sleeves you probably mean 'cases' (as in 'envelope of a projectile'), probably.

Edited for better readability.

Mass closing resolved tickets from last month.

One issue/request per ticket, plus we have already other tickets who ask for engine volume to be reduced.

Try to make useful tickets and suggest exactly on which vehicle(s) and why.

Mass closing resolved issues not updated since November.

Dupe of #12524