Mass-closing resolved issues updated only last year - assuming fixed correctly.
Cheers!
Mass-closing resolved issues updated only last year - assuming fixed correctly.
Cheers!
Mass closing resolved issues not updated since November.
Could repro.
Dupe of #9319.
Confirming, nothing changed there.
Mass closing resolved issues not updated since November.
Mass-closing resolved issues updated only last year - assuming fixed correctly.
Cheers!
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.
Feedback timeout.
The fact that you changed/upgraded hardware indicates to me that there must be an issue with your components or drivers.
Try the BI forums if you need additional support (http://forums.bistudio.com).
Mass-close of resolved tickets not updated in last two weeks.
Mass closing resolved issues not updated since November.
Mass-close of resolved tickets not updated in last two weeks.
Mass-close of resolved tickets not updated in last two weeks.
Dupe of #16188
As long we don't have committed community members re-testing everything immediately after something's announced resolved, I'll go down the path and resolve tickets immediately.
Many times there will be no feedback and tickets remain open indefinitely, if they're on "feedback". But if they're "resolved" and receive no feedback, we can safely assume that they're fixed for good and I will close them routinely using mass-close functions.
No worries, I'll monitor those tickets I set to resolved. I kindly ask you not to interfere by setting around states at will. George told you that the build isn't out yet, but the bug is supposedly resolved.
I'm always resolving based on developer/CL statements. You can still give feedback, but only if you're polite (hint!).
OTOH I'm only closing it, if it's confirmed.
Resolved according to Dev CL.
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.
I'll call it resolved until proven otherwise. Feedback is still possible.
Mass closing resolved issues not updated since November.
Dupe of #16188
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Mass-close of resolved tickets not updated in last two weeks.
You mention a specific mission, King of the Hill. I assume you hear players using direct chat or simply their radio channels. Also, as far I know there is no AI in this mission.
Please only report one issue per ticket and make sure it's not community-mission specific.
Mass-closing resolved issues updated only last year - assuming fixed correctly.
Cheers!
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.
Got it. I tried teamswitch after dying, this works, but through the map -> team -> team switch on soldier doesn't work.
Hmm, works for me. You know that you can only use the Teamswitch button when a unit is marked playable?
Mass closing resolved issues not updated since November.
High Command was only ever meant to command multiple squads, while you usually only control your own squad, so always enabling High Command view would make no sense, sorry.
That said assigning team colors isn't purely visual, you can quick-select those with Shift-Fx key (F1 being red and up to F4 being the last color, if I remember correctly). Then you also can go to the map and use clicks to send the colored teams to places.
Mass closing resolved issues not updated since November.
Removed redundant and personal information from ticket.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Mass-close of resolved tickets not updated in last two weeks.
Dupe of #7805.
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.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Dupe of #15404. Apologies for the title - it might not be identified with the issue of deploying it on the roof. But it also happens when you put it on a edge somewhere on the floor.
Mass closing resolved issues not updated since November.
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.
Dupe of #13648.
Mass closing resolved issues not updated since November.
Updated ticket. Still persists with 1.06 stable.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Jep, I was wondering about that too, no reason for them not to shoot down on the buggars with that 30mm.
I'd rather replace those Mi's with some transport chopper.
EDIT: I mean it's okay if they just rush over the survivors' heads since they might not have spotted them or have a different order, but if they land in front of them just to unload a couple soldiers, it seems quite hilarious.
Dupe of #15857.
Dupe of #8799.
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.
Confirmed, still an issue in stable, in dev 1.09 doArtilleryFire seems completely broken! :-o
What's the status of this? Today some material tweaks have been announced in the dev build changelog.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Also, make sure you kill the savegame, if there's any.
Closing since noone was able to repro.
Maybe you should also try flicking the mouse-wheel and check for "get in" actions, since sometimes action icons don't show up when approaching, for whatever reason.
If there's still an issue for you, try seeking help at the BI Forums: http://forums.bistudio.com
Dupe of #15755.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Cannot repro anymore, looks like the fix came with a delay.
Resolved according to dev build changelog.
Mass-closing resolved issues updated only last year - assuming fixed correctly.
Cheers!
Mass closing resolved issues not updated since November.
Apparently not yet fixed.
Mass closing resolved issues not updated since November.
Note that Zipper5 said "fixed as of the latest dev branch". Please be patient and standby for upcoming stable (I suspect by tommorow or Thursday).
Added keyword Combat Life Saver to title, so searches on that will hit on this ticket too, the term "medic" remains in description
Mass closing resolved issues not updated since November.
Mass-closing resolved issues updated only last year - assuming fixed correctly.
Cheers!
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Going for unable to repro.
Yeah, I've encountered this too, and it's very random and very seldom too and not related to the mission.
It seems like the group leader is unwilling to execute the waypoint action for some reason.
Reverting helps.
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.
I agree with your assessment that they're too good at firing flares, OTOH in my tests every second missile did hit the target regardless of the pilot flaring. Maybe I was just lucky, though.
I don't like the original ticket #10249 in terms of quality, but it's assigned and being worked on.
Mass closing resolved issues not updated since November.
Marking resolved then.
Mass closing resolved issues not updated since November.
Can you attach the pictures and a repro mission to this ticket?
Still an issue?
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Mass closing resolved issues not updated since November.
Apparently extended armor is only for players, not for AI.
I was always wondering why AI repeatedly takes 3-5 rifle rounds without even flinching. The cause is different.
Mass-closing resolved issues not updated in 10 days.