transform.edge_crease ignores Factor when used as with hotkey #93642

New Issue

Aivis Ozols · 2021-12-04T11:39:37+01:00

Aivis Ozols commented

2021-12-04 11:39:37 +01:00

System Information
Operating system: Windows 10
Graphics card: RTX 2070

Blender Version
Broken: Blender 3.0.0
Worked: Blender 2.93 and before

Short description of error
transform.edge_crease is ignoring set Factor in Keymap settings!
If I set Factor to be 0.9 and then when I press hotkey and release it, factor value is not set on edge, this worked perfectly in previous Blender versions!
Same issue if I try to remove edge crease with Factor of -1
This worked in all previous Blender versions, and allowed for pre-defined Factor strength be set with single key press!

I added an image with keymap settings and blender version !
Video is showing how it need to function and was functioning in Blender 2.93.5 and previous versions !

YL0qE50zqs.mp4

Exact steps for others to reproduce the error
Open Blender 3.0.0
Open Keymap
Make new Keymap or use existing one with " transform.edge_crease"
Set Factor to .9 in keymap settings
tick "Confirm on Release" in keymap settings
Make a Cube in viewport, enter edit mode, select edge, and Tap your new made or existing key for "transform.edge_crease"
You will see that Factor is not updated with value set in keymap settings !!!

Same process to test Factor -1, for removal of crease!

**System Information** Operating system: Windows 10 Graphics card: RTX 2070 **Blender Version** Broken: Blender 3.0.0 Worked: Blender 2.93 and before **Short description of error** transform.edge_crease is ignoring set Factor in Keymap settings! If I set Factor to be 0.9 and then when I press hotkey and release it, factor value is not set on edge, this worked perfectly in previous Blender versions! Same issue if I try to remove edge crease with Factor of -1 This worked in all previous Blender versions, and allowed for pre-defined Factor strength be set with single key press! I added an image with keymap settings and blender version ! Video is showing how it need to function and was functioning in Blender 2.93.5 and previous versions ! ![blender_H2CKmSeHDf.png](https://archive.blender.org/developer/F12688794/blender_H2CKmSeHDf.png) [YL0qE50zqs.mp4](https://archive.blender.org/developer/F12688821/YL0qE50zqs.mp4) **Exact steps for others to reproduce the error** Open Blender 3.0.0 Open Keymap Make new Keymap or use existing one with " transform.edge_crease" Set Factor to .9 in keymap settings tick "Confirm on Release" in keymap settings Make a Cube in viewport, enter edit mode, select edge, and Tap your new made or existing key for "transform.edge_crease" You will see that Factor is not updated with value set in keymap settings !!! Same process to test Factor -1, for removal of crease!

Aivis Ozols commented

2021-12-04 11:39:37 +01:00

Added subscriber: @Positivity

Germano Cavalcante commented

2021-12-08 17:08:39 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-12-08 17:08:39 +01:00

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

Germano Cavalcante commented

2021-12-08 17:08:39 +01:00

Thanks for the report.

It is strange to execute a modal operator (whose final value depends on the mouse position) with the final value pre-established.
In this case, should the operation really be modal?

I'm confirming the report as a bug as the behavior changed and because of the strangeness of a modal operation with pre-established final values.

Thanks for the report. It is strange to execute a modal operator (whose final value depends on the mouse position) with the final value pre-established. In this case, should the operation really be modal? I'm confirming the report as a bug as the behavior changed and because of the strangeness of a modal operation with pre-established final values.

blender-admin commented

2021-12-08 18:20:03 +01:00

This issue was referenced by f32b63ec58

This issue was referenced by f32b63ec583ce70081a1998b31470dbb74450a0f

Germano Cavalcante commented

2021-12-08 18:22:35 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Germano Cavalcante closed this issue

2021-12-08 18:22:35 +01:00

Germano Cavalcante self-assigned this 2021-12-08 18:22:35 +01:00

Aivis Ozols commented

2022-01-27 00:07:02 +01:00

@mano-wii Hey, I finaly got to download blender 3.0.1, however, when I tested this, it still won't work. Same steps that I described above with key and factor and I still can't set value with the key press !

Is this fix not in blender 3.0.1 ? or maybe I need to do something else for Factor to work in "transform.edge_crease" ???

@mano-wii Hey, I finaly got to download blender 3.0.1, however, when I tested this, it still won't work. Same steps that I described above with key and factor and I still can't set value with the key press ! Is this fix not in blender 3.0.1 ? or maybe I need to do something else for Factor to work in "transform.edge_crease" ???

Germano Cavalcante commented

2022-01-27 00:37:18 +01:00

Changed status from 'Resolved' to: 'Needs Developer To Reproduce'

Germano Cavalcante reopened this issue

2022-01-27 00:37:18 +01:00

Germano Cavalcante commented

2022-01-27 00:37:18 +01:00

In #93642#1295569, @Positivity wrote:
Is this fix not in blender 3.0.1 ? ...

To make sure try the latest daily build: https://builder.blender.org/download/

> In #93642#1295569, @Positivity wrote: > Is this fix not in blender 3.0.1 ? ... To make sure try the latest daily build: https://builder.blender.org/download/

Aivis Ozols commented

2022-01-27 09:19:38 +01:00

I just tested and yes, sadly it is not included in blender-3.0.1-stable+v30.dc2d18018171 it is only included in blender-3.1.0-alpha+master.0e86c60c28b6 .... :( really sad
I like working with stable versions so 3.1.0 alpha is not option :(

But Thank you, I will just wait for stable release of 3.1.0

I just tested and yes, sadly it is not included in blender-3.0.1-stable+v30.dc2d18018171 it is only included in blender-3.1.0-alpha+master.0e86c60c28b6 .... :( really sad I like working with stable versions so 3.1.0 alpha is not option :( But Thank you, I will just wait for stable release of 3.1.0

Philipp Oeser commented

2022-01-27 09:29:13 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-01-27 09:29:13 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Philipp Oeser closed this issue

2022-01-27 09:29:13 +01:00

Philipp Oeser commented

2022-01-27 09:29:13 +01:00

Yep, fix is not included in 3.0.1.

@mano-wii : though I go over fixes to include in LTS, this was not case entirely for the 3.0.1 corrective release [devs added fixes there themselves mostly. Whenever we do another corrective release, maybe we should define exactly who is responsible in that case]

In any case, now that 3.0.1 is out, the fix is not included (sorry), we'll have to either dare using Alpha (or wait for 3.1 release which is scheduled for March 9).
Will close (since there is not much we can do here now).

Yep, fix is not included in 3.0.1. @mano-wii : though I go over fixes to include in LTS, this was not case entirely for the 3.0.1 corrective release [devs added fixes there themselves mostly. Whenever we do another corrective release, maybe we should define exactly who is responsible in that case] In any case, now that 3.0.1 is out, the fix is not included (sorry), we'll have to either dare using Alpha (or wait for 3.1 release which is scheduled for March 9). Will close (since there is not much we can do here now).

Germano Cavalcante commented

2022-01-27 14:57:04 +01:00

This report is not exactly about a bug. It's about a behavior that changed in edge_crease due to a problematic change that was carelessly added in some version of 2.8x and therefore removed and limited to just a few transform modes.
I didn't really see a need for a backport.
The commit is not exactly a "Fix", it's more: "Support offset for more transform modes"

This report is not exactly about a bug. It's about a behavior that changed in edge_crease due to a problematic change that was carelessly added in some version of 2.8x and therefore removed and limited to just a few transform modes. I didn't really see a need for a backport. The commit is not exactly a "Fix", it's more: "Support offset for more transform modes"

Germano Cavalcante commented

2022-01-27 14:59:28 +01:00

Ooops, I don't know how that Needs Information from Developers came out!

Ooops, I don't know how that `Needs Information from Developers` came out!

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

transform.edge_crease ignores Factor when used as with hotkey #93642