In the launcher were it says version type i changed it from release to beta, I’m not sure what you are talking about, i only click play in the steam app. But today it’s working again i don’t know why, the only thing i did was reinstall the game but it was yesterday and it didn’t fixed the problem yesterday, but today it’s working again with Proton-6.16-GE-1.
1 Like
Last night after I was already in game I set the launcher to use the beta launcher…
Today launcher doesn’t start up all the way. Just shows the CCP splash, and then nothing.
Kind of annoying…can’t even turn it back because it doesn’t get far enough.
Swapped to all versions of proton, back to 5.0-13 or whatever the old version is.
Guess I won’t be mining while I telework today. Hopefully I can figure it out later this evening when I can dedicate time to it.
Mint with steam.
Use Proton-6.16-GE-1. Tutorial on how to install Glorious Egg. I dont think that the official proton versions will work anymore until they update to wine 6.14 or 6.16.
There is a problem with glorious egg, if the game is windowed it will get the wrong position of the cursor but it works fine in fullscreen. The best option to play eve in linux right now is using lutris with wine staging, just install the lutris version and in the runner options inside lutris change the wine version to wine staging (make sure you have wine staging installed in your system). You can use this command in the terminal to install wine staging in ubuntu based distros: sudo apt install --install-recommends winehq-staging
lutris-ge-lol-6.16-2 version removed the mouse issue that was seen in the ge-1 version.
I have had issues logging into SiSi unfortunately in the past couple of days.
If I select sisy, the client doesn’t start at all, is that what you mean with that?
Or does it sometimes work for you?
If I select sisy, the client doesn’t start at all, is that what you mean with that?
Yep, this is what I mean.
I try to get the client to start my accounts to load on SiSi, and they seem to start up. That is, the play button stays turns to stop, and the CPU starts to ramps up and behaves accordingly as if it were trying to start the client. No Errors pop up.
However, I don’t get the window with the character choice window so I can log into the game on SiSi.
TQ is working fine at the moment for me.
yep. same here.
Very weird. I don’t think I ever had that problem before.
So, just out of curiosity and to clarify, are you having the same issue/problem when trying to get on SiSi?
Just want to know if it’s “just me”, or others are seeing this too.
yes, same problem. had to boot windows to get on Sisy.
Would not show the client under linux, even though starting TQ account worked (from the same launcher and setup)
I sincerely hope this is just a temporary bug in the Sisy client.
If this goes to TQ and we can’t start clients at all under linux, I’ll be upset.
1 Like
Got version 1945091 today, seems fine on wine-staging 6.16.
Have not tried Sisi but I’ll take a look at that.
1 Like
I’m getting the same behavior with Sisi, looking at the logs it looks like it’s failing to load a DLL:
2021-09-28T15:00:41.293Z default debug " \r"
2021-09-28T15:00:41.293Z default debug "Formatted exception info: ImportError: DLL load failed: Success.\r"
2021-09-28T15:00:41.293Z default debug " \r"
2021-09-28T15:00:41.294Z default debug "Common path prefix = c:/buildagent/work/28f796d548f5b3f2/eve/staging/2021-iceberg\r"
2021-09-28T15:00:41.294Z default debug " \r"
2021-09-28T15:00:41.294Z default debug "Caught at:\r"
2021-09-28T15:00:41.294Z default debug "<pre>/packages/bluepy/__init__.py(52) CallWrapper\r"
2021-09-28T15:00:41.294Z default debug " \r"
2021-09-28T15:00:41.294Z default debug "Thrown at:\r"
2021-09-28T15:00:41.294Z default debug "<pre>/packages/bluepy/__init__.py(43) CallWrapper\r"
2021-09-28T15:00:41.295Z default debug "<pre>/carbon/common/lib/autoexec_client_core.py(166) Startup\r"
2021-09-28T15:00:41.295Z default debug "<pre>/carbon/common/script/sys/serviceManager.py(132) Run\r"
2021-09-28T15:00:41.295Z default debug "<pre>/carbon/common/script/sys/serviceManager.py(88) _BuildClassMap\r"
2021-09-28T15:00:41.295Z default debug "<pre>/eve/common/modules/nice/client/_nastyspace/svc.py(81) <module>\r"
2021-09-28T15:00:41.295Z default debug "<pre>/eve/client/script/parklife/fleetSvc.py(17) <module>\r"
2021-09-28T15:00:41.296Z default debug "<pre>/eve/client/script/ui/shared/fleet/fleetwindow.py(16) <module>\r"
2021-09-28T15:00:41.296Z default debug "<pre>/eve/client/script/ui/shared/fleet/fleetRespawnPoints.py(1) <module>\r"
2021-09-28T15:00:41.296Z default debug "<pre>/eve/common/modules/nice/client/_nastyspace/listentry.py(92) <module>\r"
2021-09-28T15:00:41.296Z default debug "<pre>/eve/client/script/ui/shared/incursionJournal.py(11) <module>\r"
2021-09-28T15:00:41.296Z default debug "<pre>/eve/client/script/ui/shared/mapView/mapViewUtil.py(12) <module>\r"
2021-09-28T15:00:41.297Z default debug "<pre>/eve/client/script/ui/shared/systemMenu/betaOptions.py(11) <module>\r"
2021-09-28T15:00:41.297Z default debug "<pre>/packages/launchdarkly/__init__.py(69) <module>\r"
2021-09-28T15:00:41.297Z default debug " __builtins__ = {'AUR': 30,\r"F
2021-09-28T15:00:41.297Z default debug " 'ArithmeticError': <type 'exceptions.ArithmeticError'>,\r"
2021-09-28T15:00:41.297Z default debug " 'AssertionError': <type 'exceptions.AssertionError'>,\r"
2021-09-28T15:00:41.297Z default debug " 'AttributeError': <type 'exceptions.AttributeError'>,\r"
2021-09-28T15:00:41.298Z default debug " ...\r"
2021-09-28T15:00:41.298Z default debug " __doc__ = None\r"
2021-09-28T15:00:41.298Z default debug " __file__ = None\r"
2021-09-28T15:00:41.298Z default debug " __loader__ = None\r"
2021-09-28T15:00:41.298Z default debug " __name__ = None\r"
2021-09-28T15:00:41.298Z default debug " __package__ = None\r"
2021-09-28T15:00:41.299Z default debug " __path__ = None\r"
2021-09-28T15:00:41.299Z default debug " _make_user_object = None\r"
2021-09-28T15:00:41.299Z default debug " client = None\r"
2021-09-28T15:00:41.299Z default debug " client_instance = None\r"
2021-09-28T15:00:41.299Z default debug " ext = None\r"
2021-09-28T15:00:41.299Z default debug " get_client = None\r"
2021-09-28T15:00:41.300Z default debug " imp = None\r"
2021-09-28T15:00:41.300Z default debug " json = None\r"
2021-09-28T15:00:41.300Z default debug " logger = None\r"
2021-09-28T15:00:41.300Z default debug " logging = None\r"
2021-09-28T15:00:41.300Z default debug " monolithconfig = None\r"
2021-09-28T15:00:41.300Z default debug " on_client = None\r"
2021-09-28T15:00:41.301Z default debug " os = None\r"
2021-09-28T15:00:41.301Z default debug " platform = None\r"
2021-09-28T15:00:41.301Z default debug " sdk = None\r"
2021-09-28T15:00:41.301Z default debug " set_user = None\r"
2021-09-28T15:00:41.301Z default debug " \r"
This error doesn’t occur when launching tranquility. Next step is to try to get a stack trace to figure out which DLL is having problems. There are other various errors in the logs that aren’t related to the game not launching so this may not be relevant.
Not getting a clear crash in winedbg, but I am noticing this fixme stepping through the code:
0x0000000140012908 EntryPoint+0xfffc80c0 in exefile: calll *%r9d
Wine-dbg>ni
0a34:fixme:winedbg:be_x86_64_is_func_call Unsupported yet call insn (rex=0x01 0xFF 0xd1) at 0x140012909
Execution then jumps into blue.dll which I’m still working on analyzing. Not sure if this stuff is related but still working on figuring things out.
Unfortunately it looks like the issue is occurring pretty deep within the game client, somewhere within the stackless Python main loop. I’m not sure how to debug that effectively but I’ll keep trying as time permits.
Absolutely no idea why, but now I’m getting a page fault when calling PyStackless_CallMethod_Main() that I wasn’t getting when I was stepping through before…
2 Likes
SiSi does not work for me either. @Renard_DuGaulle, which logging channels did you enable to see this exception? Or is it EVE logs?
edit: nvm im dumb, it is clearly EVE client logs
It was eve logs to see the python exception, winedbg plus manual breakpoints/stepping to trace the execution.
This appears to be something broken with the launchdarkly Python SDK not initializing correctly (Configuration)…I’m not seeing any real indications that there’s anything wrong with wine. Does anyone have a windows machine they can try launching Sisi with and check the launcherlog-<date>.txt file that gets created in the Launcher folder in the eve directory? I’m curious if that error shows up there as well, even if the game launches normally.
1 Like
So this is super bizarre, but I found a way to launch the Sisi client without the launcher using cmd.exe via wine:
wine cmd.exe
.\exefile.exe /server:singularity /ssoToken=<> /refreshToken=<> /settingsprofile=Default /machineHash=<> /language=en /verbose
The client launches but doesn’t connect to Sisi due to a problem with formatting the ssoToken. This means the issue should between the launcher and the client, not with the client itself. Will continue debugging but I have to take a break now.
1 Like
My corpmate is using native linux launcher and he reports no issues with logging into sisi.
What version of wine are they running? Or are you referring to AUR (en) - evelauncher which uses a bundled wine AFAIK?
Yes, he uses bundled wine (4.4).
1 Like
Thanks, that’s helpful info. I’m going to try with a wine build from before the change to CRT (wine 5.5) in case it’s a similar root cause to the previous launcher issue.
Well that sucks…there seems to be some sort of a bug making it so I can’t build wine on Arch:
../wine-staging/configure: line 7547: syntax error near unexpected token `newline'
../wine-staging/configure: line 7547: ` '''
==> ERROR: A failure occurred in build().
Aborting...