Maximum brush size snaps back to default max value when its set to a higher number than maximum allowed number #45060

New Issue

Fasit · 2015-06-13T12:30:18+02:00

Fasit commented

2015-06-13 12:30:18 +02:00

AMD Phenom II x6 1100T - ATI HD 6850

Blender 2.75 RC1 and versions before have the issue

We need to set the maximum value for some transform brushes like Grab.Global or Twist.Global (By global I mean it preserves details by using a "Max" Curve).
For this brushes to work the maximum brush size should be something really big like 2000; so that all the model is under the stroke.

The current max is 500; so when we set it to 2000 or something higher than max value and press "F" shortcut by mistake and move mouse it snaps back to the max value (500).

Here is a short video demonstrating the transform brushes , the need for maximum value of 2000 and the maximum value snap back (near the end).

https://www.dropbox.com/s/ep2d6gjrzt0qntr/Max_BrushSize_2000.avi?dl=0

AMD Phenom II x6 1100T - ATI HD 6850 Blender 2.75 RC1 and versions before have the issue We need to set the maximum value for some transform brushes like Grab.Global or Twist.Global (By global I mean it preserves details by using a "Max" Curve). For this brushes to work the maximum brush size should be something really big like 2000; so that all the model is under the stroke. The current max is 500; so when we set it to 2000 or something higher than max value and press "F" shortcut by mistake and move mouse it snaps back to the max value (500). Here is a short video demonstrating the transform brushes , the need for maximum value of 2000 and the maximum value snap back (near the end). https://www.dropbox.com/s/ep2d6gjrzt0qntr/Max_BrushSize_2000.avi?dl=0

Fasit commented

2015-06-13 12:30:18 +02:00

Changed status to: 'Open'

Fasit commented

2015-06-13 12:30:18 +02:00

Added subscriber: @ygtsvtr

Bastien Montagne commented

2015-06-13 14:19:34 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2015-06-13 14:19:34 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2015-06-13 14:19:34 +02:00

Bastien Montagne self-assigned this 2015-06-13 14:19:34 +02:00

Bastien Montagne commented

2015-06-13 14:19:35 +02:00

Thanks for the report, but no bug here, it is working as expected - values outside of 'nominal' range can only be defined by explicit keyboard typing, grab and such shall always stay in nominal range.

PS: I do not quite understand the need to go that high, if you want your whole model inside a 500px brush, just zoom it out. And if you really need a 200px one, hit F and move the mouse, just hit escape/RMB instead of enter/LMB, and you'll stay at 2000px…

Thanks for the report, but no bug here, it is working as expected - values outside of 'nominal' range can only be defined by explicit keyboard typing, grab and such shall always stay in nominal range. PS: I do not quite understand the need to go that high, if you want your whole model inside a 500px brush, just zoom it out. And if you really need a 200px one, hit F and move the mouse, just hit escape/RMB instead of enter/LMB, and you'll stay at 2000px…

Fasit commented

2015-06-13 22:13:29 +02:00

Hi Bastien; Campbell was the person who said I should open a report about this (I PM him actually and he said its a bug so I should report it).

Maybe you should talk with him.

The need for a bigger brush size is pretty clear actually. When you zoom out to fit the model inside the 500 px size, you lose precision. The distance where you need to move the mouse to edit the model is so small that the mouse or pen axis fails.

Hope I explained clearly.

Hi Bastien; Campbell was the person who said I should open a report about this (I PM him actually and he said its a bug so I should report it). Maybe you should talk with him. The need for a bigger brush size is pretty clear actually. When you zoom out to fit the model inside the 500 px size, you lose precision. The distance where you need to move the mouse to edit the model is so small that the mouse or pen axis fails. Hope I explained clearly.

Bastien Montagne commented

2015-06-13 22:24:20 +02:00

Changed status from 'Archived' to: 'Open'

Bastien Montagne reopened this issue

2015-06-13 22:24:20 +02:00

Bastien Montagne commented

2015-06-13 22:24:20 +02:00

Please state it clearly in the report, when you have already discussed an issue with a developer… makes things simpler to triage.

Bastien Montagne removed their assignment 2015-06-13 22:24:57 +02:00

David Campbell was assigned by Bastien Montagne

2015-06-13 22:24:57 +02:00

Bastien Montagne commented

2015-06-13 22:24:57 +02:00

Added subscriber: @Psy-Fi

Antonis Ryakiotakis commented

2015-06-13 23:00:42 +02:00

Even if Radial control only supports UI range, we can at least support cancelling to a previous out of bounds value.

Bastien Montagne commented

2015-06-13 23:11:41 +02:00

@Psy-Fi from my test, this is already working… That’s why I closed it as 'not a bug'…

Fasit commented

2015-06-13 23:19:22 +02:00

Sorry Bastien, will do so if it happens again.

@ Antony : That would definitely solve the problem, I thought It was simple as increasing max value threshold to 2000px. But which ever you choose booth of them solve the issue.

PS : I talked with ideasman42 (I think there is a mix with Campbell's)

Sorry Bastien, will do so if it happens again. @ Antony : That would definitely solve the problem, I thought It was simple as increasing max value threshold to 2000px. But which ever you choose booth of them solve the issue. PS : I talked with ideasman42 (I think there is a mix with Campbell's)

blender-admin commented

2015-06-15 14:27:52 +02:00

This issue was referenced by 9090d64544

This issue was referenced by 9090d645440ccd55a0b4f4155f485ff7cee0746c

Campbell Barton commented

2015-06-15 14:32:10 +02:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue

2015-06-15 14:32:10 +02:00

Campbell Barton commented

2015-06-15 14:42:56 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2015-06-15 14:42:56 +02:00

UI supports buttons outside of soft range.

This is practically the same issue. Just expand bounds by initial value to avoid glitch.

Committed fix.

Note, the reason I considered this a bug is that its a case the UI can handle but the operator not.

UI supports buttons outside of soft range. This is practically the same issue. Just expand bounds by initial value to avoid glitch. Committed fix. ---- *Note, the reason I considered this a bug is that its a case the UI can handle but the operator not.*

blender-admin commented

2015-06-18 17:24:16 +02:00

This issue was referenced by 84e4eed317

This issue was referenced by 84e4eed317c6bb3df2186aea46afee158ed81d90

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

Maximum brush size snaps back to default max value when its set to a higher number than maximum allowed number #45060