Quoting: PatolaThat's amazing. I already consulted their CAD files for the Steam Controller to create the piece they did not include, the trigger/bumper mechanism [External Link], the only bad thing is that it will take a long while for me to get my hands on an Index here in Brazil... :-(

I am curious though, how many of you guys have a 3D Printer so that this would be actually useful? Considering that in general us Linuxers are more "maker" than other groups. :)

We have one in my job but I doubt that they will allow me to use it (I probably should learn how to use it too :P).

View this comment - View article - View full comments

The question here would be on how much does PS4 Store, Xbox Store, Nintendo, etc. charges for publishing and ask if they consider them "outrageous" too.

Steam is probably the most featured-rich store application in the market, so it's quite obvious why it has most the PC market share. To say that the 30% is outrageous they should take in the equation how much would cost to them the marketing campaign in order to reach a similar market share without using their platform.

By the way, many mentioned the taxes but bare in mind that many times those taxes aren't in the price (out of the income tax, of course), so it's a number that is payed by the buyer and not by the seller. For example, in my country we have a VAT of 21% but it is the credit card of my country the entity that takes care of retain and pay the taxes (that in the end I pay as an extra fee in my credit card bill).

View this comment - View article - View full comments

Quoting: cprn

Quoting: kaimanHave you tried verifying the installation?

Yup. Didn't do anything.

Quoting: kaimanOtherwise, you could look at the DXVK logs in the game directory or enable proton logging [External Link] if those are inconclusive.

The thing is there are no new logs or files changed in the game directory after I try to start it from Steam client or command line. There's nothing. And I have the PROTON_LOG=1 %command% in the game's launch parameters but there's still no steam-379430.log in my $HOME... :(

Actually, I tried with 3.16-9 Beta and it works (didn't have to copy DLLs), game runs (freaking slow, like a half of the performance I used to have, but works) and the log is generated then, complaining about overlay lib not loading (but it still works). After switching back to 4.2-8 it stopped working again.

Edit: You know what? I think it's the prefix installation. When I switch Proton version it runs the installation scripts, installs VC Windows patches and DirectX. But for 4.2-8 it doesn't. How do I force run the installation scripts without removing/redownloading the whole game?

Try deleting the proton prefix for the game.

View this comment - View article - View full comments

Steam is having a hard time trying to explain how their new sale event works. From my point of view is simple: the tried to give more money to devs by moving the sales trading card market into the games purchase market. Still, they make it way over complicated with the boost, fuel, etc. If they would have just made a token based event (similar to the Lunar sale), everything would have been easier for everyone.

By the way (and just in case some valve brain is reading), next time they should give as price the chance to get a full (or partial) refund of one of the games you bought during the sale (of course, return the most expensive one, valve ;)). Also, they should keep giving events point by visiting the discovery queue (as they always did), that's what helps a lot the indies.

View this comment - View article - View full comments

Quoting: F.Ultra

Quoting: x_wing

Quoting: F.Ultra

Quoting: TobiSGD

Quoting: GuestI can see why they want to remove 32 bit libs because it's a ton of work.

But a ton of work for whom? They still get the majority of their packages directly from Debian, throwing a patch on one or the other package and just compile. If Debian still supports newer versions of 32 bit libraries, how much work is there really to be done for canonical?

They get the base source code of each package from Debian, then they have to build the IA-32 version themselves, and provide support themselves. Considering the amount of packages in the repo it will take quite some time to build the packages for IA-32 and that is time taken from building for other archs and so on. If there where no cost for providing IA-32 builds then they clearly wouldn't have planned to throw them out to begin with.

The only real cost is QA. Building is normally cheap.

Currently Ubuntu have 6391 packages in Main, building that will take hours even for Canonical.

Seriously, do you people really think that Canonical decided to drop IA-32 for some other reason and then have their devs lie that it had to do with resources? What is next, UFO conspiracies, 9/11 Truthers, Freemasons, anti-vaxxers and anti-GMO fools?

Never said such thing. But if you have the build pipeline for amd64, adding the i386 is trivial, not to mention that server processing time is quite cheap. Also, they already had the idea to keep supporting some essential 32 bit libraries as packages in the amd64 arch. So, the building scripts would still be there.

The discussion here is more about on what users need and not if "i386 is legacy and we should user resources in something else". When you have a lot of people that uses application that requires 32 bit libraries, you can't just drop support when you still doesn't have a working solution for that group.

View this comment - View article - View full comments

Quoting: F.Ultra

Quoting: TobiSGD

Quoting: GuestI can see why they want to remove 32 bit libs because it's a ton of work.

But a ton of work for whom? They still get the majority of their packages directly from Debian, throwing a patch on one or the other package and just compile. If Debian still supports newer versions of 32 bit libraries, how much work is there really to be done for canonical?

They get the base source code of each package from Debian, then they have to build the IA-32 version themselves, and provide support themselves. Considering the amount of packages in the repo it will take quite some time to build the packages for IA-32 and that is time taken from building for other archs and so on. If there where no cost for providing IA-32 builds then they clearly wouldn't have planned to throw them out to begin with.

The only real cost is QA. Building is normally cheap.

View this comment - View article - View full comments

I think that we all should keep away any bias or hate that may have with Canonical when giving an opinion.

They definitely had a stupid idea, but they're finally backtracking. Ubuntu is still by far the most popular Linux distro and the base of many distros created for common users that just want to "replace their Windows", so desire their destruction won't help at all to the Linux community.

Keep calm and keep gaming, folks.

View this comment - View article - View full comments

Quoting: ShmerlThey might be more expensive to develop, but it can be better than having nothing when upstream libraries simply decide to drop 32-bit support to begin with. They can do it at some point. Then what?

In the moment that any library drops 32-bit support (which is kinda debatable as x86 and AMD64 are a very related instruction set) you just freeze to the last version of the library that is supported. Basically, what Ubuntu says are going to do now but with the problem that they are doing this before any common library got into such "milestone".

View this comment - View article - View full comments

Quoting: Shmerl

Quoting: x_wingAnd will never be an option having the retro compability at hardware level. Also, creating such emulation layer stills requires to have the 32 bit libraries to run, so not a solution for the current problem.

32-bit libraries can be completely bypassed, by modifying 32-bit code on the fly in some way, into 64-bit one. Something like thunking idea: https://en.wikipedia.org/wiki/Thunk [External Link]

Not sure how well that would work, but hard to say until someone tries.

But what if you have a code that plays around with pointer size values? Is a call for disaster that. Also, you have to support all the code required to translate your 32 bit app to 64 bit just to avoid building the required deps in 32 bits. Having the support at hardware level and libraries that can be compiled for 32 bit is a no brainer decision.

In short, all the suggested workarounds are by far more expensive than simply compiling the base deps for x86.

View this comment - View article - View full comments

Quoting: Luke_NukemI just purged all *386 libs from my install, including Steam. Then installed Steam via flatpak...

No. Issues. At. All.

But this doesn't solve HumbleBumble or GOG. Though I do seem to recall and automated GOG->flatpak creator?

And what about proton games? Do they work without problems?

View this comment - View article - View full comments