I guess there games that you can only play on PC with Nvidia graphics. That begs the question why someone create a game and ignore large console market.
With their current generation of cards AMD has caught up on all of those things except CUDA, and Intel is in a similar spot now that they've had time to improve their drivers, so it's pretty easy now to buy a non-Nvidia card without feeling like you're giving anything up.
AMD doesn't care about consumers anymore either. All the money in AI.
I mean, this also describes the quality of NVIDIA cards. And their drivers have been broken for the last two decades if you're not using windows.
I suspect the thing you're referring to is ZLUDA[0], it allows you to run CUDA code on a range of non NVidia hardware (for some value of "run").
Traditionally the NVIDIA drivers have been more stable on Windows than the AMD drivers. I choose an AMD card because I wanted a hassle free experience on Linux (well as much as you can).
It's not that I can't live like this, I still have the same card, but if I were looking to do anything AI locally with a new card, for sure it wouldn't be an AMD one.
Wrt/ a1, it worked at one point (a year ago) after 2-3 hours of tinkering, then regressed to not working at all, not even from fresh installs on new, different Linuxes. I tried the main branch and the AMD specific fork as well.
Wrt/ Open WebUI, it works, but the thing uses my CPU.
And... they don't need to. Most of the most played video games on PC are all years old [0]. They're online multiplayer games that are optimized for average spec computers (and mobile) to capture as big a chunk of the potential market as possible.
It's flexing for clout, nothing else to it. And yet, I can't say it's anything new, people have been bragging, boasting and comparing their graphics cards for decades.
[0] https://activeplayer.io/top-15-most-popular-pc-games-of-2022...
The past few years (2018 with the introduction of RT and upscaling reconstruction seems as good a milestone as any) feel like a transition period we're not out of yet, similar to the tail end of the DX9/Playstation3/Xbox360 era when some studios were moving to 64bit and DX11 as optional modes, almost like PC was their prototyping platform for when they made completed the jump with PS4/Xbox one and more mature PC implementations. It wouldn't surprise me if it takes more years and titles built targeting the next generation consoles before it's all settled.
I understand the reason for moving to real time ray-tracing. It is much easier for development, and apparently the data for baked/pre-rendered lighting in these big open worlds was getting out of hand. Especially with multiple time-of-day passes.
But, it is only the "path tracing" that top end Nvidia GPUs can do that matches baked lighting detail.
The standard ray-tracing in the latest Doom for instance has a very limited number of entities that actually emit light in a scene. I guess there is the main global illumination source, but many of the extra lighting details in the scene don't emit light. This is a step backward compared to baked lighting.
Even shots from the plasma weapon don't cast any light into the scene with the standard ray-tracing, which Quake 3 was doing.
You don't get headlines and hype by being an affordable way to play games at a decent frame rate, you achieve it by setting New Fps Records.
Software. AMD has traditionally been really bad at their drivers. (They also missed the AI train and are trying to catch up).
I use Linux and have learned not to touch AMD GPUs (and to a lesser extent CPUs due to chipset quality/support) a long time ago. Even if they are better now, (I feel) Intel integrated (if no special GPU perf needed) or NVidia are less risky choices.
The situation completely changed with the introduction of the AMDGPU drivers integrated into the kernel. This was like 10 years ago.
Before then the AMD driver situation on Linux was atrocious. The open source drivers performed so bad you'd get better performance out of Intel integrated graphics than an expensive AMD GPU, and their closed source drivers were so poorly updated you'd have to downgrade the entire world for the rest of your software to be compatible. At that time Nvidia was clearly ahead, even though the driver needs to be updated separately and they invented their own versions of some stuff.
With the introduction of AMDGPU and the years after that everything changed. AMD GPUs now worked great without any effort, while Nvidia's tendency to invent their own things really started grating. Much of the world started moving to Wayland, but Nvidia refused to support some important common standards. Those that really wanted their stuff to work on Nvidia had to introduce entirely separate code paths for it, while other parts of the landscape refused to do so. This started improving again a few years ago, but I'm not aware of the current state because I now only use Intel and AMD hardware.
Then there is the (in)famous AMD reset bug that makes AMD a real headache to use with GPU passthrough. The card can't be properly reset when the VM shuts down so you have to reboot the PC to start the VM a second time. There are workarounds but they only work on some cards & scenarios [1] [2]. This problem goes back to around the 390 series cards so they've had forever to properly implement reset according to the pci spec but haven't. nvidia handles this flawlessly
[0] https://gitlab.freedesktop.org/drm/amd/-/issues/3911
Lesser OpenGL version, and I never managed to have hardware accelerated video until it died last year.
* Purchase always AMD.
* Purchase never Nvidia.
* Intel is also okay.
While Nvidia comes up with proprietary stuff AMD brought us Vulkan, FreeSync, supported Wayland well already with Implicit-Sync (like Intel) and used the regular Video-Acceleration APIs for long time.
Meanwhile Nvidia:
https://registry.khronos.org/OpenGL/extensions/NV/NV_robustn...
It’s not a bug, it’s a feature!
Okay. But that is probably only a short term solution? It is Nvidias short term solution since 2016!
They do care about but reports, and their drivers — when given time to stabilize — provide the best experience across all operating systems (easy updates, etc), but IME mainline kernels should be treated as alpha-to-beta material.
NVIDIA's drivers also recently completely changed how they worked. Hopefully that'll result in a lot of these long term issues getting fixed. As I understand it, the change is this: The nvidia drivers contain a huge amount of proprietary, closed source code. This code used to be shipped as a closed source binary blob which needed to run on your CPU. And that caused all sorts of problems - because its linux and you can't recompile their binary blob. Earlier this year, they moved all the secret, proprietary parts into a firmware image instead which runs on a coprocessor within the GPU itself. This then allowed them to - at last - opensource (most? all?) of their remaining linux driver code. And that means we can patch and change and recompile that part of the driver. And that should mean the wayland & kernel teams can start fixing these issues.
In theory, users shouldn't notice any changes at all. But I suspect all the nvidia driver problems people have been running into lately have been fallout from this change.
Sadly, a couple of years ago someone seriously misunderstood the news about "open sourcing" their drivers and spread that misunderstanding widely; many people now think their whole driver stack is open, when in reality it's like 1% of the code — the barest minimum they could get away with (I'm excluding GSP code here).
The real FOSS driver is Nova, and it's driven by the community with zero help from Nvidia, as always.
Yes, there are translation layers[1] which you have to know about and understand how to install correctly, which partially solve the problem by translating from VAAPI to NVDEC, but this is certainly not for the average user.
Hopefully, in the future browsers will add support for the new Vulkan Video standard, but for now, unfortunately, one has to hardcode the browser launch parameters in order to use the integrated graphics chip's driver (custom XDG-application file for AMD APU in my case: ~/.local/share/applications/Firefox-amdgpu.desktop): `Exec=env LIBVA_DRIVER_NAME=radeonsi DRI_PRIME=0 MOZ_ENABLE_WAYLAND=1 __NV_PRIME_RENDER_OFFLOAD=0 __GLX_VENDOR_LIBRARY_NAME=radeons i /usr/bin/firefox-beta %u`.
On my Steam deck, I have to use vulkan. AV1 decoder is straight up buggy, have to disable it with config or extensions.
I have no NVIDIA hardware, but I understand that the drivers are even worse than AMD's.
Intel seems to be, at the moment, the least worse compromise between performance and stability,
In my experience an AMD card on linux is a great experience unless you want to do something AI related, in which case there will be random kernel panics (which, in all fairness, may one day go away - then I'll be back on AMD cards because their software support on Linux was otherwise much better than Nvidia's). There might be some kernel upgrades that should be skipped, but using an older kernel is no problem.
Err, what? While you're right about Intel integrated GPUs being a safe choice, AMD has long since been the GPU of choice for Linux -- it just works. Whereas Nvidia on Linux has been flaky for as long as I can remember.
Not OP, I had same experience in the past with AMD,I bought a new laptop and in 6 months the AMD decided that my card is obsolete and no longer provided drivers forcing me to be stuck with older kernel/X11 , so I switched to NVIDIA and after 2 PC changes I still use NVIDIA since the official drivers work great, I really hope AMD this time is putting the effort to keep older generations of cards working on latest kernels/X11 maybe next card will be AMD.
But this is an explanations why us some older Linux users have bad memories with AMD and we had good reason to switch over to NVIDIA and no good reason to switch back to AMD
That said, I've been avoiding AMD in general for so long the ecosystem might have really improved in the meantime, as there was no incentive for me to try and switch.
Recently I've been dabbling in AI where AMD GPUs (well, sw ecosystem, really) are lagging behind. Just wasn't worth the hassle.
NVidia hw, once I set it up (which may be a bit involved), has been pretty stable for me.
I have no opinion on GPUs (I don't play anything released later than about 2008), but Intel CPUs have had more problems over the last five years than AMD, including disabling the already limited support for AVX-512 after release and simply burning themselves to the ground to get an easy win in initial benchmarks.
I fear your perception of their products is seriously out of date.
How's the chipset+linux story these days? That was the main reason for not choosing AMD CPU for me the last few times I was in the market.
Now wayland support is an important factor and AMD is a perfectly acceptable and indeed economical choice.
Basically 15 years inertia is hard to counter.
its been great. flawless in fact.
Maybe there's a difference for the people who buy the absolute top end cards but I don't. I look for best value and when I looked into it amd looked better to me. Also got an amd CPU which has aso been great.