@Steffen Dünner (SteffenD) Yes that looks like the same issue. Hopefully the fix is straightforward.

Hi, for me everything works blazing fast. I think you need to try to track down the problem somehow.

Can you try to increase thickness and distance on contact shadows but also decrease bias and increase exponent on the Sun Lamp?

I noticed there are FaceMaps now which are not only useful for animators but really for any modeller who wants to save certain face selections (some checkerboard selections weren't possible with vertex groups).

Not sure but for me it looks still the same? Maybe it's because I'm using the 2.79 instead of newest builds?

Yeah it looks similar but after watching the video I don't think it's the same.

Hi again,

Yeah it looks like the speed is linked to font size. So what Bastien noted in the first comment might be the cause - loading huge amount of glyphs.

@Stephen Pflanze (megasoid) Question for you ^

@Dong-Hyun Kim (temeddix) if you read all the comments you'd realize it's actually not a simple problem. It's really not helpful to call problems simple and urging people to fix them. It's good to bring the issue up and ask if there has been some progress but try to steer clear of the "can't believe this still hasn't been fixed" or "such a simple problem". Let me be clear though that I've done both in the past but I wish I hadn't.

@Alma Talp (AlmaTalp)
All this doesn't take from the fact that 2.8 wireframes do a lot more heavy-lifting and provide much more clarity in many scenarios that aren't extreme.
For example if you only work on one floor at a time it gives you much much much better understanding of what you actually see, although everything is dithered.
2.79

@William Reynish (billreynish) That's great news. Amazingly great news^^ Application template ready. So does this mean we could change color per icon if needed?
I will probably tune mine in Properties menu to corresond with the current general set of colors / greys.

AFAIK unless you start changing materials you don't break anything. It would be fine to have a warning but this issue kind of resolves itself with 2.8 materials being synchronized across renderers.

Not sure here but have you trying holding ALT before clicking into the number field and then typing it? There is sort of a hidden feature in Blender that if you hold down ALT the action gets performed for all selected. But that does not work completely consistently (probably why it's hidden) so it might not work here.

Closing this as duplicate of: T57320

Can the icons be scaled up and have more white space between keys? Asking more as a UI question if icons can scale together with text tbh (are vector). Or are the icons bitmap? Good job this looks great now just the interpolation with the curves, that would be a massive help with motion graphics.

In T53840#505679, @Andrzej Ambroz (jendrzych) wrote:

1. in real use, icons are apposed in UI in small bunches that are contextual. Colour ain’t that much needed here. Honestly, some of current icons pop out too much because of their colour, attracting user’s attention to particular parts of interface. It would be good to incorporate some colour codes though - in File Browser, Asset Manager or Outliner. In every place, where one has to manage big lists of items.

Sorry but this website is in English.

In T55162#543383, @Paul Kotelevets (1D_Inc) wrote:

Current Blender Keymap Inconsistencies:

V - Merge vertices
Alt+V - Rip verices
have horrible defaults

Doesn't happen here. Also you should not have to work on 500k+ mesh in Edit Mode. It's something to avoid at all costs.

I don't recall reading there is a rule not to reopen tasks from others when they are still valid.

Reopening this to raise awareness after 5 months as many many materials rely on NodeGroups with inputs.

@adam earle (adamearle) It needs to be reproducible every time.

Check here for more info on the process of how this was thought out: T55162

Sorry, opened again as I see it's a Patch and can't judge the code^^ Still a good idea to further discuss this on devtalk or mailing lists.

This is mainly a bug tracker so closing this.

Could you try if this happens with the latest 2.8 builds too?

When it comes to "visual" issues it's always best to attach images describing it well. In this case maybe even editing how you think it should look.

Don't think this is an issue but you're not using the modifier right.

@adam earle (adamearle) could you please change the name of the task and it's description so that it's clearer?

Don't think there is a problem with reflection but there is an issue with refraction.

Guessing from your hardware specifications this is just the way it is and is most noticable on slower computers.

Can confirm this issue.

In D3788#86520, @William Reynish (billreynish) wrote:

@Adam Preisler (Alphisto): Yikes, I don't think that will work in practice. That's way too information dense and will just look like visual noise. You have to understand that these icons will be displayed really small and there will be loads of them.

To be useful, this feature has to be simple and clear to the user, otherwise it's just visual noise and random shapes.

@William Reynish (billreynish) I had a go at it and figured something out.. but question remains how it works in the dope sheet UI and also how it feels during work..
I noticed that different handle types use different colors for their handles in 2.79b at least. That is not too bad, but the problem is that for example aligned and auto-clamped use almost the same shade of pink. So maybe long dashed and dotted could be introduce to ease this up a bit.

It's not that easy because the mesh doesn't have volume data for material assignments.

Can Confirm It's true that Boolean modifier seems to break UVs. Doesn't really matter if it's animated or not. If you apply modifiers the UV Map is simply gone. It works fine in 2.79b also for Material viewport shading mode.

Closing this because AFAIK it's not a bug. Try adding materials with the same name to the boolean brush object. It cuts with those materials:)

@adam earle (adamearle) then I suggest we consider this issue as resolved and you can close this task.

Good to read:)

Maybe this helps?

In D3788#86490, @Alexander Gavrilov (angavrilov) wrote:

For instance, if you scale an auto-keyed stretch of animation in time via Dope Sheet (or move keys in time), auto handles will adapt, but manual ones won't and your curve won't be smooth anymore.

Thanks for further clarification. I see that there is a lot of underlying complexity and personally I don't need a parametric slider because the 7 presets work just great and at least no need to have random "on a whim" values like 1.5123 in the slider...

In D3788#86487, @Alexander Gavrilov (angavrilov) wrote:

Free and Aligned are all non-automatic handles and thus I represent them with one <X> "here be dragons" icon.

@William Reynish (billreynish) Curves when it comes to sequentially always rising value with different interpolations.. Looks great and really readable.

I tried this in the October 12 version and couldn't reproduce this on 2 computers, both Windows 10. Have you tried to reproduce this multiple times?

Thanks Troy! I always enjoy reading a good explanation of such topics. The 7 premade Contrasts for filmic work great it's just that I realized that Corona Renderer has a value input for Contrast so wondered if maybe it's not exposable. Some discussion about it is here: https://corona-renderer.com/forum/index.php?topic=12552.0

@William Reynish (billreynish) I like both but see an inconsistency with the current look of "Keyframe is not changing"

Can confirm this and it also happens in 2.8.

This issue will be solved, closing this as a duplicate of: D3650

Please post screenshots, otherwise this is too vague.

@William Reynish (billreynish) Looks great. My favorite is the graph version but I can see all of them useful tbh.

Why so much system information? This doesn't look like a hardware issue.

Just click on the minus next to vertex color data and that deletes it.

Out of curiosity: could you try this on another computer? It's just that this being a specific Wacom tablet chances are it's caused by it or only for it in Blender for some reason.

Doesn't happen to me here, Win10 newest 2.79.

I can't really judge if this should be a feature request but maybe one of the addon's authors might?

Hi, you can uncheck "Use Nodes" in the World tab in Properties Window. That turns off the Environment light.

I think what might be happening here is either:

Can't seem to reproduce this issue.

This is not due to Filmic.

Can confirm this.

Hi, after a quick search I found this and I think you might find it useful:)

Unfortunately these 2 features contradict each other on a fundamental level so this is the way it has to be...

I think opposing sides are related. Left Right and Top Bottom are very important for the brain.

@Duarte Farrajota Ramos (duarteframos) I think it's actually amazing how the options are organized. Left Right are opposites and Top Down are also related to each other + additional options for lookdev and rendered.
People are simply more used to moving mouse either horizontally or vertically than in a hexagonal grid.

I looked over the rest of the 2.8 theme and it seems that active option background actually uses the blue color that in the pie menu is currently used as highlight background color.

Like that while hovering with the mouse over let's say "Solid" and you press Z it would open another 3 options which are for example user defined custom versions of the solid shading mode with stuff turned on / off as set up by the user?

Ok agreed. I was trying the pie menus the other day and it seems that double tapping Z doesn't close the menu after it's opened. Shouldn't the key be like a toggle that pops it up but can also close it? I know LMB and ESC can close it but could be intuitive to have the key close it.

Z wireframe / solid
(you can choose occlude selection but wireframe and solid mode remember both it's own Occlude Selection Setting. Wireframe Occlude Selection off by default, Solid Occlude Selection on by default.)

Well frankly, I think there was nothing wrong with the way Z key worked in 2.79.. I never heard anyone complain, maybe because it's so commonly found in every modelling software.

Hi, I was trying to render some of my production archviz images and found out that 2.8 renders the scene about 23% slower with the same amount of noise.

It has been almost two months so I would like to at least hear back from someone, possibly @Brecht Van Lommel (brecht) who asked me to prove my point.

In T55162#507550, @William Reynish (billreynish) wrote:

Yes - viewport presets is something we considered, but decided against for now, in favour of a more direct system. We think that Workspaces can act as a type of viewport preset.

Re the Z-key behaviour, that's intentional. From the start, 2.8 was designed to eschew Wireframe mode as a necessary feature to work in 3D. That's why we've replaced the Z key to enable see-through X-ray mode instead.

Wireframes can still be seen in Edit Mode, and enabled anywhere via the Wireframe overlay option.

To make viewport settings quicker to set, we could perhaps add a shortcut to open the Overlays popover.

Hello everyone:)

@Alma Talp (AlmaTalp) I wouldn't really call the latest build buggy. I would call it in development. The fact that Blender is changed so well (and so deep) every once in a couple of years really makes Blender stand the test of time and might even make Blender the go-to software for 3D creation in the future.

I have to add to Alma, Evandro and Mindinsomnia. Z key is the ultimate key in Blender for me too. I haven't worn the key itself completely yet as there is a little bit of white ink left on the top left but I'm very close to having it completely black.

Just found this today and it reminded me of this. Seems like the functionality is similar and maybe the intersection could be less bulbous?
https://www.blendermarket.com/products/metaball-skinner

Could someone please check if this is a bug? Thanks! ;)

Hezaro you should really prepare a blend file of the problem otherwise it seems too hard to reproduce.