Page MenuHomeFeedback Tracker

0.59 Experimental - Hunting Scope ADS Overlay Incorrect Proportions
Closed, ResolvedPublic

Description

The Hunting Scope appears squished on my screen. Rather than the normal circle that one would see when looking through the scope, I see an oval. See attached photo. {F32818}

Details

Legacy ID
255831317
Severity
None
Resolution
Duplicate
Reproducibility
Have Not Tried

Event Timeline

ColdAtrophy set Category to category:weapons.Nov 3 2015, 9:52 PM
ColdAtrophy set Reproducibility to Have Not Tried.
ColdAtrophy set Severity to None.
ColdAtrophy set Resolution to Duplicate.
ColdAtrophy set Legacy ID to 255831317.May 8 2016, 11:59 PM

i think 0.59 has some issues with aspect ratio, did you check that?

No I didn't. The thing is, the image itself isn't distorted or out of proportion. It's only the scope overlay. I will check the settings and see what it looks like under Aspect Ratio.

EDIT: I have no available options under Aspect Ratio. Definitely messed up there. It stands to reason that this issue may be tied with that, but my game is not producing weirdly proportioned images in any other circumstance that I can find thus far. Also, Tatanko said that his scope was rendering normally so I know that this issue is not universal.

Gekker added a subscriber: Gekker.May 8 2016, 11:59 PM

My scope has the same issue. I got a damaged Hunting Scope on my Blaze and it has an oval shape, squished in in its width.

Double checked my aspect ratio as well. Tried out different resolutions. The issue persists.

Additionaly the iron sights of my MP5 is not lined up with my line of sight. I cannot see the nose sight attachment when i look through the iron sight. Haven't checked yet if the aiming is off due to that though. No idea if its related or not.

Hmmm. My Hunting Scope is damaged as well. Might be a good place to start looking for the cause. Perhaps a Worn or Pristine one would not be out of whack?

Geez added a comment.Nov 4 2015, 12:41 PM

Hello ColdAtrophy and thank you for the report.
This is a known issue (#0028405) and it has been scheduled for a fix.
Regards,
Geez