angle_limit
in Bevel Modifier does not show enough precision
Well it seems that I can reproduce it now again, but not sure what exactly is causing the display to vary from seemingly not changes to my code.
angle_limit
in Bevel Modifier does not show enough precision
I guess it's just the UI didn't show enough precision while the value itself is correct.
From the report I assume blender didn't run on your side? HD 520 should support OpenGL 4.6 just fine, I guess you could try updating your graphics driver tho
I think we can bring this up to the infrastructure guys. Google captcha is gonna be a road blocker for Chinese users without a VPN and many don't have that set up already.
Switching to another…
In OpenGL backend it works fine, but in Vulkan here it appears to be consistent with what you recorded.
I guess we could close this now since the problem have apparently resolved itself. But feel free to poke again if any further problems arise
OH I see. I thought layer transform is on top of point coordinates.
I guess we still meant to keep layer transform values right? (Transform back, do additional transform, transform to original)
🤔 I think this basically applies transformation in the object level so whatever layer transformation should get preserved because it's kind of internal?
There is a bpy.ops.gpencil.recalc_geometry() operator for GreasePencil v2. It would be terrific to have for GPv3
I think I can do it together in 1 PR.
Looks like adding a recalc geometry in rna_Frames_frame_new
would solve the issue, but I'm not sure if this is the correct way to go since I don't know if this recalculates all frames or just…
Dang... Then I guess inferring language intention from the font table is a no go for now :( Probably has to be manually selected then.
Hi @YeCrotMR , This should be the same as #125875 and a few other reports. Other people have reported upgrading graphics driver solved the issue. Could you try doing that? Also try latest daily…