I guess, I would need it to utilize my Logitech-Extreme 3D Pro in flightgear.Joytran does what you want.
poot@E6420:~/SDLjoy/SDLJoytest-GL # SDLJoytest-GL
Found 1 joystick(s) on this system.
Joystick 0
Name:.........Game_Pad (0)
Axes: 6
TrackBalls:...0
Buttons: 11
Which Joystick do you want to use(0 - 0):
0
Joystick 0:Game_Pad (0) selected.
Screen resolution set to: 640x480x32bpp
I guess, I would need it to utilize my Logitech-Extreme 3D Pro in flightgear.
ATM, I'm getting (simulated) pilot training with fgfs, so the joystick would help.
I'll try the joytran and see if it works for me.
See this patch, which in turn is based on https://reviews.freebsd.org/D16830. Although I would rather recommend you to try my previous approach to enabling wow64…
…10 months. Does anybody here actually want WoW64 Wine or not?
So yes, I would like to see all the advancements of wine for Linux to be available for FreeBSD as well. So please, anyone who can do something to port all necessary stuff for wine, please do.
I guess, I would need it to utilize my Logitech-Extreme 3D Pro in flightgear.
ATM, I'm getting (simulated) pilot training with fgfs, so the joystick would help.
I'll try the joytran and see if it works for me.
Now, I'll be waisting my time with flightgear, instead of learning FreeBSD
Ah, you are actually aren't talking about Proton… WoW64 doesn't need any porting from Linux, it's an inherent part of 64-bit Wine. It's not enabled simply because our Ports Collection build process for Wine is a mess.
The second sentence "It's not enabled ..." is the problem then I am talking about. So is something being done / can something be done to solve the problem in order to enable WoW64 in 64-bit wine? At this point I would also like to ask, now that you have mentioned it: What about proton and dxvk? Does that work on FreeBSD and what is the status of those two things on FreeBSD?
So is something being done / can something be done to solve the problem in order to enable WoW64 in 64-bit wine?
At this point I would also like to ask, now that you have mentioned it: What about proton and dxvk? Does that work on FreeBSD and what is the status of those two things on FreeBSD?
Well, had you taken your time to read and understand the discussion(s) I referred earlier in this thread, specifically D14721 and D16830, then you would know that I'm already sitting on what I consider a complete and proper solution to the WoW64 Wine problem for quite some time. Patches, however, do not commit or review themselves.
dxvk and d9vk work fine for me, no Proton for now.
Well then thank you so much for working on that! So when do you think that great work of yours will be done and available to the end-user? Half a year or year maybe? I am really looking forward to it!
Well, what things you are actually expecting to get from the Linux client (as opposed to running its Windows counterpart under Wine)? This is often repeated complaint, but I don't really understand the motivation.
On the other hand, Linux games under FreeBSD work so well and with astonishing performance in comparison to DirectX games in wine, that the desire to have the linux steam client working under FreeBSD is not only understandable but also rather promising in the sense that the games would actually work (not just the client) and with much better performance.
From the FreeBSD ports repository
i386-wine-4.0.1,1
i386-wine-devel-4.11,1
wine-4.0.1,1
wine-devel-4.11,1
From the Wine website
Latest Releases
Stable:
Wine 4.0.1 (shortlog)
Development:
Wine 4.11 (shortlog)
So, the latest wine version can be compiled and run on FreeBSD. Both version numbers are in sync (cfr. your earlier question).
Why do you want wine 4.2 if you can have wine 4.11? For the record I don't know if it has vulkan support, but just saying that it is the latest version.
This isn't talking about Proton though, which is a Valve distribution of Wine with DXVK and some other changes.
That piece of software isn't ported to FreeBSD, probably in part because it uses a lot of Linux-centric scripts to do the building. Reminds me of Google projects
shkhln we were basically typing the same things so I cut it off here.Also, you have a double postYou were right about that ajax issue
$ pkg search wine
i386-wine-3.0.4_1,1 32-bit Microsoft Windows compatibility environment for 64-bit FreeBSD
i386-wine-devel-4.0.r1_1,1 32-bit Microsoft Windows compatibility environment for 64-bit FreeBSD
py27-twine-1.13.0_1 Collection of utilities for interacting with PyPI
py36-twine-1.13.0_1 Collection of utilities for interacting with PyPI
wine-4.0.2,1 Microsoft Windows compatibility environment
wine-devel-4.15,1 Microsoft Windows compatibility environment
wine-gecko-2.47 Gecko Layout Engine for Wine (HTML support)
wine-gecko-devel-2.47 Gecko Layout Engine for Wine development branch (HTML support)
wine-mono-4.7.5 Mono .NET implementation for Wine development branch (HTML support)
wine-mono-devel-4.9.2 Mono .NET implementation for Wine development branch (HTML support)
winetricks-20190615 Easy way to work around problems in Wine
$
if you personally want to see just how much Linux games suck under FreeBSD (and in general), today is your lucky day: https://github.com/shkhln/linuxulator-steam-utils.
Even gaming on CentOS is a lottery as some games want newer libstdc++.
That's completely untrue. Anyway, if you personally want to see just how much Linux games suck under FreeBSD (and in general), today is your lucky day:
It is amusing how often people claiming "I need X by yesterday!" drop the subject entirely when offered "Here's how to do X" advice.
I was referring to Linux Games like Doom3, Quake4, UT2004, linux-et, ETQW, etc.
That has nothing to do with the Linux-Steam-Client.
I am not dropping the subject, but as I can see from the description it looks that in the end games do not work, right?
But ports do not have a newest 4.0, 4.2 WINE with Vulkan or DX12 support. And FreeBSD need a dedicated driver for Graphic.
And how about "borrowed" games you know, securities.
View: https://www.youtube.com/watch?v=TYmSoEhJL18
- IDK.