You can sign up to get a daily email of our articles, see the Mailing List page!
Latest Comments by Leopard
Valve gets another developer to work on Linux graphics drivers, starting with AMD RADV
28 July 2020 at 10:07 pm UTC Likes: 6

Quoting: Whitewolfe80Great news that valve keep investing in linux, I would love to know what the return is for valve corp on linux investment. Do we spend enough for them to retain profit even after monthly wage bill and investments, in graphics compatibility and innovation or do they make a loss on it each qtr banking on the long game.

They are probably burning money.

NoiseTorch is another tool to remove background noise while recording on Linux
17 July 2020 at 3:03 pm UTC Likes: 14

Any new Linux background noise supressor released

Liam: Hammer Time!

3D adventure thriller 'Beyond a Steel Sky' is out now for Linux PC
17 July 2020 at 11:34 am UTC Likes: 1

Quoting: TheRiddickInteresting, I hope its not using OpenGL...

It is Vulkan but you would actually want OpenGL here Vulkan on UE4 sucks.

Probably throwing it to Proton would yield to better perf.

DirectX 12 exclusive DEATH STRANDING runs on Linux with Proton 5.0-10
16 July 2020 at 4:33 pm UTC Likes: 1

Quoting: Patola
Quoting: Leopard
Quoting: PatolaSpeaking of drivers, the 450.57 drivers got to the graphics-drivers PPA for Ubuntu 20.04, however they come only in 64 bits packages, thus Steam does not even start. For 18.04 and 19.10 the 32-bits packages are there. So it seems the 32bitscalypse for Ubuntu has started...

As a workaround, changing the ppa sources.list file to point to eoan instead of focal then changing the driver version works and steam starts. A packaged 450.07 working on Ubuntu 20.04 jumping through many hoops and stuff.

Update: the packager (Alberto Milone) responded. He said he made a request to whitelist the new nvidia drivers, so that they are allowed to build i386 binaries. So soon the workaround will not be necessary.

Is that fixed? I still lack 32 bit libs.

Btw what kind of change you are talking about?

/etc/apt/sources.list.d

deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main
# deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main

Simply changing focal to eoan is sufficient?

Yes, that's it, just change focal to eoan, then of course after that do an apt-update, and then apt install nvidia-driver-450 <...other nvidia-450 packages>.

If you do not know which are the other packages, this line should work and pull the other dependent packages, i386 and amd64:

sudo apt install nvidia-driver-450 libnvidia-gl-450 libnvidia-compute-450 libnvidia-extra-450 nvidia-compute-utils-450 libnvidia-compute-450:i386 libnvidia-decode-450:i386 libnvidia-ifr1-450 libnvidia-fbc1-450 libnvidia-gl-450:i386 libnvidia-ifr1-450:i386 libnvidia-decode-450:i386 libnvidia-compute-450:i386

I am also monitoring the repository. Whenever I detect that the 20.04 source has been fixed, I'll tell here.

Thanks , that worked.

DirectX 12 exclusive DEATH STRANDING runs on Linux with Proton 5.0-10
16 July 2020 at 4:07 pm UTC Likes: 1

Quoting: PatolaSpeaking of drivers, the 450.57 drivers got to the graphics-drivers PPA for Ubuntu 20.04, however they come only in 64 bits packages, thus Steam does not even start. For 18.04 and 19.10 the 32-bits packages are there. So it seems the 32bitscalypse for Ubuntu has started...

As a workaround, changing the ppa sources.list file to point to eoan instead of focal then changing the driver version works and steam starts. A packaged 450.07 working on Ubuntu 20.04 jumping through many hoops and stuff.

Update: the packager (Alberto Milone) responded. He said he made a request to whitelist the new nvidia drivers, so that they are allowed to build i386 binaries. So soon the workaround will not be necessary.

Is that fixed? I still lack 32 bit libs.

Btw what kind of change you are talking about?

/etc/apt/sources.list.d

deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main
# deb-src http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu focal main

Simply changing focal to eoan is sufficient?

VKD3D-Proton is the new official Direct3D 12 to Vulkan layer for Proton
7 July 2020 at 9:21 am UTC

Quoting: Shmerl
Quoting: iiariMS seems to realize that a cloud based X-Box service is their gaming future. Does DX12 have any role in such a service?

Luckily MS decided to abandon their cloud gaming. So one more DX lock-in bites the dust.

Can you even read what you linked?

They closed their Twitch variant , Mixer. How is that related to cloud gaming?

https://www.xbox.com/en-US/xbox-game-streaming/project-xcloud

They still have plans for it.

NVIDIA 440.66.17 Vulkan Beta Driver released
24 June 2020 at 11:16 am UTC Likes: 1

Quoting: KibaAre they going to give us decent VR support? Because i want to buy the new 3000 series at the end of the year but not having async reprojection is terrible and induces motion sickness.

There is an extension in the works to solve this.

EVERSPACE 2 sure does look shiny in the new Alpha footage
14 June 2020 at 7:36 pm UTC

Quoting: ShmerlOK, so it's Steam allowing Geforce Now pull their games from it. I don't see how it helps with the above issue. Developers won't start running fixing any bugs that pop up there, they never signed up for it.

On the other hand, when they release for Stadia, they support their games. So Geforce Now is nowhere comparable even in its concept. It's just a VM renting service, with the "use it as is" idea.

I think you have serious understanding problems.

1-) Geforce Now runs on a Windows environment.

2-) Steam Cloud lets Geforce Now to utilize those games on a Windows environment that has native d3d drivers that are provided by Nvidia on desktop too.

3-) How the hell games might be borked on Geforce Now? If some game is borked on Geforce Now it means it is also borked on a desktop installation of Windows.

EVERSPACE 2 sure does look shiny in the new Alpha footage
14 June 2020 at 7:25 pm UTC

Quoting: Shmerl
Quoting: LeopardThis is a service that developers are very well aware and can opt-in to use it.

I'm talking about Geforce Now, not about Steam cloud. Geforce Now relies on existing games. Stadia relies on games released there. What happens if something is bugged when played through Geforce Now? Nvidia won't go and fix those bugs for you, and neither will developers who didn't even release their games for it.

Can you please read the link i posted , pretty please?

It is entirely about Geforce Now.

QuoteSteam Cloud Play is currently in Beta and features are being added over time. We are now accepting a limited amount of games into the service as we continue to build features and server capacity for players. The first service we are connecting to Steam to allow users to play games from their Steam Library from the Cloud is NVIDIA GeForce NOW. There are more details below about how to opt your game(s) into the service as well as answers to a few common questions below.

Currently NVIDIA GeForce NOW is available in North America, Western Europe and Asia Pacific. Currently, Steam users will need to download the GeForce Now client and connect their Steam account to the GFN service to play their Steam Library. The user may pay a subscription cost to use the GFN service. Customers will continue to acquire games on Steam the same way they do today, and partner payouts will remain the same.