The problem is not solved. Compare 2 screens in both versions. Hidden particles in 2.79 are translucent, and do not interfere with editing. In 2.8, they are solid and visually pollute the view.
Agreed, it’s way better. Thank you!!
The setting is in the preferences now (where it belongs!):
It's happening a lot. Specially when using images in the file. They suddenly disappear and everything else becomes unselectable.
I can't reproduce this error today so I'm closing it.
Clip Studio Paint for comparison on windows.
Do gimp or krita have the same issues? I’m wondering if they’ve solved the problem.
We have been testing several options and even MS-Paint has the same problem. I'm thinking that maybe the solution is not at event side, but to generate a Beziert in the segments to get a smooth transition. Using Beziert, we keep event system, don't overpopulate events and get the same result in all OS's. I need to think, but I have a rough idea already.
Collections system is related to common layer systems (3Ds Max, Maya, AutoCAD, Sketchup, and any other application that have unlimited entities called "layers")
The main problem with the usability of collections is the limitations of the designed infrastructure - the collections were not designed as a system with unlimited entities support.
It is nice to have 10-20 collections to work with default solutions, managing 50 is challenging, having 100 is tough, 1000 are impossible to control.
As a result, to manage dozens of projects with hundreds of collections with several settings in each, obtained from different people is extremely exhausting.
It's possible that your graphics card doesn't meet the minimum requirements: https://www.blender.org/download/requirements/ or
that your graphic drivers need to be updated. But it's impossible to tell because you didn't provide any information.
I misunderstood. You're right, in 2.80 it works:
In 2.81 (sub 15), branch: master, commit date: 2019-10-11 19:43, hash: rB60d02b336eaf it's greyed out:
So it does look like a bug.
oh, ok, it's not bug. all works but by unlogic way. (target > forces)
Yeah, long time "paper cut".
Update problem description
TYPO: issue is that ffmpeg libraries are NOT being pulled down to local machine... sorry for the unnecessary hits on this report
ok, issue is that ffmpeg libraries are being pulled down to local machine thus can't link when building. I pulled the 2.18 ffmpeg archives from here (https://svn.blender.org/svnroot/bf-blender/tags/blender-2.81-release/lib/darwin/ffmpeg/lib/) and dropped them into INSTALL_HOME/lib/darwin/ffmpeg/lib and build/install ran fine
I have also same crash in windows.
Apologies folks, I think some neglectfulness on my end. Running make generated the error above. When I run make full I don't get the linker error above but I do get ld: library not found for -logg. I have a feeling perhaps I'm not pulling down latest versions of those dependencies. Will investigate and update.
Yes, think the issue was discussed and was put on my desk, but not administrated correctly.
Your operating systems is very old and has no bug fixes. The driver is recent. The operating systems is extremely old and has absolutely none of the bug fixes released in the last decade.
Loading factory settings didn't help.
Sorry I had missed the "apply on spline" button on the modifiers
Upload a simple .blend file showing the problem, please. Did you check if loading factory settings helps?
Opened 12 of them in Gimp, PC did slow down a bit, Task manager froze for a while
Then it was fine after
I was asking to open those EXRs in another application, like an image viewer, 12 at once. To check whether your computer is able to handle that many EXR reading or not (Blender does nothing more than that, but with 12 threads it might do 12 at once).
This is probably a side-effect of D5191: Alembic: import & export face-varying normals. I guess this has always been an issue in the export, but now that we import correctly it's showing up. I'll have to investigate.
Why did you wipe the report? :o I downloaded the file you attached before you deleted everything, and couldn't reproduce the crash. Did it stop crashing for you and that's why you made the report empty?
Double-report of T70769, closing this one.
Can you clarify the issue? I see this relates to T69432, and a fix was submitted for that. Was the issue not fixed? Or did you submit this report just to confirm that it was fixed?
@William Reynish (billreynish) just a side note.. the override error is only on move gizmo. Rotate gizmo is working smooth.
As I thought, this is not a bug, but is a good example of the poor decision to use multiple controls to override the same thing:
If I follow your instructions exactly with your example file names I see this (correct) order:
Notes: looks like make update is pulling down ./include/*/*.h, but, isn't pulling down any ./lib.*
Actually this issue is not caused by moving the sequence.
It's a duplicate of T70581.
I can confirm this.
I also confirm on the radeon
When to increase program performance? This is not a bug, but why important tasks are postponed to the archive, and are no longer performed. Performance, terminator artifact?
Sat, Oct 12
@LazyDodo (LazyDodo) I tested with these lines:
Are you using the factory default keymap? I cannot reproduce your issue, even if I don’t follow what you are trying to do and why.
Maybe this give us some ideas: https://devblogs.microsoft.com/oldnewthing/20120314-00/?p=8103
@LazyDodo (LazyDodo) Sure!
This seems fun, mind if i take it?
Thank you, I actually tried cycles with the monkey, before, I tried again and it is working, I think my computer was just taking a while to update.
Like the tooltip states, that option works only in orthographic side view:
It's greyed out when viewport is in perspective mode.
Unfortunately I'm not sure how to get rid of the generated thumbnails
I can't test them in any Blender versions anymore.
I have been debug with Ghost and the events received in the operator.
Pointiness is not supported in Eevee. In Cycles you need dense mesh for it to work. Default cube doesn't have enough polygons. If you subdivide the cube pointiness should work:
And, if you set them both to "Right" A Right click sets the Origin, and a Left Click produces the error. (And the error was the problem for me, since it took a while to figure out the cause. I found it natural to think that if the Blender Select With preference was set to Right, Blender would select with a right click. I would not have thought the natural setting would be for the Mac Preference to be set to Right and the Blender preference set to Left.