In D17189#468952, @Enes Ayalp (Playasene94) wrote:

If the type ever changes on one side, we will have to update it here as well without auto.
In this case, i dont mind what type of "b_scene.render()" is. But i expect threads_mode() to be a definite member of it.

I don't think this is a bug. I'm patching a function that would copy socket values when a link is dragged. But this is not what should be happening now. And the values don't go anywhere. They still exist, you just don't have access to them.

I did take a short peek at this diff. And while there are some nice changes in it, I don't think it's going to be accepted like this.

• It changes many unrelated parts of the code. Which is generally a bad idea because if it makes bisecting for regressions much harder. Better split it into multiple patches, each only changing a single area.
• Change for the sake of change, without actual measurable performance gain is imo not really a good idea. Unless it makes the code a *lot* more readable or less error prone. I'm not saying it shouldn't be done ever. But the explanation why it is better must be compelling.

Seems to be working fine here... but I'm on windows... blender-3.5.0-alpha+master.06305e5ca800-windows.amd64-release

Hey! I made a new discovery (tested in 3.3) - The blurry artifacts seem to have somekind of dependency with the specific VDB file -> I recently tried some VDBs that i bought from a pack created with Houdini.

Making a guess about the cause based on the timings
@Hans Goudey (HooglyBoogly)

To mention, B3D is not the only software that hide gizmos during operation.
For example, substance 3d modeller also use such a strategy, this allow to check the resulting composition while having pretty complex gizmos.

I'll check

@Torrent (Torrent) Examples and showing typical use cases are crucial actually. Pros and cons are constantly being weighted.
The negative response has set the patch into moment of pause. Only the bug fixes that were part of the patch have been committed for now.

I want to share my experience about gizmos in order to provide some contextual logics, in case if it will be useful.

• Changed direction a bit.

@Paul Kotelevets (1D_Inc) Save it man. There is no need to overcomplicate things with arguments and such.

Hi! I just wanted to throw in a comment regarding surface collision when grooming. It would be very useful to have the option of defining a custom collision collection.

Let me Know If This issue is still open , I am ready with solution, It can be solved by using Linked list or tree

I think is is important to understand one of the reasons industry standard software has gizmos always turned on.

In D15451#469159, @Jacques Lucke (JacquesLucke) wrote:

FYI, I'm currently merging master in this patch and check if we can make the initial functionality master ready for Blender 3.5. I might strip it down a bit for that, while keeping the general API in place to allow for more complex/better implementations in the future.

@nutti (Nutti) - I use blf.dimension for checking the max height of the characters provided from the font.

Played with this a bit, I like how this generally works well with non-mesh objects too. Especially had fun using this with bone editing.

About meta holder variables - a slight fix(at minimum) was necessary after all -- to prevent use before declaration error, I've missed that one.

Downloaded latest with blender launcher.
Reset defaults.

In T63369#656530, @Gavin Scott (Zoot) wrote:

It does *not* happen when in true full screen mode (Window -> Toggle Window Fullscreen), so see if it does or not for you.

bad news:
I can confirm this Bug is also present on MacOS.

With the patch as is I can still reproduce the issue, but that seems to be a small fix.

Thanks for taking the action.
I tried your patch, but the issue is much worse than before.
When I tried zoom in/out, Blender will freeze.

I had same problem ! Rx 7900 XTX is very slow in editing mesh. Even "hide" - "unhide" 100-200k vertex it's frozen my computer. My old GTX 1080ti is faster for everything related to mesh edit too (BTW 7900xtx gaming is good, ultra settings in Red dead 2 with resolution 5120*1440 i have 110fps). So with Blender 3.5 it's work better with AMD GPU ?

On the design of adding speed ramp key points through a gizmo next to the playhead, has this been discussed with the User Interface team?

Oh now I see this is mentioned in the original diff. I guess this is more of a todo then.

I did update my drivers and still dose not work and I will update my crash logs Tomorrow as soon as I can

You can download previous versions of Blender from here: https://www.blender.org/download/previous-versions/

Thanks for reviewing :)

I can confirm this issue. And it's not just the Shadows option, it's anywhere that uses the vector ball (I don't know the proper name for it)

oops accidently added two of the same report

Thanks for the update, closing.

Huh, I even noticed that but didn't put together that was the problem. A bit spacey.. Thanks, I'll take another look. That seems bad enough that it would be worth fixing even if it ended up looking like a "new feature' in the code.

@Hans Goudey (HooglyBoogly), this issue would show up in wireframe mode

3.3.2	3.5

CC @Patrick Mours (pmoursnv)
Do you think this is a bug or a limitation with OptiX OSL?