In T61474#675173, @Ludvik Koutny (rawalanche) wrote:

In T61474#675150, @Adrian Rutkowski (rrtk) wrote:

the problem is still there even with today's build

I think that saying its related to gizmo is super misleading.
It is way more noticeable when gizmos are present but it's still there without it

I mentioned that before on topic that was merged here, the problem is there only if other software ( even in the background) is not using the video card
Opening anything next to blender instance will give an instant speedup that includes Nvidia Experience Overlay which is enabled on GTX cards by default, so 99% of users will not even notice unless they disable everything.

Yes, exactly! Most people don't notice because they run lots of garbage in the background which prevents GPU from idling. Only in rare cases do people care about their system background processes remaining clean and not utilizing much of hardware resources. And only then this bug manifests. For some reason, in some cases, which include gizmos being visible, Blender keeps getting the GPU to idle, which causes constant lag spikes and stutter. I have to solve this by always launching OBS and keeping it running in the background, so that it keeps the GPU awake.

In T61474#674967, @Clément Foucault (fclem) wrote:

Did the situation improved with todays build?

In T64131#672000, @Sebastian Parborg (zeddb) wrote:

Can you try the latest blender beta and the latest nvidia drivers?

Same bug with Duplicate Linked (Alt + D) - proportional editing is turning on.

In D4683#106672, @Brecht Van Lommel (brecht) wrote:

One problem is that the current icon loading code assumes monochrome icons. For a colored icon set this means the icons will be tinted with with text and theme colors, which is not great.

The easiest way to distinguish between such icons would be based on the filename. For example if it's called blender_icons_mono_32.png it could do the same as it does now, and for blender_icons_color_32.png it could set all of them with type ICON_TYPE_COLOR_TEXTURE.

My team also making move from 3DS Max to Blender .
Actually, I use Blender for 2 years as main software (after 3DS Max and Maya), but it is interesting to see how people get confused by things that I never thought of might be a problem.

In T61474#647002, @Clément Foucault (fclem) wrote:

Can anyone try to reproduce the issue with tomorrow's built (March 24th) using --debug-gpu as command line argument? This should disable Polygon and line smoothing on the gizmos. I want to know if that's the issue or something else.

@Clément Foucault (fclem) This weird lag behavior is last about month for now, don't it should be high priority and fixed since it is totally ruin usability?
This lug still in all latest builds and I can reproduce it on different machines.
Please, don't throw such bugs that makes blender unusable at all.

Ok, found solution:

As @Rombout Versluijs (rombout) said this added in 779860d34e26, 2019-02-22 build, so I close task as invalid.

I tried open file with 779860d34e26, 9541ce2c261b, 1af810b4ff17 - loads instantly on windows.

Blender 2.8 requirements for VGA is OpenGL 3.2 compatible graphics with 2 GB RAM.
NVIDIA GeForce 9600 GT supports only OpenGL 2.1

Can't reproduce on
2.80, 9541ce2c261b, blender2.8, 2019-02-22.
2.80, 1af810b4ff17, blender2.8, 2019-02-21.
2.80, 855b3e68ef27, blender2.8, 2019-02-20.
Try latest build.

Can reproduce on 2.80, 9541ce2c261b, blender2.8, 2019-02-21.
I think it caused by
Outliner visibility unification: Implement 3 levels of viewport visibility like in here T61788.

Hi!
Please, share your .blend file to investigate problem easier otherwise it hard to know what happening.
And please add Blender Version (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen).

It seems same bug take place when rendering using F12 as mentioned in here T61788.

Ok, sorry ... That's problem from my side.
I'm launching Blender using PYQT5 QProcess and it hides the console in some way.

In T61651#622364, @LazyDodo (LazyDodo) wrote:

Can't reproduce, window is still there on the latest buildbot and toggle works fine. i am however highly suspicions of the blender version reported.

Open Blender -> Press F3 -> Search for "Toggle System Console" -> Press Enter

F3 is the 2.8 shortcut, in 2.79 this is the space key.

Wow, just noticed that Blender now starting without opening console window, that's great!
That's why operator not working I suppose...

Hi!
First, please use an english (it is an International language, and it used all across blender services) to write you report.
Secondly, fill all the info in the description and describe you problem more or attach a screenshot.
It will help developers investigate problem faster.

It seems mirror can't read geometry produced by curve modifier. Don't know is this a bug or by design.

Please, provide full information including:

• Operating system
• Graphics card
• Blender Version (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)

In T59626#584709, @Brecht Van Lommel (brecht) wrote:

Probably caused by rBf4c70a35a292: UI: tweak text editing fields for higher contrast.

I guess this background just needs to become opaque.

Well, it's not a bug, there is now options to affect specific type of transformation.
Weird... Maybe enable all by default since it is confusing?

@Szymon Warunek (szymi) Hi.
You forgot to apply scale to your object.
There is a thread explaining why you need to do such thing.

@George Harris (rambobl) Please, add a hash and date from splash screen into Blender Version. "Blender 2.80 latest build" is useless.

Already fixed rBac80ceae7707918eb410dcef6df199adf1615ca7

Fixed rBac80ceae7707918eb410dcef6df199adf1615ca7

Same situation covers the Select Linked operator too.

Had a look at this part of code. I can confirm that T57086 caused by this.
I'm new to blender code, can't really fix it for now - the Alt key still behave as it was in 2.7*.
Why in transform.c lines 4989, 5004 used input from Alt key not actual value of use_even_offset?

I can't get it work with array modifier too...

Select Linked to Shift + RMB Double Click needed because then you can add it to selection, either way it will deselect everything before it.

Is there possibility to change Select Linked to Shift + RMB Double Click and Select Linked All to RMB Double Click in case of user-friendly selecting workflow? I mean make it as default shortcuts, because now there is no easy way to discover how to select whole complements of the mesh.

Well, it's tricky to make a proper behavior on this. But user still expect 'auto join' in my opinion.
Thanx for explanation by the way!

In T54643#539686, @William Reynish (billreynish) wrote:

Oleg are those two different objects? If so I don't think it will work. You also cannot create edges or faces between different objects.

We could have a better error message here though.

@Dalai Felinto (dfelinto) MESH_OT_bridge_edge_loops committed but it is not working at all 😞

@William Reynish (billreynish) @Dalai Felinto (dfelinto) @Campbell Barton (campbellbarton) Hi guys! I made a proposal on Right-Click Select about checkboxes. I think it should work very well for parts of panel where checkboxes mixed with other UI elements. It easy to click on them and they don't distract the layout. What do you think about it?
P.S. Didn't notice my proposal is already mentioned in messages above. Glad peoples like it!

@William Reynish (billreynish) Hi. It will be very convenient to have "Camera Facing Billboard" option per "annotation" object, when it automatically face to camera view all the time like 3d sprites in games.

Will be very consistent to swap Y and C for axis switch ([Z, X, Y] to [Z, X, C]). All in a row!
It is like using 1, 2, 3 for modes and selection.
Y is too far from X and Z on keyboard and C is only for rare circle selection tool.

In T55303#507456, @Vuk Gardašević (lijenstina) wrote:

Can you please be more specific what exact version has the error? The 2.8 branch is the blender 2.80 if you build your own blender and currently most of the add-ons will not work as they need conversion to the new API calls.

Setting as incomplete until additional information is provided.

Will there be option for F6 floating menu? It is still a lot faster in my opinion.
I maped it to SHIFT+RMB and always have permanent access to tool settings under mouse cursor.

In T54643#501480, @Leon Eckardt (Leon95) wrote:

VIEW3D_OT_snap_cursor_to_selected: the only problem is that the manipulator (or calculated center) of the selection is only calculated with parts of the active object.

@Dalai Felinto (dfelinto)
This operators already working:
MESH_OT_quads_convert_to_tris
MESH_OT_tris_convert_to_quads

"Move the '{' to the previous line" done.
"Move RNA.*_get outside the for loop" done.

@Dalai Felinto (dfelinto) I found out that TRANSFORM_OT_edge_slide is already working without any patching.
Also, how we should solve workflow design for tools like MESH_OT_bridge_edge_loops?
It seems like this operation should join objects, but I don't no how solve that task with my current knowledge(

@Dalai Felinto (dfelinto) Hi! I uploaded my first diff and the only thing I can't understand is how to know that no one works on the current task?