WINE updated to version 3.0 – Great update for Gamers thanks to Direct3D 10 and 11 support and more!
Linux and MacOS users rejoice as your favourite game may now be playable without having to boot into Windows. Thanks to the hard work of the WINE team and many contributors, we now have WINE 3.0 to give us a better Linux/Mac gaming experience!
What is WINE? Why should I be interested in it?
WINE is an emulation layer for Windows applications/games that runs on most Linux distributions and MacOS. It’s been in active development for years upon years and with various free companion applications such as PlayOnLinux and PlayOnMac, it’s also been made available for non-techy people that don’t like the idea of tinkering too much.
Thanks to WINE, you can migrate to Linux or MacOS and still keep on using your favourite applications and games. While game compatibility wasn’t always the best, it’s greatly improved over the past 2 years so if you’re not much of a heavy gamer, WINE may actually be enough for your gaming needs. Popular titles like Overwatch are now said to be playable but your mileage may vary as always.
What got added/updated in version 3.0?
WINE version 3.0 brings about the following important features:
- Direct3D 10 and 11 support so you can play games that require Windows Vista and newer.
- Direct3D command stream.
- Improved DirectWrite and Direct2D support for better performance in your 2D games.
- Windows 7 is now the default version reported to applications when running/installing them.
- Applications now look much better on HiDPI displays
- Much more
As you can see, this is a pretty major update and may potentially fix some games that were previously buggy or unplayable so it is recommended you grab it ASAP.
Conclusion
To get WINE 3.0, you can use your Linux distro’s package or update manager or you can wait for the companion application you use to be updated to automatically grab the required files. If you have issues, report them on WINE’s bugzilla.
WINEHQ (everything you need about WINE + links to bug reporting): https://www.winehq.org
The compatibility list which is constantly updated: https://appdb.winehq.org
Changelog source (with more info from OMGUBUNTU!): https://www.winehq.org/news/2018011801
“WINE is an emulation layer for Windows applications/games”
Wrong, as stated by its own acronym, Wine Is Not an Emulator ! It’s a compatibility layer that translates windows calls to Linux / Mac kernel calls. It does not emulate windows in a technical meaning. That also means that little performance is lost through it, unlike with emulation where a big performance loss is visible. (Hope you just fix the part soon 🙂 )
Still, great news ! DirectX 11 support is a major step forward for games.
I knew there would be a comment like that when I read it, but I agree with you and I would have typed it if you didnt
Yeah, you really can’t go around calling WINE an emulator. The target audience will know better and correct you immediately XD
NICE!
Wine Is Not (an) Emulator –> W-I-N-E
Wine Is Not (an) Emulator = WINE
Wine Is Not (an) Emulator –> W-I-N-E
Good name. “Wine is not an emulator” is a stupid and somewhat inaccurate phrase. It may not be a HARDWARE emulator, but it certainly emulates the main windows functionality on non-windows devices. (Running windows programs.)
ALL emulators are a “compatibility layer” for software for another system. That’s basically the core concept and main point of an emulator. Wine is most certainly an emulator. It emulates windows functionality by translating it for other API systems to understand.
Wine is not a hardware emulator, but it’s most certainly a windows functionality emulator. It emulates Windows’ main feature of running windows programs built for windows API and programming.
This is not correct and the phrase is accurate. To be considered an “emulator” it has to be emulating a system of different architecture, such as MIPS to x86, ARM to x86, etc. When it’s running the same type of architecture, such as an x86-64 Ubuntu virtual machine running within x86-64 Windows 10, they’re the same architecture, so this is “virtualization” rather than “emulation.”
However, WINE is neither virtualization nor emulation. It’s using APIs to translate the system calls on-the-fly. I think what you’re trying to say is that it “simulates” windows functionality, but even that wouldn’t be technically accurate, as it’s still delivering the same system calls, it’s just operating as a compatibility layer in-between.
I have one question can i use wine with linux on ps4 4,05 and play pc games?
Thanks in advance.
Try it out if you already know how to run Linux on that firmware it wouldn’t hurt anything it’ll either run or it wont
As the others write, WINE is not an emulator…which exactly boils down to your question.
WINE is a compatibility layer roughly translating windows to linux system calls.
That alone won’t let you CPU dependent stuff like x86/x64 on non for example, you would need an emulation.This can be done using for example Bochs to emulate the CPU part. This is already done for Android/ARM or on PowerPC for example.
As the PS4 has a x64-CPU, there should be no problem running PC games with WINE once all the drivers are working properly as for example GPU acceleration.
hey that s a good idea to try man
I don’t see why not. Especially with this update, it should be so much less of a headache to accomplish than with previous versions. But of course, YMMV.
As far as I’m aware WINE only runs on an x86 CPU hence why it isn’t an emulator.
That’s a doodley,
zsnes, and cemu both run on x86 cpu’s and ARE emulators(there is a lot more)(they also emulate the whole system(cpu,gpu,ram,filestorage,etc) because your computer does not have the hardware that a real console has in it)
Wine however runs on x86 and x86_64 cpus’s but is not emulating a whole x86 chip, it’s just translating calls windows makes(because your system DOES have the hardware in it to run windows)
(example: hey directx, display THIS object HERE, wine interrupts seeing this command happen and quickly writes an OpenGL command that accomplishes the same task)
and to quote you, “hence why its not an emulator”
Witch version of wine would-be used in basiliskii-vita and weer to download?
I don’t have ps4 with 4.05 fw, mine is with newest fw, can someone with 4,05 fw try and share results
I don’t have ps4 with 4.05 fw, mine is with newest fw, can someone wit05 fw try and share results
This post is really so much helpful thanks for the post. i have no idea about such kind of item . i know it from your post
A couple issues – first one is that WINE is a compatibility layer, not an emulator. Two, it wasn’t purely WINE team’s work, but most of the underlaying code for D3D10 and D3D11 was provided by CodeWeavers, developers of a bit more advanced CrossOver (which is a compatibility layer as well) and they made those parts of their code open-source and contributed to the project.
Please get that stuff fixed.
#would wine via em-sdk do the same as em-wine or em-dosbox if i did …
sudo apt-get update
sudo apt-get install build-essential
sudo apt-get install cmake
sudo apt-get install python2.7 python-minimal
sudo apt-get install nodejs
sudo apt-get install default-jre
sudo apt-get install git-core
sudo apt-get install libsdl1.2-dev libsdl1.2debian libsdl-image1.2-dev
#now git clone emsdk
wget https://s3.amazonaws.com/mozilla-games/emscripten/releases/emsdk-portable.tar.gz
tar -xvf emsdk-portable.tar.gz
cd emsdk-portable
./emsdk update
./emsdk install latest
./emsdk activate latest
source ./emsdk_env.sh
edit exports paths and variables correctly in .bashrc (correct paths)
export EMSCRIPTEN=/PATH/TO/emsdk/emscripten/master
export EMSCRIPTEN_ROOT=$EMSCRIPTEN:
export PATH=$PATH:$EMSCRIPTEN:
Part 2: Install em-dosbox
After you are sure that emcc shows no errors or warnings, let’s clone em-dosbox. You will need automake & autoconf packages installed
sudo apt-get install autoconf
git clone https://github.com/dreamlayers/em-dosbox.git
cd into em-dosbox
following commands are better run in bash as root (do exactly as it is listed below)
sudo -s
./autogen.sh
emconfigure ./configure
make
if u finally compiled em-dosbox go figure why the blocks.exe dont work in ur browser lol
Run ./packager.py blocks blocks.exe
It should create blocks.html file
cd to /src folder
python -m SimpleHTTPServer
in browser go to localhost:8000/dropbox.html
now u are ready to install em-wine or payload-sdk as u
managed to install a good llvm+clang+payloadsdk so u can load compile
Great news! It may now be playable without having to boot into Windows!