Hello everyone, welcome to my talk about the state of gaming in FreeBasie. First, it was
an introduction on Ramai, so I'm a FreeBasie user since the release of 9.2. I become part
right now, since 2016, and as a professional career, I'm a C++ developer on some
time Python 1. So in this talk, I will discuss several methods to play games on FreeBasie.
I will first discuss how to leverage wine to play Windows games on FreeBasie. Then I will discuss
both ways to use a Linux router to play the native Linux games. And finally, I will discuss
the use of BI and GPU pass through to game on it. So let's start with wine. So in the Part 3,
we have a Free version of wine. We have the Stable version of wine, which is the version 10.0.
The developer on version, wine devils, which is i9.0.3. Having this variety of version,
I always have more wider compatibility option when it comes to games, because sometimes a new
version of wine will break a game compatibility. So we have some feedback. So on Windows,
we have a lot of applications that are both 64 bits and 40 bits. Like for instance, for a game,
you will have set up to install the game, but we will be 40 to bits executable. Why is a game
itself? We will be 64 bit application. So how do we resolve this issue? We could use a 64 bit version
of wine on the one path and the 40 to bits version on the other. But wine requires to have both
version working two gaseers. And so this is what you have in the Part 3. So we install the 64 bit
version of wine, which will be applied and we finance our tools, we install 40 to bits version
inside the directory. So when you launch wine, what is actually happening is that you first launch
the chasquite, that is located in the user local b, but if self will run another chasquite,
that will be the 40 to bits content. So this one will be located in the home directory of the
user and there the i386 pick a wine package directory, which then will run the 40 to bits
binary executable. So in a free busy, when you run any Windows application full wine,
you need to have the 40 to bits compatibility here be enabled and you need to be able to
don't want the 40 to bits components. So how do we do that? So in the part of
wine, we have a fine, we have a package 42 to attach and help us fit, that is located in the shared
directory of wine, that we use internally a package to install the 40 to bits version of the
fine inside a directory. To do that, we will tell a picadic to use another
aviai. So instead we use the 60 for bits from the current vertex itself, we use the 40 to bits
content. And the same for the root directory instead of using slash as a root, we tell picadic to
install inside the home directory and our dot i386 wine package. So now what we have wine,
install both in 60 for bits and in 30 to bits. How do we go from this state to running again?
So first we will want to specify a prefix for a game and we will do that by running a wind
config and specifying the prefix you select directory, you pass it in the wind wine prefix
and we are not, and the wine wine CFG, this will pop up the wind configuration for your prefix
and you press OK. Once you're done that, you can install the XVK and picadic freely, which are
compatibility dials for direct freely from 9 to 12, but we will use a velcan instead.
And so you also need to install windfacts and so on. Finally, you just have to launch a
seller like any application and as an optional step, you can configure the game controller,
this game controller settings for making sure that your controller is properly detected.
And finally, you can load the game. So for the controller, we have multiple options. So here,
I have dual-sense controller. The total requirement to select the XDL driver for the controller
and disable the HCI-DL drivers. So if I disable the HCI-DL and enable the XDL driver,
my controller is properly detected as an X input device, which as you can see,
register the axis movement here in the screen and the button crisis.
And as I said, I note, we can associate that wine, I'm implement the Windows gaming input API
and Vatitize property or just a red here. So now I'll show you some demonstration of wine working.
So here, Vatitize set, seller point, 2,000, 7,000, 7, Vatize running out of the box by using wine
so you have no additional step, then the previous one.
And here, we can see that the game works perfectly fine, same as for example,
all night section, but was working right after release. So no additional fix needed to be done.
Same for Skyrim, the just role 5 and the role 4 work as well with Vatitize and some of their game
too. Now I will discuss how we use a Linuxulator to play Linux games on a free list.
So it's the same step, except instead of installing wine, we enable the compatibility layer for Linux
which require you to enable the Linux service in a RC.D or just call the Linux module and
mooting the correct file system. Once this is done, you can install the Linux
base which is from Ok Linux 9 which is now the default on FreeBanset and then you can just install
your Linux game which usually is a chess script, but we just exploit the game into a directory like
what DOD is only. And then you just need to correct the pre-bung and the chess script at
start the game because usually you use a bin bash as a path, but you want to use the one from the
Linux Linux to the tower, so you need to be as compact Linux bin bash. So once you
do all this change, you can directly run your game, but of course it was really right. So you have
some difficulty, if you have an Nvidia cards, in addition to the Nvidia driver for FreeBanset,
for the rest, you also need to install the Linux Nvidia Lips corresponding to your driver.
So not so difficult, you just install the package, it's available. The difficult part is when you have
a driver, it's based on my app, so for this you may need to apply one of the two patch,
for allowing a Linux CSFS, which is a Linux module that allows you to have the DRAM node,
the SHDF Sajui, 4-0, and Ronda Rd, and of course on the competitive bit of the year,
to be in SHDF Sajui. So the Ronda node are missing, actually, on any FreeBanset. So you need to apply
your patch, as games won't recognize the GPU acceleration on certain difficulties. Not all of them,
some Intel GPU just work, but not all of them, and same for MDGPU. So once you're
dosat, your game will have a GPU acceleration. I will now then discuss another method that
is using the Linux Timutrize, which is a package that allows to run the team, client,
on a FreeBanset, by using the Linux Timutrize, and applying a set of work-around
around it. The first notable work-around is that it's fixed the GPU acceleration issue,
so you don't need the previous patch, because it does it in a user-land. So you use the FreeBanset driver
in SHDF, to parse the DRM config, to know which, which Dreen node, and is associated with which
Ronda Rd node, and right to reconstruct the correct character of the race. In addition,
it can use short, unrivileged functionality, functionality in FreeBanset,
but allow a normal user to shoot into a directory, to use the system on runtime. So it will
be called LSU, shoot in or case. And finally, it will always play Windows game via WineProton,
which is a fork of Wine from Wive. And the project, the project Github pages, you can find
a little fix for a gamepad detection, so it will fix the permission of any gamepad connected
on the system on the Linux compatibility layer. And how you go from not having to seem, it's simple,
enable Linux onpad, and install the packages. You will read the entire, you will enter your
read me on the Github page, you follow the instructions, and then you run Steam. And it will
it will run, you can see some examples. So here you have the system client, and we will go to
see the compatibility option. So here you have game, but you select the LSU shoot runtime sniper.
And you can see here, in fact, the game run, and you may see a sense of controller,
where it's correctly detected, and you can see that in-game footage, that's the game,
and I think it's perfectly fine. Same as for don't staff, too, Github. And you can also
leverage WineProton to run Steam games, which are only available on Windows. And here is the same
story. My controller is still detected, and the game run perfectly fine. And you can run all
the games. So in case where the game won't work on Windows, particularly for games that use
anti-tits at far, you may need to use virtual machine for it. So with BI, you will be able to run
Linux game, and have proper GPU acceleration by using GPU password. So here, how I do.
So I will use a VM BI to create a config for my VM. I will set the password device for my GPU
for the audio on my GPU, and one USB controller. So what I will be able to attach my keyboard,
my mouse, even my controller, I have all sorts of buttons for the device. And I have some
script, but I will need to prepare my system for the next boot. So if it starts the VM,
and take control of monitors and then as the next boot, it will be a free-daiser again.
So the step as simple, you will launch the script to enable the game in the VM. As
root, you reboot the system, and once you reboot your system, the monitors are connected to the
GPU. We will be able to control it by the VM, and same for the keyboard and mouse, and mouse,
that are connected to the USB controller, but it just password. So if you have two monitors,
you can have one monitor on the VM, those are on the GPU, so you will be the free-daisers,
and you will be able to run a desktop session for both the VM and the free-daisers at the same time.
And for this, KVM will be easier, since you can connect it to two separate USB controller.
And as you can see, in my VM, my GPU is quite detective. X7, 4, and 8, 100x, and you can see the model
of the free-daiser guide, so it's a free-daiser machine. And that game is like Elder Ring,
which is easy on the cheat, is working perfectly fine, and sometimes with the player seems to work
since some user can connect to it. And Badger's guide free, but I didn't succeed to make running
unwind or just unwind, because there is more the next native version. Worked as well,
and so on and so on and so on and so on. It's working perfectly fine on V7.
In conclusion, gaming and free-daisers can be achieved by multiple means. One means,
what I did on this course is just running an open source game, a directee and free-daisers,
super-tossed cards, z-y-y-d, megagress, etc. Or some just open source-on-jings like Open Moro-Win,
for an instance. You can use Nikon-Fage-Wine to play Windows Game, or you can use the Linux
game, and finally, you can run your game through BI, with the P-Pastro, to pay your game
only next, and I guess you'd really unwind us, but I didn't test it. And there is other tools too,
that I did on this course, for instance, very mid-sumary, which is a fontan to Wine,
but I have some pre-configuration, but we'll install with Wine Tricks, some components,
so I'd are known to be required for it's game, which is an ice tool, and you can also use
cloud computing for gaming from your browser, or maybe trying running the Windows application
through Wine, and play like that. Thank you for your attention.
Okay, the question was, do I provide the new world 64, I guess, not the old one?
Okay, for the new world 64, there is Wine Python 10.0, which is a waiting review in a pair
that have the new mod, and there is one attempt of Wine for the version 10.8 from another
computer, which is the one that do in XML, and you can use Wine exclusively exclusively in a new
mod, in a new world 64, but for the next version, I didn't succeed in having a Wine that
worked in the sick fault every time, so it's a lot of SMAs and Liwa, for that.
And how, so I know it's not currently possible that, but you said I've asked a little bit,
but I'll think about what it is, I'd like to single use Wine, but you don't have to
use Wine. The question was, how to do with single GPU system, integrated or
discrete, for discrete GPU, like if you have a system with a CPU, we thought an integrated GPU
and a DGPU, for me, it should work, because when you start FUBAZ, you lose the console at some point,
and it will divide to the VM, so in this case it should work, for HGPU, some people have
tested, but there is solo show with the RAM and memory region, there is backup automation,
and this, so maybe I have custom patch to do that.
Hey Yumi, we will see you in the next video, thank you very much.