Adding the +cl_liveapi_enabled 1 to game launch causes the game to get to the connecting screen, and then freeze up and crash.It seems to connect to the websocket server I have and then crash once it gets to the end of the loading.It also happens when no LiveAPI server is provided but not when LiveAPI is disabled.Is there something I should be sending back to the game or is it crashing for some unknown reason.The internal documentation that comes with LiveAPI in the game files isnt really helping me either so if theres any other docs I could use I would appreciate them being forwarded.Some random information that may help:System: Windows 10, 32GB of RAMMy api is getting a single init payload before the game crashesAudio on the video is muted since I have music onhttps://youtu.be/GtEy2ObNy3k

@avdiamond I've noticed this too.S16 brought the 2.0 revision, which brings new launch parameters.Refer to the config file in the LiveAPI folder, it contains the new parameters.I've copied it over for ease:// Sample config.json // Refer to the readme.txt for more info on these options { // Live API general settings "settings": { // Enable Live API 2.0, which includes websockets and protobuf support "cl_liveapi_use_v2": true, // Use WebSockets client and connect to a server "cl_liveapi_use_websocket": true, // Allow the API to process requests from a WebSocket connection "cl_liveapi_allow_requests": true, // WebSockets client networking options "cl_liveapi_ws_retry_count": 5, "cl_liveapi_ws_retry_time": 5, "cl_liveapi_ws_timeout": 300, "cl_liveapi_ws_keepalive": 10, // Use protobuf as the serialization format. Otherwise, use JSON. "cl_liveapi_use_protobuf": false, // When using JSON, whether to use human readable formatting "cl_liveapi_pretty_print_log": false }, // List of websocket servers Apex should connect to "servers": [ "ws://127.0.0.1:7777", ] }// Sample config.json // Refer to the readme.txt for more info on these options { // Live API general settings "settings": { // Enable Live API 2.0, which includes websockets and protobuf support "cl_liveapi_use_v2": true, // Use WebSockets client and connect to a server "cl_liveapi_use_websocket": true, // Allow the API to process requests from a WebSocket connection "cl_liveapi_allow_requests": true, // WebSockets client networking options "cl_liveapi_ws_retry_count": 5, "cl_liveapi_ws_retry_time": 5, "cl_liveapi_ws_timeout": 300, "cl_liveapi_ws_keepalive": 10, // Use protobuf as the serialization format. Otherwise, use JSON. "cl_liveapi_use_protobuf": false, // When using JSON, whether to use human readable formatting "cl_liveapi_pretty_print_log": false }, // List of websocket servers Apex should connect to "servers": [ "ws://127.0.0.1:7777", ] }

@avdiamond @conxumed Seems like I got confused, the parameter seems to be indeed broken.Thought I had resolved it but seems like I was mistaken.Well, guess we'll just have to wait for a fix.

Same here.Crashes when websocket option is enabled.But when I disable it, then isn't connecting anymore.Is there any alternative protocol, that game supports?

@Pa3kc1337 yes same here. only init then nothing more. Requests not working either (the observer thingys)

I've already used the config files, let me send a copy for you

Enabling LiveAPI crashes apex on launch

16 Replies

SourOldGeezer
3 years ago
@Pa3kc1337 yes same here. only init then nothing more. Requests not working either (the observer thingys)
XHelperZ
Hero+
3 years ago
Note that not all servers support LiveAPI, if at all, I'm unsure if private matches themselves will have this enabled for us to use.
SourOldGeezer
3 years ago
@XHelperZ would be weird to put it in the patch notes if they were not meant for everyone to use? even private lobbies are available for public now, but at least I cannot get any events from them either.
old json writing livedata could be enabled by anyone as well, right?
XHelperZ
Hero+
3 years ago
@SourOldGeezer
Could be, though I'm not so well versed with this system.
IIRC, the people at Apex Legends Status know a bit more about this API since they were using the 1.0 version before this 2.0 revision got released.
Might be something to ask them there, though I'm not sure.
SourOldGeezer
3 years ago
@XHelperZ I've been using the 1.0 as well from the json file, but this websockets thing is new for 2.0 as well as the protocol buffers you can optionally use.
I can receive Init event on my websocket server and unpack the Init message just fine, but I just don't seem to get any other Events anymore. Ping/Pong seems to work so the session is kept alive fine as well...
I suppose since this thread was about the crash and that seems to have been fixed I should probably create another thread for the Events not being received issue...
Atomicman_J
3 years ago
This is interesting, because prior to the patch I had this problem. Would get a websocket connection at startup screen and init message, and then game freeze and crash. After the patch it seems to work fine for me. Using the default config file.

Forum Discussion

Enabling LiveAPI crashes apex on launch

16 Replies

About Apex Legends Technical Issues

Community Highlights

What to do if your Apex Legends account got banned or suspended

Do Not Unlink Your EA Account

Game Crashes on Loading Startup screen

Community Crashing Troubleshooting Guide

Zeels in-depth Troubleshooting Guide

Recent Discussions

Game is infested by cheater

My Account Reset to Level 1

Permanent Ban After I Woke Up....

Can´t buy anything

Annoying input lag?