Physics engine V2 breaks many 3D codeblocks, and code being broken upon loading a project
-
While working on one of my projects, I’ve found that the V2 version of the physics engine breaks many 3D code-blocks, for example the collision detectors. Whenever I try to use the “broadcast (message) upon collision between (object) from (sprite) and (object) from (sprite)”, “when colliding with (sprite)”, “distance between objects (object) and (object)”, “names of physics bodies in contact for (object)”, and many other 3D code-blocks, simply just break or dont work whenever being used with the physics engine V2. it also breaks things like changing the direction of objects (when using blocking) and other things like the Move, Rotate, and Scale, and Bounding Box tools, are only able to be used once before breaking, and changing the direction of blocks requires you to manually use the rotate tool for it to work.
I’ve also noticed that whenever I open up my project, some bits of code seem to break apart, forcing me to manually re-assemble them whenever I open up my project.
All of this can be viewed in the project: https://play.creaticode.com/projects/69f2233a8efecb354f1e200f
-
While working on one of my projects, I’ve found that the V2 version of the physics engine breaks many 3D code-blocks, for example the collision detectors. Whenever I try to use the “broadcast (message) upon collision between (object) from (sprite) and (object) from (sprite)”, “when colliding with (sprite)”, “distance between objects (object) and (object)”, “names of physics bodies in contact for (object)”, and many other 3D code-blocks, simply just break or dont work whenever being used with the physics engine V2. it also breaks things like changing the direction of objects (when using blocking) and other things like the Move, Rotate, and Scale, and Bounding Box tools, are only able to be used once before breaking, and changing the direction of blocks requires you to manually use the rotate tool for it to work.
I’ve also noticed that whenever I open up my project, some bits of code seem to break apart, forcing me to manually re-assemble them whenever I open up my project.
All of this can be viewed in the project: https://play.creaticode.com/projects/69f2233a8efecb354f1e200f
@regis Also, after fixing the physics engine, you should add a new block, which is just like the “when colliding with (sprite)” code-block, but more customizable.
What I mean by this is to add drop-down menus to parts of it, for example: “when (colliding/not colliding) with [object] from [sprite]”
the () are drop-down menus (whats inside the () are what should go into the dropdown menu)
are text boxes, where you can put in the name of the object for the first one, and the sprite name for the second.please consider adding my idea for this block, and I feel like it would be very useful!
-
@regis Also, after fixing the physics engine, you should add a new block, which is just like the “when colliding with (sprite)” code-block, but more customizable.
What I mean by this is to add drop-down menus to parts of it, for example: “when (colliding/not colliding) with [object] from [sprite]”
the () are drop-down menus (whats inside the () are what should go into the dropdown menu)
are text boxes, where you can put in the name of the object for the first one, and the sprite name for the second.please consider adding my idea for this block, and I feel like it would be very useful!
We will look into the issue with the broken blocks.
For the new block you are suggestion, there are 2 potential issues:
-
It is not easy to trigger when “not colliding”, as collision is an instant event.
-
If the existing block is fixed that sends a message when collision happens, then there is no need to add this new block right? You can just handle that message?
-
-
@regis Also, after fixing the physics engine, you should add a new block, which is just like the “when colliding with (sprite)” code-block, but more customizable.
What I mean by this is to add drop-down menus to parts of it, for example: “when (colliding/not colliding) with [object] from [sprite]”
the () are drop-down menus (whats inside the () are what should go into the dropdown menu)
are text boxes, where you can put in the name of the object for the first one, and the sprite name for the second.please consider adding my idea for this block, and I feel like it would be very useful!
-
@regis Also, after fixing the physics engine, you should add a new block, which is just like the “when colliding with (sprite)” code-block, but more customizable.
What I mean by this is to add drop-down menus to parts of it, for example: “when (colliding/not colliding) with [object] from [sprite]”
the () are drop-down menus (whats inside the () are what should go into the dropdown menu)
are text boxes, where you can put in the name of the object for the first one, and the sprite name for the second.please consider adding my idea for this block, and I feel like it would be very useful!
We have released a fix for this issue, so it should work now. If you sitll see any issue, please let us know.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login