Project

General

Profile

Bug #3488

AI combat aiming is too slow

Added by scrawl . over 1 year ago. Updated 3 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
AI
Target version:
Start date:
08/09/2016
% Done:

0%

Reproducibility:
Always
Operating system:
Other
Severity:
Normal

Description

https://www.youtube.com/watch?v=zUPOY1jPOq8

Problem 1: creature doesn't start aiming until within attack range. Once within attack range, the attack fires immediately, giving no time to aim.

Problem 2: if the creature was looking away from the player before being aggro'd, projectile fires in completely wrong direction.

I suspect that problem 1) is partly caused by the fact that movement and aiming use the same vector. When the "move towards player" and "aim towards player" vectors are not the same, a conflict occurs. The vectors might not be the same because moving uses the creature position as a basis, but aiming uses the center of collision height.

The attack should not be started until the desired aim vector is reached.


Related issues

Related to OpenMW - Bug #2131: Lustidrike's spell misses the player every time Confirmed 11/15/2014

History

#1 Updated by Alexei Dobrohotov 3 months ago

  • Related to Bug #2131: Lustidrike's spell misses the player every time added

#2 Updated by Alexei Dobrohotov 3 months ago

  • Related to deleted (Bug #2131: Lustidrike's spell misses the player every time)

#3 Updated by Alexei Dobrohotov 3 months ago

  • Duplicated by Bug #2131: Lustidrike's spell misses the player every time added

#4 Updated by Alexei Dobrohotov 3 months ago

  • Status changed from New to Confirmed
  • Target version set to openmw-1.0
  • Reproducibility changed from Have not tried to Always

#5 Updated by scrawl . 3 months ago

  • Duplicated by deleted (Bug #2131: Lustidrike's spell misses the player every time)

#6 Updated by scrawl . 3 months ago

  • Related to Bug #2131: Lustidrike's spell misses the player every time added

Also available in: Atom PDF