People really REALLY need to lobby against games like this and DON'T BUY.
By buying this, gamers are just telling EA its ok to steal their money and kill games, and also offer terrible release support (no linux because of anti-cheat, Linux has anti-cheat)

@TheRiddick, this is the most privileged first world problem "everyone MUST share my exact philosophy in this subject nonsense I've ever heard.

90% of all PC gamers don't REMOTELY care about what you think they should do and they want to play the games they love. if someone's favorite game is Apex or COD or Destiny 2, telling them to boycott that game makes you sound like a sanctimonious prick, doubly so when you tell them to just "pick another game."

I play Fighting games, and luckily Street Fither 4-6 all work on Linux, but if SF7 came out and added some bullshit kernel anticheat, if you told someone like me to just play tekken, it does nothing other than make you look like an absolute prick who also has NO clue what they're talking about.

View this comment - View article - View full comments

Quoting: CatKillerRepetition for emphasis: this is the global top sellers; the other things in the list are sold everywhere but the Deck is only sold in a handful of regions and is selling enough to take the top spot.

It's also the price of 6-10 AAA games, and this list is total revenue.

View this comment - View article - View full comments

Quoting: realmzfkrbought jedi: fallen order on a discount in steam today... i even tried installing origin through desktop mode, even logged in, but that too was futile. it just shows a blank screen and prompts me to use the keyboard on it. EA are the worst!

You can't use the non-Steam desktop Origin *or* EA App to run games you own on Steam. So please don't waste your time trying to install non-Steam desktop apps for EA games.

This isn't even a Linux issue. Go install Windows, install EA App or Origin and look in your library. Jedi Fallen Order will show up, but with a Steam logo over it. If you click Play, it just launchs Steam and then launches the Steam-bundled EA launchers.

But since you're on Linux, if you go trying to install the regular EA App, when you click Play nothing will happen because that wineprefix has no Steam.exe in it. Yeah, it'll try to launch the Windows version of Steam, too.

Give it 2-3 days. It'll be working soon enough.

But this is exactly why I buy my EA Play Pro pass through Origin (or I guess EA App now), and not on Steam. Because I never have any of these issues whatsoever. I've been able to run Jedi Fallen Order without even thinking about it through Lutris since the week it launched.

View this comment - View article - View full comments

Quoting: psy-qWorks mostly fine on Lutris with various WINE versions. This may be a Proton-specific issue. I've also had fewer problems with EA App than with Origin, even when the app was still in beta.

One caveat: When an update is downloaded, it downloads into some staging dir but never runs the destager and instead just quits. If you launch it again in Lutris, this will start the old EA App version. You'll have to "run EXE in WINE prefix" and select the "Destager.exe" from the newly downloaded version. This'll merge the staged update with your existing install and it should work fine again after that.

A nuisance but better than the randomly disappearing windows and odd CPU-hogging processes that Origin had.

Yeah, I've been using EA App for like a year alongside Origin in Lutris, and I've not encountered any issues. The Origin Thin Client that got used with EA games on Steam always had problems too, even though the desktop Origin app worked perfectly through Lutris for years.

View this comment - View article - View full comments

Quoting: ljrkNow we "only" need drivers for Windows and macOS to interface with that. Plus dxvk (dx9-11) und vkd3d for dx12 for Windows and MolteVK for macOS and we'd have pretty neat graphics accelaration ;)

None of that would be necessary. VirtIO-GPU virtual GPU with lib.vfio has already been shown to run Call of Duty Warzone in a Windows VM as if it's a native app using vGPU. You wouldn't need anything to do with vkd3d-proton, dxvk, or Windows drivers.

View this comment - View article - View full comments

Quoting: fearnflavio

Quoting: Ehvis

Quoting: fearnflavioHave someone tested it to check if it fixes the Gsync/Freesync issue that the stable driver has?

Did the Vulkan beta have this issue to begin with?

On the nvidia forums it was mentioned that the fix will be in the next release, but it may just be the stable driver.

I'm still not sure if gsync is actually affected since all reports seem to have come from freesync (gsync compatible) users.

Yes, I have a Freesync compatible monitor.
The issue was with the stable driver, which fixed the memory leak when using vkd3d. But for me, the freensync was more important. So I reverted back to the old Vulkan Driver. And for all vkd3d games I have, only on Assassins creed Valhalla I noticed the memory leak, on Cyberpunk, Death Stranding, Mortal Shell, Control, I do not have it.

But still, using nvidia-tkg I cannot find this new version to download. The latest is 470.62.02.

Edit: Just saw this on the Stable release post on their forums: The new 470.62.05 vulkan dev drivers released yesterday are also impacted by this.

So... no, it's not fixed.

nvidia-all from TKG definitely does have the update to 470.62.05. You need to do a git pull.

View this comment - View article - View full comments

Quoting: massatt212waiting for it to release for manjaro or arch

Manjaro and Arch don't provide Vulkan Beta driver packages. Only the stable release (so 470.74).

View this comment - View article - View full comments

Quoting: PhiladelphusI interpreted that initial comment as saying 100% of games would work with Proton, and I was definitely skeptical of Valve pulling that off before December, unless they're sitting on a ton of improvements they haven't released yet. This interpretation makes a lot more sense. Thankfully it doesn't make a difference to me, but I can see this being a turn-off for Windows gamers. Hopefully Valves pulls off enough Proton improvements by December to get enough of the popular games working that Windows gamers are willing to wait for further improvements.

Valve themselves have explicitly said that they want 100% compatibility with PROTON. So even though Pierre's quote was referring to hardware, Valve have also said that every game will be able to run on the Steam Deck from a software/compatibility standpoint as well.

Source: https://youtu.be/5Q_C5KVJbUw?t=134 [External Link]

View this comment - View article - View full comments

Quoting: mphuZ

Quoting: gardotd426Your entire comparison is complete and utter nonsense.

Damn, what does vkd3d-proton have to do with it, if we're talking about drivers?

I do not care about VKD3D-Proton, like potential developers who want to want to release native games for Linux.

Joshua says the main obstacle is the driver and its support. I do not agree with his harsh statements.

Um, for one, even you never mentioned "native games." And the things Josh mentioned are absolutely relevant. vkd3d-proton has to work with the Vulkan driver. That's literally how it works. And if the Vulkan driver is trash, doesn't support extensions it should, etc., how is that not relevant?

Your tirade of a post about how what Josh said was "offensive" is blatant AMD worship. And you excuse their waiting 5 months to bring RT support to *just* their proprietary driver and not AMDVLK even though Nvidia had it on day one by saying "well who cares RT is a niche," but it's not just RT where AMD does this.

AMD hasn't released a GPU in the last 4-5 years where they supported all of its functions at launch on Linux. Not just in the userspace drivers, but in the amdgpu kernel driver. It took months and months for RDNA 1 to get overclocking/voltage control, and the same goes for RDNA 2, it just now got it. That's a basic functionality. And there are countless other functions that AMD didn't enable for new GPUs until months after launch. Like I said, they've not released a single architecture in the last 5 years where they've actually fully supported it on Linux at launch.

It's really not a good idea to worship a corporation like that.

View this comment - View article - View full comments

Quoting: kfpenguin

Quoting: gardotd426Um, no?

I have an RTX 3090 and my overall resolution is 5120x1440@165Hz (2x2560x1440@165Hz), with both connected over DisplayPort. Never once has it failed to boot. And I'm on 5.13-rc4 right now.

Well, this is an nvidia-recognized bug that is currently affecting many people across multiple distributions. And anyone it does affect is in for a rough day. The type of bug that leaves a sour impression on the company for those affected.

But you aren't having this issue, so I'm sorry I've wasted everyone's time.

The thing is, you misrepresented the situation.

Their new drivers crashes on boot if your montior is connected with DP and/or resoution greater than 1080p.

That's what you said. When in reality, the truth is "**if** you happen to own one of just a handful of monitor models, you're running a resolution above 1080p, *and* it's over DisplayPort, then you can have trouble booting on the current driver."

There are legitimately thousands of people running Linux on Nvidia GPUs above 1080p that aren't having this issue, and it's probably less than 1/10th of 1% of the Nvidia users on Linux that are experiencing this bug. But you decided to make a blanket unequivocal statement, which was false.

View this comment - View article - View full comments