NilPointer

I tried it before posting, the file is overwritten on launch. In reality, it is being deleted and a new one written with the same name, in the same directory. Oh really, smartass, then where do you set the FrameRate settings in it? I know what I am talking about, I didn't start yesterday despite the forum reputation. I am referring to the correct file.

I am unsure when you introduced this (last Wednesday or two days ago) but I noticed that when APB.exe is launched, the config file under `APB Reloaded\APBGame\Config\APBEngine.ini` file is overwritten with a default one. I am not really sure what you are trying to prevent, but this has a few relevant downsides you clearly have not considered nor have you announced publicly of this decision. Namely the frame rate settings. I am fortunate enough to have a 144hz screen. To take advantage of this monitor and a CPU 10 years ahead of this game's time, I edit my APBEngine.ini file, under `Engine.GameEngine`, raising the values of `MaxSmoothedFrameRate=62` to something reasonable and 2022-ish. Now of course this is impossible since on launch you're overwriting this file with the 62fps cap. If there is a ground-breaking config that cannot be changed, it should not be in an .ini file, and instead compiled along the APB binary. If there is a need for a local file that needs to be replaced (or checked with a checksum) then at least break apart your business logic so it does not interfere with customizable settings by the client. Refresh rate surely is one of them. Don't ignore this issue like all the rest. Thank you in advance.

Thanks for your reply. Can you address the concerns in my second post if you know of course, on whether it's possible to connect a Steam login to a GamersFirst account (not having done so before)? There are no controls for this in the account management section, nor can I login with steam (website offers G1, PS and Xbox SSO) Thanks in advance

Note: AFAIK you can't connect a Steam account to a GamersFirst account (at least after the fact) making this Steam account stuck and unable to login.

Hi folks, For about 24h, users logging into the game via Steam Single Sign-On are unable to login with error 10017. Waiting didn't work. GamersFirst SSO works fine, so G1 accounts are able to login and play. Similar issue reported in 2018 in the thread below, received no attention or replies. I can't imagine how you're not setting up tests and health checks for login actions, honestly... Do I have to wait until Wednesday or is it a good time to trash the game? Issue (at least) happening in Citadel. Reproducible. Thanks in advance.