You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider a Blender object whose origin is not in its geometrical center (that is, Object > Set Origin > Origin to Geometry changes its origin). When they are animated using movement or rotation, their physical and graphical appearances are not located in the same place.
More precisely, it seems like if $v$ is a vector from the origin to the geometrical center, then physical location can be obtained from the graphical location using movement by vector $v$, and the intended location is graphical location. It feels like the physics animation location modifier is applied relatively to the object, and not to the world.
It probably isn't really noticeable on the maps with objects without rotation, as for them authors tend to just move the origin to the geometrical center and then adjust location animation by a fixed value. But for rotated objects, the origin is also a point around which the object is rotated, and it cannot be solved as easily.
Example (simple arena, cubes with side length 10m, one of cubes is raised up by 20m, kart can go through the cube, same picture happens when they are moved and when they are rotated):
Maybe I am not aware of some other method to modify something in Blender and not in the code - those methods I heard about are way too complex to handle a simple rotation. An example of addon with that bug is Emerald Arena version 2 which will be released in May 2024 (you can see many normals for the karts which are standing on the podium, in another place):
Steps to reproduce
Make an object whose origin is not a geometrical center (e.g. a cube moved by 1m in edit mode)
Add location/rotation animation
Open STK with physics debug and make sure physical boundaries are not in the same place
Configuration
STK release version: latest git e47958f, happens in many commits before too - I failed to bisect for now due to strange visibility bugs, I'll edit it I manage to.
STK Source (PPA, distribution package, official binary, etc.): github
Blender version used: 2.93
The text was updated successfully, but these errors were encountered:
Description
Consider a Blender object whose origin is not in its geometrical center (that is, Object > Set Origin > Origin to Geometry changes its origin). When they are animated using movement or rotation, their physical and graphical appearances are not located in the same place.
More precisely, it seems like if$v$ is a vector from the origin to the geometrical center, then physical location can be obtained from the graphical location using movement by vector $v$ , and the intended location is graphical location. It feels like the physics animation location modifier is applied relatively to the object, and not to the world.
It probably isn't really noticeable on the maps with objects without rotation, as for them authors tend to just move the origin to the geometrical center and then adjust location animation by a fixed value. But for rotated objects, the origin is also a point around which the object is rotated, and it cannot be solved as easily.
Example (simple arena, cubes with side length 10m, one of cubes is raised up by 20m, kart can go through the cube, same picture happens when they are moved and when they are rotated):
Maybe I am not aware of some other method to modify something in Blender and not in the code - those methods I heard about are way too complex to handle a simple rotation. An example of addon with that bug is Emerald Arena version 2 which will be released in May 2024 (you can see many normals for the karts which are standing on the podium, in another place):
Steps to reproduce
Configuration
STK release version: latest git e47958f, happens in many commits before too - I failed to bisect for now due to strange visibility bugs, I'll edit it I manage to.
STK Source (PPA, distribution package, official binary, etc.): github
Blender version used: 2.93
The text was updated successfully, but these errors were encountered: