- User Since
- Mar 11 2020, 9:55 PM (71 w, 2 d)
Can you please check if the original reported issue is resolved?
Wed, Jul 21
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.
Tue, Jul 20
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. The node tree doesn't matter as long the input after the reroute isn't connected to a value input.
Okay, I put my guess to test and figured a sure way to break switch nodes. That detail about hidden links and inconsistent behavior depending on forcing the nodes to reevaluate their links held true.
Sun, Jul 18
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 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.
Sat, Jul 17
The previous report is still open, you should be able to comment on it with more information, if not edit the original post.
Fri, Jul 16
Thu, Jul 15
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.