Help The referenced script (Obi.BurstColliderWorld) on this Behaviour is missing! - Printable Version +- Obi Official Forum (https://obi.virtualmethodstudio.com/forum) +-- Forum: Obi Users Category (https://obi.virtualmethodstudio.com/forum/forum-1.html) +--- Forum: Obi Fluid (https://obi.virtualmethodstudio.com/forum/forum-3.html) +--- Thread: Help The referenced script (Obi.BurstColliderWorld) on this Behaviour is missing! (/thread-2565.html) Pages:
1
2
|
RE: The referenced script (Obi.BurstColliderWorld) on this Behaviour is missing! - eganki - 05-11-2020 (05-11-2020, 11:46 AM)josemendez Wrote: No worries! I'll take a look at the editor logs and get back to you with my findings.I managed to figure out a method to prevent "freeze" upon playing. By default, there will have 2 CollisionWorld gameobjects. [attachment=809] If I delete away the one not targeted by Backend, it will work. [E.G. Backend -> Burst setting Scenario 1 If OniCollisionWorld gameobject is removed from the scene and only the BurstCollisionWorld remain, it will work as per normal. Scenario 2 If Both CollisionWorld gameobject remain on the scene, it will freeze upon Play Scenario 3 If BurstCollisionWorld gameobject is removed from the scene and only the OniCollisionWorld gameobject remain, it will freeze upon Play. Hope this might helps! RE: The referenced script (Obi.BurstColliderWorld) on this Behaviour is missing! - josemendez - 05-11-2020 (05-11-2020, 12:04 PM)eganki Wrote: I managed to figure out a method to prevent "freeze" upon playing. This does help, thanks! Based on this, it looks like it is a recently reported (and fixed) bug: http://obi.virtualmethodstudio.com/forum/thread-2523-page-3.html As we speak, I'm uploading an update to the store that contains a fix for this bug. (v5.6.1). Will nevertheless investigate further, in case it is a different issue. RE: The referenced script (Obi.BurstColliderWorld) on this Behaviour is missing! - eganki - 05-11-2020 (05-11-2020, 12:09 PM)josemendez Wrote: This does help, thanks! Based on this, it looks like it is a recently reported (and fixed) bug:Great! Keep up the good work I'll notify my teammate about this new update before he pulled out all his hair away. |