- User Since
- Jun 6 2008, 3:37 PM (593 w, 8 h)
Sep 10 2018
Aug 30 2014
Not seeing that here on my iMac 10.9.4
More information needed about your system.
If you have another mouse try that. I think you were on BlenderStack exchange asking about the Logitech 510. I'm using Logitech 505.
Aug 11 2014
Sorry to jump in here, but I don't see this as a bug.
You must either apply scale before doing bevel or scale in edit mode.
Aug 8 2014
Aug 7 2014
Works fine now on OSX 10.9 for both this blend file and one from T41123.
Jul 20 2014
My Windows 8.1 version works okay using the latest build e0d8e62 of Jul 19.
So must be a Mac thing. Crashes on my OSX 10.6.8 older mac, and the newer 2011 OSX 10.9.3 one as well.
Jul 19 2014
Last version I had worked okay, it was 7-10-14 hash a1aa969.
Jun 25 2014
Jun 21 2014
Jun 15 2014
Works great. Thanks.
May 30 2014
Apr 23 2014
@Kévin Dietrich (kevindietrich) If I knew it was a different bug I would have reported it. I thought it was the same issue, just wanted to add symptoms to what looked like one bug.
Apr 22 2014
I think it is still not enabled.
"Currently scale motion is not supported, only object transformations like translation and rotation. "
I have that problem just with the 'viewer' node.
It updates and displays though if you just drag a line from say 'alpha' or 'Z' closure on the Render layers node.
The line don't have to go anywhere, just drop it and it updates.
Mar 23 2014
Oh, after adding cubes do the Union in Boolean. (forgot to add that step).
I do see the error here.
Add cube scale X 2,
Add cube.001 scale Y 2,
Edit> select face of 'arms' at the end, delete, select next, delete. Do all four.
Only two faces actually delete. The other stay there and can't be selected.
Mar 16 2014
Yes, does it here on OSX as well. Hash 3d3031d1
Mar 14 2014
I see that happen on 2.66 where you need to hit "." to correct it.
But on the latest release of 2.7rc2 I don't see that on OSX.
If you hit "." does that let you zoom in further?
Mar 13 2014
I agree. There is also the 'measure panel' addon that works quite well.
Yes, crashes in OSX as well.
Bug should be reported in Addons though.
Crash log and pic of error attached.
Mar 8 2014
Yes, I see it happens as far back as 2.65.
'Show Brush' should really hold user selection between modes.
Not seeing that on OSX 10.9.2
Mar 7 2014
You have one plane exactly on top of another. If you remove that plane or move it the circles go away.
Maybe there was a bug in 2.69 and now it's fixed.
Backwards compatibility is not very important.
If there is a bug with 2.7 that is important.
Mar 5 2014
For me this bug works just by adding cube, add monkey, add boolean to monkey (leave default intersect) choose cube, crash.
Yes, that was fixed in T38742.
Try the latest build from BuildBot.
Yes, confirm that is breaking in 2.7 release candidate.
But that bug was fixed in T38742
If you download the latest build from BuildBot you will see it is fixed.
Mar 4 2014
Can't reproduce on OSX.
So to clarify, you are saying it is broken on 2.69.7, but works on 2.7 4789793?
Mar 2 2014
Can confirm it on Mac OSX 10.9.2
Feb 27 2014
More information needed.
Feb 23 2014
Yahoo, that was fun!
Hmm, I could not make it work in Terminal either.
I'd like to add, (maybe a new bug, maybe connected) that when you RMB > edit source
on a button on a pop up (a crashless button) it will give you an error of "Active Button Not Found"
Yes, I can confirm that in this (T38780) a crash happens on mouseover of
the box type that has two arrows on the right, one up, one down.
(I guess it's still called a 'dopdown' box even if it drops up).
Same box on UV editor and two different F6 pop ups.
So that pop up with that box is consistent with this crash.
Feb 22 2014
Found one more mouseover event that causes crash:
Feb 21 2014
Feb 17 2014
crash report here:
Jan 20 2014
Ah, I see, yes you are right.
The clip distance when set the same in 2.68 does it as well.
Moving it to start at 1cm instead of 1mm gets rid of that.
Sorry about that.
Jan 18 2014
To add, first pic is 2.69
second pic is 2.68
Bug reporter totally erased my bug. (Maybe because I did not add title, added title and hit submit.)