Page MenuHomeFeedback Tracker

Optics mil-dot spacing is incorrect
New, WishlistPublic


The observed angle of targets calculated by mil-dots on vanilla weapon scopes is higher than expected, breaking stadiametric rangefinding capabilities.


Legacy ID
Operating System
Windows 7 x64
Steps To Reproduce
  1. Start singleplayer editor.
  2. Place down a player-sniper unit, and a 1mx1m VR cube 250m from the player
  3. Observe the apparent angle of the target with your scope's mil-dots
  4. Observe that the object does not measure 4 mil on your scope like it should
Additional Information

Target size (metres) = s
Target distance (metres) = d
Observed angle of target (mil) = a

Calculating range: d = s*1000/a

At 250m, a 1m object should measure 4 mils:
s = 1
d = 250

The behaviour is consistent across all scopes I tested:

Event Timeline

Sniper_Party edited Additional Information. (Show Details)
Sniper_Party set Category to Visual-Weapons.
Sniper_Party set Reproducibility to Always.
Sniper_Party set Severity to None.
Sniper_Party set Resolution to Open.
Sniper_Party set Legacy ID to 148005752.May 8 2016, 11:55 AM
Vitdom added a subscriber: Vitdom.May 8 2016, 11:55 AM

After exact pixel-measurement, I found the soldier at 300m range to fill an angle of 6.54 mildots. I have attached the sample picture to this issue. Using your formula, s = d*a/1000:

300 * 6.54 / 1000 = 1.96 m

In my opinion, this is a realistic size of the Target size.

I found the soldier at 600m range to fill an angle of 3.27 mildots. This yields 600 * 3.27 / 1000 = 1.96 m.

So my conclusion is that the mildot angle spacing in the video is very accurate, consistent and realistic.

Size is consistent, but every single soldier being 1,96m tall is extremely unrealistic, even if the mil-dots are correct and the issue is with the size of the models.

I haven't got a primary source but according to this thread the soldier height should be 1,82m "according to samples released".

Thank you for the exact measurements. In my opinion they serve to highlight the issue instead of writing it off.

Unit is 1.83m tall in the standard T-pose (legs slightly apart) without a helmet. Height will differ slightly depending on animation and headgear.

If you want to check the mil-spacing properly, use the 1m x 1m User Texture object in the editor. I've always found that the BIS scopes are well calibrated to this object, as are some community addons like RHS's Leupold scopes, and I use it myself to calibrate mildots on my own scope reticles.

Use this setObjectTexture [0,"#(rgb,8,8,3)color(1,0,0,1)"]; in the initline to make it a perfect 1m x 1m red square that you can see. You can set the range from your player using getpos/setpos to set precise values from the point where you're standing. IIRC the Rangefinder only works to the nearest meter, so you can get some discrepancies in terms of cm scale accuracy.

Oh thanks, da12thMonkey, I had not thought about using the 1mx1m object. The observed angle of the object should, at 250m, be 4mil:

a = s*1000/d

s = 1
d = 250

a = 1*1000/250
a = 4

This is what it looks like to me:

You can clearly see the target size does not match what it is supposed to be.

EDIT: attached picture for easier access

Aye, I just re-checked myself with the VR 1m Cube obstacle instead of the User Texture object (never thought to use that one before, but it's probably easier since you don't need to setobjecttexture to make the cube visible).

You're right: the objects observed through most BIS sniper scopes seem to be about 1/8th bigger than the size they should be (1.125 scale), so the 1m cube spans 4.5 mils @ 250m instead of 4.0 mils, 2.25 mils @ 500m instead of 2.0 mils, 1.125 mils @ 1000m instead of 1.0 mils, etc. etc.

I was certain that the LRPS and MOS had properly scaled reticles recently, but I think BIS has tweaked the FOV/magnification values slightly since then, to standardise magnification values between scopes prior to releasing Marksmen.

BIS could solve it by scaling the affected reticle textures by a factor of 9/8 (1.125) or increasing the FOV by the same factor, in the config for those afflicted scopes.

Thankfully my own scopes are still perfectly scaled :D

I can see it now. Apparently they've changed the FOV-zoom of the optical sights, so that the mildot spacings are improperly scaled.

This should be simple to fix, either scale the optics' zoom-FOV or extend the optics's distance from the screen.

Sniper_Party updated the task description. (Show Details)Jul 12 2016, 7:09 AM
Sniper_Party edited Steps To Reproduce. (Show Details)
Sniper_Party edited Additional Information. (Show Details)
Sniper_Party set Operating System to Windows 7 x64.
Sniper_Party updated the task description. (Show Details)Jul 12 2016, 7:14 AM
Sniper_Party changed Severity from None to Minor.
Sniper_Party edited Additional Information. (Show Details)

Updating with recent pictures and to confirm issue still exists.

m1croN added a subscriber: m1croN.Aug 13 2016, 5:44 PM

Confirming the issue as well.

Confirming the issue as well

Confirming the issue as well.

Wololo added a subscriber: Wololo.Aug 13 2016, 9:26 PM

The problem still persists.

Still an issue

razy added a subscriber: razy.Aug 13 2016, 11:30 PM

Same here.

Defenettly an issue. I believe It is the worst bag of A3.

Sniper_Party changed Severity from Minor to Major.Mar 14 2018, 8:03 PM

Confirming that this is still an issue.

Jukk added a comment.Mar 14 2018, 8:11 PM

Confirming, just tested on the latest dev build 1.83.144470