2.5.2.17559.377@openbeta:MP:DeSync client side crates don't remove when destroy()

Project: DeSync client side crates don't remove when destroy()

Type: Crates are not properly removed when staticObjectCrate:destroy() is called on them

Status: not sure

Reported: not sure

Priority: High

Summary: Crates are not properly removed when staticObjectCrate:destroy() is called on them

Description: Crates are not properly removed when staticObjectCrate:destroy() is called on them, the server shows them removed and they disappear off the server but NOT on the client, they are left there.

This crates a massive mess on the client.

To reproduce you need TWO MACHINES, 1 to host and 1 to act as a client. you'll notice the host PC removes the crate properly but all the clients the crate stays around even though it doesn't exist on the server, creating a massive mess

Example, loot at the huge amounts of left over crates because they dont dissappear on the clients (they dont exist on the server), https://clips.twitch.tv/ResoluteSuaveCobraANELE

+1

can confirm this and also weirdness like floating crates in MP

such a PITA

2.5.2.18307@openbeta:MP:DeSync client side crates don't remove when destroy()

Project: DeSync client side crates don't remove when destroy()

Type: Crates are not properly removed when staticObjectCrate:destroy() is called on them

Status: not sure

Reported: not sure

Priority: High

Summary: Crates are not properly removed when staticObjectCrate:destroy() is called on them

Description: Crates are not properly removed when staticObjectCrate:destroy() is called on them, the server shows them removed and they disappear off the server but NOT on the client, they are left there.

This crates a massive mess on the client.

To reproduce you need TWO MACHINES, 1 to host and 1 to act as a client. you'll notice the host PC removes the crate properly but all the clients the crate stays around even though it doesn't exist on the server, creating a massive mess

Example, loot at the huge amounts of left over crates because they don't disappear on the clients (they dont exist on the server)

I included a picture of what the landscape looks like (its silly)

The bug is still here. Client side crates will not despawn.

```if request.action == "REMOVEOBJECT" then

--env.info('REMOVE OBJECT')

local removeObj = Unit.getByName(request.removeObject)

local removeObjStat = StaticObject.getByName(request.removeObject)

if removeObj ~= nil then

--env.info('Destroying '..request.removeObject)

removeObj:destroy()

elseif removeObjStat ~= nil then

--env.info('Destroying Static '..request.removeObject)

removeObjStat:destroy()

end

end```

I send in the unit name into that. thats run on the lua side. one of the few lua commands called remotely. it tries to grab unit name first. if no unit, must be a static. then runs the static destroy command

So I ran some more tests and what happens is while the client is connected to the server the client will not see the crates despawn but the server host will. If the client reconnects the crates will appear despawned. So the issue is despawning the crates client side while connected.

This is still a big problem guys

The patch that was to fix the bug seemed to not work. No change observed.

Okay so the crates do despawn like they are supposed unless you have slung the crate. If you try to sling the crate with a cable it will not despawn.

Bump. Desync floating crates are still there