Thorium

[NotHereToPlayGames]

I took his reply to mean he was performing this IN XP.  Regardless, he is talking about another matter, agreed.

[NotHereToPlayGames]

6 minutes ago, Saxon said:

are Vulkan capable, unlike yours,

I'll run CPU-Z (?) tonight and verify.

[AstroSkipper]

The Vulkan feature is not an issue for me as my graphics card does not support this. It is simply disabled in Thorium.

Edited August 14, 2024 by AstroSkipper

[AstroSkipper]

2 hours ago, NotHereToPlayGames said:

I'll run CPU-Z (?) tonight and verify.

You should better use GPU-Z to see all features of your graphics card.

[NotHereToPlayGames]

My nVidia 635 reports I am Vulkan-capable.

 

One moment...  Performing additional tests...

Edited August 14, 2024 by NotHereToPlayGames

[UCyborg]

vulkan-1.dll is still used to load software-backed Vulkan implementation for running WebGL content.

Inside the GPU process:

Getting rid of vulkan-1.dll will produce errors and break WebGL.

Screenshots are from Supermium, but I doubt Thorium is any different in that regard. So Vulkan components that come with these browsers are functional on XP, but that doesn't change anything regarding the ability to use GPU for it since no XP drivers provide the working implementation AFAIK.

Deleting DLL doesn't break the browser here, but generally such interventions appear pointless to me. Why look for even more trouble? Experience of running these browsers on archaic operating systems already seems a lot like experience of living a life with mutilated genitals as it is.

[NotHereToPlayGames]

55 minutes ago, UCyborg said:

vulkan-1.dll is still used to load software-backed Vulkan implementation for running WebGL content.

Inside the GPU process:

Getting rid of vulkan-1.dll will produce errors and break WebGL.

Screenshots are from Supermium, but I doubt Thorium is any different in that regard. So Vulkan components that come with these browsers are functional on XP, but that doesn't change anything regarding the ability to use GPU for it since no XP drivers provide the working implementation AFAIK.

Deleting DLL doesn't break the browser here, but generally such interventions appear pointless to me. Why look for even more trouble? Experience of running these browsers on archaic operating systems already seems a lot like experience of living a life with mutilated genitals as it is.

Eureka!  THAT explains it all.  The *two* (and only two) members that shout from rooftops to delete vulkan files also do not enable WebGL.

I didn't used to enable WebGL, not even for my uploaded releases here at MSFN.

But I do enable WebGL nowadays.  Partly because each and every "bug report" for my uploaded releases were dang near ALWAYS tied to the end-user needing WebGL.  Partly because the "security risk" associated with WebGL is "much ado about nothing".

[Dixel]

15 hours ago, NotHereToPlayGames said:

I took his reply to mean he was performing this IN XP.  Regardless, he is talking about another matter, agreed.

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

[Dixel]

12 hours ago, NotHereToPlayGames said:

My nVidia 635 reports I am Vulkan-capable.

 

One moment...  Performing additional tests...

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

Edited August 14, 2024 by Dixel

[Dixel]

11 hours ago, NotHereToPlayGames said:

Eureka!  THAT explains it all.  The *two* (and only two) members that shout from rooftops to delete vulkan files also do not enable WebGL.

I didn't used to enable WebGL, not even for my uploaded releases here at MSFN.

But I do enable WebGL nowadays.  Partly because each and every "bug report" for my uploaded releases were dang near ALWAYS tied to the end-user needing WebGL.  Partly because the "security risk" associated with WebGL is "much ado about nothing".

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.

 

12 hours ago, UCyborg said:

Deleting DLL doesn't break the browser here, but generally such interventions appear pointless to me. Why look for even more trouble? Experience of running these browsers on archaic operating systems already seems a lot like experience of living a life with mutilated genitals as it is.

 

[NotHereToPlayGames]

Deleting the dll's ONLY ONLY ONLY breaks the FIRST LAUNCH after a REBOOT/HIBERNATE.

I'm DONE!  You are correct.  It only affects me.  There's actually very FEW XP x64 users, most here are all x86.

Unless, of course, @UCyborg is willing to verify FIRST LAUNCH after a REBOOT/HIBERNATE (assuming UCyborg is running XP x64 and an nVidia GPU).  That is (and has been ALL ALONG) my only only ONLY issue when I delete the vulkan dll's.

Edited August 14, 2024 by NotHereToPlayGames

[mina7601]

2 hours ago, UCyborg said:

vulkan-1.dll is still used to load software-backed Vulkan implementation for running WebGL content.

Inside the GPU process:

Getting rid of vulkan-1.dll will produce errors and break WebGL.

Screenshots are from Supermium, but I doubt Thorium is any different in that regard. So Vulkan components that come with these browsers are functional on XP, but that doesn't change anything regarding the ability to use GPU for it since no XP drivers provide the working implementation AFAIK.

Deleting DLL doesn't break the browser here, but generally such interventions appear pointless to me. Why look for even more trouble? Experience of running these browsers on archaic operating systems already seems a lot like experience of living a life with mutilated genitals as it is.

UCyborg, my man, you are back! How are you doing? Haven't seen you in a while.

[UCyborg]

I always forget (read my mind doesn't register it properly as it's not that picky on some details) it's first launch after hibernating that @NotHereToPlayGames is emphasizing. I can try with rebooting. Besides that, I only have standby working, but not hibernation; space constraints of my XP x64 partition. Though in any case, I still think it's preferable to not intentionally cause error conditions.

Edit: OK, no first launch crash.

Just now, mina7601 said:

UCyborg, my man, you are back! How are you doing? Haven't seen you in a while.

Went through a bad wave of depression. It hit me that another decade is behind me and I don't know what to think of the future. The past still haunts me.

Edited August 14, 2024 by UCyborg

[AstroSkipper]

3 hours ago, UCyborg said:

vulkan-1.dll is still used to load software-backed Vulkan implementation for running WebGL content.

Inside the GPU process:

Getting rid of vulkan-1.dll will produce errors and break WebGL.

Screenshots are from Supermium, but I doubt Thorium is any different in that regard. So Vulkan components that come with these browsers are functional on XP, but that doesn't change anything regarding the ability to use GPU for it since no XP drivers provide the working implementation AFAIK.

Deleting DLL doesn't break the browser here, but generally such interventions appear pointless to me. Why look for even more trouble? Experience of running these browsers on archaic operating systems already seems a lot like experience of living a life with mutilated genitals as it is.

I checked my Thorium processes regarding loaded modules, and on my Windows XP Pro SP3 32-bit, the vulkan-1.dll is not loaded. 

[mina7601]

58 minutes ago, UCyborg said:

Went through a bad wave of depression. It hit me that another decade is behind me and I don't know what to think of the future. The past still haunts me.

Oh, that hurts badly. ☹️ Hope you recover from this.