PropEnterEvent przestał działać dla obiektów poruszanych przez prop_mover

Summary

Hello,

I’m reporting a critical regression since a recent update that has broken PropEnterEvent. This issue is specific to a setup that was working perfectly before the patch: a volume_device detecting another moving volume_device.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Devices

Steps to Reproduce

Minimal Reproducible Code: The Verse code itself is correct and has not changed. The problem is that the PropEntered event is no longer being triggered by the setup described below.

Fragment kodu

using { /Fortnite.com/Devices }
using { /Verse.org/Simulation }
using { /UnrealEngine.com/Temporary/Diagnostics }

test_device := class(creative_device):

@editable Zone:volume_device=volume_device{}

# Runs when the device is started in a running game
OnBegin<override>()<suspends>:void=
    Zone.PropEnterEvent.Subscribe(PropEntered)

PropEntered(EnteredProp: creative_prop):void=
    Print("Prop Entered", ?Duration:=6.0)

Steps to Reproduce (This is how it worked before the update):

  1. Place the test_device above in the scene.

  2. Add a Volume Device (call it Zone) and assign it to the test_device’s Zone slot. Set Affects Props = true. This is our static detector.

  3. Add a prop_mover_device to the scene.

  4. Add any Creative Prop (call it MovingProp) to the scene.

  5. Add a second Volume Device (call it MovingVolume) to the scene.

  6. In the UEFN Outliner, parent MovingVolume to MovingProp so they move together.

  7. In the prop_mover_device’s details, assign MovingProp to its Prop property.

  8. Configure the prop_mover to move the MovingProp (and its child MovingVolume) so that it passes through the static Zone.

  9. Launch the session.

Expected Result

Observed Result (BEFORE Update): When the MovingVolume entered the Zone, the PropEnterEvent would correctly fire. The log would show “Prop Entered”. Curiously, the event seemed to trigger for the MovingVolume (a device) itself, not the MovingProp.

Observed Result

Observed Result (AFTER Update): The Print(“Prop Entered”) message never appears in the log. This event is no longer triggered by this setup.

Platform(s)

windows

Island Code

2217-1489-9193

Upload an image

Additional Notes

Conclusion: A (perhaps undocumented) behavior existed before the update where PropEnterEvent could detect another volume_device entering it as part of a prop_mover assembly. This regression has completely broken mechanics (like my custom kayak) that relied on this behavior.