Bug: Attempting to pickup (+use) an prop, whilst holding another prop, results in the held prop becoming bugged out. #1316
Labels
Type: Bug
This is a problem with something that should be working one way, but isn't.
Describe the bug
If you attempt to pickup (+use) an prop, whilst you are currently holding another prop, the held prop will enter a bugged out state, where it is pratically frozen in place, and no amount of
Wake
orEnableMotion
inputs can free it.From my testing, this can happen with any classname of physics prop (I've tested
prop_weighted_cube
,prop_physics
,prop_physics_override
,npc_portal_turret_floor
andnpc_security_camera
(detached variant).In the turret's cases specifically, their animations + sfx act as if they're still picked up whilst in the bugged state, so my guess as to why this bug is occuring is that the pickup isnt corrently being uninstantiated, if that makes sense.
(Image showcases a
prop_physics
, and aprop_physics_override
both in the bugged state)I understand this is an incredibly niche bug, and one that likely wouldn't come about in normal gameplay, however since I've ran into it whilst creating new gameplay mechanics inside vscript, I thought it would be worthy of a bug report since I imagine others may run into it too.
NOTE: This bug is also present inside base Portal 2, and Portal 1.
To Reproduce
This is the easiest way to reproduce it, from my testing.
ent_fire [targetname] use
, wheretargetname
is the name of another physics prop.Here is a clip of me doing these exact steps:
https://drive.google.com/file/d/1l3VXJDG9y97dwiZShPZhXOPKs076NxKa/view?usp=sharing
Issue Map
Here is an incredibly basic test map I've created, including a
prop_weighted_cube
,prop_physics
,prop_physics_override
and annpc_portal_turret_floor
(same one as featured in the video above): prop_pickup_whilst_holding_object_bug_testmap.zipExpected Behavior
The held prop should be dropped as if +use was invoked, rather than becoming bugged.
Operating System
Windows 11 Home 23H2 Build 22631.4602
The text was updated successfully, but these errors were encountered: