Closing this task, 2.83 isn't maintained anymore. https://code.blender.org/2022/06/blender-2-83-lts-2-years-later/

Do aov use MRT now?

In D11537#403092, @Frederik Steinmetz (SpiderguyF) wrote:

Silly me, no it's not. Just the possibility of occasionally creating invalid connections, but that's fine, just do it manually when it fails.

Silly me, no it's not. Just the possibility of occasionally creating invalid connections, but that's fine, just do it manually when it fails.

@Frederik Steinmetz (SpiderguyF) : sorry this has been lying around (I usually dont do review).

This report does not contain all the requested information, which is required for us to investigate the issue.

Does selection work when you open Blender with LIBGL_ALWAYS_SOFTWARE=1 blender?

poke.
Blender still not have any retopo overlay.
And it is important to have it.

Archiving in favor of D12871: Cycles: Light Groups.

I have been working on fixing the static scenes w.r.t. removing ray offsetting with some success. However, as can be seen in the images below adjacent triangles in the mesh have some issues that need looking at. Also at large sizes precision problems start occurring which also need some work.

	origin1e-3	origin1e-5	origin1e5	Black Lines	Glitch
original
CUDA static					CUDA Error
Optix static					CUDA Error

Dynamic scenes were largely working last week with similar issues but they rendered glitch on CUDA and optix just fine. I need to investigate why this has started occurring with the static scene solution.

In D5919#330989, @gwobbler (gwobbler) wrote:

Isn't this feature developed anymore? It's a necessary feature for game makers, so I'm waiting.

Isn't this feature developed anymore? It's a necessary feature for game makers, so I'm waiting.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thank you for your report. Unfortunately, it does not contain the requested information that we need to investigate the issue. Please read this guide, it may help you write a bug report that allows us to identify the cause of the problem.

I'm not sure whether or not you consider this important enough to backport: rB1bdaf0ebec5bafd6c0b945de49cc74515b93fe1c

This is not fixed, has been reported again and again, see T87975: Mantaflow simulation stops and crashes at the end of the bake (or when closing blender): The CG solver diverged, residual norm > 1e30, stopping.

Yes it's just based on this as lots has changed in cycles-x so I'll create a new patch.

In D6250#324398, @William Leeson (leesonw) wrote:

Also, I am wondering if it is best to create an new diff instead of altering this one?

If it's a completely changed implementation (which is likely due to cycles-x changes), it's best create a new diff. Still I guess you will reuse code and ideas from this patch.

Hi All, I have been working on getting this working in cycles-x and have achieved some success.

I'd like to see if we can get this patch into cycles-x. I was wondering if you would help out with this?

In D6250#320582, @Tom Smalley (tomsmalley) wrote:

Is there any movement on this?

@Brecht Van Lommel (brecht) I know you have concern over performance regressions, but I'd rather it be correct and slow than incorrect and fast. I haven't been able to work around the artefacts (https://developer.blender.org/T85057) except for in some special cases.

Is there any movement on this?