Quoting: Guest

Quoting: psyminIf someone is mean to someone else in a realm that isn't related to linux, gaming or godot, that shouldn't have any impact on their ability to contribute.

Right, Hitler was very nice to his dogs after all...

This is a slippery slope... And not everyone might agree that Hitler should be barred from contributing code to Godot, let's not derail this thread ;)

View this comment - View article - View full comments

Quoting: TermyTechnical Exclusivity is kind of OK

OK as long as they don't shoehorn extra stuff in and then declare it's not portable without the extra stuff.
I wouldn't be against a lite version running on my computer. And technical exclusivity goes both ways, I'm pretty sure that there is stuff my PC can do that's not possible in the cloud.

View this comment - View article - View full comments

The art and theme reminds me a bit of genital jousting. It's a shame we didn't get that one. Couch co-op with friends :D

View this comment - View article - View full comments

Eeh? I thought you were talking about this wipeout [External Link]. I had never heard of that one, although I also get the appeal :)

For wipeout-the-antigrav-racing-game fans, Redout runs quite well under steamplay, and has a demo :)

View this comment - View article - View full comments

Quoting: SalvatosThis is in-home only, right? I couldn’t run a friend’s console while they’re at work?

Edit: From that twitter thread:

Quoting: Florian Märkl @thestr4ng3r

Quoting: wayne@puffpuff @matshayinyokaThanks for this, can we use it outside of home network with a static IP?

Yes, just run registration once, forward tcp 9295 and udp 9296 and 9297 and connect. Dyndns should work too. Theoretically you can also forward tcp 987 for wakeup, but I wouldn't recommend it because the way Sony did the authentication allows for a trivial replay attack.

I’m very curious to try this out if I can figure out what that means...

Let me break that down for you. You need to get your home (where the ps4 lives) IP adress. Just ask duckduckgo what is your IP address. If you don't have an IPv6 (that looks like 1234:5678:9abc::def), it is likely that your IP will change with time (around one day or one week). Curse your ISP, preferably on the phone, and use a "dynamic DNS" that is a fancy way of updating a domain name to always point to your current IP address (like a phonebook, but updated every 5 minutes). If your friend turns on his PS4 and gives you his IP before going to work, that would work as well :)

Now, port redirection. That has to be done on your router (or "box"), usually trough the web interface. That means connections incoming from the Internet to your home IP address will land on your selected computer (which is the ps4).

The port number typically identifies a service (typical ones are likely written in /etc/services on your computer). Here, we want to make only those that correspond to that remote play service land on your PS4 from the outside net (and deny the others). That's traditionally what a firewall is for: to say what services can be contacted on your home network from the outside. So, if you have an ipv6 (one public IP per machine), grab the one for your ps4, and allow the indicated ports.
You likely don't have IPv6. ISPs have invented (yeah, I know, not really) a wonderful "abomination" to escape the fact that they have less and less IP addresses to give away: "Network Address Translation". It actually works more or less the same: find in your router's web interface this "NAT" setting, then find your playstation, and allow the indicated ports on the outside to correspond to the same ports on the outside.

wakeup in that context is asking trough the network your ps4 to power itself on. The replay attack means that if someone sees you doing this, he can do it as well just by sending the exact same thing. I guess you could do it, and if it ever happens, disable it.

An alternative to all of this is to use a VPN to virtually bring you on the same network as the ps4. That's more or less what the well-known hamachi does.

Fr more info, do look up "NAT", "Network address translation", "Port forwarding", "dynamic DNS" (simple English wikipedia is also a thing!). Those work always the same way. Hope that helps.

View this comment - View article - View full comments

Quoting: scaine

Quoting: MayeulC

Quoting: scaine

Quoting: x_wing

Quoting: linuxcityI have the Mesa aco drivers should I stick with that or go with this one

If you want to use valve compiler for AMD GPU you should stick with your current drivers or use a bleeding-edge version of Mesa (aco was merged and will be shipping with Mesa 19.3).

From my point of view, your best option is to keep at system wide a stable version of Mesa and compile ACO drivers by yourself. That way you will have a stable system and you will also be able to use ACO on the games/app you prefer.

EDIT: worth mention that compiling may not be mandatory if you have an Ubuntu based distro. In that case you can unpack deb files of a Mesa-ACO ppa in specific directories in order to get the driver running (the same should be possible with arch based distros).

You lost me at "compile". I kept at it, but then there was something about unpack deb files. Jesus, it's 2019. This isn't 2012 Linux anymore. Either it'll work by adding a package/snap, or at worst, I have to add a PPA. Compiling? C'mon.

In all seriousness, I didn't understand pretty much any of your answer. And while I realise that ignorance is nothing to be proud of, if this is what we need to learn to play games on Linux, we've already lost this fight, I think. No idea what "KDE Neon" architecture is, but it sounds like Gentoo, Slackware, or Arch - totally hardcore. Not my scene (obviously).

Oh, please. If you want the latest, bleeding-edge, experimental stuff (like ACO), then you are obviously going to dirty your hands. The ecosystem around them isn't mature, the projects cannot necessarily be considered "stable", and are not included by default in most "simple" environments :)

I mean, this is like trying to perform some extremem overclocking, and complaining that you have to learn stuff on CPU and memory architecture. Or buying a custom set of "performance" parts for your car, and complaining about having to bolt them on yourself.

It isn't that hard to do or learn, but are you sure that's reeally what you want, if you are not prepared to spend some time learning?

Personally, even though I could do it, and have done so occasionaly, I prefer to stay with the defaults, and spend my energy elsewhere ;)

Yep, x_wing already answered to this effect. The fact that this is all very experimental/cutting-edge was lost on me when I typed my comment. Like you, I prefer to just "play games" these days. My interest in that level of tinkering pretty much dried up when Steam launched on Linux and the whole experience became that much more mainstream.

My apologies, I didn't mean to lecture you on this. I was still asleep when I wrote this, and it wasn't clear to me that x_wing had already pointed out this was an experimental project :P

Hopefully, this work will end up profiting every mesa driver. I can see some shader being initially compiled with ACO, then being asynchronously replaced by a more performance-optimized version a bit later, if needs be :)

But yeah, these days, I try not to bother with all of this; that's why I bought a Ryzen "X" series: the promises of automatic overclocking won me over :D

Quoting: ZeloxCool, better performace is always better ^^. Only thing i never got or understood, some here seems to still want to stick with an older mesa. Any reason for this? And how do one still stick with an older version?
I use manjaro so I mostly dont bother, the community tests everything before it goes on the stabel version of manjaro. And I havent got any hickups before, still the more you know :).

Well, I guess they are using their distro packages. And it's often distro policy (Debian, Slackware) to follow "if it ain't broken, don't fix it": no major upgrades between distribution releases, because you risk breaking stuff that's already working. That's stability at all cost, which is great for some uses. Your stuff won't necessarily work better with updates, but at least it won't be worse.

View this comment - View article - View full comments

Quoting: scaine

Quoting: x_wing

Quoting: linuxcityI have the Mesa aco drivers should I stick with that or go with this one

If you want to use valve compiler for AMD GPU you should stick with your current drivers or use a bleeding-edge version of Mesa (aco was merged and will be shipping with Mesa 19.3).

From my point of view, your best option is to keep at system wide a stable version of Mesa and compile ACO drivers by yourself. That way you will have a stable system and you will also be able to use ACO on the games/app you prefer.

EDIT: worth mention that compiling may not be mandatory if you have an Ubuntu based distro. In that case you can unpack deb files of a Mesa-ACO ppa in specific directories in order to get the driver running (the same should be possible with arch based distros).

You lost me at "compile". I kept at it, but then there was something about unpack deb files. Jesus, it's 2019. This isn't 2012 Linux anymore. Either it'll work by adding a package/snap, or at worst, I have to add a PPA. Compiling? C'mon.

In all seriousness, I didn't understand pretty much any of your answer. And while I realise that ignorance is nothing to be proud of, if this is what we need to learn to play games on Linux, we've already lost this fight, I think. No idea what "KDE Neon" architecture is, but it sounds like Gentoo, Slackware, or Arch - totally hardcore. Not my scene (obviously).

Oh, please. If you want the latest, bleeding-edge, experimental stuff (like ACO), then you are obviously going to dirty your hands. The ecosystem around them isn't mature, the projects cannot necessarily be considered "stable", and are not included by default in most "simple" environments :)

I mean, this is like trying to perform some extreme overclocking, and complaining that you have to learn stuff on CPU and memory architecture. Or buying a custom set of "performance" parts for your car, and complaining about having to bolt them on yourself.

It isn't that hard to do or learn, but are you sure that's really what you want, if you are not prepared to spend some time learning?

Personally, even though I could do it, and have done so occasionally, I prefer to stay with the defaults, and spend my energy elsewhere ;)

View this comment - View article - View full comments

I guess Valve could argue that as you buy games, you make a "bundle" that's not splittable.

I could see valve allowing to sell one's account after that ruling, though.

View this comment - View article - View full comments

I spent quite some time on it myself this week-end. It's quite lovely, and a worthy successor to tower of guns.

I mean, with all those double jumps and insane gun recoil, I have felt more like an attack helicopter than in many flight sim games :D

It had been on my wishlist for a while (since it was announced). Finding it in the monthly was a pleasant surprise. And I can confirm that it runs very nicely, especially after shaders have been compiled during the first mission or so.

View this comment - View article - View full comments

Can't we just have nice things? Why does it always have to be political, and not based only on technical merit?

On the other hand, the FSF is a political institution as well... :S:

View this comment - View article - View full comments