Halo: The Master Chief Collection / Halo: Reach

3 hours ago, Quasar36 said:

I've been testing around different sens for some clip lineups.

I tried sens 4.977720 using cheat engine because according to the calculator it should give me 2pixels/count at 86fov. I looked at a specific pixel and did a 360 spin to see if I could still line it up but it didn't work, it would always shift 1 pixel after doing a 360. If I instead use 5 with cheat engine or ingame, I can line it up after every spin.

Either I'm doing something wrong, or the calculator is off 

How exactly are you testing? Sensitivity 4.977720 will actually give you a 360 distance of 3254.5 counts, so it's impossible to line it up perfectly with scripts if that's what you're doing.

14 minutes ago, Quasar36 said:

I was doing it manually with a texture on the wall, I thought 2 pixels/count meant that I would always skip 1 pixel per count and that they would be always the same pixels. 

A sens of 5 gives me 3240 counts for 360 so I see now why it lines up but it also shows 2.009 pixels/count, what does it exactly mean? Every 112 pixels it will skip 1?

2.009 means it will move 2.009 resolution pixels for every count from the mouse. The game renders sub-pixel images so this is no issue.

This is all based on FOV, resolution and sensitivity. 360 distance is irrelevant in this case, and since your 2 pixel/count sensitivity results in an uneven 360 distance it will not line up if you spin 360. This is correct and expected.

9 minutes ago, TheBrandon said:

This thread may actually save me from buying. Did the devs ever fix this? I was looking for a close 1:1 of 15ish inches 360 and FOV hdeg 107. Is that possible or is it the same where you’d need some hacks. 

It depends on your DPI, just try the conversion and check the discrepancy you get. FOV should be quite close if set to 111 in-game (equals Actual HFOV: 107.074515 degrees for 16:9).