As Lobo suggested, you can use Intel HD graphics with Blender, however, it will not help you with Cycles rendering.  Cycles will only use your CPU unless you have one of the supported graphics cards and architectures.  Intel HD can help with Eevee rendering, but even then performance will be limited compared to Nvidia or AMD cards.

WOW indeed Lux that is amazing looking I have not ventured into Geo/Nodes as a couple of the tuts I have tried to follow have not really clicked maybe yours will give me that kick in the boot. And good to see you back it has been a while 

WOW Lux, what more can I say?  I always like your tutorials . . . so . . . are you going to give us one like this?

Ehhh ... not a fan.

I just skimmed thru it, but it looks like most of the creasing/weighting could have easily been sorted by an extra loop, and that would make the mesh universal to all software. Using creasing/edge weighting you're left with a mesh that's software specific [possibly even version specific], and you've only saved maybe a couple hundred polygons, if that? I'm sure there are situations where it has its merits, but I'd rather see proper edge flow without the crutch.

Is there any way you can project the details to a vector displacement map or even a normal map on a much more lower density column like the cylinder in your example, then manually unwrap that?

Warlock279 posted at 11:33 AM Thu, 19 January 2023 - #4454235

goofygrape posted at 7:40 PM Wed, 18 January 2023 - #4454196

Thank you Lobo3433

I found Rigify in 3.1 now on to YouTube.

The only problem with Youtube is I've been banned for life

goofygrape aka bigjohn

Some crazy thoughts here, but . . .

Log out of youtube/google? Delete any cookies you have on your system from google/youtube, and DON'T try to log-in again? Use "private" mode in your browser? Use a different browser? Use a different device? Reboot your router if you have a dynamic IP? VPN?

Short of your ISP blocking you [for I can't even imagine what?!], I don't think there's any way for google/youtube [as pervasive and far reaching as their tracking is] to actually prevent you from watching videos if you visit anonymously [at least videos that aren't age restricted, which I doubt tutorials would be].

Yeah, all you would need is a VPN.  If you wanted to log in, obviously, then a new gmail account would be in order too.

Happy New Year, my friend!  I hope we all have a prosperous and healthy New Year!  Stay well and tell the wife I said Happy New Year too!

Yeah, he must have accidentally enabled the "line" stroke method for the brush.  It's an easy fix.  Go to the stroke dropdown at the top of the screen and change it back to "space" in the stroke method panel.

I agree with Lobo.  Looks like a weight mapping issue on the fingers, probably caused by certain incompatibility between the python version of the addon and this version of Blender.

Keep in mind, folks, that Blender dev team will be integrating eCycles programming into CyclesX very soon.  In fact, you can actually download eCycles Lite for free now, since that will basically become a native part of Blender in future releases.  eCycles was previously a separate build of Blender that contained impressive rendering enhancements, and the Pro version still has some features that are not available in any other render addon.

However, in my most recent testing and experimentation, I've found the Turbo CyclesX addon actually outperformed eCycles Lite in many of my animations.  This primarily came from the ability to "clean" noise from a volumetric fog in an animation that I previously could not clean up with Optix or the OID node in eCycles Lite or regular CyclesX before.  This was the one thing that completely sold me on the Turbo CyclesX addon as a true solution for difficult-to-render animated scenes.  I had about two or three scenes that I had to put on the backburner for months, simply because I could not render them in a reasonable timeframe with the quality I wanted.  Thankfully, now I'm capable of rendering these scenes without a significant upgrade in hardware.

One thing I noticed straight away.  It has its own denoiser built in somehow.  Make sure when you use it, you disable the render denoiser in Cycles.  If you don't do that, it may override them anyway, but I've been experimenting and so far noticed it may actually take extra time for it to do that.  Make sure you watch the videos showing the creator using the addon, because that helped me. I was a little confused as to why render times were exactly the same no matter what sample count I chose.  Come to find out the reason for that is because it will only consider your input samples when you use the "User" preset.  If you use the "low", "medium" or "high" presets, it overrides any of your manual values with preset internal values of its own.  So even if you have render samples set to 64, for example, it will not use that value unless you choose "user" preset.

Update:  I just purchased this addon tonight and have played with it for an hour or so.  I'm still getting used to how to use it properly, although it is very easy to use out of the box.  There aren't many settings if you choose the presets, but there are still many things you can tweak by hand if you wish (which is what I've been doing).  So far, it's definitely handling large, complex scenes far better than anything else I've tried so far.  I'll show some examples when I get a chance, but since I'm trying to use it for animation purposes I'd like to render an animation with it before I show anything.  However, I also have K-Cycles, and so far this plugin has been able to render a 4k scene with heavy volumetrics and adaptive displacement in roughly half the time of K-Cycles, and triple as fast as vanilla Cycles, with better detail than using Optix denoiser.

One thing I would like to point out is that this is an actual ADDON, not a separate build like I originally suspected.  K-Cycles and E-Cycles are separate builds.  This is just an addon that you would install like any other addon to your existing build of Blender.  It uses a nifty node-cache system for composite nodes, so if you use process heavy nodes in composite, such as lens effects, this will cache the node results and reduce the render expense of such processing.   There are definitely some clever things going on.  My concern is animation, so the jury is still out on that until I can render a full animation with it, but for still images, it seems to be very fast and the results are extremely impressive.

That certainly does look interesting, but since I haven't taken the plunge into Blender 3 yet, I'll wait and see, as the saying goes.

I agree with Lobo3433 here as well.  You can have multiple versions of Blender running on the same machine without any conflicts if you use the zip downloads.  You can try going back until you find a version that works, but if it's a hardware issue due to the age of the machine, then you may need to go back as far as 2.79 because this particular issue began with the 2.8 generation.  Still, some versions of 2.8 could work for you.  There may be many more display issues underlying this that just haven't manifested themselves yet.  Even if you solve this issue, the old hardware might bring you more headaches down the road, such as viewport display anomalies and rendering problems.  If you can find a GPU that will work on that motherboard but is also on the official supported card list from Blender Foundation, that would be the best option.

Blender Foundation claims that any GPU with at least 1gb of VRAM and support for OpenGL 3.3 or above should work with the 2.8x series, but that is minimum spec requirements and it will definitely still have some problems.

This type of thing has been reported as far back as 2.8, and it's usually caused by unsupported GPU or graphics card drivers.  If the hardware is from 2009, then it's going to be quite outdated, so I would be confident in saying it's the GPU.