Hi, By curiosity, I downloaded your blender file and tried to render it on my work PC. It's running on Windows 10, has only 8Gb ram, and old I3 CPU and a Nvidia GTX1050. So far it has been rendering, and no crashes. (Using Blender 3.0)
This is frame 103

Hi, checked your scene with Blender 2.93, and Blender 3.0, on windows 10 with a NVIDIA Graphic card (GTX 1050) and there is no issues whatsoever. Here is a screenshot:

Hi, Seem like a vertice that is selected to me. Your could press <A> twice to deselect. If you do that, is vertice is kept selected?

Thanks for the info @Germano Cavalcante (mano-wii) ! I'll watch the issue on T55365.

Hi, The reported error is:

Also you might an issue with your firewall blocking transfers from the installer.

Hi, I don't see the issue. Once I logged in with my Blender cloud account, the tutorial was available.
The link to www.manuco.com is only for looking at the author site, not for watching at the tutorials.

Hi, you can't fix shaders since they are coded in the software. You seem to have lots of issues with other software and not just Blender; upgrading the driver is recommended.

The intel integrated is being used as first display by Blender and there not enough video ram to being used. Could you go into your BIOS setting of the laptop and increase it at maximum values (Blender and EEVEE will use a lot of video memory). This should help make it work at startup.

Could this be related to the GPU memory being hit at maximum on the GTX1050? Is there a way to know the used graphic memory at the moment of the crash? This card is being rated at 2GB of VRAM...

Hi, Just checked the informations and while it's better to use a dedicated video card instead of the integrated one, this should also work, but the problem is that the video memory assignment is too low on the integrated video.

Hi, I was able to look at your first log. Your AMD Video is recent and should support OPENGL 4.5. And it seem that your drivers are installed.

Cool! So this could be used to motion retarget from one character to the other?

This is great! Any ideas about optimizing viewport refreshes while editing? This could surely improve feedback response... How is the viewport refresh managed right now?

In D10484#281874, @Brecht Van Lommel (brecht) wrote:

.... Such popups should not flicker on the screen if the operation is fast, and that's impossible to predict in advance.

A proper implementation should use multi-threading, executing the operator in one thread while another thread monitors progress and draws a popup if necessary.

Wow! Thanks Harley!
That's a great improvement for me when loading bigger scenes. I love it.

Hi, Having a button to lock the current active camera with the viewport camera, was a great addition. I'm really sorry it's being removed completely with no design or improvement plan upon removing it.
It made sense it was in the viewport camera control icons, and made it fast and intuitive for newcomers. I've seen some complaint theses controls were not easy to find.

Just a question out of curiosity about this. Will the port work without Blender using METAL from GL on the new Apple devices? (I mean, blender using Vulkan/MoltenVK)
I was thinking they dropped OpenGL, OpenCL for Metal...

That would be a nice thing to have when doing UV maps on a model! I'm using an addon to do that right now.

For the Dyntopo problem with performance, why not force the user to select a region of the mesh to work on? If it's too laggy, then select a smaller region of the mesh.

Interesting. Yeah, looking at the log, it suffered from a memory corruption error.

Thanks! Jeroen! I asked the french community user to try again with the fix.

Update: (june 29)
Got new result from my french community user testing the problem with 2.83.1
User tried with 2.83.1. It still freeze.

Hi, Have to report the same problem with someone from the french community using a Intel NUC (Intel GPU), and using Ubuntu 20.04 as OS. The issue happen more often when using the gizmo to rescale an object. The UI freeze and he can only force quit Blender.

I can understand you. I don't have much income too. If you can do it, you could try to install XUbuntu on this old PC just to be sure it's not related to the distro, since your other PC run fine on this distro. If you install XUbuntu and there is no issue, the you will know it's something in your distro, if it's still persist in the problem then we will have a confirmation that it's hardware related.

Unfortunately, If I'm not wrong, this are compiler directives to build using theses CPU extensions.
The only way I would know is to modify the code to not use the extensions your CPU is not supporting (still a guess, I'm not sure the developper uses theses extension, but it would made sense as it accelerate lots of things)

Thanks for the info about your hardware. I'm not totally sure, but Blender might use some CPU extensions that are not supported by the old Pentium 4 (Like SSE), but are present on the newer Intel Atom.

You did not mention what CPU you have, how much ram. CPU Spike could be happening with libraries that are needed by Blender, but your distro have problem with them. Do you have another PC with another Linux version to check?

Hi!
This seem directly related to the OpenGL support of your card in your environment. Using "Software-gl" is only using the CPU to do everything. Have you tried something else that require HARDWARE OPENGL on your system? It almost look like you don't have openGL drivers installed. Version 2.79 is less demanding for video card requirement and can almost run on anything.

They added draw call batching in 2.81 to make it faster. (23 sept) The problem is probably related to this. Your old video card seem to have difficulty with this.

when ever i go to rendering my computer
shuts down

Thanks Francesco! Confirmed on my end.