box mask doesn't work in sculpt mode #97112

New Issue

Leon Nolan · 2022-04-06T17:05:36+02:00

Leon Nolan commented

2022-04-06 17:05:36 +02:00

System Information
Operating system: Win 10 21H2
Graphics card: GTX 1070 Ti

Blender Version
Broken: 3.12 stable
Worked: (newest version of Blender that worked as expected)

Short description of error
In sculpt mode box mask doesn't work at all, it shows nothing, only lasso and line works well within the same button, very strange.
key_config_problem.7z
Exact steps for others to reproduce the error
Based on a default startup fileonly with my key config changed (attached config file: leon_keys.py) the above mentioned problem happens with a simple sphere or with more complex shapes also, it doesn't matter. This key konfig was based upon the "Industry Compatible" ca. in Blender 2.8. So I don't know what could be the problem only with a key config file, but it is frustrating, because with every other key configs works well. Please tell me how could I resolve the problem without rewrite the whole key config file again.
Thank you!

**System Information** Operating system: Win 10 21H2 Graphics card: GTX 1070 Ti **Blender Version** Broken: 3.12 stable Worked: (newest version of Blender that worked as expected) **Short description of error** In sculpt mode **box mask doesn't work** at all, it shows nothing, only lasso and line works well within the same button, very strange. [key_config_problem.7z](https://archive.blender.org/developer/F12978480/key_config_problem.7z) **Exact steps for others to reproduce the error** Based on a default startup file**only with my key config changed** (**attached config file**: leon_keys.py) the above mentioned problem happens with a simple sphere or with more complex shapes also, it doesn't matter. This key konfig was based upon the "Industry Compatible" ca. in Blender 2.8. So I don't know what could be the problem only with a key config file, but it is frustrating, because with every other key configs works well. Please tell me how could I resolve the problem without rewrite the whole key config file again. Thank you!

Leon Nolan commented

2022-04-06 17:05:36 +02:00

Added subscriber: @L7N9

Leon Nolan self-assigned this 2022-04-06 17:09:15 +02:00

Leon Nolan commented

2022-04-06 17:09:15 +02:00

This comment was removed by @L7N9

*This comment was removed by @L7N9*

Pratik Borhade commented

2022-04-07 05:11:27 +02:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-04-07 05:11:27 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Pratik Borhade closed this issue

2022-04-07 05:11:27 +02:00

Pratik Borhade commented

2022-04-07 05:11:27 +02:00

Hi, thanks for the report. If problem is in your custom keyconfig then it's less likely a bug in Blender.
Bug tracker is only for bugs and errors in Blender.
In your keymap B key is mapped for the box mask.
Please use other channels for these queries : https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Hi, thanks for the report. If problem is in your custom keyconfig then it's less likely a bug in Blender. Bug tracker is only for bugs and errors in Blender. In your keymap `B` key is mapped for the box mask. Please use other channels for these queries : https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Leon Nolan commented

2022-04-07 11:17:26 +02:00

Hi, what a frustrating thing to do a bug report... While this seems to me a bug, you handle it otherwise, what is understandable somewhere, and that is ok.
But in this case, I have tried an earlier key config, in where the "B" doesn't appeared at all for this function, it was empty, and it has also this issue. And after all I can make a full new config from scratch, for the sake of time, why not, and I can also go back to Maya for eg, for an another why not :) It has also strange things and 'bugs' which ones treated otherwise, also. Everything is just about decisions and for reasons. And that is ok.
Thank you, by the way!
LN

Hi, what a frustrating thing to do a bug report... While this seems to me a bug, you handle it otherwise, what is understandable somewhere, and that is ok. But in this case, I have tried an earlier key config, in where the "B" doesn't appeared at all for this function, it was empty, and it has also this issue. And after all I can make a full new config from scratch, for the sake of time, why not, and I can also go back to Maya for eg, for an another why not :) It has also strange things and 'bugs' which ones treated otherwise, also. Everything is just about decisions and for reasons. And that is ok. Thank you, by the way! LN

Pratik Borhade commented

2022-04-07 14:00:22 +02:00

Hi, with your configs box mask works when I press B to drag with LMB

And box mask fails to work when you select the tool from toolbar because there is no entry for "box mask gesture" at {nav 3D view > Sculpt > 3D view tool: Sculpt, Box Mask}

To fix this I would suggest you to add a new entry at above path and write paint.mask_box_gesture in identifiers field
Or just change identifier of existing keymap

Hi, with your configs box mask works when I press B to drag with LMB ![image.png](https://archive.blender.org/developer/F12980655/image.png) And box mask fails to work when you select the tool from toolbar because there is no entry for "box mask gesture" at {nav 3D view > Sculpt > 3D view tool: Sculpt, Box Mask} ![image.png](https://archive.blender.org/developer/F12980710/image.png) To fix this I would suggest you to add a new entry at above path and write `paint.mask_box_gesture` in identifiers field Or just change identifier of existing keymap

Leon Nolan commented

2022-04-07 15:20:57 +02:00

Hi Pratik, you are awesome, you saved my day! It works fine. Thank you!

However! This raises a serious question: if you change a tool name in the future, like this (previously this tool was called "view3d.select_box"), will it affect in the future the previously defined key config the existed but newly renamed tools behaviors in the tools palette, like this? I think it would be frustrating too...

Thank you for your reply!

Hi Pratik, you are awesome, you saved my day! It works fine. Thank you! However! This raises a serious question: if you change a tool name in the future, like this (previously this tool was called "view3d.select_box"), will it affect in the future the previously defined key config the existed but newly renamed tools behaviors in the tools palette, like this? I think it would be frustrating too... Thank you for your reply!

Pratik Borhade commented

2022-04-08 14:20:40 +02:00

Hi, good to know that worked for you

This raises a serious question: if you change a tool name in the future, like this (previously this tool was called "view3d.select_box"), will it affect in the future the previously
defined key config the existed but newly renamed tools behaviors in the tools palette, like this? I think it would be frustrating too...

I'm not sure if I understand this. I may able to answer if you rephrase it :)

Hi, good to know that worked for you > This raises a serious question: if you change a tool name in the future, like this (previously this tool was called "view3d.select_box"), will it affect in the future the previously > defined key config the existed but newly renamed tools behaviors in the tools palette, like this? I think it would be frustrating too... I'm not sure if I understand this. I may able to answer if you rephrase it :)

Leon Nolan commented

2022-04-10 14:01:39 +02:00

Hi, well I have made a comparative picture for you, to see what I am talking about. I thought it was self explanatory, because it is a simple logical deduction. Because all (non)changes had happened only was in the keymap (in my personal key config file).

And I am talking about custom key configs which remain unchanged through the versions of Blender (and only that 3 of the built-in key config will be updated properly to the updated or renamed tools). Because you have made a very strange programming structure for hotkeys and its configurations, which impacts the tools accessibility in the palette right now. Which reveals a not too good "thinking structure" made for the keymaps in the program right now. I think it is a strange behavior what is happening in Blender if a palette tool can be broken after a remained old hotkey of an existing tool that was only renamed by you. I don't know, is it clear now?
Thank you!

Hi, well I have made a comparative picture for you, to see what I am talking about. I thought it was self explanatory, because it is a simple logical deduction. Because all (non)changes had happened only was in the keymap (in my personal key config file). ![naming-convention-changes-in-blender-from-2.8-to-3.0.jpg](https://archive.blender.org/developer/F12989640/naming-convention-changes-in-blender-from-2.8-to-3.0.jpg) And I am talking about **custom key configs** which **remain unchanged** through the versions of Blender (and only that 3 of the built-in key config will be updated properly to the updated or renamed tools). Because you have made a very strange programming structure for hotkeys and its configurations, which impacts the tools accessibility in the palette right now. Which reveals a not too good "thinking structure" made for the keymaps in the program right now. I think it is a strange behavior what is happening in Blender if a palette tool can be broken after a remained old hotkey of an existing tool that was only renamed by you. I don't know, is it clear now? Thank you!

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

box mask doesn't work in sculpt mode #97112