So for the past four hours I’ve had red-level recoil on a colt 45.
What exactly did I do wrong? Why won’t the recoil go down? According to my save I have no driving recoil, attempting to reset the recoil to 0 in the save and it goes back to 150 immediately after I load and wait a turn. There’s no apparent cause of the recoil.
[quote=“EkarusRyndren, post:1, topic:8087”]So for the past four hours I’ve had red-level recoil on a colt 45.
What exactly did I do wrong? Why won’t the recoil go down? According to my save I have no driving recoil, attempting to reset the recoil to 0 in the save and it goes back to 150 immediately after I load and wait a turn. There’s no apparent cause of the recoil.[/quote]
I think it’s to do with the new aim system.
What exactly did I do wrong? Why won't the recoil go down? According to my save I have no driving recoil, attempting to reset the recoil to 0 in the save and it goes back to 150 immediately after I load and wait a turn. There's no apparent cause of the recoil.Just thinking logically, I can assume you are too weak to hold such a gun or have your hands encumbered.
[quote=“EditorRUS, post:3, topic:8087”]
What exactly did I do wrong? Why won’t the recoil go down? According to my save I have no driving recoil, attempting to reset the recoil to 0 in the save and it goes back to 150 immediately after I load and wait a turn. There’s no apparent cause of the recoil.
Stranth 22, no encumberment on Hands, Eyes, or Arms. 2 on Torso, 2 on Head, 1 on Mouth.
Apparently my colt is made of hyper-dense gold and no one told me.
I think that meaning of “recoil” changed: it’s no longer just “recoil from firing”, but generally “weapon not centered on target”.
I skimmed src/ranged.cpp and found that aiming decreases recoil.
This would probably mean that whenever you aren’t aiming, you have some extra recoil that accounts for the weapon simply not being aimed at the target.
[quote=“Coolthulhu, post:5, topic:8087”]I think that meaning of “recoil” changed: it’s no longer just “recoil from firing”, but generally “weapon not centered on target”.
I skimmed src/ranged.cpp and found that aiming decreases recoil.
This would probably mean that whenever you aren’t aiming, you have some extra recoil that accounts for the weapon simply not being aimed at the target.[/quote]
how do I aim then? Because it’s not such an obvious function anymore.
When you press ‘f’ to get targeting menu, you get the list of binds in it. Confirm attack with ‘p’ to aim a long time, with ‘c’ to aim less, with ‘a’ to aim a tiny bit, with ‘f’ for a snapshot with no aiming. The aiming time depends on how much recoil do you have right now.
‘.’ is supposed to be “aim”, but it also instantly fires the gun. Not sure whether it’s a bug or just me misunderstanding things.
Hit ‘f’, this brings up the targeting/aiming menu. Said menu has instructions, but a quick rundown:
Hit ‘.’ to spend a small amount of time (a second or so) aiming, the “confidence” and “steadiness” bars should advance a bit.
“Confidence” is your character’s evaluation of how likely they are to hit, the '|'s indicate chances of an ordinary hit, the '+'s indicate chance of a “good” hit, and the '*'s are the chances of a headshot.
“Steadiness” is how close you are to having the best aim you can for the weapon you’re using. Once it’s full, it’s not going to get any better no matter how long you keep aiming, though confidence will tend to go up as monsters get closer to you.
Hit ‘f’ to fire with your current aim level.
Hit ‘a’, ‘c’ or ‘p’ to aim until you reach some level of steadiness and then fire. The level is determined by which one you pick, obviously(?).
That having been said, the fact that it’s warning you about high recoil all the time is an oversight on my part. I’m leaning toward just removing that now, because it doesn’t make much sense when you aren’t aiming at something.
[quote=“Coolthulhu, post:7, topic:8087”]When you press ‘f’ to get targeting menu, you get the list of binds in it. Confirm attack with ‘p’ to aim a long time, with ‘c’ to aim less, with ‘a’ to aim a tiny bit, with ‘f’ for a snapshot with no aiming. The aiming time depends on how much recoil do you have right now.
‘.’ is supposed to be “aim”, but it also instantly fires the gun. Not sure whether it’s a bug or just me misunderstanding things.[/quote]
It’s a keybinding thing: you probably have a custom bind somewhere, so you need to go into the firing-window bind screen (bring up the window, then press ?) and manually set things.
[quote=“KA101, post:9, topic:8087”][quote=“Coolthulhu, post:7, topic:8087”]When you press ‘f’ to get targeting menu, you get the list of binds in it. Confirm attack with ‘p’ to aim a long time, with ‘c’ to aim less, with ‘a’ to aim a tiny bit, with ‘f’ for a snapshot with no aiming. The aiming time depends on how much recoil do you have right now.
‘.’ is supposed to be “aim”, but it also instantly fires the gun. Not sure whether it’s a bug or just me misunderstanding things.[/quote]
It’s a keybinding thing: you probably have a custom bind somewhere, so you need to go into the firing-window bind screen (bring up the window, then press ?) and manually set things.[/quote]
I had to go to keybinds.json and remove “.” under “fire” and now it works.
[quote=“KroganElite, post:10, topic:8087”][quote=“KA101, post:9, topic:8087”][quote=“Coolthulhu, post:7, topic:8087”]When you press ‘f’ to get targeting menu, you get the list of binds in it. Confirm attack with ‘p’ to aim a long time, with ‘c’ to aim less, with ‘a’ to aim a tiny bit, with ‘f’ for a snapshot with no aiming. The aiming time depends on how much recoil do you have right now.
‘.’ is supposed to be “aim”, but it also instantly fires the gun. Not sure whether it’s a bug or just me misunderstanding things.[/quote]
It’s a keybinding thing: you probably have a custom bind somewhere, so you need to go into the firing-window bind screen (bring up the window, then press ?) and manually set things.[/quote]
I had to go to keybinds.json and remove “.” under “fire” and now it works.[/quote]
Yeah, we can change the default bindings but not your saved keybind file, so any user-side change prevents new defaults from applying. Bit of a bugbear here but not much we can do about it.