Quoting: Liam Dawe

Quoting: toorBut i don't think they can "simply" release it open source and let anybody change it and allow it for anti cheat without some kind of verification

Why not? That would just be security by obscurity and would show that the anti-cheat systems aren't very good if a few changes to Wine/Proton would suddenly enable cheating. I doubt there will be any closed part on the side of Proton for this.

I don't mean that being proprietary would fix the problem. I just mentioned that they didn't confirm it would be open source.

Proton/wine is translation windows system calls to Linux ones, and dxvk directx calls to vulkan, right? Then what guarantees that you don't change those calls to do something that allows you to cheat? Like, add transparency to whatever, I dunno.

Anti cheat systems are always catching up with hackers, and having that layer of abstraction to system calls seems to make it more complicated than it already is.

But that's from my naive understanding, I haven't worked on that of course. Just expressing my opinion.

View this comment - View article - View full comments

Quoting: fagnerlnI was expecting some proprietary workaround to make the AC work, good to know.

They say that every system that use proton will have those changes, not that it will be open source. I mean, they could add proprietary code to proton too.

If they don't, then what guarantees that the code handling the anti cheat isn't modified?
They could disallow anti cheat for non official proton, sign the proton versions or they could allow proton forks to be signed too after verification, I guess.

But i don't think they can "simply" release it open source and let anybody change it and allow it for anti cheat without some kind of verification

View this comment - View article - View full comments

Quoting: Guest

Quoting: toor

Quoting: KuJoCheck out the releases from Feral Interactive. The number of ports has been drastically reduced. This is certainly also due to Proton ... because if it runs well with Proton, then you don't need a port to play a game on Linux anymore.

You assume a correlation between Feral's release reduction and the raise of Proton.
But you don't consider the fact that Feral may have been asked/pushed by Valve to make some ports. If valve is the reason they ported to Linux, and taking into account the fact that we see Valve putting efforts to make games work with wine, it could also be that it's Valve strategy that is at play, not the existence of Proton being a reason "not to port anymore because it works with Proton"

Valve isn't responsible for everything.

Sure not. But I remember the time when they weren't supporting Linux at all and we had only quake-based video games and tux kart.
The arrival of steam seems to be very correlated with the huge increase of Linux targeted games. Although it started already a bit with humble indie bundles.

View this comment - View article - View full comments

Quoting: KuJoCheck out the releases from Feral Interactive. The number of ports has been drastically reduced. This is certainly also due to Proton ... because if it runs well with Proton, then you don't need a port to play a game on Linux anymore.

You assume a correlation between Feral's release reduction and the raise of Proton.
But you don't consider the fact that Feral may have been asked/pushed by Valve to make some ports. If valve is the reason they ported to Linux, and taking into account the fact that we see Valve putting efforts to make games work with wine, it could also be that it's Valve strategy that is at play, not the existence of Proton being a reason "not to port anymore because it works with Proton"

View this comment - View article - View full comments

Personaly I don't really think it gets people to not port to Linux as a "lazy thing". Proton is risky for the game devs in the way that it can stop working at anytime as you update your game. Also some versions of proton would work, some others wouldn't. So it's not reliable that much, and few users will even deal with twicking the version and even less would actually apply patch and other joy to get the games working.
I guess the point for valve is to bring users onto the device, by having enough games working good enough, and then if the device ends up being used enough, the developers would follow and make the effort to either keep their games working for proton, or have more control on it and do a native port.
Anyway, they are doing much better on the marketing part, and on the more simple options to chose from, as well as the prices. The steamos, steam controller idea to allow to play mouse/keyboard games, and proton to increase the available library without requiring to move the whole gaming ecosystem all come together nicely and actually makes a lot of sense.
Bringing the openness of the PC to a console-like market.

View this comment - View article - View full comments

Quoting: slaapliedje

Quoting: toor

Quoting: slaapliedje

Quoting: toor

Quoting: DaiKaiser93

Quoting: toor

Quoting: DaiKaiser93I'm trying to run the GOG version on EndeavourOS and I get:

Running Hellpoint
Set current directory to /home/daikaiser93/Storage/GOG/Hellpoint/game
Found path: /home/daikaiser93/Storage/GOG/Hellpoint/game/Hellpoint.x86_64
./start.sh: line 16: 117614 Aborted (core dumped) ./"Hellpoint.x86_64"

Anyone know what it could be?

I have the same error. Did you figure out how to solve it?

I'm not currently running Endeavour (switched to Pop), but I remember running the binary with "ldd" to list the dependencies and hunt them down, also make sure you have vulkan installed as it only runs in vulkan.

That's all I remember, apologies if is not helpful

Thanks for your tip.

All the shared libraries are found

linux-vdso.so.1 (0x00007ffd9dbce000)
UnityPlayer.so => /home/toor/.local/share/Steam/steamapps/common/Hellpoint/./UnityPlayer.so (0x00007ff30b539000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff30b3c7000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ff30b3ac000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff30b389000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff30b197000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff30b191000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007ff30b184000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff30d6ba000)

And the game even launches, it crashes while loading the first level.
I guess I'll have to deal with what is dumped when it's crashing, and/or contact the devs.

What does line 16 of the start.sh script show?

It's just calling the actual executable (./Hellpoint.x86_64)

Running Hellpoint
Set current directory to /home/daikaiser93/Storage/GOG/Hellpoint/game
Found path: /home/daikaiser93/Storage/GOG/Hellpoint/game/Hellpoint.x86_64
./start.sh: line 16: 117614 Aborted (core dumped) ./"Hellpoint.x86_64"

According to that it's not?

Oh, or are you saying it's line 16 is running that. Ha, that's not very useful.

yep, and the steam version is slightly different and doesn't include that .sh script, but the result is (at least in appearance) similar.

./Hellpoint.x86_64 
Set current directory to /home/toor/.local/share/Steam/steamapps/common/Hellpoint
Found path: /home/toor/.local/share/Steam/steamapps/common/Hellpoint/Hellpoint.x86_64
Abandon (core dumped)

View this comment - View article - View full comments

Quoting: slaapliedje

Quoting: toor

Quoting: DaiKaiser93

Quoting: toor

Quoting: DaiKaiser93I'm trying to run the GOG version on EndeavourOS and I get:

Running Hellpoint
Set current directory to /home/daikaiser93/Storage/GOG/Hellpoint/game
Found path: /home/daikaiser93/Storage/GOG/Hellpoint/game/Hellpoint.x86_64
./start.sh: line 16: 117614 Aborted (core dumped) ./"Hellpoint.x86_64"

Anyone know what it could be?

I have the same error. Did you figure out how to solve it?

I'm not currently running Endeavour (switched to Pop), but I remember running the binary with "ldd" to list the dependencies and hunt them down, also make sure you have vulkan installed as it only runs in vulkan.

That's all I remember, apologies if is not helpful

Thanks for your tip.

All the shared libraries are found

linux-vdso.so.1 (0x00007ffd9dbce000)
UnityPlayer.so => /home/toor/.local/share/Steam/steamapps/common/Hellpoint/./UnityPlayer.so (0x00007ff30b539000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff30b3c7000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ff30b3ac000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff30b389000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff30b197000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff30b191000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007ff30b184000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff30d6ba000)

And the game even launches, it crashes while loading the first level.
I guess I'll have to deal with what is dumped when it's crashing, and/or contact the devs.

What does line 16 of the start.sh script show?

It's just calling the actual executable (./Hellpoint.x86_64)

View this comment - View article - View full comments

Quoting: DaiKaiser93

Quoting: toor

Quoting: DaiKaiser93I'm trying to run the GOG version on EndeavourOS and I get:

Running Hellpoint
Set current directory to /home/daikaiser93/Storage/GOG/Hellpoint/game
Found path: /home/daikaiser93/Storage/GOG/Hellpoint/game/Hellpoint.x86_64
./start.sh: line 16: 117614 Aborted (core dumped) ./"Hellpoint.x86_64"

Anyone know what it could be?

I have the same error. Did you figure out how to solve it?

I'm not currently running Endeavour (switched to Pop), but I remember running the binary with "ldd" to list the dependencies and hunt them down, also make sure you have vulkan installed as it only runs in vulkan.

That's all I remember, apologies if is not helpful

Thanks for your tip.

All the shared libraries are found

linux-vdso.so.1 (0x00007ffd9dbce000)
UnityPlayer.so => /home/toor/.local/share/Steam/steamapps/common/Hellpoint/./UnityPlayer.so (0x00007ff30b539000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff30b3c7000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ff30b3ac000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff30b389000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff30b197000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff30b191000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007ff30b184000)
/lib64/ld-linux-x86-64.so.2 (0x00007ff30d6ba000)

And the game even launches, it crashes while loading the first level.
I guess I'll have to deal with what is dumped when it's crashing, and/or contact the devs.

View this comment - View article - View full comments

Quoting: DaiKaiser93I'm trying to run the GOG version on EndeavourOS and I get:

Running Hellpoint
Set current directory to /home/daikaiser93/Storage/GOG/Hellpoint/game
Found path: /home/daikaiser93/Storage/GOG/Hellpoint/game/Hellpoint.x86_64
./start.sh: line 16: 117614 Aborted (core dumped) ./"Hellpoint.x86_64"

Anyone know what it could be?

I have the same error. Did you figure out how to solve it?

View this comment - View article - View full comments

we do fully expect any of their future titles to skip over Linux support since it's not likely Microsoft / Xbox will want their next games to be supported on Linux.

That would be such a shame, I like most of what they produce, and they often released it for Linux with a quite good quality.

View this comment - View article - View full comments