Dixel

Or this one, very good! https://www.touslesdrivers.com/

Perhaps you missed, @NotHereToPlayGames told - WebGL works regardless of that file, he simply blocked it via the flag, at first.

So much for Revo Uninstaller or similar popular "uninstallers". Nevertheless, congratulations! I frequently check the driver folder and sort out non-Vista junk by the date.

Then it's like we both told from the very beginning, those files aren't needed for Web-GL, and @UCyborg may be confusing stuff.

And most importantly, in Thorium and Supermium, they all are disabled by default, you'd need to force 'em via those flags to even get the idea of how they may work/don't work. I'm pretty sure it was disabled in 360EE, too. Relevant Chromium command line switches When running the chrome executable from the command line, SwiftShader can be enabled using the following Switches: As the OpenGL ES driver, SwANGLE (ANGLE + SwiftShader Vulkan) As the WebGL fallback, SwANGLE (ANGLE + SwiftShader Vulkan) As the Vulkan driver (requires the enable_swiftshader_vulkan feature)

https://github.com/google/swiftshader "SwiftShader is a high-performance CPU-based implementation of the Vulkan graphics API. Its goal is to provide hardware independence for advanced 3D graphics." I don't see it's demanded for running Web-GL at all.

It can only be used as the WebGL fallback, if you borked something in your release, we aren't at fault Web-Gl didn't work for you. Here, you can familiarise yourself with the official Google docs. https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/docs/gpu/swiftshader.md

Explains what? The *one* (and only one) member that shouts from rooftop to have his PC broken after the deletion of vulkan files is you. UCyborg just wrote to you, without them - no crashes with the browser at all.

Why it's cropped? Not only Win10 is not related to this topic, it's also non-informative at all. No device, no driver version, no bitness is shown. Edit. Driver version is important since Vulkan was fully implemented starting from 369.xx

It's XP, not XP64 you claimed to have problems with.

How is this related to Vulkan DLLs?

Pfffffff! That doesn't count even for one second, only real hardware does.

First do the following to make sure. From extensive research on this topic, I understand that all those .dlls are a delay load dependency, not an immediate startup dependency. Chrome will only load them if it gets a proper Vulkan config from your setup. Get the latest XP capable GPUz, see if you have a Vilkan capable system. Example:

Shoot a short video like @66cats does, add here so we can see.

Thorium, Supermium use DX9 acceleration on XP (but only if forced via flags). It's written at github. Not a word about Vulkan, of course.

Spam/rumours/fake_news/hearsay topic that was locked for a good reason, yet you continue to spread those falsehoods.

Chrome doesn't request those to be present on any OS.

I'd start with removing outdated VC redist packs, they are known to cause issues, on XP especially. If you ever had them, remove all remnants. I don't install those at all.

Just as soon as you were notified Dixel suggested that flag. I wonder how many others will be thrown out, if you knew I too suggested them, anyways, upvote for previous Firefox post, I like when you post factual information without bias. I like when everyone posts factual information without bias.

Here you can see what Chrome thinks of your device. Go to: chrome://metrics-internals/ Click on "variations" Look at the "Low End Device" param.

It depends on the user's behavioural patterns, one would need to extensively use youtube or instagram to notice, twitter maybe, which I think you don't.

In that case, go to chrome://net-internals/ Tell me what you see in: Attribution Reporting is currently "insert here" in this browser.

Does the same happen with Thorium?

Google's definition of "Low end" is very laxed, I tried to run Thorium on an ancient 775 socket computer, it still says: low end - no.

Replace with empty stabs, see what it gives you.