Mass close.

Mass close.

Mass close.

Mass closing resolved issues not updated since November.

Mass closing resolved tickets from last month.

Mass closing resolved tickets from last month.

Seen this one a bit late, already had #11360 assigned.

Mass-closing resolved issues not updated in 10 days.

Mass close.

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.

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.

Mass close.

Mass close.

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 close.

Btw. I still have the problem, reproducable always. It's not a tragedy and easily fixed and could as well be related to my old joystick (even though I believe the model hasn't been changed ever since, I may be wrong).

Realized that Z-axis is used in Control Panel for rotation axis and what I meant is called "Slider" (also with + and - though). Fixed description and title accordingly.

Mass close.

Mass close.

Mass close.

I believe this was fixed, please confirm?

Could you please update the ticket with new repro steps or repro mission and remove outdated information?

I believe this issue has been revisited by the developers since. Still occurring?

Just verified in 1.18, it's still happening.

I'm sorry, this feature request is way too overloaded and barely anyone will be looking at this and IF they're looking at this, they won't be able to process it accordingly.

Also, by looking through the different suggestions, you completely change how the game was designed for. You should be getting accustomed to the game for a longer time, some of your suggestions seem redundant and already implemented, e.g. the group system already works that way, that automatically within a rank hierarchy, groups are split into teams automagically.

Then come again and write up tickets for each of your suggestions which are still valid, only combine those who are specific to the same function.

nvm - just seen it's fine

Outdated. Open a new ticket if new issues arise.

Done.

Yes, there were map tools in ACE2. You had to add the item to your inventory.

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 close.

Mass close.

Mass close.

Outdated. Open a new ticket if new issues arise.

Mass close.

Mass close.

Mass closing resolved tickets from last month.

Mass close.

Mass close.

Outdated. Open a new ticket if new issues arise.

Mass close.

Mass close.

Mass close.

Fixed, I believe.

Mass closing resolved issues not updated since November.

Mass close.

Mass closing resolved tickets from last month.

Mass close.

Mass close.

Mass close.

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 close.

Mass close.

It shouldn't stay that long, but if the infantry unit is never killed and you didn't spot it again (to update the true location) or at least confirm that it's in fact NOT there, it should disappear/update.

It's basically by design. If you can reproduce the issue, and show that it's not disappearing even if you're on the spot of the marker, please tell exactly how (step by step) and best use a simple editor mission as proof-of-concept (e.g. one AI, one player).

Mass closing resolved issues not updated since November.

Outdated. Open a new ticket if new issues arise.

Mass closing resolved tickets from last month.

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.

Marking resolved then.

Please do not mix different issues. Mines revealing you as a player is very different from the original issue.

If there are any remaining issues, please open a new ticket for each. Closing down.

Are you sure, that they don't see you moving in that direction, before they lose line of sight?

I just tried this as a BLUFOR sniper at 500m:

1. against 3 OPFOR default Riflemen in a group (skill 0.5)
2. against a default OPFOR Riflesquad (group placement, different skills)

in case of

1. they didn't find me when I was prone, when I got up and kept on shooting the one I left alive was just looking at me (beyond engagement range without scope)

2. after one kill in their lines and after a couple more shots just around them to get their attention only, eventually those units with a scope would open fire on me and were very inaccurate, as their skill suggested

So I consider this fixed. Anything else is probably still caused by #12669.

It's funny, when they're not yelling, half of the community complains that the radio voice-overs are "kitchen table recordings", which inhibits immersion.

And now they're intense, you complain they should be calmer.

For that reason, I like them how they are. :-)

Mass close.

Mass close.

Mass close.

Mass close.

Outdated. Open a new ticket if new issues arise.

Mass closing resolved tickets from last month.

Mass closing resolved tickets from last month.

Outdated. Open a new ticket if new issues arise.

Mass close.

Mass close.

Mass close.

rogerx: What "internal influence"? I'm not BI, I'm doing this on my own spare time.

sofianebilal: Go outside (preferably in a rural area) at a full moon lit night, and you won't need NVG. Use military-grade binoculars and the light will be even be amplified. But the ticket was about achieving pitch black night, and this is currently possible, specifically in moonless nights.

Thanks Gugla.

rogerx, you apparently don't seem to grasp what I'm saying. Night sky brightness is not the focus of this ticket, the original description only involves the night time visibility (ground lighting).

The sky brightness is a sort of "ticket-hijack". Please consider my two options.

My main issue is, that the issue what you acclaim does not represent what was written by FerarCircus in first place, in the original ticket description.

I give you two options

1. stick with #12717 and improve it
2. create a new ticket with the description similar to what rogerx wrote (maybe a bit shorter, the elaborate text in additional info)

Because the creator of the ticket said it looks good now. I share his opinion.

Maybe you and the OP don't speak of the same thing.

For me it looks alright right now. Can we resolve the ticket?

Thanks.

I can get a pitch black environment again (not that I like it, but it works)...can you confirm?

Resolved according to reporter.

Mass closing resolved issues not updated since November.

Mass close.

Outdated. Open a new ticket if new issues arise.

Thanks.

Outdated. Open a new ticket if new issues arise.

Outdated. Open a new ticket if new issues arise.

Mass close.

Mass close.

Thanks for the feedback, closing down.

Could this be related to the Saitek profiler software? Can you try without the software once?

Mass close.

Thanks.

I believe it's resolved or at least better in the current dev build, isn't it? I think you can turn off/tone down the blur which is currently used for fatigue.