WEBVTT 00:00.000 --> 00:13.300 Hello everyone, welcome to my talk about the state of gaming in FreeBasie. First, it was 00:13.300 --> 00:22.960 an introduction on Ramai, so I'm a FreeBasie user since the release of 9.2. I become part 00:23.040 --> 00:31.040 right now, since 2016, and as a professional career, I'm a C++ developer on some 00:31.040 --> 00:40.000 time Python 1. So in this talk, I will discuss several methods to play games on FreeBasie. 00:40.000 --> 00:47.760 I will first discuss how to leverage wine to play Windows games on FreeBasie. Then I will discuss 00:47.840 --> 00:54.320 both ways to use a Linux router to play the native Linux games. And finally, I will discuss 00:54.320 --> 01:02.560 the use of BI and GPU pass through to game on it. So let's start with wine. So in the Part 3, 01:02.560 --> 01:09.120 we have a Free version of wine. We have the Stable version of wine, which is the version 10.0. 01:10.000 --> 01:21.200 The developer on version, wine devils, which is i9.0.3. Having this variety of version, 01:21.200 --> 01:29.440 I always have more wider compatibility option when it comes to games, because sometimes a new 01:29.440 --> 01:38.960 version of wine will break a game compatibility. So we have some feedback. So on Windows, 01:40.160 --> 01:46.720 we have a lot of applications that are both 64 bits and 40 bits. Like for instance, for a game, 01:46.720 --> 01:52.640 you will have set up to install the game, but we will be 40 to bits executable. Why is a game 01:52.640 --> 02:05.600 itself? We will be 64 bit application. So how do we resolve this issue? We could use a 64 bit version 02:05.600 --> 02:16.480 of wine on the one path and the 40 to bits version on the other. But wine requires to have both 02:16.560 --> 02:24.000 version working two gaseers. And so this is what you have in the Part 3. So we install the 64 bit 02:24.000 --> 02:29.440 version of wine, which will be applied and we finance our tools, we install 40 to bits version 02:29.440 --> 02:39.600 inside the directory. So when you launch wine, what is actually happening is that you first launch 02:39.680 --> 02:46.960 the chasquite, that is located in the user local b, but if self will run another chasquite, 02:47.360 --> 02:54.400 that will be the 40 to bits content. So this one will be located in the home directory of the 02:54.400 --> 03:04.320 user and there the i386 pick a wine package directory, which then will run the 40 to bits 03:04.320 --> 03:12.000 binary executable. So in a free busy, when you run any Windows application full wine, 03:12.000 --> 03:19.120 you need to have the 40 to bits compatibility here be enabled and you need to be able to 03:19.120 --> 03:28.960 don't want the 40 to bits components. So how do we do that? So in the part of 03:28.960 --> 03:36.720 wine, we have a fine, we have a package 42 to attach and help us fit, that is located in the shared 03:36.720 --> 03:46.160 directory of wine, that we use internally a package to install the 40 to bits version of the 03:46.160 --> 03:55.280 fine inside a directory. To do that, we will tell a picadic to use another 03:55.280 --> 04:02.560 aviai. So instead we use the 60 for bits from the current vertex itself, we use the 40 to bits 04:02.560 --> 04:10.400 content. And the same for the root directory instead of using slash as a root, we tell picadic to 04:10.400 --> 04:22.160 install inside the home directory and our dot i386 wine package. So now what we have wine, 04:22.240 --> 04:31.280 install both in 60 for bits and in 30 to bits. How do we go from this state to running again? 04:31.840 --> 04:38.720 So first we will want to specify a prefix for a game and we will do that by running a wind 04:38.720 --> 04:47.360 config and specifying the prefix you select directory, you pass it in the wind wine prefix 04:47.360 --> 04:55.840 and we are not, and the wine wine CFG, this will pop up the wind configuration for your prefix 04:55.840 --> 05:03.360 and you press OK. Once you're done that, you can install the XVK and picadic freely, which are 05:04.480 --> 05:14.160 compatibility dials for direct freely from 9 to 12, but we will use a velcan instead. 05:15.040 --> 05:21.120 And so you also need to install windfacts and so on. Finally, you just have to launch a 05:21.120 --> 05:31.600 seller like any application and as an optional step, you can configure the game controller, 05:31.600 --> 05:39.680 this game controller settings for making sure that your controller is properly detected. 05:39.760 --> 05:47.840 And finally, you can load the game. So for the controller, we have multiple options. So here, 05:47.840 --> 05:56.560 I have dual-sense controller. The total requirement to select the XDL driver for the controller 05:56.560 --> 06:05.760 and disable the HCI-DL drivers. So if I disable the HCI-DL and enable the XDL driver, 06:06.480 --> 06:13.120 my controller is properly detected as an X input device, which as you can see, 06:13.840 --> 06:20.400 register the axis movement here in the screen and the button crisis. 06:21.520 --> 06:28.240 And as I said, I note, we can associate that wine, I'm implement the Windows gaming input API 06:28.240 --> 06:37.360 and Vatitize property or just a red here. So now I'll show you some demonstration of wine working. 06:37.360 --> 06:46.560 So here, Vatitize set, seller point, 2,000, 7,000, 7, Vatize running out of the box by using wine 06:47.280 --> 06:53.120 so you have no additional step, then the previous one. 06:54.880 --> 07:00.240 And here, we can see that the game works perfectly fine, same as for example, 07:00.240 --> 07:08.800 all night section, but was working right after release. So no additional fix needed to be done. 07:09.760 --> 07:18.240 Same for Skyrim, the just role 5 and the role 4 work as well with Vatitize and some of their game 07:18.240 --> 07:27.200 too. Now I will discuss how we use a Linuxulator to play Linux games on a free list. 07:28.480 --> 07:36.560 So it's the same step, except instead of installing wine, we enable the compatibility layer for Linux 07:37.520 --> 07:50.720 which require you to enable the Linux service in a RC.D or just call the Linux module and 07:50.720 --> 07:56.720 mooting the correct file system. Once this is done, you can install the Linux 07:56.720 --> 08:03.680 base which is from Ok Linux 9 which is now the default on FreeBanset and then you can just install 08:03.680 --> 08:11.360 your Linux game which usually is a chess script, but we just exploit the game into a directory like 08:11.360 --> 08:19.600 what DOD is only. And then you just need to correct the pre-bung and the chess script at 08:19.680 --> 08:26.880 start the game because usually you use a bin bash as a path, but you want to use the one from the 08:26.880 --> 08:35.280 Linux Linux to the tower, so you need to be as compact Linux bin bash. So once you 08:36.000 --> 08:45.280 do all this change, you can directly run your game, but of course it was really right. So you have 08:45.360 --> 08:53.840 some difficulty, if you have an Nvidia cards, in addition to the Nvidia driver for FreeBanset, 08:53.840 --> 08:59.200 for the rest, you also need to install the Linux Nvidia Lips corresponding to your driver. 09:00.480 --> 09:06.800 So not so difficult, you just install the package, it's available. The difficult part is when you have 09:06.880 --> 09:12.800 a driver, it's based on my app, so for this you may need to apply one of the two patch, 09:14.240 --> 09:26.160 for allowing a Linux CSFS, which is a Linux module that allows you to have the DRAM node, 09:27.120 --> 09:34.560 the SHDF Sajui, 4-0, and Ronda Rd, and of course on the competitive bit of the year, 09:34.560 --> 09:44.800 to be in SHDF Sajui. So the Ronda node are missing, actually, on any FreeBanset. So you need to apply 09:44.800 --> 09:52.240 your patch, as games won't recognize the GPU acceleration on certain difficulties. Not all of them, 09:52.800 --> 09:59.680 some Intel GPU just work, but not all of them, and same for MDGPU. So once you're 09:59.680 --> 10:08.400 dosat, your game will have a GPU acceleration. I will now then discuss another method that 10:08.400 --> 10:15.360 is using the Linux Timutrize, which is a package that allows to run the team, client, 10:16.320 --> 10:23.040 on a FreeBanset, by using the Linux Timutrize, and applying a set of work-around 10:23.040 --> 10:29.680 around it. The first notable work-around is that it's fixed the GPU acceleration issue, 10:29.680 --> 10:36.720 so you don't need the previous patch, because it does it in a user-land. So you use the FreeBanset driver 10:36.720 --> 10:44.080 in SHDF, to parse the DRM config, to know which, which Dreen node, and is associated with which 10:44.080 --> 10:51.680 Ronda Rd node, and right to reconstruct the correct character of the race. In addition, 10:51.680 --> 10:59.440 it can use short, unrivileged functionality, functionality in FreeBanset, 10:59.440 --> 11:08.960 but allow a normal user to shoot into a directory, to use the system on runtime. So it will 11:08.960 --> 11:17.200 be called LSU, shoot in or case. And finally, it will always play Windows game via WineProton, 11:17.200 --> 11:26.560 which is a fork of Wine from Wive. And the project, the project Github pages, you can find 11:26.560 --> 11:33.840 a little fix for a gamepad detection, so it will fix the permission of any gamepad connected 11:35.120 --> 11:45.280 on the system on the Linux compatibility layer. And how you go from not having to seem, it's simple, 11:45.280 --> 11:50.640 enable Linux onpad, and install the packages. You will read the entire, you will enter your 11:50.720 --> 11:57.120 read me on the Github page, you follow the instructions, and then you run Steam. And it will 11:57.120 --> 12:06.640 it will run, you can see some examples. So here you have the system client, and we will go to 12:06.640 --> 12:13.040 see the compatibility option. So here you have game, but you select the LSU shoot runtime sniper. 12:14.000 --> 12:19.920 And you can see here, in fact, the game run, and you may see a sense of controller, 12:19.920 --> 12:25.440 where it's correctly detected, and you can see that in-game footage, that's the game, 12:25.440 --> 12:33.600 and I think it's perfectly fine. Same as for don't staff, too, Github. And you can also 12:34.000 --> 12:40.640 leverage WineProton to run Steam games, which are only available on Windows. And here is the same 12:40.800 --> 12:49.760 story. My controller is still detected, and the game run perfectly fine. And you can run all 12:49.760 --> 12:58.960 the games. So in case where the game won't work on Windows, particularly for games that use 12:58.960 --> 13:07.520 anti-tits at far, you may need to use virtual machine for it. So with BI, you will be able to run 13:07.600 --> 13:15.280 Linux game, and have proper GPU acceleration by using GPU password. So here, how I do. 13:15.280 --> 13:24.320 So I will use a VM BI to create a config for my VM. I will set the password device for my GPU 13:24.320 --> 13:31.600 for the audio on my GPU, and one USB controller. So what I will be able to attach my keyboard, 13:31.680 --> 13:42.560 my mouse, even my controller, I have all sorts of buttons for the device. And I have some 13:42.560 --> 13:49.040 script, but I will need to prepare my system for the next boot. So if it starts the VM, 13:49.760 --> 13:56.800 and take control of monitors and then as the next boot, it will be a free-daiser again. 13:57.120 --> 14:08.480 So the step as simple, you will launch the script to enable the game in the VM. As 14:08.480 --> 14:15.280 root, you reboot the system, and once you reboot your system, the monitors are connected to the 14:15.280 --> 14:23.280 GPU. We will be able to control it by the VM, and same for the keyboard and mouse, and mouse, 14:23.520 --> 14:33.360 that are connected to the USB controller, but it just password. So if you have two monitors, 14:33.360 --> 14:39.600 you can have one monitor on the VM, those are on the GPU, so you will be the free-daisers, 14:39.600 --> 14:46.880 and you will be able to run a desktop session for both the VM and the free-daisers at the same time. 14:47.760 --> 14:54.240 And for this, KVM will be easier, since you can connect it to two separate USB controller. 14:57.360 --> 15:09.280 And as you can see, in my VM, my GPU is quite detective. X7, 4, and 8, 100x, and you can see the model 15:09.280 --> 15:14.800 of the free-daiser guide, so it's a free-daiser machine. And that game is like Elder Ring, 15:14.800 --> 15:21.280 which is easy on the cheat, is working perfectly fine, and sometimes with the player seems to work 15:21.280 --> 15:28.800 since some user can connect to it. And Badger's guide free, but I didn't succeed to make running 15:29.120 --> 15:35.760 unwind or just unwind, because there is more the next native version. Worked as well, 15:36.880 --> 15:42.240 and so on and so on and so on and so on. It's working perfectly fine on V7. 15:44.320 --> 15:50.640 In conclusion, gaming and free-daisers can be achieved by multiple means. One means, 15:50.640 --> 15:56.080 what I did on this course is just running an open source game, a directee and free-daisers, 15:56.880 --> 16:05.120 super-tossed cards, z-y-y-d, megagress, etc. Or some just open source-on-jings like Open Moro-Win, 16:05.120 --> 16:11.680 for an instance. You can use Nikon-Fage-Wine to play Windows Game, or you can use the Linux 16:12.000 --> 16:26.880 game, and finally, you can run your game through BI, with the P-Pastro, to pay your game 16:26.880 --> 16:37.120 only next, and I guess you'd really unwind us, but I didn't test it. And there is other tools too, 16:37.200 --> 16:43.520 that I did on this course, for instance, very mid-sumary, which is a fontan to Wine, 16:43.520 --> 16:49.600 but I have some pre-configuration, but we'll install with Wine Tricks, some components, 16:49.600 --> 16:58.000 so I'd are known to be required for it's game, which is an ice tool, and you can also use 16:58.880 --> 17:06.720 cloud computing for gaming from your browser, or maybe trying running the Windows application 17:06.800 --> 17:12.400 through Wine, and play like that. Thank you for your attention. 17:28.640 --> 17:33.600 Okay, the question was, do I provide the new world 64, I guess, not the old one? 17:34.320 --> 17:47.600 Okay, for the new world 64, there is Wine Python 10.0, which is a waiting review in a pair 17:47.600 --> 18:00.960 that have the new mod, and there is one attempt of Wine for the version 10.8 from another 18:00.960 --> 18:10.640 computer, which is the one that do in XML, and you can use Wine exclusively exclusively in a new 18:10.640 --> 18:18.400 mod, in a new world 64, but for the next version, I didn't succeed in having a Wine that 18:18.480 --> 18:26.240 worked in the sick fault every time, so it's a lot of SMAs and Liwa, for that. 18:31.040 --> 18:35.200 And how, so I know it's not currently possible that, but you said I've asked a little bit, 18:35.200 --> 18:41.760 but I'll think about what it is, I'd like to single use Wine, but you don't have to 18:41.920 --> 18:53.120 use Wine. The question was, how to do with single GPU system, integrated or 18:53.120 --> 19:04.560 discrete, for discrete GPU, like if you have a system with a CPU, we thought an integrated GPU 19:04.640 --> 19:14.400 and a DGPU, for me, it should work, because when you start FUBAZ, you lose the console at some point, 19:14.400 --> 19:23.920 and it will divide to the VM, so in this case it should work, for HGPU, some people have 19:23.920 --> 19:32.560 tested, but there is solo show with the RAM and memory region, there is backup automation, 19:33.520 --> 19:37.520 and this, so maybe I have custom patch to do that. 19:41.920 --> 19:50.160 Hey Yumi, we will see you in the next video, thank you very much.