News for hackers. Stuff that matters.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by ivraatiems on Tuesday February 22, 2022 @04:01PM (#30433724)
Thank goodness. Bethesda's launcher was uniquely awful in a number of unpleasant ways. Slow, prone to crashes, bad user communication, not suitable for use on small monitors. The worst of the launcher apps I have used - and there are so many!

I remember when it was in vogue for every game maker to build their own launcher or even full Steam clone - when EA pulled all its new games from Steam to get people to use Origin, when Ubisoft forced uPlay on you no matter how you bought the game, and so on. Now, it seems like we're pulling back from that situation somewhat - a lot of EA games are back on Steam, for example.

I wonder whether the experiment didn't work, or if it worked, but now the goals have changed again?

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by LudwigNagasena on Tuesday February 22, 2022 @06:01PM (#30435106)
It's kind of weird how the same companies that can squeeze all possible computational abilities and use every tick that exists to force a computer to show amazing graphics with complex logic behind can't make a simple GUI.

Well, even Steam nowadays is kind of a wrapper for a browser.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by martinald on Tuesday February 22, 2022 @06:26PM (#30435328)
Is that really surprising? Even a simple GUI is not that simple these days.

This was reinforced recently when an incredibly good software engineer I knew recently got stuck with a problem. It ended up being a networking problem but his understanding of anything deeper than basic DNS settings was approximately zero. I was actually amazed given I assumed from his other knowledge that he would have a similar understanding of deep network concepts.

I think this happens just as much in companies. Yes, they may have 100s of insanely good graphic programmers who can do crazy low level stuff with shaders on GPUs, but do you know how to build a set of scalable and extendable web services to power a GUI app, with localisation, payment methods, 2FA, etc. I have seen some absolutely insane APIs written by game devs before, basically reinventing the wheel to pull a news feed in.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by mywittyname on Tuesday February 22, 2022 @07:03PM (#30435673)
Let's not discount the other possibility: they outsource development to the cheapest bidder.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Haegin on Wednesday February 23, 2022 @10:59AM (#30442460)
Another example of this is Dan Abramov's post from 2018 about things he doesn't know - https://overreacted.io/things-i-dont-know-as-of-2018/

As a very well known figure in the React community, the creator of Redux and currently working for Facebook on the React core team, he says people often think he's an expert in everything.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by vgb2k18 on Wednesday February 23, 2022 @01:28AM (#30438310)
>Is that really surprising?

>I was actually amazed...

You countered your own argument there.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by maven29 on Wednesday February 23, 2022 @03:26AM (#30438946)
Nothing wrong with changing your mind in light of new evidence. While you might be aware of the effect, you can still easily underestimate its impact.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by egypturnash on Tuesday February 22, 2022 @09:10PM (#30436745)
It never fails to amuse me when I am playing some sprawling open world tasklist from Ubisoft and something happens that diverts me into the weird world of achievements kept on Uplay. All this highly-optimized 3D work and lovingly-polished 2D menus is suddenly covered up by a collection of React placeholder items doing their "loading data of unknown size" pulse animation at an erratic 3-10fps.

I imagine that it is implemented and maintained entirely by people who are biding their time waiting for an opening on a team where they get to do something they give half a damn about, because it is pretty clear that nobody has put any love into this stuff.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by KiranRao0 on Tuesday February 22, 2022 @06:37PM (#30435419)
Unverified Rumor, so a healthy grain of salt is required:

A friend at a large GPU maker was mentioning that a lot of "squeezing all possible compute abilities" for games are in the driver, rather than in the game itself. Which is why you'll often see significant performance improvements with driver updates after a game has launched.

It makes sense as it's in the GPU makers' best interest to have the maximum performance, or else they'll be crushed in benchmarks.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by AussieWog93 on Tuesday February 22, 2022 @06:57PM (#30435593)
My old boss worked on the PC port of Dead Space 3.

He actually did spend significant effort optimising his shaders to get good performance on PC, but an Nvidia driver update would silently replace some of his code with hardware-optimised shaders they'd written themselves (similar to how Windows 95 had a hard-coded fix for Sim City).

This was never advertised publicly, and the only reason he found out was because he debugged the executable and noticed his shaders were never actually being executed.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by philistine on Tuesday February 22, 2022 @08:47PM (#30436538)
Can you say more about the hardcoded fix for Sim City? This sounds fascinating.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by alxexperience on Tuesday February 22, 2022 @08:54PM (#30436609)
EDIT: Was rushing, but updated with the exact quote here so people don't need to go digging :)

I believe this is the story OP mentioned [1].

> Windows 95? No problem. Nice new 32 bit API, but it still ran old 16 bit software perfectly. Microsoft obsessed about this, spending a big chunk of change testing every old program they could find with Windows 95. Jon Ross, who wrote the original version of SimCity for Windows 3.x, told me that he accidentally left a bug in SimCity where he read memory that he had just freed. Yep. It worked fine on Windows 3.x, because the memory never went anywhere. Here’s the amazing part: On beta versions of Windows 95, SimCity wasn’t working in testing. Microsoft tracked down the bug and added specific code to Windows 95 that looks for SimCity. If it finds SimCity running, it runs the memory allocator in a special mode that doesn’t free memory right away. That’s the kind of obsession with backward compatibility that made people willing to upgrade to Windows 95.

[1] https://www.joelonsoftware.com/2000/05/24/strategy-letter-ii...

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by AussieWog93 on Tuesday February 22, 2022 @10:17PM (#30437171)
Yep, that's exactly what I was referencing in GP!
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by throwaway09223 on Tuesday February 22, 2022 @06:57PM (#30435600)
It is absolutely the case that drivers contain code to fix errors or optimize away mistakes made in top tier games. This is well-known and often can be demonstrated by renaming the game binary or making other changes. Sometimes this happens with the blessing of the game company, and sometimes it doesn't.

Or, sometimes GPU folks will send a team over to help the game studios fix performance issues during their development.

There are some studios who push the envelope and make beautifully optimized games. There are many, many more who ineptly cobble together components and make something that runs well-enough.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by selestify on Wednesday February 23, 2022 @05:07AM (#30439567)
So it might actually be a good business strategy to just focus on building a popular game, and outsource optimization to the graphics card companies for free?
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by bombcar on Tuesday February 22, 2022 @11:14PM (#30437520)
xx:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by ziml77 on Tuesday February 22, 2022 @09:40PM (#30436927)
The reason that you see drivers release with specific games mentioned is exactly because of this. And also why the driver installer packages are so large. What I can't say is how much of a difference the GPU manufacturers work makes on average. I would have to assume there's a reasonable bump otherwise it wouldn't be worth it.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by p1necone on Wednesday February 23, 2022 @02:47AM (#30438710)
You get an absolutely massive performance boost by using newer drivers on Halo Infinite. I don't know exactly why, but it never goes above about 36 fps on low settings on older (AMD, 6800xt) drivers, but hits smooth 80+ at 4k on high with the drivers that mention Halo Infinite in the patch notes.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by ziml77 on Wednesday February 23, 2022 @03:15PM (#30445813)
That’s wild. But if they have cases where gains can be that much then it’s very clear why it’s worth it to fix the the stuff that other companies wrote
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by p1necone on Wednesday February 23, 2022 @07:14PM (#30448609)
Yeah - I assume this particular case must be due to an actual bug in the games engine, rather than just poorly optimized shaders etc. I'm curious to know exactly what causes it though.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by dundarious on Tuesday February 22, 2022 @10:49PM (#30437356)
Modern CPUs are extremely capable superscalar processors. In order to properly feed them, you must design with SIMD in mind. Even then, you can almost never rely on compiler auto-vectorization, and you must use intrinsics yourself. This is necessary even for such simple things as automatically opening doors when you move near them. In other words, many many things that are never even done on the GPU.

Of course, after release, the biggest improvements come from outside the game dev team. The point is not to forget all the improvements very carefully and skillfully baked in before release, just because consumers don't see the delta.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by dspillett on Tuesday February 22, 2022 @07:23PM (#30435864)
* companies that can squeeze all possible computational abilities … to show amazing graphics with complex logic … can't make a simple GUI.

The wage slaves they've got working on the store and launcher front-ends are probably not the same highly talented designers and others that they have working 80 hours trying to panel-beat a game into a shape that they can get out of the door without too many major patches being needed in the days following release.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by LegitShady on Tuesday February 22, 2022 @10:43PM (#30437318)
>without too many major patches being needed in the days following release.

this is bathesda. There won't be many patches, but not because its bug free, but because its broken and will remain that way. The community will patch it, right?

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by maccolgan on Wednesday February 23, 2022 @02:21AM (#30438573)
Two words: Fallout 76
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by throwaway09223 on Tuesday February 22, 2022 @06:58PM (#30435608)
There are a couple of highly technical, highly capable game studios. Bethesda isn't one of them.

Most game studios produce poorly optimized junk and are barely managing to ship a working product.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by JohnJamesRambo on Tuesday February 22, 2022 @07:11PM (#30435744)
The question I ask is if Bethesda spent all the time on technical things would they make the amazing games they do? Give me a Bethesda game with bugs over any other smooth game with no heart any day.

Every company has an attention budget to spend from.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by LegitShady on Tuesday February 22, 2022 @10:48PM (#30437351)
hasn't bethesda been limping "the creation engine" which is really gamebryo along for the last 10 years? They are doing technical things, they're just doing them poorly.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by ralusek on Tuesday February 22, 2022 @08:48PM (#30436545)
Nobody wants them to spend energy on the technical side, we want them to use an existing engine like Unreal.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by remexre on Tuesday February 22, 2022 @10:48PM (#30437352)
The incredible moddability of their RPGs, at least, is in large part to the flexibility of their engine. How many other games have active modding communities 12 years after launch as large as New Vegas'?
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by throwaway09223 on Tuesday February 22, 2022 @07:16PM (#30435799)
Sure. There's nothing wrong with a non-technical focus.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by oAlbe on Tuesday February 22, 2022 @08:16PM (#30436310)
> There are a couple of highly technical, highly capable game studios.

Which ones are those?

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by derac on Tuesday February 22, 2022 @08:38PM (#30436466)
Naughty Dog is (big) one that comes to mind immediately. Check out their GDC talks. GDC in general is a good place to find in depth technical talks from devs.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by ceravis on Wednesday February 23, 2022 @11:42AM (#30442994)
FromSoftware (Dark Souls/Sekiro) Polyphony Digital (Gran Turismo) Santa Monica Studio (God of War) Kojima Productions (Death Stranding) Larian Studios (Divinity Original Sin) Playdead (Inside/Limbo)

Studios who choose/have the freedom to release a game "when it's ready", and/or have Sony/Microsoft backing.

One can hope Microsoft's acquisition of Bethesda will change their ways, but having set the release date of Starfield (11/11/22) so far ahead of time doesn't inspire confidence... hopefully they'll have the freedom to push this back if needed.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by iyasu on Tuesday February 22, 2022 @08:41PM (#30436490)
From the people I've talked to, Epic Games and Riot developers seem to have their shit together as far as being able to scale their backends to millions of players. Improbable too (although they're more of a game services studio), who are the creators of Thanos*

* https://www.improbable.io/blog/thanos-prometheus-at-scale)

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by netheril96 on Tuesday February 22, 2022 @09:24PM (#30436833)
> Riot developers

The League of Legends client (which launches the actual game) is awful too. I don’t understand how it continuously burn 20% of CPU when doing nothing.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Bayart on Wednesday February 23, 2022 @10:02AM (#30441742)
id Software is the one that comes to mind. Even with the Zenimax acquisition and Carmack's departure, they don't seem to have lost their engineering chops. Doom 4 and Doom Eternal are known to run incredibly well.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by seabrookmx on Wednesday February 23, 2022 @01:06AM (#30438184)
id

Epic

Valve

Guerilla Games

(IMO)

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by psyc on Wednesday February 23, 2022 @01:14AM (#30438233)
Bungie

Rockstar San Diego

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by greggman3 on Wednesday February 23, 2022 @01:33AM (#30438339)
GUIs are actually a ton of work. They look simple because it's a collection of simple parts, formatted text, buttons, sliders, text input, etc... but if you go through all the various screens and ubique interactions in something like a game hub/store/user/friends etc it ads up to a huge amount of work. Often more than graphics engines
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by rtpg on Tuesday February 22, 2022 @06:18PM (#30435251)
To be fair steam has always been a wrapper around a browser for its store content etc. Maybe the outer chrome has been pulled into that though…
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by chungy on Tuesday February 22, 2022 @06:21PM (#30435278)
In early Steam days, the store and community pages where handled by using mshtml.dll, with most of that ported to Chromium when they launched Linux and Mac OS versions.

I'm pretty sure the "new" Steam UI (the current one) is fully ported to basically be like an Electron app (I don't think it's literally Electron, but same concept).

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by modo_mario on Wednesday February 23, 2022 @05:15AM (#30439620)
They use CEF(Chromium Embedded Framework)
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by guywhocodes on Tuesday February 22, 2022 @06:52PM (#30435548)
Wow, my impression was the opposite. Slow and crashing: Just like every game they made. They have a uniquely high input lag and bugs is kind of their thing in general.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by bathtub365 on Tuesday February 22, 2022 @06:49PM (#30435528)
The people with the skills and desire to work on games are working on games. Even within the games themselves, the front end is often an afterthought.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by bastawhiz on Tuesday February 22, 2022 @10:23PM (#30437211)
One might say the same about the AWS management console.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by sbarre on Tuesday February 22, 2022 @04:21PM (#30433993)
With the rise of the Epic Game Store, I think there's more competition in the launcher/store space and I bet the big publishers got better deals which removed the need for them to invest in the ongoing development and maintenance of their own stores/launchers.

It can't be that cheap to maintain an app like Origin or UPlay and all the associated infrastructure, etc..

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by mjevans on Tuesday February 22, 2022 @05:49PM (#30434984)
Intangibles are a major cost factor as well. Not just the servers, but an entire authentication and customer support infrastructure.

Scammers are not an easy cost to estimate or an easy value to sell resistance against.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by judge2020 on Tuesday February 22, 2022 @10:52PM (#30437373)
The issue with Epic is the pure lack of features (user profiles, reviews[^1], community forums) , and no Mac/Linux support.

^1: I doubt reviews are ever coming since it would mean bad games would get fewer sales; Imagine how many more sales Cyberpunk 2077 has gotten on the Epic store as no potential buyer sees the negative reviews for the game.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by eulers_secret on Tuesday February 22, 2022 @11:38PM (#30437699)
The other issue is Epic's buying exclusivity for certain titles on PC - even after they were announced as available on other online stores. These bribes, especially since Epic wasn't involved during development, upset a lot of folks.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by account42 on Wednesday February 23, 2022 @06:46AM (#30440077)
Right, they did that even for some crowd funded games.

And for others it has meant that the Linux version was delayed until after the excusivity deal was over (e.g. Metro Exodus) or removed (Rocket League).

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by baud147258 on Wednesday February 23, 2022 @04:27AM (#30439302)
it's not (wasn't? I don't know if they still do it) as much as making games exclusives to Epic as making sure they aren't released on Steam; I'm pretty sure Epic's head honcho said something to that effect and a few games which had deals with Epic also released on the Microsoft store
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Talanes on Tuesday February 22, 2022 @11:08PM (#30437484)
I've had to struggle with Epic just to delete a game at times. And the giant tiles in the library are already a pain to navigate through with a library 1/20th the size of my Steam library. I could live without features if the core functionality was nailed in, but it's just not there.

The only people I know using it as a broad Steam replacement are doing so ideologically: they want a competitor to exist so they use it even if it's worse.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Mindwipe on Wednesday February 23, 2022 @04:42AM (#30439406)
The Epic launcher supports Macs.

There's not much software that supports Macs, but there's increasingly little on Steam too that runs on a modern version of MacOS too because of Apple's decision to abandon the space.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Macha on Tuesday February 22, 2022 @05:58PM (#30435079)
It's not just the store cut. From what I understand, a big part of the motivation of Origin was also to avoid having to compete, at least in consumer perception with the sales. Battlefield 3 at €80 while it was a year old looked terrible value when Borderlands 2 had dropped to €50 and was regularly 30% off despite being only a couple of months old.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Talanes on Tuesday February 22, 2022 @11:16PM (#30437533)
That seems backwards to how the actual customer perception worked out though. I very quickly noted that Origin prices were worse than Steam prices, and avoided it. If that was their intent, they forgot the storefront itself has a perceived value.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Narishma on Wednesday February 23, 2022 @05:41PM (#30447595)
Epic's launcher is one of the worst, constantly consuming resources doing who knows what in the background.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by brendoelfrendo on Tuesday February 22, 2022 @04:40PM (#30434260)
Microsoft owns Bethesda, and has transitioned to primarily offering its games via Steam or via the Xbox app. I imagine that Bethesda is doing this to align with Microsoft; existing library through Steam (with potential to add them to the Xbox app if they join get added to GamePass, maybe), future releases through Steam and Xbox.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by nimbius on Tuesday February 22, 2022 @05:55PM (#30435055)
Occhams razor: Microsoft owns Bethesda, so one would naturally assume they would seek to kill off competition to the windows store, or any poor performers that arent driving the appropriate revenue.

the worst part of the bethesda launcher was it existed as a cudgel for Todd Howard and others to effectively silence dissent during the launch of Fallout 76 in 2018 either by flogging it as an excuse to refuse refunds, or using the platform to outright threadlock and silence user complaints and criticism. the launcher directly contributed to the wholesale review bombing of virtually every bethesda title on Steam and even showed up in the class action lawsuits filed during the fallout 76...well...fallout.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by munk-a on Tuesday February 22, 2022 @06:00PM (#30435088)
I think, honestly, that Microsoft is feeling pretty happy with how things are working with steam right now - they've probably only got to do a very minimal amount of work to integrate with the platform while internally they have MS Game accounts that tie everything together for any of the tracking needs they have. I'm sure they'd love to convert all of the MS Games users to their own store but they've managed to extract a whole bunch of unexpected business from AoE2 and other titles and they're probably hoping to minimize any damage to the ecosystem.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by stubish on Tuesday February 22, 2022 @09:04PM (#30436684)
> Occhams razor: Microsoft owns Bethesda, so one would naturally assume they would seek to kill off competition to the windows store, or any poor performers that arent driving the appropriate revenue.

What I find interesting is that Microsoft and/or Bethesda chose to migrate users to Steam rather than the Microsoft Store or Gamepass. It would have been an opportunity to get more eyeballs looking at Gamepass subscriptions, but also would have been less popular. Or maybe all the legacy stuff being migrated is a burden they don't want?

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by ocdtrekkie on Tuesday February 22, 2022 @04:17PM (#30433936)
More than likely Valve has offered better deals to these larger companies to get them back in-house. It's very probable EA, Bethesda, Microsoft, etc. all have gotten more favorable terms now, by proving they were willing to leave Steam and roll their own launcher.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Ekaros on Tuesday February 22, 2022 @04:24PM (#30434045)
30% from 0 to 10 million

25% from 10 to 50 million

and 20% from 50 million on.

They might have even better deals, but at some point 20% for handling everything and supporting payments with potential of fraud, chargebacks etc. in nearly every country should start look like not horrible deal. Remembering what the retail margins were back in the day when they needed to make and ship physical boxes...

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by xxs on Tuesday February 22, 2022 @05:21PM (#30434714)
>at some point 20% ... start look like not horrible deal

Not, if you are Microsoft.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Godel_unicode on Tuesday February 22, 2022 @05:53PM (#30435040)
Pay 20% now, or be forced to spin out Xbox via anti-trust ruling in the future. Seems like a no-brainer to me.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by tayo42 on Tuesday February 22, 2022 @08:04PM (#30436204)
That's 10 million dollars, that pays for a team of 10 people for 4 years.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Ekaros on Wednesday February 23, 2022 @03:28AM (#30438959)
10 people in 4 years don't sound like a lot to setup and run support, distribution, payment integrations for let's say 100+ countries. Which many having unique payment providers.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by amatecha on Tuesday February 22, 2022 @11:14PM (#30437519)
source for these numbers?
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by Cthulhu_ on Wednesday February 23, 2022 @03:30AM (#30438979)
> I wonder whether the experiment didn't work, or if it worked, but now the goals have changed again?

I think Steam has a big first mover advantage, like a user's default browser or text editor, always on or starting up, while the others were an extra step that users only did when they had to. The recurring sales and frequently updated offerings of games and updates on Steam's home page is also a plus; Origin was static, Epic is minimalistic, Steam is more of a proper website with a load of different angles - sales, recommended games, new / early access games, updates, and jazzy graphics if they have a big sale on. The other launchers are purely functional.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by jeffwask on Wednesday February 23, 2022 @09:34AM (#30441375)
Epic Game Store was the nail in their coffin. They all wanted to have their own Steam and rake in all the revenue directly but didn't want to invest the time and effort to build a platform like Steam. Valve virtually stopped making games to focus only on Steam. I feel like watching EGS hit the market, the difficult road it is to build a true Steam competitor for them, and how long before it will actually be profitable was a reality check for everyone else. Like using AWS over Bare Metal, somethings are worth paying someone else to do for you.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by weaksauce on Tuesday February 22, 2022 @08:00PM (#30436181)
What's funny is the original CS:GO gui was built using flash.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by squeaky-clean on Tuesday February 22, 2022 @08:50PM (#30436567)
For anyone interested, they used Scaleform which is a middleware a lot of games would use to have flash-based UI. It's technically a discontinued product but even Hitman 3 last year used it.

As crappy as Flash is for security, it was such a good tool for interactive animations.

Here's a list of games that used Scaleform, though it often isn't used as the only UI system. Sometimes it's just main menus or world-space UI elements. Found in a quick Google so I can't guarantee it's totally accurate, but I know many on here are correct.

https://list.fandom.com/wiki/List_of_games_using_Scaleform

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by mmastrac on Tuesday February 22, 2022 @09:07PM (#30436711)
When I was doing work for Nickelodeon around the iPad 1 days, we just could not get around the fact that flash was an amazing tool for animation and anything else we used would have tradeoffs. Tech-wise, a poor product. As a tool for design-minded people? Unmatched.
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by seabrookmx on Wednesday February 23, 2022 @01:09AM (#30438205)
Flash "for animations" still exists. It was rebranded Adobe Animate (presumably just to avoid the negative branding).

It's still used heavily for vector animations to my knowledge.

Re:Sunsetting the Bethesda.net launcher and migrating to Steam by mmastrac on Wednesday February 23, 2022 @10:00AM (#30441707)
I didn't know this - thanks!
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by sam0x17 on Tuesday February 22, 2022 @06:22PM (#30435290)
It's mainly the economics of "If you don't ship on steam, you miss out on the steam market" imo
Re:Sunsetting the Bethesda.net launcher and migrating to Steam by BeefWellington on Tuesday February 22, 2022 @11:28PM (#30437622)
Yeah I for one am glad that these launchers are going by the wayside, especially the onerous DRM-"enforcing" launchers.