- User Since
- Aug 14 2011, 8:17 AM (396 w, 6 d)
Sep 10 2017
Jul 6 2017
May 10 2017
Very nice solution, Aaron! ❤
Apr 28 2017
@Luca Rood (LucaRood) Basically I mean the UV coordinate, which is different from other coordinates. Please see the updated file / screenshot.
Apr 24 2017
+1 for soft limit.
Apr 23 2017
Oct 21 2016
Agree. It should be moved out of that tab.
Jul 22 2016
Jul 18 2016
Jun 18 2016
It does work. Thanks for the info! :)
@eroMoD, it seems you selected all edges. To reproduce, just select the corner loop. It both occurs with Ctrl B and modifier ( with Vgroup method).
Jun 17 2016
Jun 11 2016
Jun 8 2016
Jun 7 2016
Jun 6 2016
Actually, there are several crash triggers here, all related to backdrop. See this video: https://youtu.be/GWx4XrIQilA
And I do reproduce it with the daily build today. 04bcaf0
Yes. I can't reproduce it with 2.77a official release either, but I do reproduce it with the daily builds. (June 2nd, I think). File uploaded, though I tried many different image sequences, even single image.
Jun 4 2016
PS: It also occures with other nodes like Mix, not sure if something wrong with the Image node.
May 15 2016
May 7 2016
Apr 16 2016
Mar 9 2016
Mar 4 2016
Oops, I see. Sorry for misreport... :)
Mar 3 2016
Mar 2 2016
Jan 29 2016
Jan 7 2016
Jan 2 2016
Dec 27 2015
I see, thanks for reminding.
Dec 21 2015
Yes. Another thing here is : we have to manually type "000001‘ after the default editable "0.0" value. And, if clicking on arrows, it only allows increasing / decreasing by increment of 0.01, instead of 0.0000001), which is not that easy to control as well imho. So, maybe it is reasonable to set a higher scale for this value for easy tweaking.
Dec 19 2015
Dec 18 2015
Then maybe implementing as a toggle named, for example, "Make Compatible"?
It works now. like a magic! :D
As I mentioned in the duplidated task, it seem to be related with fonts, some fonts are OK, while others not (including the default font). I just tested in Ubuntu 14.04 LTS 64bit (English version), it still occurs. So i don't think it's kinda OS related.
Dec 17 2015
Dec 16 2015
Dec 15 2015
Nov 14 2015
Oct 24 2015
Thx Campell, border select works fine with 4ff1011. :)
Oct 19 2015
Oct 16 2015
Sep 21 2015
Sep 11 2015
Sep 4 2015
Aug 29 2015
Aug 27 2015
Thanks a lot for targeting it finally!
Aug 16 2015
Aug 8 2015
Jul 29 2015
Sorry for off topic, but for quite long time I was wondering why not bring a kind of "Auto Refresh" button. Because each time when I need to adjust something based on the current VSE preview, the "Refresh Sequencer“ button has to be countlessly clicked. Is that for the similar reason as this?
Jul 28 2015
Jul 22 2015
Two more examples to show the importance of this feature:
Jul 16 2015
Sure. Done yesterday, discussion is needed indeed. :)
Jul 15 2015
Ah, cool, though I think it would be better to add it as an option to the modifier, sometimes we do need global masking for multiple strips. :)
Jun 1 2015
I confirm It happens on all node mode (material nodes, compositor, etc), it just happens more obvious on that addon due to the node item design. Or can it possibly be an OS based issue? :| Since all people I know who are experiencing this is on Windows OS. Didn't get chance to test on other OS yet.
It would be helpful to reproduce it by zooming out a node a lot. And I noticed a single or double clicking again somewhere apears to recover it from that behavoir.
eh... I guess mostly by clicking while dragging around the border of the checkbox instead of the center?
May 30 2015
May 18 2015
Just found someone mentioned the same thing a while ago at StackExchange here. BTW, unlike 2.74, I see 2.73 looks fine.
Just tried a bit more. I think it happens specifially when you dragging on the button while having the node dragged at the same time (by accident), especially when the initial speed is a bit fast. I just made a video here, and added by the time it happend there. Hope it helps.
Apr 30 2015
Apr 19 2015
Thanks for the information. The resolution tip does help a bit, though not perfect :). However, I'm still wondering why 03:33 and 03:53 behave differently? They used different but quite similar fonts, but you can see different results on some closed holes that I marked. I think there seem to be something else there other than the self-interesection issue, because, as you see, the 2nd one actually works perfectly, while the 1st one doesn't, though both are in the same complex level, and which cannot be solved by the resolution trick.
Apr 18 2015
Apr 13 2015
Though I want to do more solid tests on this. But, so far so good. :)
Apr 8 2015
Ah I see. Thanks for the information. :D
Great work guys! I noticed it also supports preview for complex fonts like Chinese, Japanese and Korea, which is really cool. However, the preview text seems always be English. IMHO, for such fonts, it would make much more sense to use localized characters or symbols. I wonder if it would be possible, too?
Apr 4 2015
Apr 3 2015
This is a long waited i18n feature (just thought it would be super hard to implement). Thank you so much Bastien!
Mar 24 2015
@Antony Riakiotakis (psy-fi), I just thought it is very intuitive, to repeat it, just:
Mar 23 2015
@Campbell Barton (campbellbarton), I don't quite understand "the proportional edit center just happens to use the pivot point." In fact, the operating center is still on active element, not using the pivot point. Please correct me if I didn't follow you well.
Mar 21 2015
Mar 18 2015
Ah, yes, it is copy to selected that crashes blender. sorry for typo! , :)
Mar 13 2015
Mar 11 2015
Ah, I see, so it isn't a sort of perppective-only issue actually, and same would happen in ortho, right? I believe this is about the algorthm as well at the beginning, but not so sure about that. Thanks for clarify.
sorry, I should mention that, Yes, with tablet, for sure. :)
Mar 7 2015
Yes, typing asian characters accidentally in numerical slider will crash blender, tested in Windows 7 64bit, with Chinese IME.
Mar 6 2015
Mar 3 2015
Err... I think so. This is a feature since 2.71. see here.