Object origin conflicts with physics #35930

New Issue

Kristopher Reed · 2013-07-01T04:39:20+02:00

Kristopher Reed commented

2013-07-01 04:39:20 +02:00

%%%--- Operating System, Graphics card ---
Windows 8 64bit
CPU: Core i3 2120 3.30ghz
RAM: 8GB
GRAPHICS: GTX460 1GB

- Blender version with error, and version that worked ---

Bugged: 2.67(a/b) Working: 2.65(any) 2.66 (Possibly?, see below)

- Short description of error ---

When using Blender 2.67 (The original release and revisions A and B) changing object origin stops working properly at random. Once the bug gets triggered and you click any of the options in the transform menu the Origin Point does not move. What happens is either the mesh it self gets moved or nothing happens at all. However opening a bugged save file in 2.65 the problem disappears and all options in the transform menu begin working properly on the bugged save file. Fixing the problem in 2.65, saving and reopening in 2.67 and the issue is no longer present.

Absolutely NOTHING that I try fixes the issue inside of 2.67! I've cleared the settings of the origin, location, etc. I've used Ctrl-A to try to reset all options, nothing works?

Triggering the bug is difficult as it happens at complete random, however once a mesh is bugged it stays bugged forever until you open it in an older version. I can complete whole meshes without any issues at all, while other times almost every mesh gets bugged out and I have to open the file in an older version to fix the problem. I have NOT checked 2.66 for the issue, as I had skipped 2.66 when it was released as 2.65 was the most stable version that I had used for what i was doing at the time. I really enjoy using 2.67b as it has most of the bugs fixed and features I had wanted in blender for a long time, but this origin issues is really making it difficult to work at a stable pace.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Use the attached save file in 2.67(any) see bug happen, then open in 2.65(any) to see it working properly.

Object Mode - Object - Transform - Origin to 3D Cursor ( Any of the options really, as once the bug triggers none of the options really work like intended)

Using the above save triggers the bug 100% of the time. If i'm being stupid and have something turned on that is causing this please let me know. However i'm pretty sure this a bug as I've never had any issues until 2.67.

%%%

%%%--- Operating System, Graphics card --- Windows 8 64bit CPU: Core i3 2120 3.30ghz RAM: 8GB GRAPHICS: GTX460 1GB - Blender version with error, and version that worked --- Bugged: 2.67(a/b) Working: 2.65(any) 2.66 (Possibly?, see below) - Short description of error --- When using Blender 2.67 (The original release and revisions A and B) changing object origin stops working properly at random. Once the bug gets triggered and you click any of the options in the transform menu the Origin Point does not move. What happens is either the mesh it self gets moved or nothing happens at all. However opening a bugged save file in 2.65 the problem disappears and all options in the transform menu begin working properly on the bugged save file. Fixing the problem in 2.65, saving and reopening in 2.67 and the issue is no longer present. Absolutely NOTHING that I try fixes the issue inside of 2.67! I've cleared the settings of the origin, location, etc. I've used Ctrl-A to try to reset all options, nothing works? Triggering the bug is difficult as it happens at complete random, however once a mesh is bugged it stays bugged forever until you open it in an older version. I can complete whole meshes without any issues at all, while other times almost every mesh gets bugged out and I have to open the file in an older version to fix the problem. I have NOT checked 2.66 for the issue, as I had skipped 2.66 when it was released as 2.65 was the most stable version that I had used for what i was doing at the time. I really enjoy using 2.67b as it has most of the bugs fixed and features I had wanted in blender for a long time, but this origin issues is really making it difficult to work at a stable pace. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Use the attached save file in 2.67(any) see bug happen, then open in 2.65(any) to see it working properly. Object Mode - Object - Transform - Origin to 3D Cursor ( Any of the options really, as once the bug triggers none of the options really work like intended) Using the above save triggers the bug 100% of the time. If i'm being stupid and have something turned on that is causing this please let me know. However i'm pretty sure this a bug as I've never had any issues until 2.67. %%%

Kristopher Reed commented

2013-07-01 04:39:20 +02:00

Changed status to: 'Open'

Campbell Barton commented

2013-07-01 11:23:17 +02:00

%%%The problem here is caused by the object being a dynamic rigid-body,
the physics system and the origin functions are conflicting, assigning to Sergej.%%%

%%%The problem here is caused by the object being a dynamic rigid-body, the physics system and the origin functions are conflicting, assigning to Sergej.%%%

Sergej Reich commented

2013-07-03 10:21:27 +02:00

%%%Setting the origin for a rigid body (as well as other modifications) won't always work correctly midway through the simulation.
If you want to modify the simulation objects you have to do it on simulation start frame.

The other problem in the file is that the object has a rigid body but isn't in a rigid body group.
You can eiher remove the rigid body or create a group and assighn it to the rigid body world.
%%%

%%%Setting the origin for a rigid body (as well as other modifications) won't always work correctly midway through the simulation. If you want to modify the simulation objects you have to do it on simulation start frame. The other problem in the file is that the object has a rigid body but isn't in a rigid body group. You can eiher remove the rigid body or create a group and assighn it to the rigid body world. %%%

Kristopher Reed commented

2013-07-03 23:51:54 +02:00

%%%That's the thing though I never made it a rigid body, It was part of a subdivided model that I am creating. I never once turned on rigid body, knowingly anyway. I don't see any Hot-Keys for any of the physics options, so I don't think I would have accidentally turned it on? Are there any Hot-Keys for those options that I may have brushed or something?%%%