The shortcuts have changed with: rBAe08d6983c05f
This is the current state of the shortcuts:

Yes agreed 4 billion light groups is excessive ;) but I have been on many productions where a limit of 8 or later 15 was really restricting. An upper-bound of 32 seems like a good number of not too many and not too little, and your concerns with LPEs sounds like it is best to treat it as a bitmask in the future anyways.

Most of my comments in this patch are related to the Blender integration. I would be fine with merging the Cycles-side implementation first, and then doing the Blender integration as a second step. So a patch for just that would be welcome. Ideally it would be on top of the cycles-x branch, but probably merging will not be hard for us.

Hi all,

In T82419#1048648, @Antonio Vazquez (antoniov) wrote:

@Daniel Martinez Lara (pepeland) @Matias Mendiola (mendio) Would you mind take a look at this? I don't use the mask and not sure if this is a bug or it's because now the masking system is totally different of 2.82.

GPU capabilities needs to be updated. for this. Related to T82856: After updating the video card drivers to 20.11.2, interface artifacts appeared.
Should be done for 2.83 and 2.93.

@Sybren A. Stüvel (sybren)
Ah this post is literally a duplicate, my bad, considering the issue seems to have been around so long i'm glad it's getting fixed XD

I'm closing the task, because the current pose breakdowner works as designed. It's not a nice design, but not being nice isn't a bug ;-) There are improvements coming soon anyway.

Take a look at D9054, the pose breakdowner will soon see a nice update.

This has been committed to the 2.93 branch

Fixed stuff pointed out in the comments

I think this looks good to me now.

Updated for better grammer

Other than me new remarks, I think it looks fine.

Updated manual for:

Can this be closed ?

Okay yeah I'll update document for that part as well.

I started working on rB3e87d8a4315d794efff659e40f0bb9e34e2aec8a in rBM7942 the line art sub panel still needs text for 2.93.

Any chance to see this in master anytime soon? Its 21 century and it is quite uncomfortable to move scene to "world center" just to render a scene without artefacts :)
Just hit a problem with black lines when mesh is far from center (although it was only 100m, not so far in fact) - https://developer.blender.org/T87301

Yes, you can say edge angle.

Updated to fix those commented and for the confirmed UI. Relevant images are uploaded below:

This patch has an approved status however it was not committed yet. So I'm assuming the other reviewers are blocking. Updating the reviewers list to reflect this. This way the patch status still show as Need Review.

There are some fixes to the page titles that should be made.

It would be nice to use consistent capitalization for "line art". I think I would go with not capitalizing it.

Updated to reflect on current changes:

Oh yeah... that way it's more consistent with the rest of the blender. But the operation here still isn't "clipping" though, it's treat all non-zero weights as 1 (act like a selection), so what do you think would be the best way to express this?

In D10742#272862, @YimingWu (NicksBest) wrote:

@Hans Goudey (HooglyBoogly) The UI part you got the Clip checkbox wrong, should be Soft Selection, or otherwise the checkbox will have inverted logic (enabling the checkbox should allow weight to be passed through directly without being forced to 1).

@Hans Goudey (HooglyBoogly) The UI part you got the Clip checkbox wrong, should be Soft Selection, or otherwise the checkbox will have inverted logic (enabling the checkbox should allow weight to be passed through directly without being forced to 1).

Cleaned up...

I would also suggest that we add the following image (perhaps with some draw over scribbles to show the material mask numbers) to the occlusion transparency section:

@YimingWu (NicksBest) All manual images should be done using the default Blender Dark theme

I tried to apply Diff to the current version of Blender, but it doesn't work. Could you indicate on which version Diff works? I would like to try this tool

I managed to get an older driver from XP-Pen (1.6.4.200810) and everything appears to be working as before.

I looked through 2.83's changes and didn't see anything that stood out. If 2.93 is working then I agree that it wouldn't make sense to invest much time into debugging this.

I downloaded Blender Launcher and went through each LTS build and discovered that it's no longer working in any of them which means that it's either my system or their last driver update on Jan. 11th 2021 is what broke it? They have no option to download older versions of their drivers and since we're so close to 2.93 LTS, this is probably more trouble than it's worth since it is working perfectly in 2.93 alpha.

@Kyler Moritz (KMoritz) could you verify the last version of 2.83 LTS that worked correctly? 2.83 LTS release history for your convenience.

I can't reproduce it... Maybe I'm not fast enough :D
@Falk David (filedescriptor) can you bisect this? (beware that bisecting between branches can be a bit tricky at times, but given that you reproduced this today, there shouldn't be too many commits to check)

This seems to be fixed in the current master. I was not able to reproduce it there.

sys.exit(0) will hang blender 100% of the time.

I put in a switch in for 2.83 for this bpy.ops.wm.quit_blender() call as i figure should still be used with blender ?

Ah sys.exit(0) is the correct way to exit with python, will do this.