Character Creation: Loop After Initial Cutscene

Good afternoon,

I am currently having an issue with the character creation screen looping on Arch Linux, not sure if this applies to other distros.

Whenever I create my character, the game starts showing the initial story. Whenever the story ends or is skipped, it puts me back to the character creation screen, but still has UI elements as if I was in game. See screenshot: https://imgur.com/unZz2Hi

Whenever attempting to connect with that character after restarting the game, nothing happens upon pressing play.

In the player.log file, I did notice that there was multiple errors referring to a missing json file:

Exception: ‘AccelByteServerSDKConfig.json’ isn’t found in the Project/Assets/Resources directory

Gonna keep poking around while I wait for a response. This appears to be the same issue that was reported on Apr 13, however the previous player refunded the game before there was closure.

(steam.log is the system information exported from steam)

steam.log (85.2 KB)
Player.log (3.3 MB)

edit: The “websocket is not open.” errors are what happens whenever I click “Enter Game,” the missing json file prints constantly while the game is open.

WebSocketInvalidStateException: Websocket is not open.
at HybridWebSocket.WebSocket.Send (System.String message) [0x00019] in <8a0de9ce70e4426db102a988a58e3b4c>:0
at AccelByte.Api.Lobby.SendRequest[U] (AccelByte.Models.MessageType requestType, AccelByte.Core.ResultCallback1[T] callback) [0x00056] in <8a0de9ce70e4426db102a988a58e3b4c>:0 at AccelByte.Api.Lobby.JoinDefaultChatChannel (AccelByte.Core.ResultCallback1[T] callback) [0x00029] in <8a0de9ce70e4426db102a988a58e3b4c>:0
at ChatManager.InitDefaultChannel () [0x00012] in <8a0de9ce70e4426db102a988a58e3b4c>:0
at ChatManager.InitChat () [0x0000c] in <8a0de9ce70e4426db102a988a58e3b4c>:0
at CharacterSelect.LoadCharacterClick () [0x0000c] in <8a0de9ce70e4426db102a988a58e3b4c>:0
at UnityEngine.Events.InvokableCall.Invoke () [0x00010] in <792031f4c08a45adb522199a61807534>:0
at UnityEngine.Events.UnityEvent.Invoke () [0x00022] in <792031f4c08a45adb522199a61807534>:0
at UnityEngine.UI.Button.Press () [0x0001c] in :0
at UnityEngine.UI.Button.OnPointerClick (UnityEngine.EventSystems.PointerEventData eventData) [0x00009] in :0
at UnityEngine.EventSystems.ExecuteEvents.Execute (UnityEngine.EventSystems.IPointerClickHandler handler, UnityEngine.EventSystems.BaseEventData eventData) [0x00007] in :0
at UnityEngine.EventSystems.ExecuteEvents.Execute[T] (UnityEngine.GameObject target, UnityEngine.EventSystems.BaseEventData eventData, UnityEngine.EventSystems.ExecuteEvents+EventFunction1[T1] functor) [0x00063] in <a157fd91195842fe8963297ce2cd7914>:0 UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object) UnityEngine.DebugLogHandler:LogException(Exception, Object) UnityEngine.Logger:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) UnityEngine.EventSystems.ExecuteEvents:Execute(GameObject, BaseEventData, EventFunction1)
Rewired.Integration.UnityUI.RewiredStandaloneInputModule:ProcessMousePress(MouseButtonEventData)
Rewired.Integration.UnityUI.RewiredStandaloneInputModule:ProcessMouseEvent(Int32, Int32)
Rewired.Integration.UnityUI.RewiredStandaloneInputModule:ProcessMouseEvents()
Rewired.Integration.UnityUI.RewiredStandaloneInputModule:Process()
UnityEngine.EventSystems.EventSystem:Update()

Update 2: Running the game via proton still ends up with the same behavior. Issue also continues to exist after a reinstall. Validating the files via steam has no impact either, it always comes back with “files validated successfully” and has nothing to reacquire.

Attached log running under proton 5.13-6 ; still seeing same error along with some null pointers.
Player.log (412.2 KB)

Also confirmed that the issue still exists when launching via the standalone launcher off of the website, in addition to the steam download.

Hey… Welcome to the forums…

Sorry you are having such hassles trying to play…

Foreword: I dont play on Linux (Linux is for proper work not playing :stuck_out_tongue_winking_eye: ) so I have no experience in debugging the os specific issues related to LE and can only provide generic things to try. As you may have seen in your search, there are a few Linux players who have posted problems & potential fixes - everything from drivers updates/Mesa issues to vulkan to successfully running LE in docker. - it may be worthwhile to reach out to them directly to see if they have a suggestion or two for you.

However, I would suggest you hold off a little until the big 0.8.2 patch drops today… Its go so many changes that it may be worth seeing if the patch inadvertently fixed the issues you are having…

Update 0.8.2 did not resolve this either. Still receiving “The websocket is closed and incompatible address errors” The other error doesn’t repeat indefinitely now at least though.
Player.log (114.9 KB)

Final update: rolled back to Linux native and it is working now. I had forgotten that I was still on the proton version. Proton version is still broken with the same old issues. Closing now though as the intended version is functioning properly

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.