Do they have enough docs from Nvidia in order to not rely on reversing stuff?

View this comment - View article - View full comments

Late revenge for the NES release schedule
JP: July 15, 1983 (Famicom)
NA: October 18, 1985
EU: September 1, 1986

View this comment - View article - View full comments

Hope it supports cross-platform cloud saves.

Such a great game!

View this comment - View article - View full comments

Leak: It's a card game

View this comment - View article - View full comments

There was a VR mode for Half-Life 2 from Valve.
At the time the Occulus Rift DK2 hit the road.

https://steamcommunity.com/app/290930/discussions/2/611701999528654463/?ctp=1 [External Link]

Never got it to work back then.

View this comment - View article - View full comments

Quoting: wit_as_a_riddleLinux needs MARKET SHARE before it will be worth a developer's time to make native linux titles. Proton is the stepping stone to break the chicken and egg catch-22 problem of no native linux titles because no linux market share, no linux market share because no native linux titles.

The real world problem I see with this argument in the current situation is that if we would reach a much higher market share by devs just using Proton, they "learned" that it's not really worth investing additional resources in native ports and just stick with the Proton way.

View this comment - View article - View full comments

Quoting: drjoms

Quoting: StalePopcornI understand the "no tux no bux" argument but if Linux-native sales don't warrant development and maintenance while the same product works just as well via Proton, why bother?

Don't disagree with this, but have a point or two.
1. How do i know if Proton is actually supported? I shall happily buy game on 90% sale, if its not native. If i want game and its not for collection only, i will also pay full price for native port on day of release. And it can be expensive AAA title.
2. How can i help with debugging where there is major layer of proton between game and OS?

Devs do shoot themselves into foot with those two points.

Agree. In most cases it looks like only Valve feels responsible to make a game supported by Proton, when it would be a good start if the devs also do their share.

View this comment - View article - View full comments

Imho bad ports are not an argument against native versions.

It's going the way lots of us expected with Proton.
Instead of supporting games without native binaries,
fewer and fewer developers are willing to port their games.
This is a problematic dependency on Proton.

I'd rather see the awareness AND SKILLS for Linux grow in developer studios.
This is quite the opposite. :/

View this comment - View article - View full comments

OMG do I despise the negativity around the art style.

It feels like poor Ron fell into the trap of showing he takes the "criticism" personal and basically admitted to be vulnerable in that regard. This is what some people on the internet love to exploit and I think this is exactly what happened (still happens) and went far beyond a legitimate criticism.

Looking forward to the game.
Grateful, Ron was brave enough for this project at all.
I mean, that's a damn fvcking risk.
And it seems his worries were justified (even more than that).

What a sad turn of events after one the most exciting game related announcements (for *me*).
Hope Ron will be fine.

It all boils down to "That's why we can't have nice things".

View this comment - View article - View full comments

Quoting: berarma

Quoting: subSo this won't be accepted in the kernel if *only* a proprietary user space drivers is available.
Mind that AMD only got their kernel driver mainlined as it provides a proprietary AND open-source
user space driver using the same API.

That's not true, drivers don't get rejected for that reason. The only reason it can't be streamlined is that the code doesn't follow Linux coding conventions. The driver as it is can be used by other software, not only the Nvidia propietary drivers. I guess it could be even used by Mesa. We'll see.

It's not a matter of *can*. If such a user-space component does not exist, or is just a cheeky unmaintained mess, the kernel module will certainly not be mainlined.

View this comment - View article - View full comments