Page MenuHomeFeedback Tracker

Iron Sights of some weapons are off target
Closed, ResolvedPublic

Description

Dear Developers,

I have to report an issue that I recently found with a few iron sights of the weapons in the game.
A few weeks ago I found an issue with the Zafir's iron sights that the shots were going high all the time. I guess that the iron sight is not properly centered and therefore too low.

The Zafir is actually not the only weapon having these issues, that cause the weapon to reliably miss their intended target on all ranges when zeroed correctly.

This issue is not a problem at all if any sight item is used on the weapon. It is just the iron sight model that seems to be off.

I found a way to highlight the issue using the laser attachment. The laser pretty much always points directle to the middle of the screen and the shot will pretty much perfectly hit the laser spot when zeroed correctly. So the sight should be exactly on the spot.

Here is a list of weapons where the sight is severely off:

MX - sight too low
MXM - sight too low (but less than MX)
Rahim - sight too low
Sting 9mm - sight too low
Zafir - sight too low
Protector 9mm - sight too high
SPAR16 - sight too high (and covers too much of the picture anyway for a tactical sight imho)
SPAR17 - sight too high (and covers too much of the picture anyway for a tactical sight imho)

This is an annoying issue since you practically can not rely on your weapons sights. Since this is kinda important in a combat situation this should be fixed.

Please Developers, take the weapons to the table and fine tune the sights so they are on target.

Thanks in advance

David / Venator

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Category
General
Steps To Reproduce

Use any of

MX
MXM
Rahim
Sting
Zafir
Protector
SPAR16
SPAR17

without optic item and try hitting targets

Event Timeline

Wulf closed this task as Resolved.Jun 10 2020, 2:50 PM
Wulf claimed this task.
Wulf added a subscriber: Wulf.

This should be fixed in the next Dev branch update.