Please provide the following when creating the Ticket:
Game Version number: 1.3.0.84
Modded?: (No)
If modded, please list the mods:
Issue Description:
Feedback regarding the implementation of nameplates to binoculars. In short: BIG dislike!
Description
Description
Details
Details
- Severity
- None
- Resolution
- Open
- Reproducibility
- N/A
- Operating System
- Windows 10 x64
- Operating System Version
- 2H32
- Category
- General
Steps To Reproduce
Players can now use binoculars to observe teammates up to 150(?) metres.
Additional Information
I admire and enjoy Arma Reforger for its show-not-tell approach to gameplay; I find this is antithetical to what I adore about the game. We are already provided with a show of who our teammates by the distinct camouflage each army wears, and needn't rely on UI elements to tell us this at the binocular's distances.
Furthermore, having engagements slowed down slightly by having to ID-check targets is a great element of tactical/strategic gameplay, and can provide a fun spontaneous micro-task when needing to get closer to confirm whether it may be an enemy in disguise.
Whilst I think it would be a good idea for this to be a server option that private servers may wish to enable, I would much rather it was not part of the default vanilla experience. Show, not tell!
Related Objects
Related Objects
- Duplicates Merged Here
- T189903: Nameplates still visible in binos/scopes
Event Timeline
Comment Actions
According to the 1.3.0.102 change log, this may be a bug report and not new feature feedback:
Fixed: Nametags rendering further away if using optics/binoculars
If this is the case, this change was not actually included in the 1.3.0.102 release, as nametags are still rendering farther away when using optics/binos. Here's a quick clip of when I tested yesterday just after the latest patch:
https://www.twitch.tv/it_is_sunshine/clip/TangentialCrepuscularAdminNotLikeThis-EUYUOosPlrHBKRbT
Comment Actions
@Geez - for visibility on this. This is still occurring in live v1.3.
The bug report was merged with this feedback ticket, wonder if it may have fallen under the radar because of that? Pretty sure this is a bug due to the patch notes quoted on the other ticket, but let me know if it's actually intended.
Comment Actions
1.3.0.144: this issue is still present - I think it might be getting lost at this point as it was marked as fixed in the 1.3.0.102 changelog, which was multiple patches ago.