- User Since
- Mar 11 2020, 9:55 PM (133 w, 3 d)
Jun 16 2022
Jun 1 2022
May 31 2022
May 30 2022
Maybe I'm just stupid, but shouldn't curve attributes be accessible in the same way meshes' are?
May 28 2022
To add more info that may be connected to this issue, something really weird is up with resampling/subdividing, numeric attributes in general and Curve to Mesh. Integers makes it obvious, but I got erratic behavior with floats too.
May 27 2022
May 8 2022
I'd just like to let you know this bug still happens with the new nodes. Set Material Index doesn't affect generated or instanced geometry, nor does the new Named Attribute node from the builds with "material_index" as the attribute—this one will crash Blender.
Mar 18 2022
Mar 17 2022
Jul 25 2021
Jul 23 2021
Can you please check if the original reported issue is resolved?
Jul 21 2021
Confirming it's still an issue on daily build "3.0.0 Alpha, branch: master, commit date: 2021-07-18 23:24, hash: 83883ae66ad3, type: release". It should be noted it only happens when using CUDA device + Optix viewport denoiser. CUDA device + Optix render denoiser works fine until you break everything through the viewport.
Jul 20 2021
Still experiencing it on build "3.0.0 Alpha, branch: master, commit date: 2021-07-18 23:24, hash: 83883ae66ad3, type: release", just installed and with factory reset for workspace and preferences for good measure. It's no longer throwing an error in the terminal, just losing the reroute type.
EDIT: Just grabbed a fresh build (3.0.0 Alpha, 83883ae66ad3) and the methods to break switches listed below are no longer valid. It could be they're no longer breakable.
Jul 18 2021
Can you tell what's your keyboard layout? Also, did you try to edit the shortcuts, setting your bracket keys as the new shortcut keys?
Hi, I just got this error and isolated the buggy nodes in a test blend file for you. It contains two groups of switch nodes throwing errors. To reproduce:
- Link switches B or A to C and the new link itself will be invalid. Do not select one of the nodes after B before linking or you might get the error version seen on step 2 instead.
- Link the switch 2 output to one of the inputs of the node 3. The existing link between 1 and 2 should throw the error.
Jul 17 2021
The previous report is still open, you should be able to comment on it with more information, if not edit the original post. Also, please use descriptive titles.
Jul 16 2021
Jul 15 2021
I'm not using the LTS, I'm using the version specified in the report. This is the earliest release I have with Asset Browser support*, but if it's making the report confusing I can edit out the references to 2.93. Or we can just close the report.
Hi! I can't reproduce it on 2.93.0, hash: 84da05a8b806 nor 3.0.0 Alpha, hash: 62d9dabc7db4 on Windows 8.1 64 Bits with a tablet Wacom Bamboo Connect, driver 5.3.5-3
Mar 13 2020
Aranuvir's assertion that the keymap seems to be using an ANSI layout no matter the keyboard you're using seems spot on. I've seen the same behavior in a different keyboard layout (ABNT2).
Mar 12 2020
@Germano Cavalcante (mano-wii) Okay. So two issues as suspected.