I did some free flights over the Caucasus and Marianas in the Warthog, Hornet, and Huey.
1080p, all settings pretty much on ultra. Works fine it seems. I had one crash (in the encyclopedia 
)
The only strange thing I noticed was chimney smoke, which looks a bit puffy. But that’s it so far.
3 Likes
Awesome! Just got DCS Standalone to run through Proton via Steam. I need Proton instead of Lutris’ Wine for VR.
Performance is no issue. (130-180 fps over Tbilisi with High preset @ 1440p)
I found the Hoggit wiki to have some good tips on udev rules:
https://wiki.hoggitworld.com/view/DCS_on_linux
Q: The contrails are puffy?
A: This is a known and persistent problem. Unfortunately there is no fix available. Hopefully this will be fixed with the introduction of Vulkan to DCS.
2 Likes
Funnily enough the contrails look fine for me, and so do explosions, smoke from fires etc, as far as I can tell at this point. It is only the smoke from the chimneys:
It is puffy but broken up instead of a steady column, and it blows away horizontally as if there was a very strong wind.
I’ll have some more time to check it at the weekend.
1 Like
Small wins today:
The chimney smoke is also OK now.
The Thrustmaster TWCS that I borrowed from a family member works fine. I’ll probably get one so I’ll have a HOTAS again.
Flew around a bit in the Warthog. I still have a lot of the switchology memorized as it turns out, but the muscle memory fails now because of the new HOTAS. Grml, that will take a while.
2 Likes
What did you do? Was it just a shader recompile or did you add some winetricks?
I first ignored the issue, flew around in the A-10 and configured my HOTAS. I tabbed out of the sim a few times to look up stuff.
Then I tabbed back in and flew some more. When I slewed around the TGP for testing I noticed a chimney with smoke and that it looked good.
So… sorry, I have no clue what I did.
2 Likes
Today I did something completely unrelated:
I checked if my new Linux rig is also usable for music. So I installed the the DAW software called Reaper (thanks again @sobek for recommending it), put my license key in, and it almost worked out of the box.
Just the ALSA configuration was not intuitive.
I had to manually enter the word “default” twice (for input and output device) because for some reason the dropdown box didn’t work (and PulseAudio has too much delay) or it won’t find the sound card.
Now I can record and play back stuff, and use Reaper normally. I haven’t done a lot with it yet though. Latency sounds OK-ish but I haven’t measured it yet.
I will test my MIDI interface and external audio interface soon, although I don’t have much hope that the latter will work. It is old.
2 Likes
IME, older hardware tends to be better supported by open source software than brand new. GPUs are the exception
2 Likes
And another small win:
I just installed the FFB driver for the TM150 wheel, and tested it in BeamNG drive.
Works fine it seems. 
EDIT: Command used was just this: paru t150_driver-dkms-git
2 Likes
With the help of some of the kindest nerds I’ve never met in the Linux VR Adventures community, I was able to launch DCS on my Reverb G2 directly with OpenXR on Linux! Haven’t had time to do a flight yet as I had to get up early this morning.
Next I need to write down exactly how I did this for the “Reverb life extension” guide.
All I need now is the controllers and I’m set to delete Windows.
EDIT: installing basalt and cjson seems to have done the trick
3 Likes
Has anyone had any experience running Windows apps in containers or a virtual machine under a flavour of desktop Linux (Ubuntu, Mint, CatchyOS, etc)?
I’ve been playing with Proxmox and really like it for what it offers, but it’s not really going to work for me as a desktop OS. I also saw Looking Glass, and unless anyone has a better suggestion I’ll probably try that out on Catchy or Arch to see how that feels…
I run a Win VM at work for when i need to quickly test or debug a MSVC build.
1 Like
On your workstation? What are you using to run the VM, and would you recommend it for a home user?
1 Like
I use gnome boxes, which uses qemu under the hood. It’s very easy to use, except for when you need TPM 2 (Win 11), but there are guides on how to enable it.
2 Likes
They just seem to work? No udev rules needed?
EDIT: had ChatGPT write me a little Bash script to dynamically rename the control binding files to import them easily from Windows:
linux_bulk_rename.zip (1.3 KB) It needs yq (on cachyOS: sudo pacman -S yq)
EDIT2: maybe the UUID being the same on all devices on the USB hub is causing issues though, weird binding mixups happen when I restart DCS
EDIT3: never mind, it’s probably a difference in the default profile the controllers get assigned on Windows and on Linux, since DCS only saves the .diff.lua. Could maybe fix it with a udev rule, but it’s much easier to just clear some axis commands the first time I fly a module than figure out how to get the controllers to look exactly as they do on Windows
And I just realized Virpil Controls configurator still needs Windows so I should keep a Windows install around on a small SATA SSD just for doing firmware changes on proprietary devices
2 Likes
Here’s good reference for the VM topic.
https://wiki.archlinux.org/title/Libvirt#
I used virt-manager (GUI) and virsh (CLI) to manage virtual machines for Linux and Win10 client OS.
They both and also the aforementioned gnome Boxes are front end clients for libvirt server, if I understood correctly.
3 Likes
Thanks @sobek and @UncleZam - I’ll check them out. I’m using QEMU for VMs in Proxmox on that side of things, so it sounds like the Gnome boxes might be a good starting point 
1 Like
Until now I hadn’t thought about VMs at all.
All I ever ran in a VM was either DOS or Linux, and never something with an elaborate GUI, like Windows.
But I will definitely try that, just to see which possibilities it might open. Thx!
1 Like
Meanwhile I have good and bad things to report about my music equipment:
My Midi Keyboard (M-Audio Oxygen Pro Mini) works, but the automatic assignment of the control buttons/axes (start/stop/pause/record/rewind/volume) doesn’t.
They do work if I assign them manually. It is very likely that this is just a Reaper setup issue, I also had some problem making it work in Reaper under Windows. Sadly I did not write a tutorial how I did it in back then.
But the bottom line is: It works fine under Linux.
My Zoom ST2 Audio Interface sadly doesn’t work it seems.
That isn’t much of a surprise since it hasn’t properly worked on Windows either, since… Win7 I think. I got it ~15 years ago. Back then I loved that it actually has a tube amp built in.
It is recognized (ALSA) but it cuts out after a second or so, regardless of how I fiddle with the blocksize, sample rate, periods, channels, or RT priority.
People recommend using JACK instead, and JACK is indeed installed on my OS, but I have no clue how to use it.
I accepted that for now. Might just spend the 40€ on a Behringer UMC22 audio interface and see if that one works better. It also has an XLR for my mic and an input for a guitar. But I think I’ll try and find a JACK for dummies video or something and try again.
2 Likes
After a lot of good news, today has some bad news:
- The head tracking is a little bit delayed with Monado compared to Windows 10’s WMR stack. Not a lot and it looks like I am already getting used to it.
- There are stutters when looking side to side in DCS. The Windows 10 experience wasn’t great either so perhaps it is the drivers of the RX 9070 XT. I did select the
VRpower profile in LACT. DCS says CPU Bound, and the GPU was only using 10 out of 16GB VRAM during a scouting mission around Fulda in the Gazelle. - Although my controllers all work in DCS under Proton, they all have the same UUID, and their bindings (at least axis bindings) get garbled on a restart of DCS. These things are probably related, as a UUID is supposed to be Universally Unique (that’s what the U’s stand for).
You can see the UUIDs in the controller name here, between the {}:
So I’m going to try to find out how to assign UUIDs to USB controllers in Linux.
2 Likes