Support Blocker - Cube Placement - Problem/Bug? Cura 3.3.1

[Tomasz_M 5]

Hi everyone,

 

today, for the first time I wanted to try to Support Blocker function available in Cura 3.3.1. The function, as is, works fine, however placement of the blocker cube is a nightmare.

 

Consider an example when you do not want any PVA support in small horizontal through-hole, like this one:

 

As I understand if I want to block the support I select the body of the object, then select "Support Blocker" and then click the red area visible on the picture above.

 

Aaaaaand nothing happens, however after changing the camera view I find a very distant dot, far away from the printer workspace:

 

If I'm very very precise with my mouse I can select them, then enter the 0,0,0 mm position in the Move menu and then use the blocker cube as intended.

 

Am I doing something wrong? How should I select the area for support blocking? Or is it a Cura bug?

 

 

Edited May 14, 2018 by Tomasz_M

[burtoogle 513]

What I do when it is difficult to click on the underside is simply to click on the side wall of the part and then use the move tool to quickly move the cube to where I want.

 

[Tomasz_M 5]

Even worse! ?

 

That's my object:

 

And that's what happens when i click the side wall:

[burtoogle 513]

Hmm, don't understand that, perhaps @ahoeben can help?

[ahoeben 1,948]

This is (obviously) not the way it is supposed to happen. Picking the "depth" of the location on the screen where you click seems to go wrong. I don't yet understand why this happens exactly, but it has been reported by a small handful of users. What GPU do you use?

[Tomasz_M 5]

Hi ahoeben!

 

It's just Intel's HD 4000.

 

Can I perform any user test for you? I'm very eager help ?

[ahoeben 1,948]

Thanks, that helped in reproducing the problem. I will try to fix it.

[ahoeben 1,948]

See https://github.com/Ultimaker/Cura/pull/3813

[Tomasz_M 5]

6 minutes ago, ahoeben said:

See https://github.com/Ultimaker/Cura/pull/3813

 

Thank you for such a quick response!

 

I'm glad to report that the patch fixed the above problem for me. PERFECT

[ahoeben 1,948]

Thanks for testing it so promptly