Patreon Logo Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal Logo PayPal. You can also buy games using our partner links for GOG and Humble Store.
Latest Comments by illwieckz
AMD reveal RDNA 2 with Radeon RX 6900 XT, Radeon RX 6800 XT, Radeon RX 6800
28 Oct 2020 at 5:21 pm UTC Likes: 12

Quoting: GuestI never had to write xorg.conf to make my hardware work, nvidia-settings takes care of the settings.
You said it: “nvidia-settings takes care of the settings”. You're experiencing Linux graphics like if you still lived in year 2004. That's not normal you have to use nvidia-settings. That's wrong you have to use it. Neither Intel or AMD hardware requires similar things. This has stopped on AMD side many year ago. The thing is: Nvidia is decade late in the race.

Quoting: GuestI never had
Quoting: GuestMy nvidia card
Ok, you answer a “works for me” statement without taking risk to leave the comfort zone.

Do you understand you're building denial about months of actual and serious testing for the only reason you may have not tried enough to face a problem yourself?

Quoting: GuestDid your GPU "fallen of the bus"? Your hardware is probably started to fail or is not connected properly. There is a very high chance it's a PSU issue.
This was verified with multiple graphic cards of the same family, on multiple motherboards, on multiple PSU (I driven the test myself and tried out all the possible combinations), and you know what? The nouveau driver runs flawlessly on the same hardware (whatever the combination).

Quoting: GuestGame developers definitely target specific hardware, it's pointless to deny it. They literally mentioned that in the video from this article.
Targeting specific hardware or driver is only required to get some extra performance boost in specific situations. Outside of optional dedicated optimizations no one has to do it. And no one must have to target specific hardware or driver to prevent driver failures.

Targeting specific hardware and driver must remain optional, not a requirement. And you talk like if it was a requirement.

Maybe are you among those people who are afraid their game would not run outside of Nvidia like there was people being afraid to lose their favorite websites if they switched from IE to Firefox two decades ago?

If you really buy Nvidia hardware because of Nvidia making you believe you'll lose something you have, then you're victim of a racket.

AMD reveal RDNA 2 with Radeon RX 6900 XT, Radeon RX 6800 XT, Radeon RX 6800
28 Oct 2020 at 4:50 pm UTC Likes: 11

Quoting: GuestThis is what an amd fanboy would say, not a conscious customer who evaluates a product properly. Nothing you mentioned is actually an evaluation of any aspect,
This is based on the actual testing of 50+ hardware pieces, more than 70 configurations, it is months of testing (and in fact, sometime, years of debugging).

All those tests in that page were driven by developers or under developer supervision, they are not automated. I was involved in all of them in several stages.

Quoting: lunisAs a game developer you develop your software for a specific driver/hardware combo.
We don't develop for a specific driver/hardware combo. You're talking like a web developer from Internet Explorer 6 era.

The specific bug I talked about is a bug where Nvidia driver wrongly announces the hardware supports a feature that is not supported. That's unrelated to how the game is developed or not. A game written properly against the OpenGL standard would query the availability of the feature and would enable code the hardware does not support because the driver made a false statement. So we have to do some guesses to attempt to detect the faulty driver/hardware combinations to not trust what the driver says.

And outside of game development, I have seen Nvidia cards requiring to plug a screen on VGA port to stop the Nvidia driver to complain when using the HDMI port (while not being able to display something on that VGA port anyway). I have seen Nvidia cards displaying the early BIOS screen on one port and the operating system on another, requiring to unplug/replug the screen during the boot process to get continuous display. This has nothing to do with game development. Some cards just disconnect themselves from the PCIe bus with the proprietary driver, not with the open source driver. This has nothing to do with game development.

I had myself to write Xorg.conf things to make Nvidia stuff working on actual hardware, things people using AMD or Intel don't do since year 2008 or so. What a blast from the past!

The thing is that Nvidia products are like dragster: they can shave 1 second over their concurrent time on a straight line, you don't know what happens if you have to take turns, they are not meant to make yourself able to take your children to school or complete the Dakar Rally, and it may just explode in your face before starting the race.

[  195.564010] NVRM: GPU at 0000:01:00.0 has fallen off the bus.

True story.

AMD reveal RDNA 2 with Radeon RX 6900 XT, Radeon RX 6800 XT, Radeon RX 6800
28 Oct 2020 at 4:17 pm UTC Likes: 12

Quoting: GuestOr just be a conscious customer and evaluate products properly instead of relying on ideologies only.
So you can't buy Nvidia, only AMD or Intel can be bought if you evaluate products properly, and if you need Navi-like power, only AMD can be bought if you evaluate products properly.

Nvidia are bad products on Linux, they require closed obsolete technology, provide experience that did not evolved since year 2000, are badly supported and become quickly obsolete and lose driver support on short time. If Nvidia asked me to build-up for them a catchword, I would say “Nvidia: bringing you year 2000 experience, faster”.

Also, Nvidia drivers are a pain to deal with. As a game developer for Unvanquished, I can testimony we face kind of bugs we never see with Intel or AMD, we even have to hardcode special workaround for their driver brokenness.

We tested more than 50 GPUs that comes from the past 18 years to today:
https://wiki.unvanquished.net/wiki/GPU_compatibility_matrix [External Link]
And I can testimony: Nvidia is trash and pain, garbage and suffering.

On the contrary AMD support is stellar, it works really well, performance are awesome, and support is stellar.

The only reason to buy Nvidia today is that if you're constrained to use CUDA, so you're likely victim of a racket. Being forced to use proprietary software is worst than not using any software, it's a kind or racket: a service that is fraudulently offered to solve a problem. Being forced to buy Nvidia hardware to run a software is a racket.

Free first-person shooter-strategy 'Unvanquished' is now properly open source
20 Sep 2020 at 5:36 pm UTC

Quoting: whizseYou're supposed to run the game using "./daemon -pakpath /path/to/pkg/" but the game version that's available to download is from 2018 and suffer from bitrot. It seems to depend on an outdated libstdc++.
You don't need to use any argument if you move the binaries right to the pkg/ folder, see my previous comment.

About bitrot, one problem we face is that we need to build the game on an old linux distribution to make sure people with old distros can also run it. So it's all about choosing a build platform that is not too much recent and not too much old at the same time. What is the distro name and version you use so we may check it for our upcoming release?

Free first-person shooter-strategy 'Unvanquished' is now properly open source
20 Sep 2020 at 4:59 pm UTC

Quoting: scaineI downloaded the torrent, got this:



No idea what to do. Nothing in the wiki either, that I could find. Why is the torrent different from the universal updater? Why are good guy open source game designers so poor at making their games easily accessible? Weird.

I'll try the actual download button. I tend to avoid them if there's a torrent, a I don't like placing load on a free game resource.
Move everything from the “linux-amd64” folder right to the “pkg” one (in fact the “linux-amd64” folder does not exist in the archive but was created by your unarchiver, we can't prevent this).

So, your folder must looks like this:

```
pkg/
crash_server
daemon
daemonded

Free first-person shooter-strategy 'Unvanquished' is now properly open source
20 Sep 2020 at 4:47 pm UTC

Quoting: Faalhaas
Quoting: TcheyAh, good to know then. I’m on Manjaro.

You do the same, right ? I don’t miss a step ?
I had this same issue on Arch.
Hi, we are investigating that crash that looks specific to Arch:
https://github.com/Unvanquished/Unvanquished/issues/1215 [External Link]

Do you used our official build (using the updater or the universal zip archive)?
If yes, can you try this instead? https://aur.archlinux.org/packages/unvanquished/ [External Link]

-- illwieckz from Unvanquished