Jump to content

NotHereToPlayGames

Member
  • Posts

    6,750
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. 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".
  2. My nVidia 635 reports I am Vulkan-capable. One moment... Performing additional tests...
  3. @Karla Sleutel -- The imgur image *DOES* show up for me. It's something on your computer that is blocking it.
  4. I'll run CPU-Z (?) tonight and verify.
  5. I took his reply to mean he was performing this IN XP. Regardless, he is talking about another matter, agreed.
  6. Good point. He posts later down that he KEEPS the vulkan files, that he only deletes D3DCompiler_47.dll.
  7. Even Thorium has crashed on REAL HARDWARE ALSO. Only in XP x64 and only first launch after reboot or hibernate. UNFORTUNATE for YOUR PROOF, that real harware has since been upgraded to Win10.
  8. Not to cloud the issue, but I have never confirmed that the .dll's are actually LOADED as a DEPENDENCY. Only that their PRESENCE is required in ALL Chrome/Chromium-based browsers EVER used on my home Dell XPS 8700 (7800?, have to look when I get home). I don't mind uploading a video because the folks that keep telling other people to delete "vulkan" files needs to realize that their "advice" may be BAD ADVICE. It certainly is for MY computer. But only for XP x64.
  9. I know that UCyborg also had this issue. Also both in Thorium and in 360Chrome. https://msfn.org/board/topic/186133-thorium/?do=findComment&comment=1265727
  10. I will post a 360Chrome video of this first launch crash. I do not keep Thorium and Supermium around, only test in VM to see if they are "ungoogled" or not. BUT THAT HAS TO PUT THIS D#MN RELENTLESSNESS TO BED! "Enough is enough."
  11. Maybe. Kind of not really worth my time. But maybe. Depends on how bored I get in the next day or two, lol. Granted, the video may be 360Chrome and not Thorium - will that still serve as your PROOF that your "advice" does NOT pertain to MY computer ???
  12. Technically, I shouldn't say that PEOPLE (it implies multiple) keep INSISTING that I do not need. There is only TWO PEOPLE and they are RELENTLESS in this pursuit. Downright RELENTLESS.
  13. Agreed! I'm honestly not finding much of anything. But I can report with 123,456,789.0% accuracy that the ONLY ONLY ONLY time that I get these FIRST LAUNCH CRASHES is when I take the advice of removing "vulkan" .dll's. That advice always comes from "users" and NEVER "developers". No offense. Again, I can only report WHAT I WITNESS. And sure, Thorium and Supermium and 360Chrome and Ungoogled are "usable" without these "vulkan" files. But I hibernate several times per day! And having to go into the OS's Task Manager to "kill" a process just to relaunch it after a CRASH is something I really have no interest in doing "for the sake of removing two .dll's that people keep insisting I do not need".
  14. I didn't see that it was locked. Thanks. I was googling for vulkan issues on XP x64 and that thread was in the top three results.
  15. nVidia web sites also confirm. They post a guide on configuring "power management support". Not sure if I will get around to testing, to be honest. My primary OS is now Win10. But I do have multiple XP machines, no partitions, just XP. But those computers are SSSLLLLLLOOOOOOOOOWWWWWW - when I retire, I'll have all the time in the world to sit and wait... and wait... and wait... LOL
  16. I can report that I'm finding several LINUX reports of the same (Chrome/Chromium crashes on first launch after reboot, additional launches work just fine). The LINUX crowd is suggesting --use-gl=desktop but I suspect this to be a Linux-Only Chrome/Chromium flag. Seems to date back to Chrome v85 and only with nVidia (my home computer is nVidia). Linux crowd reports v84 to be just fine. Another suggestion is to open Chrome's "task manager" and to END TASK for GPU Process. I have not tried that, when Thorium or Supermium or 360Chrome or Ungoogled, EACH AND EVERY ONE OF THEM, crashes, I just assumed that the browser's task manager was also crashed.
  17. Vulkan has been backported to XP and 2003 -- https://msfn.org/board/topic/176697-vulkan-backport/ Perhaps UPSTREAM has embedded these into the Chromium BASE? And anything forked from them (Thorium, Supermium, 360Chrome, Edge, Brave, Vivaldi, Opera, Ungoogled, cromite, Arc, Yandex, Kiwi, Iridium, Iron, Fulguris, Cent, you get the point) will all behave identically. I just wish that you had XP x64 so that you could WITNESS this phenomenon firsthand.
  18. Same here. Not in my VM, but on my real hardware (I would have to verify the 2019 version or not). Thorium works for me both with these and without these.
  19. They are required in XP x64. I will NEVER convince you otherwise. NOT my fight! I can only tell you what I have witnessed in Thorium and in 360Chrome and in Supermium and in Ungoogled. ALL OF THEM !!! XP x64 only. This is YOUR fight, not MINE. Please contact the DEVELOPER if you wish to dive deeper. Granted, my ONLY issue "when I take your advice" and remove these, the ONLY issue is FIRST LAUNCH after a reboot or coming out of hibernate. Without these, in XP x64, Thorium crashes on first launch after reboot, 360Chrome crashes on first launch after reboot, Supermium crashes on first launch after reboot, Ungoogled crashes on first launch after reboot. Again, please contact the DEVELOPER, they are there for a REASON and you ASSUME that just because Chrome-based works for YOU on YOUR system WITHOUT these, "then it must work for everyone". I can only tell you what I have witnessed. In Thorium. In 360Chrome. In Supermium. In Ungoogled. ON MY SYSTEM. In XP x64 only. Contact the developer. Ask him/her WHY these vulkan files are NEEDED for first launch after reboot or hibernate. I REALLY DON'T CARE. You are just trying to prove your "advice" correct. Your advice DOES NOT WORK in XP x64. First launch after reboot or hibernate. MY computer. Go out and buy a Dell XPS 8700, install XP x64. Or contact the developer. This "I get the last word" or "I'm always right" is kind of UNCALLED FOR.
  20. It's definitely older and definitely on-topic.
  21. Awesome! I'm hoping you find the root cause. I'm an engineer. My engineering mind says your issue has NOTHING to do with POSReady. If you lived within a 100-mile radius, I would personally volunteer to borrow your computer and install all of those POSReady updates ONE AT A TIME. Yes, I was under the impression that your radar was targeting POSReady as a "requirement" to run Thorium SSE2.
  22. That's why! These "vulkan" files (as far as I have WITNESSED) are only needed for XP x64. They're not needed for XP x86. They're not needed in Vista. They're not needed in Win7. They're not needed in Win10. I do not have any 8.1 machines to test whether they are needed or not. But it is a VERY SAFE assumption that they are NOT needed based on Vista/7/10.
  23. What OS are you running?
  24. No, sorry, you are reading too much into it. It was only after running it for SEVERAL hours that I was able to WITNESS the NEGATIVE side effects (YouTube would pause all audio/video for half a second or so once per hour or so). This is a great flag for sessions of one-hour or LESS. But I cannot advocate "for" it for users that keep something like YouTube open for HOURS upon HOURS.
  25. Listen, BOTH you and I are no "dummines" when it comes to computers. We BOTH know our way around computers! Firefox is a telemetry nightmare. Firefox forces the user to go through extreme firewall rules due to its "loopback" quote-unquote "feature". MOST users are CLUELESS when it comes to FIREWALL RULES SETUP (I do NOT include you in this subset of "users"). MOST users when faced with a "firewall poppup" upon launch of Firefox just click the STUPID dialog where the firewall asks "is this a WEB BROWSER" or the firewall just ASSUMES "yes, this is FIREFOX, so I'll just use default "web browser" rules. No offense to these "users", but this really is the STUPIDEST thing I have ever witnessed over the years - "just let Firefox make ANY connection it wants to, I'll accept the default firewall rules, I trust Firefox". THIS TRUST IS MISPLACED! Firefox really is the biggest telemetry nightmare I have ever come across! AND THAT INCLUDES A CHINESE/RUSSIAN REPACK OF 360CHROME !!! This "loopback" (1 byte several times each and every second) was referred to as a *BUG* in the days of Windows 2000, it's just "accepted" as 'normal behavior' by Firefox users today that DO NOT CARE (nor KNOW HOW to monitor these "loopback connections"). A CPU cycle is a CPU cycle. Make it perform a task and that means other tasks are delayed. I am NOT a Chrome/Chromium "fanboy". This world is full of "lesser of two EVILS". All OT regarding Thorium, of course. But let's be perfectly honest, if THORIUM (or 360Chrome!) made the HUNDREDS (literally!) of telemetry connections that FIREFOX does (esp FIRST LAUNCH), none of us would turn a blind eye !!! YET ALL FIREFOX USERS TURN A BLIND EYE REGARDING FIREFOX TELEMETRY CONNECTIONS !!! Firefox users "today" really are VERY different from those that used it in the 90s. Tout privacy and security but clueless that they have "sold their soul". "Do as I say, don't do as I do." But I digress...
×
×
  • Create New...