Simple, clean, and works as advertised, thank you. Endorsed.
I hate scope sway and I hate having to waste time looking through my mod list and/or reverting to an earlier save to figure out what broke my scoped aiming. I now have more time to devote to crafting slooty armors, cheers!
Is it possible to reduce the sway, but not totally delet it? I'd like at least a teeny bit, just enough to not feel totally static. Looking at the text file it seems to be a simple console command... "player.ModAV 35b 2"
Dunno wot exactly it means though, so I might try it in-game myself to see how it applies.
AimStability : 0000035B — Default value = 1. Setting it to 2 eliminates scope sway.
According to some table of console commands I found via a quick search on the net. After some testing in-game, I've found any value at or above 1.15 totally negates sway even using long-range scopes. 1.14 has some sway, but it's not enough to miss a headshot even at extended range.
Any value of 1.1 to 1.14 will provide some variety of sway, but it has a powerful impact a single placement after the decimal point.
@MgSolidus I have used that mod for years, even my last play which was only weeks ago. New load order and... it stopped working. I have been wracking my brain trying to find what is stomping it out, there are no conflicts, no errors, and as far as I can tell with my limited xEdit abilities, nothing secretly overwriting it.
And it gets worse, I tried the Player.ModAV 35b 2 in console. No go. Even relaunched the game hoping. I'll try the actual bat text now with fingers crossed. I just don't get it.
1 ) it is dependant on your AP. 2 ) You have to hold the button down which can mess up lining up / guiding your shots. 3 ) It gets real annoying to re-apply BREATHING every single time you pull out a scoped weapon. 4 ) It's a batch file someone made about a value I didn't know about, aside from the uploader being a programming genius, I just have to say: let people do what they want to do.
1. you can name it anything you want. i like to keep my batch file titles short for convenience. 2. probably, idk. i've been using this particular command for a long time and never experienced any issues.
14 comments
I hate scope sway and I hate having to waste time looking through my mod list and/or reverting to an earlier save to figure out what broke my scoped aiming. I now have more time to devote to crafting slooty armors, cheers!
I'd like at least a teeny bit, just enough to not feel totally static. Looking at the text file it seems to be a simple console command...
"player.ModAV 35b 2"
Dunno wot exactly it means though, so I might try it in-game myself to see how it applies.
According to some table of console commands I found via a quick search on the net.
After some testing in-game, I've found any value at or above 1.15 totally negates sway even using long-range scopes.
1.14 has some sway, but it's not enough to miss a headshot even at extended range.
Any value of 1.1 to 1.14 will provide some variety of sway, but it has a powerful impact a single placement after the decimal point.
The default value is 0.50 for me. I changed it to 0.2 to no avail. Weird.
But console command "player.ModAV 35b 2" worked for me.
Thats so weird, because both should be doing exactly the same thing...
Well at least its working, but I still dont understand why it doesnt work on FO4Edit.
Just activate plugin and done.
And it gets worse, I tried the Player.ModAV 35b 2 in console. No go. Even relaunched the game hoping. I'll try the actual bat text now with fingers crossed. I just don't get it.
No idea why. But this console command worked!
Thanks @Xymot666
2 ) You have to hold the button down which can mess up lining up / guiding your shots.
3 ) It gets real annoying to re-apply BREATHING every single time you pull out a scoped weapon.
4 ) It's a batch file someone made about a value I didn't know about, aside from the uploader being a programming genius, I just have to say: let people do what they want to do.
2. Can I reset the command "Player.ModAV 35b 2" by changing the parameters if problems arise?
2. probably, idk. i've been using this particular command for a long time and never experienced any issues.