Oh, yes, definitely. However, the hit-wound-save sequence is deeply ingrained in GW's DNA by now, and they seem unable (or unwilling) to challenge it.That's true, it does make a difference with field armor. Our group has never used field armor before, so it never came up. And who says having extra effects like that is a bad thing? Still, your second paragraph acknowledges the roll coming after the Wound roll is just to reduce the number of dice rolls. So they've admitted that, logically, it should come before the Wound roll.
I'm not saying that field armours triggering more often is a bad thing, but it sure is a different thing from what is (likely) intended.
If you want to houserule a hit-save-wound sequence, you will also have to change how seismic works (as it may deny a save roll based on the result of the wound roll) — or just choose not to use the corresponding weapon mind you ^^. It could be as simple as basing the no-save-allowed on a natural 6 to hit though.
Speaking of illogical weird things, it's also very strange that a fighter can choose to use their conventional armour save instead of their field armour save. How slow are those bullets if a fighter has the time to deactivate their force-field before they are hit? In the end, it all boils down to abstracted game mechanics.
Do they though?Those rules that state "ignore the attack" do that.
It seems that they either say "The attack misses" (and in this case, the fighter shouldn't be Pinned, yes) or "The attack has no further effect" (and in this case the fighter should stay Pinned as Pinning already happened and is therefore not part of the "further effects")
Step aside and Omen of fortune use the former, while Dodge and Field armour use the latter (which is yet another hint that they happen after the wound roll is made)
In my opinion, the intended sequence is:
- Hit roll
- Omen of fortune
- Step aside
- Wound roll
- Dodge
- Save roll (Conventional armour save OR Field armour save OR Precognition)
- Injury roll