large projectiles aren't synced

[juztim]

Client/server version

Build #1286, branch release

Current behavior If Player A throws a stickybomb/proximitymine Player B sees it falling through the wall/floor. Player A will see the bomb/mine correctly, Player B won't. Player B will also hear the beeping of the mine on a totally different position than where it is on Player A's screen. Player B can't trigger the mines of Player A but will die from the explosion if it gets triggered by Person A. (Also tested out grenades, they're synced properly)

Expected behavior Properly syncing the position of the proximitymine/stickybomb.

Steps to reproduce Throw a stickybomb or proximitymine somewhere.

Context (environment) I randomly threw around these bombs and a friend of mine noticed it. It kinda affects killing players? I guess.

Possible solution ~

[EtzBetz]

Can confirm

[TeubyDE]

it's more broken than written above more information below:

Description of the problem Throwables and Projectiles are not sync for other Players. Only the throwing / firing Player can see it flying. All other Players will only see the effect (explosion of grenade , fire of molotov cocktail, gas from BZ gas,...)

This is tested and reproduced in Version release/6.4, rc/7.0-rc4, dev/7.0-dev20. On Debian 10 Server Side and Windows Version 10.0.19042 Build 19042Client Side

Reproduction steps Setup a server and run the example freeroam resource. Join it with at least 2 players. Throw/Fire one of the following example weapons. weapon_ball weapon_bzgas weapon_flare weapon_grenade weapon_molotov weapon_pipebomb weapon_proxmine weapon_smokegrenade weapon_snowball weapon_stickybomb weapon_rpg weapon_grenadelauncher weapon_grenadelauncher_smoke weapon_hominglauncher weapon_firework weapon_compactlauncher weapon_raypistol weapon_flaregun Expected behaviour Throwables and Projectiles are visible/sync for all Players. Not only for the throwing / firing Player.

Additional context No response

Operating system Debian 10 / Windows 10

Version release/6.4, rc/7.0-rc4, dev/7.0-dev20

[Hutstaender]

Can confirm this. Last year (from around 10th dec to 10th jan) we had a snowball script where u could pickup and throw snowballs. Back then everything worked fine, and was sync. This year the sync is unfortunately rigged.

There are two different issues mentioned in here. Last year we already had the sticky-bomb stick problems during testing, but the throwing sync must have gone broken during this year.

[ThomasMarangoni]

confirmed for all large projectiles.

[FabianTerhorst]

it's more broken than written above more information below:

Description of the problem Throwables and Projectiles are not sync for other Players. Only the throwing / firing Player can see it flying. All other Players will only see the effect (explosion of grenade , fire of molotov cocktail, gas from BZ gas,...)

This is tested and reproduced in Version release/6.4, rc/7.0-rc4, dev/7.0-dev20. On Debian 10 Server Side and Windows Version 10.0.19042 Build 19042Client Side

Reproduction steps Setup a server and run the example freeroam resource. Join it with at least 2 players. Throw/Fire one of the following example weapons. weapon_ball weapon_bzgas weapon_flare weapon_grenade weapon_molotov weapon_pipebomb weapon_proxmine weapon_smokegrenade weapon_snowball weapon_stickybomb weapon_rpg weapon_grenadelauncher weapon_grenadelauncher_smoke weapon_hominglauncher weapon_firework weapon_compactlauncher weapon_raypistol weapon_flaregun Expected behaviour Throwables and Projectiles are visible/sync for all Players. Not only for the throwing / firing Player.

Additional context No response

Operating system Debian 10 / Windows 10

Version release/6.4, rc/7.0-rc4, dev/7.0-dev20

fixed since last update. But the main issue isnt fixed so we keep it open.

[C0kkie]

Current State in 9.0 (QA Test results)

Every projectiles are now synced correctly except molotov, sticky bombs are still not synced (remote player hear constant and fast clicking noise + dont see the bomb

[juztim]

thats how the sticky bombs were when I reported the issue