Run Excel under Wine, or just use a VM for those applications that refuse to run under Linux. I've got a VM for some work stuff.
Running Elite Dangerous on Linux Mint in 2024
- Thread starter FoxTwo
- Start date
Run Excel under Wine, or just use a VM for those applications that refuse to run under Linux. I've got a VM for some work stuff.
Try to play with dxvk.conf.
For example, on my nvidia 4 Gb I had persistent fps drops for years (till to 7-8 fps), until I added explicit
It has other settings like use memory alignment, wrong alignment could lead to crash, floats handling etc.
Just make sure you read example on the github and it matches version you use. Because they added/removed a lot of keys over the years and it is hard to say which is current now, even for AI.
Excellent suggestion.
I'd recommend starting with
Code:
dxgi.customVendorId = 0000
dxgi.emulateUMA = True
I need a heads up. I have stupidly embarked on the mission to find out if I get my VR stuff working on Linux, but the first step of course is getting ED to run, and I've hit a roadblock.
Getting the game to run was trivially easy; I've used the Steam version, copied over my Windows directory to my Linux SSD, ran steam, hit install, waited for Steam to verify the files, hit play, done. It's really a blessing how easy it has become. Now instead of moving on to see how the Envision / Monado stuff works, I got sidetracked into getting the ED part perfect first, and it doesn't.
I cannot get both of my VKB's to work. I have a normal EVO for the right hand and an Omni Throttle EVO for the left, and only the left one works in Elite. I have verified that both sticks work in the OS (I am running Mint 22.1), but ED only sees the left one. I can bind anything using the left stick, but the right one is ignored. I have played around with disconnecting and reconnecting them in different orders, and bypassing the hub the sticks are usually connected to, but no matter what, ED will not see my right stick. It also doesn't matter which one shows up as /dev/input/js0 or /dev/input/js1. The left always works, if it changes the device number I have to restart the game though.
Any ideas?
Getting the game to run was trivially easy; I've used the Steam version, copied over my Windows directory to my Linux SSD, ran steam, hit install, waited for Steam to verify the files, hit play, done. It's really a blessing how easy it has become. Now instead of moving on to see how the Envision / Monado stuff works, I got sidetracked into getting the ED part perfect first, and it doesn't.
I cannot get both of my VKB's to work. I have a normal EVO for the right hand and an Omni Throttle EVO for the left, and only the left one works in Elite. I have verified that both sticks work in the OS (I am running Mint 22.1), but ED only sees the left one. I can bind anything using the left stick, but the right one is ignored. I have played around with disconnecting and reconnecting them in different orders, and bypassing the hub the sticks are usually connected to, but no matter what, ED will not see my right stick. It also doesn't matter which one shows up as /dev/input/js0 or /dev/input/js1. The left always works, if it changes the device number I have to restart the game though.
Any ideas?
Not sure, but even on Windows sometimes its better to disable Steam input within Steam as that can interfere with the correct operation of controllers, so maybe look into that, so Wine itself is the only thing controlling the sticks.
I double checked, I had missed it in the game's properties, but I disabled everything. Didn't help.
Can't help more than a link, as I don't have joysticks.
Looks like the name /js* is historical. Try the other way.
Doh! Well was an idea.
Yeah. Thanks anyway!
well the js* are the devices jstest talks to. of course they also show up as evdev devices, but jstest was the quickest way to check if they physically work - which they do.
My best guess the problem is somwhere in the wine environment, have to look there. In the meantime I did the desperate thing and made a firmware update on the right stick, but no dice. There could be some kind of difference between the sticks as the right one is one of the first EVOs, and the left OT was bought quite some time later.
Worked my way further through the ArchWiki (the best thing about Arch in my opinion 
) and managed to run the joystick control panel with the correct wine prefix. Confirmed, wine only sees the one stick and doesn't like the other.
So I downloaded and compiled sdl-jstest, and both sticks work fine in SDL. Problem is somewhere in wine land.
) and managed to run the joystick control panel with the correct wine prefix. Confirmed, wine only sees the one stick and doesn't like the other.So I downloaded and compiled sdl-jstest, and both sticks work fine in SDL. Problem is somewhere in wine land
.Don't have a Meta headset, so can't help. But I actually got my Reverb G2 to work - sort of. I had a go through Envision, which is an environment builder for Monado. Didn't work at first, but after a replug I actually got it to work - terribly though. Latency is off the charts, and image is jittery as hell. But it worked. I actually had ED play on my Reverb G2 on Linux.
Yay.
It is a permission issue, but I don't know where. When I run the joystick control panel in wine with sudo (yeah I know, you shouldn't do that....) it lists both of my sticks. If I don't, it only lists the one. Both sticks work fine in native SDL applications, tampering with the pemissions of the event devices doesn't help. I'm not familiar enough with wine to know where the issue lies... damn.
Check virtual files created. Like
ls -l /dev/input/js1
I had wrong permissions with devices connected many times. This is fixed through udev scripts.
Sounds like you're getting close.
I've dug a little deeper. It's a wine / steam controller configuration issue. After disabling hidraw in wine's joystick control panel, the right stick shows up as an Xinput controller and is recognized as a gamepad by Elite. My bindings file loads, but all bindings from the right stick are invalid, rebinding sets them as controller bindings.
If I click "override" in the joystick panel, the right stick is moved to the DirectInput Devices, and my bindings file loads as the USB device isn't invalid anymore, but all bindings are again invalid, and this time the game doesn't recognize any input from the right stick.
I am going to reboot into windows to have a look at the setup with the VKB tool. Maybe something is screwed up with the stick that doesn't matter in Windows.
One would hope so
.It's definitely (famous last words) not a permission issue on the OS side. All device files seem fine.
meh, I am giving up for now.
Haven't found a solution yet, but the whole ED on Linux project will go back on the shelf for a while. Played around a bit more with the VR implementation, and apparently the nvidia drivers have a certain issue that introduces unfixable lag into the tracking pipeline. It's really uncomfortable.
For now it is unusable unless this gets fixed by nvidia or I win the lottery and decide to swap my 3080 ti for an AMD card - from what I read, tethered VR works pretty well with AMD cards.
Oh well.
Haven't found a solution yet, but the whole ED on Linux project will go back on the shelf for a while. Played around a bit more with the VR implementation, and apparently the nvidia drivers have a certain issue that introduces unfixable lag into the tracking pipeline. It's really uncomfortable.
For now it is unusable unless this gets fixed by nvidia or I win the lottery and decide to swap my 3080 ti for an AMD card - from what I read, tethered VR works pretty well with AMD cards.
Oh well.
try another proton than.
For example, I use for Elite this one
GitHub - rankynbass/proton-xiv: Proton-GE with additional patches for XIVLauncher
Proton-GE with additional patches for XIVLauncher. Contribute to rankynbass/proton-xiv development by creating an account on GitHub.
github.com
export PROTON_USE_NTSYNC=1
Oh, and btw, I have this one in my script:
#Joystics support
export PROTON_USE_XALIA=0
It's new, less than 1 month on Steam. Probably you could try to investigate what is it and if disabling it could help.