- User Since
- Jan 27 2005, 5:54 AM (733 w, 4 d)
This may be related to : https://developer.blender.org/T58302
Fri, Feb 8
STL is a unit agnostic format - Is it possible your consuming application is expecting 1unit = 1mm whereas Blender exports as 1unit = 1m?
I see this behaviour in Cura using Blender's 3D Print Toolkit.
Jan 16 2019
Thanks for the update Phillip.
I've posted a change proposal in Right Click Select.
Jan 15 2019
Jan 7 2019
I would expect separate Meta objects should not interact with each other (Although the Meta components within the object should)
Dec 4 2018
Under further investigation - The same behaviour seems to be present in Blender 2.79a.
This may indicate need to have a deeper dive into Meta objects than a simple bug.
Nov 30 2018
I'm changing this to Low priority due to the work around above.
UI Experience should still be that if you select Metaballs to append Blender should import the Metaballs, not just the data, so I'm not dismissing it altogether.
Mar 8 2018
By Design - See comments.
This activity is by design in Blender.
I have reproduced the error on a completely different computer with Windows 10 and an Nvidia 640m all updated drivers.
Apr 11 2014
@Sergey Sharybin (sergey) , Confirming: The file I posted causes the compositor to slow and freeze when connecting the Plane Track Node.
Apr 9 2014
You should be able to duplicate it here: Open the blend file and connect the Plane Track node as per the grease pencil arrows.
I am having the same problem.
Feb 25 2014
My card is Nvidia 640M (Laptop)
I investigated other Blender forums and found a reference to a duplicate problem - I was unable to grab the visible "Front" edge, of the manipulator, but I could grab the invisible "Back" edge.
I have no choice but to suspect my own system. The rotation widget still fails to function, but I will continue testing locally.
Feb 24 2014
OK - Now I'm really confused. Please disregard the scaling problem - It's also in 2.69 so I'll put in a separate but report once I'm sure it's not my fault!
Sorry for any confusion - second part of the video I switched to the scale widget to demonstrate how, when rotated, when I scale on the global X, the Y axis is also scaled.
(Object mode only - I switched to Edit mode after this to demonstrate the expected behavior)
Video of the issue in action!
I'll try it in different scopes (Global, Local, Normal) and get back to you...
Additional note: In edit mode, scaling widget seems OK in all directions, but X and Y seem transposed for rotation.
Jan 30 2014
On further reflection I think that you are telling me that if I want to use the build modifier, I need to reorder the faces.
In that case: The page in the Blender Manual is wrong as it specifies any elements, (With the exception of Material sorting) can be re-ordered in this way - Not just faces.
Jan 29 2014
Alternately, if you want to use the same modifier twice in the same animation, you can keyframe the Influence option. Set it to 0 when not used and keyframe to 1 and back to 0 when you need it.
Can you not use the "Restrict Frame Range" options in the modifier?