To start with, he did just fine in the intro area leading up to the Ark (he missed shots, but nothing that wasn’t expected based on his percentage chance). Also, for the record, I’m referring to STEALTH shots (pre-combat) - once combat starts he seems to magically be able to hit the enemies again with some accuracy.
I’ve tested this at least 10x EACH in Fallen Angel and two separate battles in ‘High Road’ and he’s missed every single shot (the other party members hit pretty accurately comparatively with their percentage shots at the time). If it helps for the bug sorting, each time Dux shot I made sure he had a 75% to hit (thats over 30 misses in a row at 75% to hit!). I’ve also tried shooting from different positions, changing up party order, having a teammate take a shot first, and even reloading the game itself.
The only exception to this is that Dux is still able to hit the guy if he’s at 100% to hit, but that usually involves losing stealth altogether…
It’s like in every other xcom game out there, the percentage isn’t exactly a percentage it is a bunch of conditions, you can test it with 2 silents and some save games if you missed once you never be able to hit no matter how much times you’ll load. On other hand change conditions (I don’t know use some skills b4 for instance, or make other character noticed it won’t affect anything until next turn anyway) and you could hit. Take it and use it =P
P.S. Oh and yeah don’t be shy on getting to 100%, other enemies won’t be alerted that your target saw you, if he doesn’t make it through your turn…
Thank you for replying, but after playing for a few more hours I’m still convinced it’s a bug that seems to be possibly bypassed completely for early stealth-only players. Once I had my first battle in the next area beyond high road, Dux started hitting an appropriate amount of times for his hit chance. I even came back to those battles and he started hitting like he should.
There’s already one poster in the steam forums who reported a very similar issue early on, though I haven’t confirmed if it’s these same two areas and with Dux yet.
Thank you for that really helpful tip at the end too - I just discovered that on my own today and it definitely gives me more options in changing the outcome of a battle.
I also discovered that applies to loud weapons if nearby enemies are far enough away, though there’s no indicator or consistency to what the exact distance is, but in the grand scheme of things I’m not worried about that haha
Hello! If you are reloading the same savegame, you will miss everytime. Is that what you are doing? This is to prevent players from constantly saving and loading until they hit.
I have experienced the same thing but it is not specific to Dux. The game somehow decides that this round the character is missing but yeah it’s off of a save game as well. However he should not have missed! He had 100% chance to hit. If that’s not the case then don’t say that.
This is literally making the stealth gameplay terrible. Why would I ever accept a failure in a battle off of arbitrary rules that I don’t know and am not made aware of? Every so often I have to repeat an encounter 5 - 10 times until I can figure out the magic move that makes the char able to hit again. It’s not enjoyable and I am considering just leaving the game alone now.
If this is indeed a deliberate action in terms of stopping reloads until the person hits then perhaps consider disabling it for the stealth vs 1 char. It makes the stealth combat ridiculous
This is just basically how random numbers on computers work. They follow a mathematical formula. You start with a certain initial value (a random seed) which “primes the pump” and then you tell it which index you’re on (so the 1st random number, the 2nd random number, etc.) If this seed is never changed, the 27th random number (for example) will always be the same no matter how many times you save and reload. That is because the random seed is saved as part of your save file.
On this topic, I’d like to see some screenshots first. One thing to keep in mind is that when an enemy spots you, it will use any cover it’s adjacent to if any. So if you move your mouse cursor to a certain spot on the map so you can get a 100% shot on a guy who is walking behind a low wall, as soon as he spots you that shot won’t be 100% any more.
Plus there is a bonus for just shooting from stealth, which also goes away when spotted. I’m not sure if moving the cursor around takes that into account, though.
Like I said, it’d be good to see a screenshot of the shot from the “cinematic” view that shows the shot % breakdowns. I’d like to see it say 100% there before I believed it was missing that shot. Because if so, that’d be an actual bug.