That is almost certainly because Factorio has a native Linux version and Steam installed that instead of the Windows version. It was trying to use OpenGL and defaulting to CPU rendering because you likely haven’t altered the default configuration.
If you force Steam to use steam play, it will download the Windows version and run it through Proton which will use the right hardware.
It is enough, provided that you have your system configured correctly. Which, in this case, is designating a graphics card to use. Without that it defaults to using CPU rendering.
Most people don’t want to deal with the headache of configuring their systems and would rather use something more automatic.
That’s what Proton does for you. If you’re using Proton then it can assumed that you’re gaming and so defaults can be set to support that.
Whereas people use Vulkan for many different projects and so it chooses safe defaults and depends on further configuration by the user (which Proton does for you).
Native Linux games work just fine (I play native Rimworld every week or so), you just have to configure your system manually.
Or just use the preferred method of running Windows games via Proton. You’re going to be doing it anyway in order to game on Linux and so it is often more work to run the native version than it is to run the Windows version and let Proton handle the automatic configuration.
Running the native version requires the user to configure their system correctly and then it would work. Most people who are coming to Linux from Windows are not interested in editing config files or using the terminal and, in any case, the vast majority of Linux gaming is done by running Windows games via WINE.
Proton is WINE packaged with the software and configuration scripts so that it ‘just works’ without user intervention. If you’re on Linux, you can install Steam and Go to Settings -> Compatibility and check ‘Allow Steam Play for all other titles’ and, from that point on, it will install the Windows version of the game and run it with Proton with no user interaction (other than clicking ‘Play’).
It’s this nonsense that keeps people locked in to Windows.
It isn’t nonsense, it makes perfect sense.
You can follow the error messages (which it prints to stdout when the game launches) and determine what the problem is so that you can fix it. The problem is completely understandable, the game logs would show exactly what device it was using and you could see what piece of software is responsible and go and look at the online documentation for that project to determine the exact configuration change that you need to make.
That’s how you should be troubleshooting problems, but you can’t do that on Windows because everything is a black box and provides little to no logs. If you’re lucky you’ll get an error message.
If you have a problem on Windows you first reboot and pray. Or, if that doesn’t fix it, you search random social media or forum posts, apply arbitrary registry changes recommended by Reddit comments, upgrade drivers, downgrade drivers, install motherboard firmware and dig through the various Windows GUI menus, which are change completely between Windows 8, 10 and 11 (but not 9, which doesn’t exist for some arbitrary reason), to locate a switch or checkbox that you can flip (and reboot again) until finally the problem resolves itself seemingly on its own. To me, this is the nonsense.
It shouldn’t require editing config files, except maybe in an Nvidia Optimus or AMD Switchable Graphics configuration. The fast/efficient GPU support was a dumpster fire the last time I had Linux on a laptop with it.
I know what Proton is.
No, it does not make perfect sense that a Linux native version of a game is more difficult to use than the Windows version on Proton. That may be how it is, but it does not make sense. Whatever method WINE or Proton uses to connect the Windows game to a supported graphics API in Linux must be entirely possible to do in a native Linux version of a game as well. For whatever reason, the game developers either chose not to or were incapable of developing that code.
At the third party application level, Windows applications are a black box. That has nothing to do with Windows, though. Complain to third party developers
It reads like you lack experience troubleshooting on Windows. If you’re praying to some higher power to make your software issues go away, you may also want to revaluate your troubleshooting methodology. Nearly everything you said can also apply to troubleshooting issues with Linux. Except for the whole skipping of “Windows 9”, which no one truly cares about.
You clearly feel a lot of hate towards Microsoft, and they certainly deserve a lot of it. However, it serves no purpose to resort to exaggeration and hyperbole.
That is almost certainly because Factorio has a native Linux version and Steam installed that instead of the Windows version. It was trying to use OpenGL and defaulting to CPU rendering because you likely haven’t altered the default configuration.
If you force Steam to use steam play, it will download the Windows version and run it through Proton which will use the right hardware.
I’m confused. Shouldn’t me downloading the native Linux factorio and native Linux Steam be enough? Why would it default to something else?
It is enough, provided that you have your system configured correctly. Which, in this case, is designating a graphics card to use. Without that it defaults to using CPU rendering.
Most people don’t want to deal with the headache of configuring their systems and would rather use something more automatic.
That’s what Proton does for you. If you’re using Proton then it can assumed that you’re gaming and so defaults can be set to support that.
Whereas people use Vulkan for many different projects and so it chooses safe defaults and depends on further configuration by the user (which Proton does for you).
Native Linux games work just fine (I play native Rimworld every week or so), you just have to configure your system manually.
Or just use the preferred method of running Windows games via Proton. You’re going to be doing it anyway in order to game on Linux and so it is often more work to run the native version than it is to run the Windows version and let Proton handle the automatic configuration.
I’ve not played Factorio but I’ve seen a vidjeo about it. How is the Windows version on Proton better than a Linux native version?
Wouldn’t the correct answer be to fix the graphics driver or configuration? And why doesn’t OpenGL just work? Or better yet, Vulkan?
It’s this nonsense that keeps people locked in to Windows.
Running the native version requires the user to configure their system correctly and then it would work. Most people who are coming to Linux from Windows are not interested in editing config files or using the terminal and, in any case, the vast majority of Linux gaming is done by running Windows games via WINE.
Proton is WINE packaged with the software and configuration scripts so that it ‘just works’ without user intervention. If you’re on Linux, you can install Steam and Go to Settings -> Compatibility and check ‘Allow Steam Play for all other titles’ and, from that point on, it will install the Windows version of the game and run it with Proton with no user interaction (other than clicking ‘Play’).
It isn’t nonsense, it makes perfect sense.
You can follow the error messages (which it prints to stdout when the game launches) and determine what the problem is so that you can fix it. The problem is completely understandable, the game logs would show exactly what device it was using and you could see what piece of software is responsible and go and look at the online documentation for that project to determine the exact configuration change that you need to make.
That’s how you should be troubleshooting problems, but you can’t do that on Windows because everything is a black box and provides little to no logs. If you’re lucky you’ll get an error message.
If you have a problem on Windows you first reboot and pray. Or, if that doesn’t fix it, you search random social media or forum posts, apply arbitrary registry changes recommended by Reddit comments, upgrade drivers, downgrade drivers, install motherboard firmware and dig through the various Windows GUI menus, which are change completely between Windows 8, 10 and 11 (but not 9, which doesn’t exist for some arbitrary reason), to locate a switch or checkbox that you can flip (and reboot again) until finally the problem resolves itself seemingly on its own. To me, this is the nonsense.
It shouldn’t require editing config files, except maybe in an Nvidia Optimus or AMD Switchable Graphics configuration. The fast/efficient GPU support was a dumpster fire the last time I had Linux on a laptop with it.
I know what Proton is.
No, it does not make perfect sense that a Linux native version of a game is more difficult to use than the Windows version on Proton. That may be how it is, but it does not make sense. Whatever method WINE or Proton uses to connect the Windows game to a supported graphics API in Linux must be entirely possible to do in a native Linux version of a game as well. For whatever reason, the game developers either chose not to or were incapable of developing that code.
At the third party application level, Windows applications are a black box. That has nothing to do with Windows, though. Complain to third party developers
It reads like you lack experience troubleshooting on Windows. If you’re praying to some higher power to make your software issues go away, you may also want to revaluate your troubleshooting methodology. Nearly everything you said can also apply to troubleshooting issues with Linux. Except for the whole skipping of “Windows 9”, which no one truly cares about.
You clearly feel a lot of hate towards Microsoft, and they certainly deserve a lot of it. However, it serves no purpose to resort to exaggeration and hyperbole.