Archery tracers display bug

Description:
When the Agility perk that increases projectile flight speed is active, the client-side visual tracer for arrows does not match the actual projectile trajectory/collision. This happens with both fully charged and lightly charged bow shots. Visually, the arrow appears to fly along one path, but the actual physical impact/hit registration occurs somewhere else. In other words, the graphical representation of the arrow’s flight does not correspond to where the projectile actually lands or hits.

This issue does not occur in single-player: in single-player everything works correctly. The tracer desynchronization only starts on a multiplayer server.

Steps to reproduce:

  1. Allocate the Agility perk that increases projectile speed.
  2. Equip a bow.
  3. Fire arrows at a target/wall at different distances.
  4. Test both fully charged and lightly charged shots.
  5. Compare the visible arrow tracer with the actual impact point.
  6. Repeat in single-player and on a multiplayer server.
    Expected behavior:
    The visual arrow tracer should match the real projectile path and impact point in both single-player and multiplayer.

Actual behavior:
In single-player, the tracer and impact match correctly. On a multiplayer server, the client-side tracer and the actual projectile trajectory/collision diverge. The arrow looks like it is flying along one path, but the real hit/impact happens somewhere else.

Additional info:
• Platform: PC
• Server type: all multiplayer
• Mods: No
• Ping: 0–150 ms (the issue occurs at any ping)
• Single-player: works correctly
• Multiplayer: tracer desynchronization occurs

As I suggested last time you reported this, please make sure to report this to helpshift - Contact Us — Conan Exiles Help Center - as that is where CEE bug reports need to go so that the devs see them. (But please do also continue to report here as well so that issues can be added to the player-maintained list of bugs.)

You probably won’t be able to include this level of detail in the report on helpshift, as it does not allow so much space. Therefore I would suggest giving them the basic description of the bug and including a link to this post so they can view the additional details.

Yeah, this time also I noticed that it only happens in multiplayer game. In single player trajectories and tracers match

Yeah, I did spot that difference in your two reports - when I next update the player-maintained lists I’ll move it from Player Control & Combat to the specific Multiplayer Server section to match what you’ve discovered :slight_smile: