Not starting after installation

[macmorri]

I'm starting to get really desperate. About two years ago, I had successfully installed OneLauncher (LOTRO) via "Crossover" (Win 11 bottle) on my Mac (Studio M2 max). Then I took a break and now I returned and saw that there is a new version of OneLauncher. I uninstalled the old version and installed the new one (starting the old, existing version worked). Now OneLauncher just won't start. Double-click/open does nothing more than show the OneLauncher process in the Task Manager, but it doesn't open any application. Can anyone help me? Please!? :)

Written Logfile "OneLauncher.cxlog" ends with following lines:

unimplemented ioctl _WSAIOR(IOC_WS2, 28)
06dc:06e0:fixme:winsock:server_ioctl_sock Unsupported ioctl 0x120348 (device=0x12 access=0 func=0xd2 method=0)

[JuneStepp]

OneLauncher doesn't support getting run through WINE/Crossover. It did happen to work in the past, but doesn't now.
I haven't provided native macOS builds in quite a while due to Apple dropping 32-bit support and not having testers, but I actually did some work on that these past couple days. If you want to try out a native macOS OneLauncher version you can download it from https://github.com/JuneStepp/OneLauncher/actions/runs/19210800175 (you have to be logged in to GitHub).

I don't have the hardware to do much macOS testing myself, so please let me know how it goes if you try it.

[macmorri]

Thank you for the quick reply. Unfortunately, a MacOS application doesn't help me, because the LOTRO client runs via Crossover in a Windows session (I tried but can't select the game during the setup dialog). I can access all folders and files from MacOS, but not from the setup application. In addition, I doubt that the start of the Windows application would be possible from the MacOS Launcher. I'll try to discuss this with the Crossover Team. They are very greedy to get known of applications you cannot get to run. Maybe they'll know a hint.
Nevertheless, thank you very much for your efforts, then I'm just annoyed with the standard launcher. ;)

[JuneStepp]

It's the same as on Linux. OneLauncher handles WINE for you, so you don't need Crossover. It's one of the main reasons OneLauncher exists.

[JuneStepp]

In the file setup wizard you should be able to click "Add Game", press Command + Shift + Period to show hidden files, and navigate to Library/Application Support/Crossover/bottles/<BOTTLE NAME>/drive_c/Program Files/Standing Stone Games/The Lord of The Rings Online. It might be Program Files x86 instead of Program Files.

[JuneStepp]

I also just added support, so that OneLauncher auto-detects games from MacOS Crossover. That build is here.

[macmorri]

Wow! JuneStepp - thank you oh so much! This works like a charm! Fantastic! Again - thank you!

[macmorri]

Ah okay, rejoiced too soon. Well, the launcher opens, I can enter everything, also install mods, etc. But after clicking on Play I listen to music, but I don't see a picture. Only changing colors, red and yellow, but no picture. ESC + ENTER ends the program. The log window shows no errors. Beta test report end. :) ;)

[JuneStepp]

I really wish I could do these debugging steps myself, but I can't, so I'd appreciate any amount you're able to do.

Debugging Steps:

• Download the testing build from: https://github.com/JuneStepp/OneLauncher/actions/runs/19215286895
• Confirm that you are using the 64-bit game client in OneLauncher's settings menu.
• Try running the game again with this new build.

If it didn't work, try each of the steps below until hopefully something works. Debug logs will be sent to Library/Logs/onelauncher/main.log.

• Figure out which DirectX version you're using. In Documents/The Lord of The Rings Online/UserPreferences.ini It's GraphicsCore= either D3D9, D3D10, or D3D11.
• Make sure ScreenMode=FullScreenWindowed under the [Display] section in UserPreferences.ini.
• If you're using D3D9, try changing it to D3D11, if using D3D11, try setting it to D3D9. If using D3D10 try D3D11 first.
• Try with D3D9 while starting OneLauncher with the --test-1 argument. Ex: ~/Downloads/onelauncher.app/Contents/MacOS/onelauncher.bin --test-1 if OneLauncher is in your Downloads folder.

[macmorri]

Now it works!

First, I tried the new client, made sure that 64bit was set and started LOTRO. The same error occurred as described above.

Then I checked "ScreenMode" (correct) and "GrapicsCore" in the UsersPreferences.ini and changed the latter from D3D11 to D3D9.

Then I started LOTRO again and everything started correctly. :)

If you want me to test more, feel free to tell me. Thank you very much!

[JuneStepp]

Thanks! Can you try this?:

• Run rm -r "$HOME/Library/Application Support/onelauncher/wine" "$HOME/Library/Caches/onelauncher/wine" in the terminal.
• Switch back to D3D11 in UserPreferences.ini.
• Try the build from: https://github.com/JuneStepp/OneLauncher/actions/runs/19276856919

If it does work, can you confirm if the performance seems reasonable and if running one of the movies from the movie library on the characters screen works?

[macmorri]

With pleasure.

First of all, the good: The client starts normally, access to all menus is possible.

Well, the not so good thing: Watching the movies is like operating a flipbook with a broken thumb. ;) Both the language and the images are extremely jerky. The same applies to the performance in the game itself. You can't move fluidly, it jerks and falters.

Test end. :)

[JuneStepp]

Hey. I've been working on this with help from JohnNHammer and have macOS support working well now. I'll probably make a new release with it soon if there are no new issues found. You can test the current version with this build if you'd like.

Before using any new builds, please run that rm -r "$HOME/Library/Application Support/onelauncher/wine" "$HOME/Library/Caches/onelauncher/wine" command again. That's only necessary, since you were testing stuff. You won't have to do it again in the future.

[JuneStepp]

New release is out. See https://github.com/JuneStepp/OneLauncher?tab=readme-ov-file#macos.

Before using any new builds, please run that rm -r "$HOME/Library/Application Support/onelauncher/wine" "$HOME/Library/Caches/onelauncher/wine" command again. That's only necessary, since you were testing stuff. You won't have to do it again in the future.

@macmorri remember to do that ↑