Any idea if changing fov in config file works? I usually play with 80 vdeg which the calculator translates into 112.33 in halo but the menu doesn't seem to accept decimals

7 minutes ago, zoxes said:

Any idea if changing fov in config file works? I usually play with 80 vdeg which the calculator translates into 112.33 in halo but the menu doesn't seem to accept decimals

Same thing it seems like, it just ignores the decimals and removes them.

Aiming feels really good now compared to the last flight.

Does anyone get a weird shuddering image when strafing? Everything else seems fine but if I keep my reticle on an object or character and strafe around the object kind of stutters and vibrates, making it blurry.

I'm playing on a 240Hz monitor with gsync on and the framerate capped at 200fps with rivatuner. 

When i stopped using rivatuner i had less microstutter. Give that a try.

Using G SYNC got rid of most of the visual clutter I was getting on my screen while strafing/aiming/moving around in general but I shouldn't have to use G SYNC considering I don't like using it on any other game. Seems like a fault of the game on it's own and something that hopefully gets patched.

 

Many controller players that have been swapping between Mouse/Keyboard & Controller say that playing on controller has no issues whatsoever but as soon as they start using mouse/keyboard, the visual issues start to occur immediately. 

Edited December 5, 20195 yr by pervysage

Can you add the other weapons besides just pistol 2x
DMR
Needle rifle
Sniper
etc.

When will this be available for non premium users? ;-; I was a member 2 years ago but haven't need conversions in a long time. I'm considering resubbing. I just need to figure 17.0455 in/360, I may just break out a ruler but it is only $3. I love this website and want to support it, I may even get the lifetime for $60 some day.

 

I resubbed, happy to support and I can do all the conversions I need for the time being. It'd honestly be nice if there was like a 1 day sub or something for even less.

Edited December 5, 20195 yr by saw141

5 hours ago, Feedingwolves said:

When i stopped using rivatuner i had less microstutter. Give that a try.

I've tested with and without rivatuner and gsync now but still have the same issue unfortunately. I can live with it for now but I hope they fix it in the future.

5 hours ago, pervysage said:

Using G SYNC got rid of most of the visual clutter I was getting on my screen while strafing/aiming/moving around in general but I shouldn't have to use G SYNC considering I don't like using it on any other game. Seems like a fault of the game on it's own and something that hopefully gets patched.

 

Many controller players that have been swapping between Mouse/Keyboard & Controller say that playing on controller has no issues whatsoever but as soon as they start using mouse/keyboard, the visual issues start to occur immediately. 

I prefer gsync in most games now, capping the framerate + gsync + vsync on gives consistent frame times and no tearing. 

wish i could put decimals in the sensitivity xd

14 hours ago, Skwuruhl said:

Can you add the other weapons besides just pistol 2x
DMR
Needle rifle
Sniper
etc.

Added DMR (3X) and Sniper (5X), Needle rifle is 2x.

Also did an important update to the FOV calculations.

The FOV value in the game isn't the true FOV, it's a multiplier of a 4:3 FOV (where 110 in the game is equal to 90 in 4:3 as in CSGO).

It doesn't make a huge difference in the calculations since the game lacks decimals, but now it's at least 100% correct.

 

22 hours ago, ODSYViper said:

Aiming feels really good now compared to the last flight.

Does anyone get a weird shuddering image when strafing? Everything else seems fine but if I keep my reticle on an object or character and strafe around the object kind of stutters and vibrates, making it blurry.

I'm playing on a 240Hz monitor with gsync on and the framerate capped at 200fps with rivatuner. 

player movement and animations are still stuck at 60fps with uncapped fps on. its awful...

Is the calculator broken? Changing between All w/ 2x Zoom, 3x Zoom, and 5x Zoom doesn't change Zoomed Sensitivity Scale at all, and converting from hipfire to any of the zooms or vehicle just gives the error "Too high sensitivity 1 - Maximum is 10".

Edited December 6, 20195 yr by octiceps

On 12/6/2019 at 9:20 AM, octiceps said:

Is the calculator broken? Changing between All w/ 2x Zoom, 3x Zoom, and 5x Zoom doesn't change Zoomed Sensitivity Scale at all, and converting from hipfire to any of the zooms or vehicle just gives the error "Too high sensitivity 1 - Maximum is 10".

No, it's working like intended, but the lack of decimals and the similar scaling between the scopes makes the calculation change very little. If you convert to zoom or vehicle, make sure you enter your current hipfire sensitivity.

On 04/12/2019 at 23:51, zoxes said:

 

Edited December 6, 20195 yr by fortunate reee

What Monitor distance is Halo Reach default zoom 1 value?

1 hour ago, tuphac said:

What Monitor distance is Halo Reach default zoom 1 value?

It's close to 100%, but not exactly since the FOV is calculated in a weird way.

Am 5.12.2019 um 17:51 schrieb DPI Wizard:

Added DMR (3X) and Sniper (5X), Needle rifle is 2x.

Also did an important update to the FOV calculations.

The FOV value in the game isn't the true FOV, it's a multiplier of a 4:3 FOV (where 110 in the game is equal to 90 in 4:3 as in CSGO).

It doesn't make a huge difference in the calculations since the game lacks decimals, but now it's at least 100% correct.

That why my aim felt so off and weird. Thank you for pointing that out. You are a blessing ❤️

So how do you convert halo's in-game fov to 103 hfov at 16:9? CSGO 90 hfov at 4:3 is like 106hfov at 16:9, so are you saying 110 halo fov = 106hfov @16:9?

Edited December 7, 20195 yr by Lv99

16 minutes ago, Lv99 said:

So how do you convert halo's in-game fov to 103 hfov at 16:9? CSGO 90 hfov at 4:3 is like 106hfov at 16:9, so are you saying 110 halo fov = 106hfov @16:9?

Like so, check the output for the Config FOV for Halo:

On 12/5/2019 at 8:51 AM, DPI Wizard said:

The FOV value in the game isn't the true FOV, it's a multiplier of a 4:3 FOV (where 110 in the game is equal to 90 in 4:3 as in CSGO).

What exactly is meant by this? Doing the math doesn't line up with the calculator.

2 hours ago, Skwuruhl said:

What exactly is meant by this? Doing the math doesn't line up with the calculator.

This seems to be what DPI Wizard is doing:

4:3 FOV = (0.85 * FOV) - 3.5

1 minute ago, Drimzi said:

This seems to be what DPI Wizard is doing:

4:3 FOV = (0.85 * FOV) - 3.5

Correct, it's very apparent at higher FOV where 120 in-game is barely over 114 if you measure it.

On 12/8/2019 at 2:03 AM, Drimzi said:

4:3 FOV = (0.85 * FOV) - 3.5

lmao what the fuck

1 hour ago, Skwuruhl said:

lmao what the fuck

I guess the game was made for 4:3 and they didn't bother doing the proper math to 16:9.

There's an option to use cheat engine. I'm trying it out, but can't seem to get it to work. Will it even save once I switch to the mode with anti-cheat?