\Logs\log_<timestamp>\<timestamp> errors.log
Posts by Andrudis
-
-
Client log file is invalid - you've uploaded configuration for logger and not "****errors.log" required
-
1) BE builds do not support mods, as already mentioned above
2) NO support is provided for BE builds as stated on Overview page - use BE versions only if you know what you are doing, otherwise use stable version which is now 1.5.1
-
Password protecting log files without providing password is a sure way to not receive any support
-
1) First - client 12.9.0.1521 is not compatible with AKI 1.5.1
2) Second:
Have you read the FAQ ?
Yes
You need to actually read https://hub.sp-tarkov.com/faq-question-list/, not just lie that you did - section Error: "Input string 'number' is not a valid integer."
-
You did something wrong and corrupted your profile. Now it is not a well-formed Json file. Missing or extra bracked somewhere. missing or extra coma - something like that
You can try to validate your profile with something like https://jsonformatter.curiousconcept.com/
Also it is a good practice to backup files before doing manual changes
-
Try to clear cache at: "%LOCALAPPDATA%\Temp\Battlestate Games\EscapeFromTarkov\Icon Cache"
-
I have 75 FOV, is that normal?
In my shared.ini:
Quote"StatedFieldOfView": 50.0,
"Fov": 0,
-
But why then endless loading?
In case with this support thread from Dehydrated Water - I can only assume some issue with the latest patcher based on error in logs:
Quote2021-08-11 09:13:54.069 +02:00|0.12.10.2.12893|Error|Default|Aki.Common: Error in patch BattleEyePatch
System.ExecutionEngineException: String conversion error: Illegal byte sequence encounted in the input.
Maybe the patcher was not applied correctly, maybe something else - I see this error for the first time so cannot tell for sure yet. And I do not see any other reports with the same error so far either.
In other "stuck loading" cases that was mostly due to incorrect version of client/patcher used (or patcher not used at all) or invalid FOV settings
In your case - I see neither support thread nor logs from you so cannot assist.
-
1.6.0 has too many issues. It is generally recommended to switch to 1.5.1 if possible which require the same build version (through You'll have to do a clean re-install and copy your profile)
I had a fix for this in an old Version 1.4.0 of QoL-Configuratior, but it was before AKI 1.0 and it is long outdated, since then I've removed that option because till 1.6.0 it was not an issue any more.
If you do not want to go to 1.5.1 - the easiest way would be auto-complete that quest and move on. Unless you or someone else would want to make a mod to fix this problem for 1.6.0
-
1.6.0 has too many issues. It is generally recommended to switch to 1.5.1 if possible which require the same build version (through You'll have to do a clean re-install and copy your profile)
-
AKI 1.6.0 now no. It was removed due to a ton of bugs. And they released a patcher for 1.6.0 with version 0.12.10.2. But for 1.5.1 you need version 0.12.10
AKI 1.6.0 require the same .12893 as AKI 1.5.1, whether it is 0.12.10.2.12893 or 0.12.10.12893 does not matter - it is different marking for the same build. Only the last number (build number) .12893 do really matter
-
This bug happens if you have at least 1 corrupt quest, but it is hard to tell which one.
It should be one of quests that is in "Started" state. If you do not have too many "Started" quests, you may backup your profile and try to edit different sets to check which ones cause this issue.
-
This is not a support case, go to Guilded, Modding-General section. for discussions of how to do modding
-
Client log file is absent and Wrong file loaded instead of server log file. Load correct logs:
\user\logs\server.log = for Server
\Logs\log_<timestamp>\<timestamp> errors.log - for client
without correct logs it is unlikely we will be able to provide any assistance
-
Apparently too many people were spamming support requests for their mods not working with BE builds.
Also apparently too many people cannot read and understand 3 simple small sentences in Overview for BE builds...
-
Mods are disabled for BE builds.
-
Did you check checkbox at the bottom of the trade dialog?
-
Did you try version 1.5.1 instead of 1.5.0? They both require the same client version, but 1.5.1 should be more stable
-
Do you have a bunaural audio on or off? try switching it and check if something will change.
Do you have the same issue with Live version?
