- User Since
- Mar 7 2018, 12:51 PM (75 w, 5 d)
Sat, Aug 10
Sounds good, but this is not the right place to put feature requests. I'd recommend expanding it with more details, concept pictures, maybe references to other successful implementations, etc. and posting it to RightClickSelect so regular Blender users can discuss the merits of your proposal and vote on it.
I think @Andrzej Ambroz (jendrzych) is suggesting to get rid of the inline datablock icons that appears when the item is folded (orange box in image). You can still see the object hierarchy as normal when expanded, so you can still examine which datablock belongs to which object - but it is a little redundant to tell the user that "this light has a light", "this object has a mesh", "this camera has a camera", etc. which is the only thing that the inline icons do.
Thu, Aug 8
Your card (Intel HD Graphics 4000) is an Ivy Bridge architecture GPU; this predates Haswell and is therefore, as per the requirements page, not supported.
Please fill in the report form with information about the problem you are having, the Blender version you are using, the operating system you have, etc.
The graphics card (Radeon HD 2600 Pro) is a Terascale architecture GPU; this predates 1st gen GCN and is therefore, as per the requirements page, not supported.
Wed, Aug 7
Works for me. Please specify which version of Blender you are using.
Tue, Aug 6
It seems they rotate around each element's island. If they share a common island, they are considered as one collective "individual".
Can reproduce on latest master.
Please edit your post to fill out the report form.
Describe your problem, how it happens, and what you want to change.
Not sure. I'd suggest that if you can, roll back your driver to the version that worked with 2.79.
I believe your graphics card is not supported. As per the requirements page, blender 2.8 supports "GeForce 200 and newer". Your card falls in the GeForce 9 series, older than the 200 series.
If you can open Blender 2.79, please make and attach a system info report.
Mon, Aug 5
Also please specify the graphics card you are using, as some older graphics cards are not supported (see requirements page).
Your card (from AMD Radeon 6600M and 6700M Series) is a Terascale architecture GPU; this predates 1st gen GCN and is therefore, as per the requirements page, not supported.
You must have pressed this button (or a keyboard shortcut for it):
Moreover, your card (ATI Mobility Radeon HD 4200) is a Terascale architecture GPU; this predates 1st gen GCN and is therefore, as per the requirements page, not supported.
Looks like you need go to Preferences -> Themes tab -> User Interface panel -> Menu Back subpanel -> Inner -> increase Alpha. If not that, then something in that general area.
You need to use the UV editor:
Ah! You're right, that behaviour is almost certainly not as intended.
When I uncheck UV Editor -> View Menu -> UV Local View, I can select and move correctly.
This is expected behaviour. Moving an object and constraining along an axis works in the same way. If you want to move only on X axis, then it makes sense to cancel any Y movement. If you want to constrain the cursor to the XY plane (ie. horizontal/ground plane, without Z/vertical movement), press Shift+Z.
Groups have been superseded by Collections. They are visible in the outliner under Display Mode -> Blender File.
Sun, Aug 4
make sure this is enabled.
I think this is correct behaviour. I'm guessing that internally blender does this: first unparent the object from the old parent, then parent it to the new parent. That is the equivalent of this:
Sat, Jul 27
Please, if you expect the devs to download a gigabyte-sized video and then watch it for ten minutes, at least have the courtesy to fill in the report description.
Set the curve's origin to it's start vertex.
Jun 17 2019
For both "skarnier snyer" objects, shifting them very slightly on the x-axis (say, 0.005mm) is enough to make all cuts work correctly.
on latest master, looks like this:
Please include exact steps for reproducing this problem (ideally starting from the default scene, or upload a blend file with a simple scene demonstrating the problem).
Jun 13 2019
Ah, ok then. Yep that's a bug.
I see two things here:
screenshots from that file:
That's a large file! Could you try removing extraneous things from it so that it's just the bare minimum necessary to replicate the problem? (eg. ideally your file would just be the eyes and associated material/texture.)
works for me on latest master.
Jun 11 2019
Looks correct to me. The crop option is meant for final renders. This behaviour matches 2.79.
You should provide a description of the problem when you submit a bug. Nevertheless I'm guessing the issue is that the hair doesn't collide/interact properly with the cylinder. This is a known problem and the hair system (particularly collisions) is due an overhaul at some point. For now, if you search around the blender community you should find others who've had similar issues and shared their workarounds.
Jun 10 2019
Can reproduce, crashes in latest master.
I believe this was addressed here https://devtalk.blender.org/t/blender-ui-paper-cuts/2596/2894. Does that work for you?
Jun 9 2019
Can't reproduce here with latest master, no crash.
Can't reproduce here with latest master.
Blender doesn't know how to differentiate between extruding perpendicular to the surface and extruding in the plane of the surface. If it did, and automatically toggled the extra fill face, it would potentially break workflow for those who extrude then transform in two seperate steps. Blender can't foresee your intent, so you have to let it know by choosing a particular extrusion mode.
works for me, same blender version.
Can reproduce, crashes with latest master.
This is because selecting all edges around a face also selects that face, so the face is also extruded.
You can get the behaviour you want by hitting Alt+E (or go to 3d view header -> Mesh menu -> Extrude submenu) and choosing Extrude Edges.
Jun 8 2019
Here's screens from official builds of 3rd June d62a749fcf48 and 4th June e80cbdac331a:
box select won't autoscroll but will select items even if they overflow outside the outliner window.
Can reproduce on latest master. Wiggling one end of the default bezier curve, with a subsurf modifier (view subdivs=1) it will leak about 4mb a second. Add some bevel geometry, some extrusions and up the view subsurf level, and it can start haemorrhaging 100's mb a second.
Can't reproduce in latest master with object volumetrics.
Does go darker with world volumetrics with ortho camera, which in a way is to be expected: an ortho camera is idealised as being infinitely far away, so an infinitude of even the thinnest atmosphere would obscure everything.
The weird thing is that, for me, it doesn't go full black at low densities. Go to Properties->Render tab->Volumetric panel->increase End distance.
Jun 7 2019
Can confirm that it did once work, now has the black border.
Yep, clip start.
Works as expected here. Apply scale (Object mode -> Ctrl+A -> Scale), then inset treats all axes the same.
Jun 6 2019
I think their problem is this:
Jun 5 2019
Can't reproduce with either eyedropper from Properties editor -> Tool options, or from Dyntopo dropdown in topbar (including quickly sliding the pick coords in the redo panel). Tried doing lots of picks; closing and reopening blender; alternating which eyedropper clicked - no crash.
Probably duplicate of T58920.
Can duplicate (Linux Mint 18.3, NVIDIA GeForce GTX 750 Ti, today's official build e80cbdac331a)
Just to be absolutely sure, duplicate-and-rotate is Shift+D - R - Click, and not Shift+D - Click - R - Click.
Duplicate then rotate as seperate steps doesn't cause problems.
Jun 4 2019
Mar 26 2019
It looks to me as though the memory allocation is not entirely runaway, rather blender is just going all the way up to max subdivisions (Properties -> Render tab -> Subdivision panel ->Max Subdivisions). At the default of 12 subdivisions for a simple cube, the required amount of memory is about 16gb (probably, I always pull the plug on it before it gets there though).