#Headless Client blocking different install from running. Application is already running.

160 messages · Page 1 of 1 (latest)

jovial flameBOT
#
Thedown1 has submitted a ticket

Versions: Fika - 2.4.6 SPT - 3.11.3
Networking: Port Forwarding
Description: Got the Headless Client up and running but the headless client is blocking the launcher from working on another directory.
I've attempted to review some issue here like verifying the Users/Launcher/Config.json and both installs have different game paths.
I've tried removing any additional config under BepInEx and Users Folder in the Headless install path.
Attempted to move the install to another location and verify the gamepath was updated in the launcher, still is not launching from different install.

#

Thread started by: @hexed thunder

jovial flameBOT
#

@hexed thunder please attach any applicable log files and mod lists while waiting for help!
You can find your log file at %AppData%\..\LocalLow\Battlestate Games\EscapeFromTarkov\Player.log

If you do not attach any logs, we will close the ticket without warning.

hexed thunder
#

Referenced:

#

PS1 file in the exe location, is based on PSScriptRoot path

#

Registry for install location is pointing to my client version

#

Test login with launcher from headless install
Pointing towards Headless location

#

Using Fika Headless 1.2.5

sand urchin
#

Where is the script being launched from

hexed thunder
#

from the headless folder install location as per headless instructions

sand urchin
#

I'm going to guess it's going down too far. I put explicit dir in the script so there is no confusion

hexed thunder
#

like too many folders?

#

or the PS1 script?

sand urchin
#

Well there are definitely too many characters and spaces in the folders for my tastes but making the absolute in the PS1 sure would help

hexed thunder
#

testing with absolute path for PS1 script

robust barn
#

Screenshot your launcher settings

hexed thunder
#

I have the json file I included of both, but let me grab them

robust barn
#

And the left is the one you launch your normal client with?

hexed thunder
#

right one, left is headless location

robust barn
#

Screenshot the ps1 you use to launch the headless

#

The file, not contents

hexed thunder
robust barn
#

With the rest of the folder and its address

hexed thunder
robust barn
#

So now if you launch the ps1, and then run the separate launcher (that is not in this folder), it doesn't work? And you have removed the absolute path?

hexed thunder
#

I've tested both absolute path and the $path

robust barn
#

Somewhere your tarkov process is being started from the same folder when launching the client after.

hexed thunder
#

I launch SPT.server.exe and PS1 file from headless.
I then navigate to the other folder that has my client install, open the SPT.launcher.exe and click join

robust barn
#

The launcher

hexed thunder
robust barn
#

After that, run spt server, run the ps1. Once eft is running, right click the process in task manager and open file location. Where does it go?

robust barn
# hexed thunder

I only want the client launcher. Headless never uses a launcher

#

I assume that is the 2nd image

hexed thunder
#

right is client launcher

hexed thunder
#

I:\New folder (2)\Escape from Tarkov Headless\Install_EFT

robust barn
#

And now if you launch the launcher in the right image, you cannot launch eft?

hexed thunder
#

correct

robust barn
#

Did you just try?

hexed thunder
robust barn
#

Leave that open, find the process for that window and do the same with file location

hexed thunder
#

the server or the headless?

robust barn
#

The one that doesn't start

robust barn
hexed thunder
#

looking

robust barn
#

You have 2 options

#

Wait until tomorrow morning. It's 1 AM and I'm on phone, so about 7 hours from now. Then you could stream it for me as I am still not sure if you're launching it correctly.

Or you could quickly record the entire process and upload here and I'll see.

hexed thunder
#

I can record it, you want from server start to error?

robust barn
#

The entire process yes

#

Slow and concise

hexed thunder
#

what video format you prefer?

robust barn
#

Anything that can be embedded in discord

#

Mp4 is fine

hexed thunder
sand urchin
#

what happens if you open the client first

#

same?

hexed thunder
#

I tried that too, yes same thing except the headless client says the error instead

robust barn
#

My recommendation would be to try an older version of the launch script

sand urchin
#

does it matter that the jsonc is set incorrectly?

robust barn
sand urchin
robust barn
#

No.

sand urchin
#

kk

hexed thunder
#

this portion or

robust barn
#

This error happens if you start it from the same folder. But they aren't so I'm out of ideas. I've ran up to 4 clients myself

#

As stupid as it sounds, a restart of the PC might help

hexed thunder
#

I'll try that and a different drive. the one I have it hosted on is a Raid 0 drive which may be doing something funky too

robust barn
#

I'm off to sleep bedge gl

hexed thunder
#

nope neither fixed it

#

is there a registry file location for SPT?

#

I see one for Tarkov/battlestate but not for SPT

sand urchin
hexed thunder
#

idk that's what it was set to when I looked at it

sand urchin
#

so when you installed it from the launcher it made those folders?

hexed thunder
#

yes, I tried changing it too but didn't seem to change anything either

#

it just made the SPT launcher not work or cause the SPT installer to fail

sand urchin
#

what version of eft is Live on for you?

hexed thunder
#

the latest version is from the last time I opened the launcher like a couple weeks ago:

sand urchin
#

I'm guessing its because everything is nested in that one folder

hexed thunder
#

I just looked at it is the most up-to-date version on the EFT change log

#

I tried running the headless folder from a completly different drive

#

or do you mean the install and SPT install being under the one drive?

sand urchin
#

one folder yes

#

not installing SPT to the same folder structure as Live is like #1 on the list of things they say not to do over at spt

hexed thunder
#

I'll try rearranging it and installing eft in a different directory

steady basalt
#

dont forget to change that in your SPT launcher

hexed thunder
#

interesting, I'll give that a try after reinstalling

steady basalt
#

my recommendation is to set it up this way:

C:\Fika\FikaClient
C:\Fika\FikaHeadless

#

the drive can be any of your choice of course

hexed thunder
#

I just renamed the tarkov headless and client folder exactly as you said

#

should this say headless when Im creating a session?

#

I see it in the player list:

hexed thunder
#

I double checked another thread and it said to make sure there is profile validation which shows completed:

steady basalt
hexed thunder
#

this portion?

steady basalt
#

i dont think you should be seeing the headless in the player list*

#

did you add the fika.headless.dll in your fika headless bepinex/plugins folder?

hexed thunder
#

yes I did:

#

the PS1 file doesn't work if it cant find that DLL

steady basalt
#

true

#

try generating a new profile. remove that profile from your user\profiles and then run the spt server again and copy the script again

hexed thunder
#

trying

steady basalt
#

if that still doesnt work, post your headless logs

jovial flameBOT
#
Having issues finding your log file?

You can find your log file at %AppData%\..\LocalLow\Battlestate Games\EscapeFromTarkov\Player.log

steady basalt
#

make sure to run the headless alone then get the log file

hexed thunder
#

right, will try regenerating it

#

then will post if that doesn't work.

#

new headless is still in the player menu:

steady basalt
#

ok. close your game and the headless. then, run the headless. once it's finished loading, close it and then send the log

hexed thunder
steady basalt
#

I:/FikaClient/EscapeFromTarkov_Data/Managed'

are you sure you only ran headless? log indicates its running from this path above

hexed thunder
#

doesn't look like it generated a new player entry

steady basalt
#

try deleting the log from that folder then run the headless ONLY

hexed thunder
#

running the headless isn't making an entry in that locallow folder

#

I just re-ran it again

steady basalt
#

um ok, give me the Bepinex\LogOutput.log from headless then

hexed thunder
steady basalt
#

Ok. first of all you're not running the latest version of fika core and fika server. Grab both here: #announcements message

Second, remove all other mods beside Fika.Core.dll and Fika.Headless.dll from both your headless and client. Then try again, see what happens.

hexed thunder
#

will do

steady basalt
#

Make sure you also update Fika Server. Don't forget to edit your fika.jsonc.

steady basalt
hexed thunder
#

correct, I have not done that

#

so far more in the log

steady basalt
#

there u go

#

that wasnt there

#

now the checkbox should be there

hexed thunder
#

I reverted the mods back to see if it was mods or version

steady basalt
#

most likely a mod issue

#

if the issue happen again, go in fikaheadless\logs, find the most recent folder and then post the error log here

hexed thunder
#

restoring the mods gave this result

#

so looks good so far

steady basalt
#

ok, can you start your raid with headless now?

hexed thunder
#

testing

#

success

steady basalt
#

make sure you can actually start the raid

hexed thunder
#

WOW. I feel like I ran into every issue there could be . SPTCustom error, instance error, Version error

#

thank you everyone 🙂

steady basalt
#

at least you caught up quickly and didnt give up

#

we dont mind helping people when they follow directives

#

confirmed that you can get in a raid with the headless?