Jump to content

NotHereToPlayGames

Member
 View Profile  See their activity

  • Posts

    7,015

  • Joined

  • Last visited

  • Days Won

    89

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by NotHereToPlayGames

  1. NotHereToPlayGames
    Ah, thanks. Forgot about this. I'm assuming Win10?
  2. NotHereToPlayGames
    lol Though not sure I'd really brag about three tiny months. Firefox v94 was released on November 2, 2021. Chrome v98 was released on February 1, 2022. I suppose if we want to play that game, shouldn't we dig deep into any other have/have-nots between the two versions? And shouldn't we then call this a "Mozillaism" since everything else is always called a "Googleism"?
  3. NotHereToPlayGames
    A reminder-link for those that may be interested -- https://msfn.org/board/topic/183484-polyfill-whats-all-this-then/?do=findComment&comment=1216125 Thanks again, @UCyborg
  4. NotHereToPlayGames
    Would you happen to have a breakdown of what polyfills are resolved via your palefill that are newer than Chrome v86?
  5. NotHereToPlayGames
    It has also been reported on some forums that ECC certs in XP have been FALSIFIED as "secure" by some XP web browsers.
  6. NotHereToPlayGames
    If you are talking about these, I would advise against checkmarking these two options. You essentially INTRODUCE a man-in-the-middle to "check" if you have a man-in-the-middle.
  7. NotHereToPlayGames
    In my opinion, one should NEVER "manually update" certificates. While other MSFN Members would equally swear the exact opposite as their opinion. I've NEVER updated my "certificates" and I have no problem whatsoever with the web site in question. Chrome/Chromium uses XP's "certificate store". I let XP manage that "certificate store". "Opinions are like butts. Everybody has one, not everybody wants to hear them."
  8. NotHereToPlayGames
    That could be your problem. I have never in my entire life "updated" system certificates. How they update "behind the scenes" is unknown, but I have never in my entire life "manually updated" system certificates.
  9. NotHereToPlayGames
    Also, unless I'm mistaken, you run XP x86 SP2. XP x86 SP2 was released in August 2004!
  10. NotHereToPlayGames
    Did you try in an INCOGNITO WINDOW? And without setting any extensions to be allowed during Incognito Mode.
  11. NotHereToPlayGames
    Yes. Chrome/Chromium support for CSS 3D pre-dates v86 by over a DECADE. Chromium v86 was released 06/10/2020 (day/month/year, I sure as Hades wish there was a universally-accepted date format!).
  12. NotHereToPlayGames
  13. NotHereToPlayGames
    You have your files criss-crossed and you confuse the flow of this thread until that criss-cross is resolved on your end.
  14. NotHereToPlayGames
    As I suspected. You have WebGL enabled! So you seem to NOT be using the loader.ini CORRECTLY because you screencap'd that your loader.ini has WebGL "disabled".
  15. NotHereToPlayGames
    Open chrome://gpu and post this section as a screencap -
  16. NotHereToPlayGames
    Your geolocation is perhaps being served html5 instead of webgl. Open chrome://gpu and post this section as a screencap - (crap, can't paste an image... have to delete some profile pics...)
  17. NotHereToPlayGames
    https://greatescape.co/map?departDate=2023-04-05&returnDate=2023-04-19
  18. NotHereToPlayGames
    POSITIVE. The map requires WebGL. I am only running side-by-side because they are both inside their own VirtualBox VM. It is not advised to run several versions side-by-side within the same OS Environment.
  19. NotHereToPlayGames
    Working for me in v13.5 which is the same rendering engine as v13.
  20. NotHereToPlayGames
    Only if the WebGL or embedded Google Translate features are required. The other changes were minor cosmetic changes.
  21. NotHereToPlayGames
    Agreed. It has my city off by 181 miles.
  22. NotHereToPlayGames
    Working here.
  23. NotHereToPlayGames
    You would only need to copy these files over - en-us.pak (in the locales sub-folder) iframe.srx (in the skin sub-folder) en_skin.srx (in the skin sub-folder) chrome.dll (in the root folder - you will need to select from the translation enabled/disabled version for which translation option you prefer) resources.pak (in the root folder - you will need to select from the regular or ungoogled version for which option you prefer) options.zip (in the root folder) [not 100% if this one was changed since uploading rebuild-7] 360loader.ini (in main folder - you will need to select from the webgl enabled/disabled version for which option you prefer) [there are a few chrome://flags to change also but only if your GPU is blacklisted from WebGL or other WebGL issues] You will need to add these files - libegl.dll (root folder) libglesv2.dll (root folder) libegl.dll (swiftshader sub-folder) libglesv2.dll (swiftshader sub-folder)
  24. NotHereToPlayGames
    And the results are misleading. It "thinks" I am allowing three inline scripts but my Proxomitron replaces them with "dummy scripts" instead of outright "blocking them". This enables me to block "first-party" scripts based on content instead of blocking 'all' "first-party" scripts.
  25. NotHereToPlayGames
    Cool! With some tweaking to my Proxomitron config, I bet I could hit 100%
×
×
  • Create New...