Star Trek Online Forum

Hi,

I'm running Crossover Games 9.1.0 on Mac OS X 10.6.4 and I am unable to get past the launcher's login-screen: When I start to type in the Account Name or Password field, the launcher just hangs without even displaying the typed character.

I'm trying to run the Steam Version of STO.

Is this a known problem? I only bought CXGames because STO is now officially supported, so right now I am a little disappointed ☹️

Regards,
Rainer

I'd recommend you try to use the regular version that you can download from Star Trek Online - Download and install that via the c4p profile making a new bottle while installing. There is no practical difference between the regular version and the Steam version as Steam doesn't update the client itself, the launcher downloads the updates itself.

We have confirmed that a number of recent bugs in Steam games are due to changes in the in-game community overlay DLL. For some games, disabling the in-game community feature via Steam's settings is good enough to fix the problem. For other games, that's not enough.

For those, you can go into the Wine Configuration (winecfg) tool via Manage Bottles -> select bottle with Steam -> Control Panel. On winecfg's Applications tab, click Add Application. Select the executable of the Steam game that's having the problem (or just type its filename, like foobar.exe) and click Open. Select the Libraries tab of winecfg. Type GameOverlayRenderer in the "New override for library" edit field, click the Add button, click the Edit button, select Disable, click OK, and click OK. That prevents the in-game community overlay from even being loaded for that game.

If you don't use the in-game community, you might find it simpler to just disable it for the whole bottle. To do that, just skip the above steps involving the Applications tab of winecfg. Just leave it with Default Settings selected, which is how it starts, and go straight to the Libraries tab and proceed from there.

I think what was meant was the launcher window and not the in-game login screen.

The launcher is just a basic Windows window that opens up before the game itself launches to request your username and password and has a bunch of annoyingly IE based stuff in it. I wish they'd do the friendly thing and start using WebKit in it instead...

Right, but the Steam in-game community probably doesn't know the difference between the game and the launcher. It's almost certainly trying to hook into the launcher. One of the symptoms caused by the recent update is non-response to keyboard and mouse, which is what Rainer reported.

Star Trek Online is working in CrossOver Games, in general. I just played it for several hours. I'm 99% certain that the problem Rainer is experiencing is due to the Steam in-game community overlay.

That said, our Star Trek Online installation profile does have some tweaks it makes to the bottle. Primarily, it sets the equivalent of going into the launcher's Options window and adding "-NetSockBsd" (without the quotes) in the "Advanced command line" field. I don't expect that would affect typing into the account or password fields, though.

Could be that of course.

My personal recommendation would be to forget about the one installable via Steam and install the client via the C4P profile using the installer available at STO website. Leaves that sort of problems away and Steam doesn't add any value in STO's case.

I know this because I bought the Digital Deluxe version from Steam and only moment I needed that one was to get the codes from Steam to enter at STO account management to get my items and membership opened. After that I've never used the one in Steam as I noticed that the STO client didn't get updated via Steam but via the launcher so it quite well negated the usefulness of Steam. The client without Steam has worked great for me.

yea i second that it works for me fine in crossover using the d/l installer.

Thanks for all the suggestions - turning off the ingame-community-thing solved the typing issues, but STO still wouldn't launch. I then downloaded the non-steam-version and everything seems fine so far 😊

Thanks,

Rainer