Failed To Load Original Steam Client Error Code 126
Kristin Klodzinski
If you are developing, then you need "Enable JavaScript source maps" and "Enable CSS source maps" checked to be able see your source code in Chrome Developer Tools. Unchecking those takes away your ability to debug your source code. It is like turning off the fire alarm instead of putting out the fire. You do not want to do that.
For me, the problem was caused not by the application in development itself, but by the Chrome extension React Developer Tool. I solved it partially by right-clicking the extension icon in the toolbar, clicking "Manage extension" and then enabling "Allow access to files URLs." But this measure fixed just some of the alerts.
Right: it has nothing to do with your code. I've found two valid solutions to this warning (not just disabling it). To better understand what a source map is, I suggest you check out this answer, where it explains how it's something that helps you debug:
The .map files are for JavaScript and CSS (and now TypeScript too) files that have been minified. They are called SourceMaps. When you minify a file, like the angular.js file, it takes thousands of lines of pretty code and turns it into only a few lines of ugly code. Hopefully, when you are shipping your code to production, you are using the minified code instead of the full, unminified version. When your app is in production, and has an error, the sourcemap will help take your ugly file, and will allow you to see the original version of the code. If you didn't have the sourcemap, then any error would seem cryptic at best.
First solution: apparently, Mr Heelis was the closest one: you should add the .map file and there are some tools that help you with this problem (Grunt, Gulp and Google closure for example, quoting the answer). Otherwise you can download the .map file from official sites like Bootstrap, jQuery, font-awesome, preload and so on... (maybe installing things like popper or swiper by the npm command in a random folder and copying just the .map file in your JavaScript/CSS destination folder)
Second solution (the one I used): add the source files using a CDN (content delivery network). (Here are all the advantages of using a CDN). Using content delivery network (CDN) you can simply add the CDN link, instead of the path to your folder. You can find CNDs on official websites (Bootstrap, jquery, popper, etc.) or you can easily search on some websites like Cloudflare, cdnjs, etc.
I appreciate this is part of your extensions, but I see this message in all sorts of places these days, and I hate it: how I fixed it (this fix seems to massively speed up the browser too) was by adding a dead file
Since Selenium IDE was already set to be able to read site data on all sites, I uninstalled it. (I read in another comment here that you might try enabling more permissions for an extension instead of removing it.) In my case, removing Selenium IDE (Chrome extension) got rid of the warnings.
I had the same problem. I tried to disable the extensions one by one to check it, and finally realized I had Adblock enabled, which was causing this issue. To remove that error I followed the step below,
This browser error means it has some compiled version of your JavaScript in a sourcemap intermediate file it or some 3rd party created that is now needed when debugging that same script in "devtools" in your web browser.
This can happen if your script fails (or in your case trying to get an image source hidden in the sourcemap code that created the script) but whose script error is tied to some JavaScript that got created from an original sourcemap file that now cannot be found to debug that same error. So it's an error about an error, a missing debugging file creating a new error. (crazy, huh?)
This error is likely coming from an extension in the web browser and is reporting it has generated a script error it has recorded in the console.log window of devtools (press F12 in the browser). The error is likely from the extension (not your code) saying it has some code that contains an address to a sourcemap file it cannot access, has a bad URI/URL address, is blocked, or that is missing.
A sourcemap, by the way, is a file that translates or transpiles code from one language to another language. Often this is a file that the browser uses to translate this source code into a child script like JavaScript/ECMAScript, or when it needs to do the opposite and recreate the source file from the child script. In most cases this file is not needed at all as a 3rd party software program has already compiled or transpiled the source code into the child script for the browser. For example, developers who like TypeScript use it to create JavaScript. This source code gets transpiled into JavaScript so the browser script engine can run it. The URI/URL to this sourcemap file is usually at the top of the javaScript or application compiled code file in a format like //#....
When this intermediary transpile file is missing or blocked for security reasons in a web browser, the application will usually not care unless it needs the source file for debugging the child script using this source file. In that case it will complain when it feels it needs this file and cannot find it, as it uses it to recreate the source file for the code running in the browser when debugging the script in order to allow a developer to debug the original source code. When it cannot find it, it means that any developer trying to debug it will not be able to do so, and is stuck with the compiled code only. So it is safe to turn off these errors in the various ways mentioned in this post. It should not affect your own scripts if it is connected to an extension. Even if it is related to your own scripts, it is still unlikely you need it unless you plan to run debugging from devtools.
TL;DR : Source maps aim to improve the web debugging experience. Although it is particularly useful when debugging JavaScript frameworks, if you want to disable it you can do it as follows.
However, as we are building more complex web applications nowadays,your development workflow may involve using various tools. These toolsrequire a build process to transpile your code into standard HTML,JavaScript, and CSS that browsers can understand. Additionally, tooptimize performance, it's common practice to compress (for example tominify and mangle JavaScript) and combine these files, reducing theirsize and making them more efficient for the web.
Source maps are files with names ending with .map (for example, >example.min.js.map and styles.css.map). They can be generated by most build >tools, for example, Vite, webpack, Rollup, Parcel, esbuild, and more.
Sadly, that doesn't help because it seems they did NOT UPDATE the ShooterGameServer.exe version. It is still running the 336.24 version. The updated client won't see the old server in the server list.
This is starting to piss me off. I do not have any Epic players. STOP PUTTING EPIC CRAP ON MY SYSTEM. Nobody plays the Epic version! Let me have a stable, Steam-only version! I do not give a damn if some Epic fan can play or not. If they want to play they can approach me and I can worry about it then. Every time my server has crashed int he past year or two has been after an update because we are so damned worried about some Epic players who almost don't exist. I can't use UDP straight from the Unreal Engine any more. That increased latency for many players. Then we had to have this Vivox pile of garbage for players we never see. Now that Vivox garbage is crashing my server!
Make a Steam-only version for the 90% of us on Steam, and make a second release for those who actually want or need cross-play. Crap like this makes me HATE Epic. EGS is horrible. Still better that uPlay though...
Mine *IS* a standalone version. You use SteamCMD to setup a dedicated server. I have never seen one on Steam itself. I set it up with SteamCMD back in 2015 and aside from a few patches which break things like this, it's been rock solid. My complaint is that I don't know a single soul who uses the Epic version but my privately-owned servers (I own the hardware, the fiber feeding them, the OS, and all) now cannot do raw UDP which GREATLY reduces ping because Epic players cannot do that, I have to laod this Vivox crap despite voice-comms working on Steam for YEARS without out, plus we use TS3 in my clan, and now, for the third time, stuff for the Epic players is keeping my entire cluster and players offline. None of us use EGS, so we're being punished. It's hard to walk away from 24,000hrs, but it is getting easier each time an Epic pile of garbage keeps me offline in the VERY LIMITED time I have to play these days.
I just found the options to enable Epic stuff on a Steam server like mine. I have NONE of these specified on the command-line, so why is Vivox crashing my Steam-only server? I don't care if some random Epic player can join! We are password-protected for members and friends only!
Last time they released a wrong file version for the server executable, it took them at least more than a month to fix it. After 3 bad releases in a row, I just put the game aside and played something else for a few months... but they made some other fixes in a few days. So you never know...
I was wondering "do you have to do something different to get the 678.10 version like before today's crap update"? I answered this for myself by just following the instructions Kel provided and it worked on Windows.
Incorrect. The problem is with Vivox directly. I have been in contact with many other admins today and combined we have close to 100 servers down due to them crashing the instant they attempt to start with a dump about Vivox not loading. The version problem was wanna-be admins not installing correctly from day one. The day one instructions were and have been for dedicated servers for decades, use SteamCMD. As noted above, I have ten servers and they were installed via SteamCMD. They have the correct version and never had the issue updating because it was done by the book from day one. Heck the first post here clearly states an issue with Vivox in the very first line! Vivox was added FOR EPIC PLAYERS because EGS has nothing but a storefront.
4a15465005