Sigh you should not put invalid. wait and discuss some more until found out bug. I am show you proof. I ask again, again many times. Boolean need to fix code.
May I have link "ask a question in a user forum."
@Kent Davis (mac4kent) Ok. This is not a forum for usage questions. Refer to the manual, or other training material, or ask a question in a user forum.
I don't understand how does Boolean work.
Okay. Thanks anyway!
@Kévin Dietrich (kevindietrich) Glad you came back! Could you please update your patch D2388 for the current code, so we could review and make it to the master finally, cause it's very important for fluid rendering.
If there's something I can assist with, let me know. I'm not a coder anymore, but maybe a can help.
Oh ok I see this picture and I send screen shot for you.
Can you show me screen shot where is it?
Boolean isn't 'working' because you didn't use a boolean tool or execute a boolean operator.
Why you say invalid?
There Boolean not work
I don't understand your type text.
@Kent Davis (mac4kent) This has nothing specifically to do with the Mac platform.
This is not a bug. You are using the Box Select tool and changing the selection options, which is why it says Box Select, and the tooltips say Set a new selection, Extend existing selection, etc.
May 19, 2019
do you have your own Macintosh yourself?
Yes. I think the problem started two days ago. the previous version was ok. test on two different macbooks and I had the same problem.
@Brecht Van Lommel (brecht) I made this file in 2.79 and it works fine. I opened it in 2.8 and it didnt worked. I didnt think this was a limitation because it worked in 2.79.
@Randell Acuram (Ranakade) did you try fresh build with clear installation? Another startup files?
This 4 example
seemed to be working fine with the build from 15.05.2019 - 8a6414ed46f6.
Try to change input library (windows ink / wintab), try to use viziblr fixmypen to off some services. Check if windows pen handwrite input of such services are off.
Animation playback being slow with cloth simulation is not a bug. Cloth simulation can just be slow and this does indeed make the user interface unresponsive.
I can reproduce it (win7, GT640, yesturday build)
It looks so: I move line slow, then up pen and move it aside fast. But Blender still counts pressure. The same with mouse but little less.
Feels like presure/click input lag without moving input lag, so moving is overtaking clicks.
Note also that these are settings for box select. These are not related to boolean operations on meshes.
Please follow the bug reporting instructions:
|can reproduce the exact same issue. For me this issue started after the recent edit mode selection changes - since then vertex selection has been broken.|
It is normal that rendering uses a lot of power. You can reduce the number of threads in the Performance panel, but by default it will try to use all computing power available to render as fast as possible.
We have already have tasks to plan this work:
Yes it works, thanks! :)
Thanks William. Yes, you're right, it does appear with Alt-M, but only when I switched back to the default Blender Keymap (all my custom shortcuts remained the same, since they were previously saved, but access is regained to the "Select With" and "Spacebar Action" preferences menu (which disappears under custom saves) and apparently this Merge By Distance command as well).
Not a Bug: I'm pretty sure you need to enable the Viewport anti-aliasing for it to work. Check my post history, I created an issue about this, that's when the Viewport quality setting was replaced with the Viewport anti-aliasing setting. Still no idea what the Multisampling setting affects, though.
This would have given the same issue in 2.79. The user manual generally lists limitations of tools and modifiers, though this one does not appear to be documented.
The attached file appears to be working as I expect it. The render engine is set to Cycles, so it changes the light power to match the Cycles shader node setup. That does mean the Eevee results change, but we can't avoid that since the purpose of this change was to unify the light power settings between Cycles and Eevee.
@Brecht Van Lommel (brecht) my bad. it worked in 2.79 so i thought it should have worked in 2.8. Is there a list or something that says whats the limitations because i keep accidentally making tickets for limitations?
The latest blender beta 06c4139a6833 has an api change and the script from https://docs.blender.org/api/blender2.8/gpu.html#rendering-the-3d-view-into-a-texture throws now an error: Line 19 context.depsgraph : 'Context' object has no attribute:'depsgraph'.
@Daniel Ulrich (dulrich), @Alfredo Rodrigues (galfim) did the problem show up about 2 days ago or did it last longer?
The OpenGL logic on the T64800 has not changed. It is difficult to identify how this commit can bring such problems. And where the problem really is.
(Note: X-ray selection is totally different from the other. So this information does not help much).