- Brasil
- https://www.linkedin.com/in/germano-cavalcante-77224867/
- Joined on
2012-10-07
Hi. It is possible to select elements of a geometry in Geometry Nodes by comparing values of the attribute. You can select edges with float attributes; you just need to define the true or false…
Hi, thank you for the report.
I am not sure if I understand the issue because the steps are quite complex. Could you please try simplifying the file—perhaps by removing some objects or…
Thank you for the report, @WolfgangGeithner.
Unfortunately, without clear steps to reproduce the problem from scratch, we cannot confirm the issue and forward to the developers.
Things that…
For me none of the results are really great. But I can confirm that in 4.2 it got even worse.
I can confirm. What happens is that the edge of the Blender window is outside the limits of the monitor screen, and the warp cursor does not "warp" when it hits the edge of the monitor.
![GIF.g…
Thanks for the report, but this report does not contain all the requested information, which is required for us to investigate the issue.
I couldn't perform any view rotation operations…
Since this hotkey E activates the eyedrop on the UI for other DataBlocks (like object), it makes sense that it should work for Bones as well. So confirming. Cc @ChrisLend
I will assume this is known issue for now, but maybe we should keep this issue open to keep track and to gather more input from users and developers.
This reminds me of a similar problem that happened on macOS:
#121911: macOS: Interference with sound in other applications
It could be that the problems are related.
@MacacoMalandro, it…
From what I can tell, the code was written in a way that creates a new stroke from the point selection. So this seems to be a deliberate change. I don't remember why this was done this way.
I…
I will let someone more familiar with Linux WAYLAND or Fedora check this issue. Also recommend checking if there are any available updates for Fedora or the NVIDIA driver and testing again to see…
I can confirm now! Seems like a regression.
The steps are complicated to confirm, at first it's not so clear in the script what are the blocks A, B and C to uncomment.
Also, I'm not familiar with this area. At first I didn't find any…
I can't replicate the problem. Could you try with the latest daily build and, if needed, submit a sample file?
![GIF.gif](/attachments/0e03e9d4-071c-40a7…
In that case, then it is indeed the same result. High priority then.
@LukasTonne, I got that the cursor needs to be at least 4px from the stroke. But that doesn't explain why it worked before and now it doesn't. It seems to be a regression.