DRL > Requests For Features

Usability/consistency improvements

<< < (4/5) > >>

Klear:
I think I just saw this in action (monster dodge):

I entered Phobos level 3 and there was a group of formers nearby. I began shooting them with my pistol (AoMr) and one of the bullets hit a different former than the others. It happened before the formers could even move, so it definitely wasn't dodging.

It was in graphic version. If I didn't read this thread, I'd think that I just imagined it, but I'm pretty sure it happened.

BTW, I'm playing keyboard only. I just realized that it could be explained by me bumping into mouse, thus changing the aim, but the next bullet went back where I was originally aiming,so that sounds unlikely.

eharper256:
I think I've also seen an instance or two of this. I've manual aimed and hit somewhere else a few times. Never seems to happen if you're just firing normally with just slamming f,f.

Perhaps it might be not so much the monsters are dodging, but rather your aiming location is being misreported?

This is of course on Tiles, not played Console.

Ander Hammer:
I get the feeling the following happens if you shoot at a monster that happens to move:

a.) You wind up hitting, and since everything updates simultaneously, the bullet flies towards where the monster is now.
b.) You missed, so it follows the initial path.

shark20061:
Playing the graphics version, this occurs when you're firing a long path at an enemy that's fairly close.  Ander Hammer's fairly close, but here's what's really going on:

The destination of the bullet is determined once the gun is fired.  When the game figures out what the bullet will hit, it then draws the path of the bullet to the space that it hit.  In graphics mode, it this ends up being a straight line to the destination space.  Observe what that means for a close up enemy when you're cornershooting (where it's most noticeable).  Image is attached.

Klear:
I've noticed this behaviour, but it's something else than what I reported a few posts back: the bullet missed the former I was aiming at but hit the one standing next to him. If I missed, it would have hit the one standing behind him (and there was plenty of those).

Also, this happened right at the beginning of the level and the formers didn't have any chance to move.

My guess is that it was caused by unintentional mouse input - either I bumped into it, or maybe there is something with the code, though this doesn't explain why my next shot aimed back at the former I originally wanted to shoot.

Navigation

[0] Message Index

[#] Next page

[*] Previous page