3 ms·
I wanted Intel to do well so I purchased an ARC card. The problem is not the hardware. For some games, it worked fine, but in others, it kept crashing left and
by bloodyplonker22 2y ago
I wanted Intel to do well so I purchased an ARC card. The problem is not the hardware. For some games, it worked fine, but in others, it kept crashing left and right. After updates to drivers, crashing was reduced, but it still happened. Driver software is not easy to develop thoroughly. Even AMD had problems when compared to Nvidia when AMD really started to enter the GPU game after buying ATI. AMD has long since solved their driver woes, but years after ARC's launch, Intel still has not.
- shmerl 2y agoDo you mean on Linux and are those problems with anv? Radv seems to be developed faster these days with anv being slightly more behind.
- jamesgeck0 2y agoI haven't experienced many crashing issues on Windows 11. What games are you seeing this in?
- sirn 2y agoIt's also a hardware problem. For example, Alchemist's EUs being SIMD8 but games requiring SIMD16, so it needs to be dispatched to two EUs in a lockstep, or the lack of support for Execute Indirect instruction commonly used in UE5 games, which is currently emulated in software, makes game compatibility a very hit-or-miss. Battlemage is supposed to fix all these architectural issues. EU in Xe2 is now SIMD16 (which is why the number of EUs per Xe2 core is halved from that of Xe1), and they've added all the previously software-emulated instructions, including Execute Indirect, so in theory Battlemage should be in a much better position in game compatibility side of things. On Linux side of things, lacking sparse residency support in i915 also contributes to game compatibility[1] (though this is now available under Mesa 24). This is something the new xe driver is supposed to fix, but it's still a long way to go until it's actually usable. [1]: https://www.phoronix.com/news/Intel-Vukan-Sparse-TR-TT https://www.phoronix.com/news/Intel-Vukan-Sparse-TR-TT