It might be the same issue as the side note I made regarding clear visual discrepancy between the same rendering modes for the 3D viewport and VSE preview.
However, I'm not convinced it addresses the core problem I began this report with, which seems to be stemming from the VSE preview not displaying shading options like "Backface Culling" from the 3D viewport.

Neat, thanks!

Until @Brecht Van Lommel (brecht) or some other developer can chime in, and since there was no resolution, should this task be reopened?
I don't know how these tasks are organized for visibility for developers, but I'd imagine tasks marked as "Resolved" would not easily be re-reviewed.

Oh, no problem, I appreciate you looking into it! And, yes, the black is caused by the flip normals option that I setup intentionally.

Right, because the default 3D view doesn't have Shading option enabled.

Hi, @Richard Antalik (ISS), did you open up the file I attached to check the problem? The issue still remains in 2.79 and also in the latest 2.80.

Ah, that makes sense, sorry about that.

Thanks for tackling the issue of not being able to box select while in transform mode, very welcome development!
Tried to replicate this myself by doing different things to the keymap before but I kept running into different problems, so quickly gave up. Glad to see it will officially be remedied.

Just an update that when I initially created this task, I hadn't tested on 2.8. I did just now with the latest beta and the problem is still there.
With the same test file above, Eevee actually seems fairly consistent, except for the lack of the backface culling effect (the viewport outline) in VSE (but other viewport effects seem to work, like DoF, AO, Bloom).

Okay, including a sample .blend file that should be self-explanatory:

Got it. Will try to take care not to accidentally enable it.

In T60548#600932, @Christopher Anderssarian (Christopher_Anderssarian) wrote:

Don't worry, this is being addressed:
D3934: VSE cache with frame prefetching (WIP)
D3597: Add proxy support for all sequences

Hi, thanks for the response, Antonio. Is it possible to make 2.79 act like 2.8 and not make it enable Continuous Drawing?

2.8's Grease Pencil behavior seems to be that way I wanted/expected it to work.

Ah, I see. That'll do it, thanks!

In T52586#476128, @Peter Fog (tintwotin) wrote:

Oh, so integrating the sequencer with the 3D Viewport like this, will no more be possible? Previz Camera Tools

How about allowing the Sequencer run in a "local" scene different from the "global" scene on the same screen? That way the global scene(screen setting) could be switched as the scenes changes in the sequencer(by a script), but not the contents of the sequencer(area setting). That way the annoying problem of changing the scene also changing the timeline contents of the sequencer could be avoided.

This seems to be a short-term, and patchy fix to Blender not being able to handle an ideal workflow. I really hope the idea of a "global" sequencer is being looked at by the Blender Foundation.

@William Reynish (billreynish) I see it akin to orthographic/perspective, it's a usability issue. I think this is especially true when sculpting, but I find even when modeling or animating, sometimes I want to turn the viewport a certain direction that Turntable doesn't allow me to, but it takes me out of my workflow to fire up the preferences window, find the option to toggle.

Not sure if this is where it needs to be suggested, but couldn't find a more appropriate task.

I like how the splash screen is shaping up. I saw the following shot on Blenderartists: [image]

Ah, okay, my apologies. I misread that as the usual request of dragging and clicking the mouse to enable box selection.

In T56702#544572, @William Reynish (billreynish) wrote:

As for only dragging when you are over an object, that is not how Blender works, and probably isn't a very good idea for handling complex 3D scenes. You may be working in wireframe, you may have many tiny objects, or objects with holes, or thin, long objects. It would be very fiddly for most things if you had to drag on top of the thing you want to move. One of the nice things is that you can drag wherever you want

Maybe others can chime in here, but I've used Blender in left-click select mode with left-click drag enabling box select for years and I can't think of a single time this was an issue.

This is shaping up to be an excellent revamp of the default key map.

@Duarte Farrajota Ramos (duarteframos) You mean "This is shaping up to be an excellent industry standard key map", right? The default Blender standard key map is another task altogether.

@William Reynish (billreynish) I mean is this task open to discussions on how to improve the pie menu in general, or meant only to discuss the specific items you outlined in the Description above?

Is this task meant for improvements in general to the pie menu, or just these specific proposed changes?

Hi, @lucas veber (lucky3), thanks for the response.

I just wanted to say I like the first horizontal design a lot, especially with the strip of templates with quick visual representation of the different modes. It actually stirs in me the the desire to want to get into the program and work/explore, which is a huge plus.

In keeping with the "workflow" mentality, would it be possible to get a context-based deletion behavior by default when pressing "x"? Like the Smart Delete addon.

Just a quick question: Is there a plan to make the Favorites Bar optionally a floating panel?

I just saw the new update video from @venomgfx . Kudos on all the update efforts to have a coherent and useful default keymap. I may not agree with all the changes, but I think it's a worthwhile pursuit.

@Ludvik Koutny (rawalanche) It looks like context-sensitive menu is being developed as a whole anyways for 2.8 according to T55162.

It would be great once you select an object in the scene, the object get's always highlighted in the hierarchy of the outliner. So far you can only see a selected object that is in a collection or parented to another object if it's one of the first few icons in the list:

Just so options are considered.

I use quick layer changing a lot more often than mode change, so making the number change modes isn't ideal for me, and presume would be true for a lot of Blender users as well.

I agree. Context-sensitive right-click menus I think should be a given for industry standard keymap.

@William Reynish (billreynish) The Curve Extrusion tool looks very intuitive, and far superior to what Maya has.

@William Reynish (billreynish) In Maya, the spacebar, aside from toggling the quad view, it also shows a layout of menu items while held down:

Just want to say this is a really smart move. Also, the decision to integrate pie menu to be default in Blender in general is very welcome, too.

Not sure for the scope of this task, but I agree, Blender should allow for a more robust expression system.

YES, much needed. I actively avoid drivers because they're so cumbersome to setup. I'm really curious about what "Open Driver Editor" will open.

@William Reynish (billreynish) Actually, you're right, it's pretty much the same behavior. I think my main thing is when scaling individually extruded faces, it'd be more useful to have them scale on their individual origins by default temporarily.

@William Reynish (billreynish) For #3, Maybe this helps more: https://youtu.be/aKwE_tzV7l8?t=238. It looks like it's a mirrored operation, but it's not.

This is great! I have a few suggestions for extrusions that I think would be really helpful:

@William Reynish (billreynish) Appreciate you taking the time to respond. I hope my suggestions are not derailing the purpose of this task. I got excited at the notion of making the 3D Cursor more powerful, but I think the real goal here is to make it feel more refined and less disruptive, and not adding more features.

I love the idea of expanding the 3D Cursor to be more powerful.

Hi, @Sergey Sharybin (sergey). The forum discussion is just to contextualize my problem, but reading it is not necessary to replicate the problem in this report.

I can confirm that something has changed from 2.78 to 2.79. I have a custom keymap and have this exact same problem.

Thanks, @ronan ducluzeau (zeauro), I appreciate the feedback.

Thanks for the quick reply, @ronan ducluzeau (zeauro).