what version of Wine? I used to have that issue at 5.16 and had to roll back to 5.15 until 6.0 came out.Now... The game freezes at main menu. What should I do with it?
what version of Wine? I used to have that issue at 5.16 and had to roll back to 5.15 until 6.0 came out.Now... The game freezes at main menu. What should I do with it?
This should help: custom wine mono build
That's exactly my experience. It works on mouse over and I can still type in the fields. The launcher looks correct in wine-staging but wine staging causes random pauses of 5 to 10 seconds ( heart stopping when you're exploring in a sidewinder )That black launcher happens for me too on Arch Linux. IIRC it went black after installing arial fonts or corefonts, and without those fonts the launcher crashed after typing in username and switching to password field. But it still works even if it's black, some elements do show on mouseover, and tabbing worked when typing in login creds.
I use archlinux and the launcher is fine. I installed the wine-mono, but kept the dotnet and it worked for meThat's exactly my experience. It works on mouse over and I can still type in the fields. The launcher looks correct in wine-staging but wine staging causes random pauses of 5 to 10 seconds ( heart stopping when you're exploring in a sidewinder )
Well I used: lutris-5.6, lutris-5.21, lutris-5.7.11, lutris-5.7.10, proton-ge-5.9, proton-5.13, and system (6.0)what version of Wine? I used to have that issue at 5.16 and had to roll back to 5.15 until 6.0 came out.
Wine Stable 6.0 should work but you may get the black launcher as per my pic - it's not crashed and does work. Just not fully functional in terms of display. Make sure you have dotnet40 and dxvk installed. Though I must say I am using Mint rather than Arch and I don't know the differences between them. My personal preference is for Debian based distros.Well I used: lutris-5.6, lutris-5.21, lutris-5.7.11, lutris-5.7.10, proton-ge-5.9, proton-5.13, and system (6.0)
Wine Stable 6.0 should work but you may get the black launcher as per my pic - it's not crashed and does work. Just not fully functional in terms of display. Make sure you have dotnet40 and dxvk installed. Though I must say I am using Mint rather than Arch and I don't know the differences between them. My personal preference is for Debian based distros.
If that's to me - I'm not using steam / proton, I just run EDLaunch.exe straight in Wine ( I have 2 EDLaunch one for each account as my pair of accounts are old ). I play in a borderless window. It makes no difference which monitor the launcher is on. The game itself plays fine.Have you tried the /steam /novr switches when running the launcher? (i.e. wine64 Edlaunch.exe /steam /novr)
Also - do you by chance have a multi monitor setup? I have a dual-monitor setup and for $reasons all sorts of game launchers go haywire if displayed on the 2nd monitor. Moving them to the primary monitor solves it. Still trying to figure out what causes that - whether it's an Xorg, nvidia driver, or some other issue.
If that's to me - I'm not using steam / proton, I just run EDLaunch.exe straight in Wine ( I have 2 EDLaunch one for each account as my pair of accounts are old ). I play in a borderless window. It makes no difference which monitor the launcher is on. The game itself plays fine.
Ahh cool. What does the /steam switch do? I will definitely give it a try all the same.Yes it was to you
And yes I was referring specifically to the launcher. I run EDLaunch from the command line and add the /steam and /novr switches - that's what I was asking, if you've tried that, it might solve the launcher display problem. I don't get that problem.
Rgds.
The /steam option makes the launcher think it is launched by the steam.Ahh cool. What does the /steam switch do? I will definitely give it a try all the same.
That /steam actually worked a treat! I think I'm going to go with your dxvk.conf workaround as I use 2 launchers, one for each of my two accounts and I can avoid using the terminal that way.The /steam option makes the launcher think it is launched by the steam.
This seems to trigger a different render method inside the launcher, solving the blackness/rendering problems in wine.
Downside is that it also expects that steam will do the game updates for it, so there's no update button or it doesn't work (can't quite remember which).
Either way you will need to remove the /steam option in order to perform a game update.
Another solution I've found is to change one of the dxvk settings by placing a dxvk.conf file in the same folder as EDLaunch.exe.
The dxvk.conf as a single line in it with: d3d9.shaderModel = 1
This also results in a properly rendering game launcher, without the need for the /steam option.
I've checked the dxvk logs and this only effects the launcher and not the game it self (the game uses dx11).
Personally I run the EDLaunch.exe with just two options : /autorun and /autoquit.
The first causes the launcher to automatically start the game, so no need to manually press the play button. Unless a game update is required, then it just show the launcher (where I can press the update button).
The second options closes the launcher after I exit Elite.
the config file worked even better! That's just the launcher right and not the game proper? I wasn't paying attention to graphics detail in game.That /steam actually worked a treat! I think I'm going to go with your dxvk.conf workaround as I use 2 launchers, one for each of my two accounts and I can avoid using the terminal that way.
jstest /dev/input/js0
Hello.
I installed Elite Dangerous through Steam on my Manjaro Linux.
For control I want use Thrustmaster T-Flight Hotas X.
The joystick is displayed correctly withIn wine control can I see the Joystick.Code:jstest /dev/input/js0
View attachment 206655
But in Steam it shows up as a gamepad, so I can't use the Z-Axis.
View attachment 206656
Has anybody this problem before and how can I fix it?
Sorry for my bad english.
Had the same issues, dotnet didn't fix it. But creating a support ticket, asking nicely if they could link the accounts for me due to this bug, worked.I always thought that was just a symlink to wine, but this actually changed the behavior. Now mono crashes when it looks like it wants to redirect me to a website to link the accounts. Will see if I can link them with dotnet instead of mono.