Beta Launcher v0.4.x

[Elassus_Herron]

The winetricks on a clean prefix got the installer/launcher running for me. Sadly, the launcher/installer was completely unable to find my previous EVE installation, so I’m going to have to copy over my settings manually, save all my screenshots somewhere else, and delete the old prefix.
Completely changing the install paths for the new launcher was a real galaxy-brain move
Update: well, I got to the point of trying to launch the client and got an error that “Windows 10 or higher required.” I have winecfg set to Windows 10. So, stuck again.
Update 2: I needed to run winecfg -v win10 on both prefixes – the one where the launcher is installed, and the one where the client files are stored – to get it working. But it seems to be running. Now I just need to copy my settings files over.

[John_Rochard]

@Kadesh_Priestess

On clean wine 9.1 prefix, with winetricks verbs msdelta arial tahoma vcrun2017 dxvk vkd3d installed, and EVE data moved manually from the old prefix it worked just fine.

I am still running wine 8.0.2, I made a backup of the wine prefix and removed it. Then I ran the string you recommended. That seemed to cure the launcher issue, then I pointed the installer at my existing Eve folder. After login, I spent the next hour resetting my settings and individual characters back to their “normal” UI. This made me so tired, I decide just not to play today. Thank you for doing the most exhaustive work of debugging the needed modules.

Note: This launcher is really a clock cycle and memory pig. I shut it off completely using the quit option in the wine system tray. However this will not appeal to players wanting to operate multiple omega accounts.

[Yosagi_Yojimbo]

This worked perfectly for me, thanks.

[milegrin]

Greetings

I have followed the instructions below to the letter and no matter what I try, the installation insists on trying to install dotnet45 which fails at the end when it asks to “Restart Now”.

@Stein_Bytting

So I managed to install the new launcher from scratch without Steam using the following method:

1. Install Bottles
2. Add the following runner: Preferences → Runners → Caffe-8.21
3. Create a new Win64 bottle called “EVE”. Choose “custom” and disable both DXVK and VKD3D.
4. Once the bottle is created, go to Settings and choose the Caffe-8.21 runner
5. Also add the following dependencies to it: dotnet45, vcredist2019, arial32, consolas
6. Download the new launcher and put it in a folder accessible to bottles. Typically under ~/.var/app
7. Choose “Run executable” inside the new bottle and select the launcher

This is the Terminal output if helps find a solution:

wineserver: using server-side synchronization.
002c:err:wineboot:process_run_key Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -r" (2).
011c:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
0140:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
0158:err:ole:marshal_object Failed to create an IRpcStubBuffer from IPSFactory for {659cdeac-489e-11d9-a9cd-000d56965251} with error 0x80004002
0210:err:wusa:install_files_copy Required file L"C:\\users\\myuser\\Temp\\msu2.tmp\\amd64_netfx4-servicemodel_mof_files_b03f5f7f11d50a3a_4.0.9600.17187_none_7f79f6c9b36ef700\\ServiceModel.mof.uninstall" not found
0210:err:wusa:install_assembly Failed to install all files for L"NetFx4-ServiceModel_mof_files"
0210:err:wusa:install_updates Failed to install update L"Package_for_KB2934520"
0210:err:wusa:install_msu Dry run failed, aborting installation

I have managed to Eve Installed on Steam but it’s a resource hog … no more dual-boxing for me and I have a rather beefy laptop. I am hoping that Bottles would be a better solution if I can get it working.

Regards
m

[stefnia_Freir]

have you tried the simple method, that is create wineprefix, add the deps with winetricks, set the win10 version, then start with wineconsole ?

[milegrin]

Hi
Yes I did - no luck. I eventually got it working using “Bottles” so sticking with that till teh next time EvE breaks it.

[Elysianne_Uhkretor]

I’ve kept myself quiet for some time to try out some things on my own, while other people tried theirs at the same time.

… Eve Launcher (app-1.3.5) executes on Debian distro successfully, without reinstalling EVE Online, with Wine 9.0-staging-tkg with only 1 winetrick required: vkd3d… And yes, I know that Wine version is, apparently, at 9.16.0, but I like using Stable versions (less likely to break something that was already working, and less experimental stuff being added).

Now, this requires vkd3d library to be installed in your Linux distro. Considering that the Launcher ran successfully on my computer, with a x86 vkd3d library installed, its safe to assume that the stupid launcher is still compiled for x86 (32-bit) instead of amd64 (a.k.a. x64, or 64-bit) which also means that CCP completely ignored me (didn’t expect otherwise, tbh) regarding their poor choices…

There is nothing in this world, since 2017, that only supports x86 instructions. Everything runs 64-bit stuff, even the stupid smartphones they’re using… But I digress.

Point being: Eve Launcher (app-1.3.5) runs successfully on Debian with 1 winetrick requirement, as I mentioned before, IF Launcher is executed through the AppData folder directly. I still haven’t solved the issue of not running at all if the Launcher is placed/installed in a different folder.

I hope this helps in case anyone ends up tripping into this thread while searching for a solution.