Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
und danke das du es direkt bei Git gehostet hast, yay..
:thumbsUP:
Ich habe nochmal ein eigenständiges Github Repository[github.com] erstellt und im Guide, hier als auch in der Ankündigung nochmal ergänzt
Also installed the Ui and wanted to ask if it's possible to block/remove all youtube videos via the webkit.css, since it always annoyed me that you would connect to youtube+google plus getting cookies, when you click on a game changelog with a video in it.
The more problem is it's useless to hide them via webkit.css only, because the connections are still made. In addition the only way is to block Youtube or similar embed stuff in Steam with with firewall/hosts/pi e.g... Which means block the whole Google platform itself... systemwide.
And it's not only Youtube. One YT video includes Doubleclick, Youtube Stats, Google Adsense, ReCaptcha, several Cookies and so one which were sideloading >.<
Even if you don't press the play button. Pretty annoying story in Steam
Well, i can test what's possible for the UI but i don't promise anything.
Unfortunately, CSS only addresses the classes of the respective of the appearance. The elements themselves are controlled via Javascript/Ajax.
Because most of it happens on the server side and are also prevented by Valve itself, I don't see much chance of this happening. But i guess there are people who know more.
english:
The files Unity.MemoryProfiler.dll, UnityEngine.CrashReportingModule.dll, UnityEngine.PerformanceReportingModule.dll, UnityEngine.UnityConnectModule.dll and UnityEngine.UnityTestProtocolModule.dll have been deactivated from the list of deleted files, because it differs depending on the product whether after removing the files the game itself still works or not. If anyone want, test this out yourself.
The help files have also been rewritten.
german:
Die Dateien Unity.MemoryProfiler.dll, UnityEngine.CrashReportingModule.dll, UnityEngine.PerformanceReportingModule.dll, UnityEngine.UnityConnectModule.dll und UnityEngine.UnityTestProtocolModule.dll wurden aus der Liste der zu löschenden Dateien deaktiviert, da es je nach Produkt unterschiedlich ist ob nach dem Entfernen der Dateien das Spiel selbst noch funktioniert oder nicht. Wer will, kann dies weiterhin selbst austesten.
Zudem wurden die Hilfedateien überarbeitet.
Just re/move/rename the steam.cfg, update the Steam-Client and run the batch again with option 1 (Clean Crashhandler....), the cfg will be written again and newly written Crashlytics will be deleted again.
The batch file itself stay untouched.
---
Attention, don't forget. If other customizations have been made for own skins that are OUTSIDE the skins folder, these will of course also be reset when launching Steam. Own client modifications that fall under this point should also be saved beforehand. However, this is not the task of my script.
So far i know, it's a housemade problem from Valve/Steam itself since beginning of the new library and has nothing to do with the batch/cfg.
As example i had this problem with black pages/library long before i created the file. The entries are just there to block the forced automatic updates. For nothing more.
The commands still exist since 2011 and longer. There would be a third command as well to force an offline mode "ForceOfflineMode=enable" but this was of course omitted.
From 2019 with possible fix
https://steamcommunity.com/discussions/forum/1/1640927348821473977/
Reddit
https://www.reddit.com/r/Steam/comments/denha8/steam_library_sometimes_shows_only_black_screen/
There are countless other entries on the net about the problem
If you have cleaned the html cache you have to update the whole client again without cfg file.
Tips:
- The Client should be up to date
- Disable hardware acceleration
- Verify and repair corrupted files (the deleted crashlytics from batch command do not matter)
- Use alternate launch parameter (-no-browser steam://open/minigameslist)
What I found, is that the only way the client will launch to anything other than an empty black screen while BootStrapperInhibitAll is enabled, is using steam://open/minigameslist regardless of any of the other variables. And it all breaks down the instant the client reverts to normal view (e.g. clicking anything from the View menu). This means you are unable to access any part of the client other than Library (in mini format).