Seems, that there is a bug in work of SetCollisionBox(mins, maxs)
It used in SetExtents function, but seems that it creates some wrong collision. SetExtents(<-30 -30 -30>,<30,30,30>) create some weird box collision which is 30m from one side, and 10m on the other side. Also it seems that Extent cannot be more than 30m, trying SetExtents with any bigger number creates same collision.
As visualization - barrel is center of trigger. Using rangefinder i'm showing limits after which monster will appear.
Description
Description
Details
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- General
Steps To Reproduce
Create a trigger with this extents, check borders of trigger.
m_AreaDamage.SetExtents("-40 -40 -40", "40 40 40");
Then twice numbers - trigger will be the same. Seems the problem is in SetCollisionBox, cause entering trigger called by OnTouch.
Additional Information
Event Timeline
Comment Actions
Hello Right.
Unfortunately there are no updates I could share regarding to the issue.
We are aware of the report, however, due to the amount of issues we are dealing with it may take time for this to be reviewed by the developers responsible.
Regards,
Geez
Comment Actions
Maybe you can provide some information how to enable debug visualisation of trigger? I could collect data and provide screenshots of trigger work to make your future debug easier?