pervysage

The steam input one I saw somewhere online where controller players were going insane over losing their precious aim assist because of the Steam input interfering or something along those lines lol. Apparently this setting helps controller players a lot as well. Then someone had mentioned that it seems to have a positive effect on mouse/keyboard use as well and sure enough when I tried it myself, it did. The motion assisted steering setting I discovered myself as I just went through every damn single setting I could find in the Halo menu because I could swear something was wrong with how mouse and keyboard felt in the game. I enabled/disabled the setting a hundred times to make sure I wasn't just imagining things, lol. Like surely 343 Industries couldn't have screwed up that bad and it's just placebo on my part... but I honestly don't think it is. That's why I was curious as to whether other people would notice it as well.

You definitely have to restart the game after changing the Steam Input setting (it even says so in the same window to restart the game). Otherwise it won't take effect. As for the the vehicle setting, I'd say the best way to test would be to create a custom game with some bots and then toggle the checkbox for Assisted Motion Steering on & off a bunch of times in between shooting bots to see if you can notice anything. I did myself and could feel it and so did my friend. We both agree that we can't go back to playing with the setting enabled because it feels like crap, lol.

Do y'all still see weird acceleration issues if you disable Steam Input in the Halo Infinite game properties within Steam Library (under Controller section)? Yes, that has to do with controllers but I feel that not only does it improve controller gameplay but MKB gameplay as well. On top of that, I swear there is some kind of glitch going on with the "Movement Assisted Steering" option under mouse & keyboard settings in the Halo Infinite menu (it's a checkbox that is enabled by default). Unchecking/Disabling this also made my mouse feel way better even though the option itself is only supposed to apply to movement while looking around while driving a vehicle, lol. The game is honestly a glitchy mess so it wouldn't surprise me if this were true. Making these 2 changes above made my mouse and keyboard aim feel infinitely better... at least that's how it felt like to me. EDIT: Not saying that these things are responsible for the acceleration or weird aim feel, it's just personally my aim feel felt a lot better with these changes.

Thank you again! That certainly seems to do the trick. Also helps to know where the config file for this game is, I've been looking for it!

Hmm.. so weird thing in-game, it doesn't seem to even allow for 106 FOV for some reason, haha. Setting it to 106, then leaving the menu and coming back you can see it defaults back to 105 so I guess I will just stick with that.

Awesome, that is good to know. Thank you so much!

Hmm... so I was initially going to use the 1st calculation but then I saw the talk about using 0.1 horizontal scale to get more accuracy. I then did a 2nd calculation but ended up having to use 0.4 horizontal scale instead (any lower than that and the mouse sensitivity was too high and calculator was showing the error - since I run 400 DPI) 1st calculation (normal 1 horizontal/vertical scale): https://www.mouse-sensitivity.com/?share=de2392dcba452fa5e0c1af486f870940 2nd calculation (0.4 scale): https://www.mouse-sensitivity.com/?share=6183e56798a169fd64c40bc43b8154f9 Basically, what I'm wondering is if it's really worth going through all the trouble of setting scale to 0.4 in game and using a higher mouse sensitivity? Will it be something that is noticeably more accurate? Also I also want to match my Overwatch FOV which is 103 and the calculator automatically selects Hdeg Res as the FOV type for Overwatch... so if I understood correctly, I should use the same FOV Type as I do in Overwatch (so change the Halo FOV type which is 'Multiplier' by default in the calculator to Hdeg Res) if I want to match that FOV, correct? (this is what I did in the above calculations)

Can't wait for zoom levels to be done, that will be awesome. As far as hipfire goes, I just used whatever was already available on the calculator and it feels pretty damn good already. If you say that will get updated & improved even further then that's even better. It's just the zoom levels that feel super wonky to me right now (just have them left at the default 1.0 for all zoom levels for now) EDIT: what in the heck... don't know if it's a bug in the game but when I use the default 'V' keybind switch weapons, then scoped aim feel feels just fine actually... it was when I was using secondary default keybind (which is scroll wheel up/down) to switch weapons that the scoped mode felt wonky as all hell... so weird. But updated values will be appreciated regardless.

I am also wondering about this if anyone can answer?

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.

Normally, I hate G SYNC on other games like Overwatch because it feels like it adds input delay. But with this Halo release it seems like G SYNC is the only way to make it feel NORMAL, lol. With just normal settings the screen looks so visually choppy with mouse and keyboard, it's insanely bad for me. Maybe it's tearing or something but it does not happen on other games for me... running uncapped with a 240hz monitor and VSYNC off. VSYNC itself feels awful like it usually does with lots of input delay but G SYNC actually feels quite good for some reason... and I normally never use it. By the way, even with Halo set to fullscreen in the settings, the game does not minimize on my monitor when I hit the Windows key to just browse stuff on my 2nd monitor. On any other game like Overwatch, the game would completely minimize if I were to be using my 2nd monitor for something but Halo stays running fullscreen on my other monitor while I browse on the 2nd monitor. Normally, that is behavior of having the game set to Fullscreen Borderless.... but I have it set to fullscreen and it doesn't minimize at all. Is it possible that Halo keeps itself stuck on Fullscreen Borderless even if you set it to Fullscreen? Who knows....

Looks like the new 1.09 coming out soon will give us the ability to customize ADS sensitivities (regular, scoped, etc): https://www.reddit.com/r/Blackops4/comments/a5431s/109_title_update_blackout_audio_armor_updates_mp/ "Added ADS Sensitivity Options for both high zoom optics and regular weapons."

I was converting from Overwatch Hipfire. But you were right, I didn't realize Ashe was tagged as ADS and that was why I was getting such a big difference in the resulting values. Now they are identical after I set ADS to 0% like I had on the Scope. Thanks!

Thanks for the quick work on the Ashe calculator I have a question... Converting directly from Hipfire > Ashe, you get a value of 59.95 (for both All & Ashe ADS options) Converting from Widow/Ana Scope (using a value of 37.94 which is from the Hipfire > Widow conversion) > Ashe, you get a value of 50.05 (if you use the All option) and 51.66 (if you use the Ashe ADS option) Are all these values supposed to be different like that? (I am using a Monitor View Distance - Horizontal 0% for Scope by the way)

Wait a second, so BO4 uses MDV rather than MDH like other games like Overwatch? In my past messing around with the calculator, I did find using the vertical options in the conversion options felt better to me in BO4.