Color management can be tricky and misleading, but I don't believe this is a valid todo.

Glad I could help! To answer your other question, the node setup you have is definitely not the best way to save render passes (although I've been forced to do the same thing in order to work with legacy pipelines). Look into the Multilayer OpenEXR format. Choosing this option in your main output settings will cause all enabled render passes to automatically save to a single .EXR file without any node work or technically incorrect color transforms.

The appended node groups in your example file are quite simple so those probably aren't the cause of your issue.

Confirmed on my end!

2 weeks, no response. Hope the issue went away!

Glad it all worked out!

What language is your keyboard? If you go to File > Defaults > Load Factory Settings, does the problem persist afterwards?

as @Gavin Scott (Zoot) says... this is a feature, not a bug!

Your issue is not caused by nodes. Transparency is disabled on Eevee materials by default. Check the "Blend Mode" parameter under your material settings.

Thanks for taking the time to post a video! Unfortunately, what you're experiencing still looks normal to me.

It is common for Blender to freeze up during GPU render. Is this a new issue for you? If so, can you identify under which version the issue began?

I believe it! Perhaps this has gone undetected because "easing" and "normalize" are both under-utilized in Blender. But it's definitely not helpful.

May I elevate the priority of this bug? Sorry to do this to my own report, but 4 out of 9 sculpt tools are broken for Grease Pencil objects with a non-zero transform. This seems like a severe issue!

Sorry, this is not a support forum. If you believe this problem is caused by a bug in Blender, you will need to provide more information in your report, such as the model of keyboard that you have, and exactly what happens when it fails.

This is a known limitation with the way the Blender reads certain video files. Sometimes the wrong frame of the video will be displayed in the viewport. This can often be corrected by using an image sequence instead of a video file.

I understand now, and I agree that this is not ideal behavior.

This report has no information

The Lattice Modifier is not working because there is no lattice in your scene. That's a cube.

Sorry, this is not a support forum. Try downloading the .zip file instead of the installer.

This looks like the expected behavior to me. "Indirect Only" means that the collection casts shadows and reflections, but does not appear directly. If the object appeared as a holdout, that would be direct shading.

The above solution aims to fix a small design flaw with an entire UI overhaul. With respect, I would like to suggest a simple fix instead:

I don't see any reason why workspaces in the "add workspace" menu should be disabled or inactive at all. The "disabling" only takes effect if a workspace of the same name already exists, but that is pointless. It is rather like disabling "Add Cube" if an object named "Cube" already exists in the scene.

Unicode characters do not need to be individually implemented in Blender in order to show up in fonts that support them. That would be an insane amount of work! Blender just passes the unicode data to the font, and either the font has that character or it doesn't. Bfont, in this case, doesn't have a lot of characters that other fonts do.

This is a shortcoming of the Bfont font, which is rather old and ugly and does not contain a lot of glyphs (including the € symbol, I just noticed). Perhaps the font could do with an update, but this is not a bug.

I was able to reproduce this with all of the navigation gizmos, but only the navigation gizmos. None of the other buttons fail to reset when the mouse enters another window. Strange!

I cannot reproduce this issue. What button do you mean by "tweak"?

Confirmed on my end! Although to be honest I feel like this would be a bigger bug if it didn't crash...

Understood. I won't touch the built-in icons (they look fine anyway)

That file appears to be corrupted. Try to find the .blend1 backup of the file, which might still be good, and remember to backup your files in the future.

Could be an unrelated bug, but I also seem to be having trouble assigning weights in edit mode. Only for certain objects, though-- I can't get it to reproduce reliably

Of course, if I release Ctrl key and try to paint weight, and as the target is 0, the stroke gets totally blue and this is expected.

In T65408#693418, @Antonio Vazquez (antoniov) wrote:

In you file you have a maximum target weight of 0.0
If you set this value to 0.0, as soon you paint any vertex, the value will be set to 0,0, and this is how is deigned. If you wants to have a maximum value of 0 in the vertex and you manipulate the vertex, the program check your current value and clamp it to the valid range, in this case from 0 to 0, so it's 0.

There are plans to integrate grease pencil inside the "general" Dope Sheet and remove the grease pencil mode.

Note: This regression must have occurred somewhere between the May 10th build (when I first noticed it) and the May 7th build (when it still works as expected). Hope that helps!

Thank you @Bastien Montagne (mont29) . I did discover a workaround which was to wrap the script in a function that is appended to the app handlers. Consider the following script:

Suggestion: Manipulators on Camera and Lamp objects should be accessed by entering Edit Mode for these objects.
For instance, one could select a Spot Lamp and press Tab to enter Edit Mode, which would expose the manipulators for size, angle, and falloff. These would be hidden in object mode so as to avoid clutter. Entering edit mode on a Camera could expose manipulators for viewing angle, shift, focus distance and clipping.

This will probably get archived as not-a-bug, but I agree, and I think this functionality should be reconsidered for 2.8.