I know, for that reason I think that this must be complete with a little change in the paradigm that allow users go back to the transform tools when they enter in panic mode.
i noticed that in blender 2.7 linked objects got a cyan outline color when selected and a cyan origin also when not selected to indicate the link. in 2.8 this seems not to be the case any longer and its not possible from the viewport to see if a object is linked or not.
It would be nice to get this back.
I see that also in the outliner the color scheme is the same as normal objects, was this change maybe a design decision on the new color theme?
the chain is not good enough?
how does that chain show me something in the viewport? in a example like that it might be ok but if you have hundreds of objects with multiple collections and partening level you will not see those chains
1 Like
Last Blender 2.9Alpha
This tooltip is still here
I just want a camera ālook atā constraint (similarly to ācircular arrayā). I donāt want to have to do an internet search to find out the technically correct but impossible to remember answer every time:
This actually has been āfixedā a couple weeks ago by changing the default axes for that constraint
Not sure about the others
So, next step in learning camera animation:
I understand keyframe animation, but this apparently creates a graph, which is new to me, and I had no idea where to find it without doing another search:
Here, I didnāt understand why I couldnāt just select the curve in the graph and insert control points in it and drag it aroundā¦ apparently I need to go to another āhidden by defaultā N panel and look for the oh-so-logical āmodifiersāā¦and modify some Y= value? At this point, I just gave up.
That UI is not made for normal humans.
Instead, I keyframe animated the offset of the āfollow pathā constraintā¦ itās just unfortunate that itās not normalized.
Another thing Iām trying to learn is how to have different sets of animations inside of the same file, using different scenes. However, I havenāt figured out how to move objects between scenes because dragging and dropping doesnāt work:
Also, in this view, itās impossible to tell what objects are linked into this new scene, and what objects are ālocalā to itā¦
EDIT: Apparently, if I move the objects in the layer view to the newly created collection in my new scene, they disappear from the old scene, which is very nice (but what works in one view, should really work in the other to not break UI consistency). However, I still canāt see in the outliner what collections are local to the current scene and which collections are linked!
1 Like
This operator creates a curve modifier, which are tools normally used by animators on a daily basis for cycling, stepping, etc. so nothing too spooky really. Agree this should create a linear curve from two keyframes instead, since user is likely to go and modify that curve anyway.
In any case thatās the ālegacyā way (not sure why itās not scrapped but I think it should) - you can use the āfixed positionā value and animate it instead, which allows for different objects to travel at different speeds along the curve. Thereās only one āevaluation timeā property per curve and any object bound to that curve through a constraint is going to obey that unless āfixed positionā is checked. (I hope this is clear)
1 Like
Absolutely right. Iāve brought this up before. There should be a way to distinguish collections linked throughout several scenes. They could have a little chain symbol on their icon for instance, or a number counter (so that the user knows in how many scenes theyāre linked).
Oh, now I finally understand the hate for Blenderās āwindow managerā:
Also, when I want to split a window, itās not always I can choose any corner to drag from. I have to try two or three corners before I find one that works (and no, Iām not going to use the āarea splitā menu, I clicked on a border and because it doesnāt show a preview I have no idea which of the two adjacent areas it wants to split).
More camera track + scene oddities:
The delay when I switch ātrack toā from Y to -Z is because the GPU gets pegged at 100%ā¦ this sometimes is persistent, forcing me to delete the constraint in order to re-gain control of the app.
I donāt understand why, because in the other scene, an identical setup works just fine.
EDIT: Hahahaha, my GIF recording software removed the delay! 
Perhaps because the GPU freezes the entire PC for several seconds. Anyway, you can still see that the constraint goes from red to ok and then back to red when I switch to -Zā¦
What is happening in this gif ? I can see you collapsing two editors and resizing another ?
I canāt quite see what you are trying to illustrate there. I see a successful join, but a cancelled split, and not sure why. Can you explain it better?
All four corner widgets are the same size and are in the same relative place. Generally the (crappy and hidden) detail that screws people up is not knowing where exactly to click. You donāt want to click right in the corner between areas, but at the location of those (hidden) widgets:
When I right-click on any edge I get that menu with the two āsplitā options. When I select either of those I do get a preview that will show me exactly where the split will occur. In fact I can start on any edge and then split any area at all, even those far away from that initial menu.
Iām curious if this is a display issue, where I see the preview lines and you do not, or is some part of the process confusing and could be changed or even the documentation improved.
I was testing the new geometry creation tool, and there is an option to close the base cone āBase Fill Typeā, which has been hard for me to understand its function. Maybe because Iām not English, but Fill understands it as occupying a space, not covering a hole.
I remember that at first the name the face actions āFillā and āGrid Fillā also seemed strange to me. I think, āClosing Holesā, āGrid Capā, and āBase Cap Typeā, would be more understanding.
2 Likes
He definitely mentioned āsplitā though in regards to that.
With merges they are now (in master) a bit more tolerant of being unaligned. So you could merge these left/right now:
But not any more than that as there are just too many complications possible.
1 Like
I know there are some complex cases but why not just show 2 arrows in cases where itās 2 to 1 area merge? Having to manually do split is very finicky when you just want to collapse something like outliner.
1 Like
Probably because I canāt see in your example how you would differentiate between the following two processes. The first looks more likely to be the intended outcome than your second.
2 Likes