Quoting: Craggles086

Quoting: Shmerl

Quoting: ArtenMS probably knew about Mantle before it has been made public and by then, they could have work on DX12.

AMD didn't exactly keep it a secret. They wanted to make it a base for the common API from the early on. Everyone collaborated on it. MS and Apple pushed their NIHs instead knowing very well that it will slow down progress.

So Mantle was an AMD project. Nvidia was not exactly supporting it. So by siding with AMD you alienate half your gaming base.

Say what you want about DirectX 12,
but DirectX 12 and Vulcan are both
supported by AMD and Nvidia.

Granted Nvidia’s support for Vulcan was late to the party, but that seems to be changing now.

OR, by siding with Mantle they could have forced nVidia to be onboard.

View this comment - View article - View full comments

Quoting: BogomipsNeeding an anti cheat solution in itself is sad. But instead of relying on a third party solution game developers could build a cheat aware code from the start.

An example of what I mean is, in a FPS, why send the position of all the players to a client, when it could be sent only when in the FOV (visible by the client camera). Back in CS:S it was resource intensive server side because it was a third party addon.

But I fully understand that it is time consuming and out of the mind of studios (I have few friends in the industry and sometimes decisions from above are complete nonsense for the developers like reusing game engine from other games that are absolutely not built for the task).

AFAIK that is not done due to EAC but as to remove the need for heavy servers so that all communication is p2p, the downside then of course that every client have access to the position of every other client.

View this comment - View article - View full comments

Looks like RockStar is releasing remasters of GTA3 and Vice City: https://kotaku.com/the-gta-remastered-trilogy-appears-to-be-real-and-comi-1847474620 [External Link] , perhaps that explains why they where so trigger happy to shut down this project before.

View this comment - View article - View full comments

Quoting: lejimsterHas any of this Futex stuff ever made it upstream? It seems like every year there is some attempt, but it never makes its way into the Kernel.

Yeah zero of them have been accepted so far, this one is very small and nonintrusive though so I'm holding my thumbs.

View this comment - View article - View full comments

Quoting: dos

Quoting: EikeAFAIK the main Linux developer at Valve doesn't like Debian's package format.

If that's true, then I don't think it's worth discussing any other reasons. This one is the only one that matters :P

Would be interesting to know the details on that however since it doesn't make any sense.

View this comment - View article - View full comments

Quoting: scaine

Quoting: Liam Dawe

Quoting: scaineHowever, while that creates a folder with the same name as the release as usual, with Luxtorpeda, they've put the whole archive inside another folder, just called "luxtorpeda", so Steam doesn't see it (because it's a folder inside a folder).

Must be an archive manager specific thing, the KDE Ark didn't give it an extra folder. It's probably an option in your settings.

Doesn't do it for ProtonGE though, so I assume it's the way it's packaged.

Yeah, I've just tested "Extract Here" again, with ProtonGE and Luxtorpeda. They look like they're packaged the same, but they extract differently. Not sure how that works.

To protect your privacy, external media requires approval to load.

Source: i.imgur.com

View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

Easy to see if you use the tar command directly and ask it to list the contents:
 
f.ultra@Sineya:~/Hämtningar$ tar -Jtvf luxtorpeda-30.tar.xz 
drwxr-xr-x root/root         0 2021-08-07 22:43 luxtorpeda/
-rw-r--r-- root/root       233 2021-08-07 22:43 luxtorpeda/toolmanifest.vdf
-rw-r--r-- root/root       125 2021-08-07 22:43 luxtorpeda/config.json
-rw-r--r-- root/root      4406 2021-08-07 22:43 luxtorpeda/README.md
-rw-r--r-- root/root     15487 2021-08-07 22:43 luxtorpeda/LICENSE
-rwxr-xr-x root/root   6461024 2021-08-07 22:43 luxtorpeda/luxtorpeda
-rw-r--r-- root/root       228 2021-08-07 22:43 luxtorpeda/compatibilitytool.vdf
f.ultra@Sineya:~/Hämtningar$ 

edit: two theories here though, one is that your system handles .tar.gz and .tar.xz differently. Another is that whatever archiver you use looks at the top directory and if it doesn't match the filename it creates a dummy topdir, aka "luxtorpeda-30.tar.xz" have a topdir of "luxtorpeda" which does not match the name of "luxtorpeda-30" while "Proton-6.14-GE-2.tar.gz" have a topdir of "Proton-6.14-GE-2" that does match the name.

View this comment - View article - View full comments

Quoting: Alm888New API? I wonder, what will it be?
In my impression developers just need to target WIN32 API releasing for Windows and Valve will do the "magic". Well, that and Vulkan is preferable. At least Valve has said as much…

Well to be honest in order to fulfil "that will tell games if they're being run on the Steam Deck" that API could be just /etc/os-release :-)

View this comment - View article - View full comments

Linus Tech Tips have gotten a hands on with the deck: https://www.youtube.com/watch?v=SElZABp5M3U [External Link]

View this comment - View article - View full comments

Quoting: TheRiddickOh, EA. Was thinking this was retail release.. ok, still gotta wait.

Oh it can wait alright, right there in my library.

View this comment - View article - View full comments

Quoting: TheBardI'm really sad for the people at Feral. They did a wonderful job with all their ports. They made among the best native ports and their support is excellent. I only had to contact the support once. They managed to find that my keyboard was making the game crash. I don't even understand now how they were able to find it but they were right.

But the next step for Linux gaming is definitely Proton so I guess we will see lesser and lesser native ports. Maybe if the Steam Deck becomes a massive success and the next version Proton's compatibility isn't perfect, then native ports may become a thing again.

I'm quite sure that native ports or rather native versions from the ground up will be a thing again. We are now in the middleground where things like proton is good enough but the userbase is still too small, at some point IF our userbase raises then some publisher will move away from being dependent on a 3d party (proton) to be in better control of their own software as well as being able to push things to their technical limits.

The huge problem with native ports now is not really proton, it's the fact that our userbase is still so small. Proton just made it more apparent/transparent.

View this comment - View article - View full comments