The First Descendant

The First Descendant

View Stats:
7 minutes to launch every time.
My game takes about 7 minutes from the moment I click it to launch.

I'm using an M.2 drive, and it's the only game that does this. Any solutions or ideas on what it could be?

Once I'm in the game, the maps load instantly without any issues.
Originally posted by Grimzy:
I just came to say that after the patch today, the game again, starts immediately within a few seconds xD.....like....idk xD
< >
Showing 1-15 of 35 comments
Grimzy 14 Aug @ 8:18am 
Originally posted by Vekkaro:
My game takes about 7 minutes from the moment I click it to launch.

I'm using an M.2 drive, and it's the only game that does this. Any solutions or ideas on what it could be?

Once I'm in the game, the maps load instantly without any issues.


I actually have the same, it originally started when I did a bios update, but then the day 1 of season 3 it was launching instantly, and after the first hotfix post season 3 launch it again takes a while to start.

Have not been able to figure it out. Asside for this launch delay the game runs perfectly with 0 crashes or stutters.
HaloSign 14 Aug @ 8:19am 
Indeed, the start is delayed but this is a server issue (the network connection negotiation procedure seems to have a wrong time out setup)
7 minutes for boot doesn't sound like a network issue. More like compiling shaders each time maybe?
Try disabling and re-enabling shader pre caching in steam->settings->download. Maybe that helps...
Vekkaro 14 Aug @ 9:02am 
No luck so far. I also tried reinstalling the video drivers as well (with several versions) and even activate and disable some things in the bios like secure boot.


It's the only game that's giving me this kind of problems. Is super strange.
Might be worth checking the size of your shader cache in the Nvidia control panel>Manage 3d settings, if you're on Nvidia. It defaults to less than 10gb, which isn't anywhere near enough space if you are playing more than one game. Skyrim with CS shaders needs 50gbs all by itself. I'd imagine with all the zones, enemies and effects this game has it would need near the same.
Last edited by Apost Khan; 14 Aug @ 9:23am
Vekkaro 14 Aug @ 9:33am 
Im using an AMD gpu (RX6600). I'll see if there's something similar for my card, thanks!
Nemesis 14 Aug @ 12:14pm 
you guys should read this, really trying to get people to notice it...
https://steamhost.cn/steamcommunity_com/app/2074920/discussions/0/604163783076875065/?tscn=1754733741

you can check your disk usage in Resource Monitor on your computer, watch your disk die...
Grimzy 14 Aug @ 12:36pm 
Originally posted by Nemesis:
you guys should read this, really trying to get people to notice it...
https://steamhost.cn/steamcommunity_com/app/2074920/discussions/0/604163783076875065/?tscn=1754733741

you can check your disk usage in Resource Monitor on your computer, watch your disk die...

Stop posting that in every thread because that is completely unrelated to any of the issues.....
Vekkaro 15 Aug @ 3:20pm 
After reinstalling Windows and all my games again im still having this issue. Idk what to do.
Just because you have an M.2 does not mean you have the BUS speed to fully utilize it.
NOR does it account for how much other garbage you have running in the back round while the game is loading.
Vekkaro 15 Aug @ 8:36pm 
I did a clean W11 install, I debloated my sysyem after the first boot and im still having the same problem.

I still don't understand why this is the only game that do that.
HaloSign 15 Aug @ 10:25pm 
Originally posted by Vekkaro:
I did a clean W11 install, I debloated my sysyem after the first boot and im still having the same problem.

I still don't understand why this is the only game that do that.

I actually wrote what the most probably root cause of this issue is.
Reinstallation of the local OS on your PC will never fix such issues…

Anyhow, in order to find the delay, you need to use the “tracert" command.
usage: tracert -d <ip-address>

IP-adress: how to identify
TFD uses these ports:
27015, 27036 for TCP, and 27015, 27031-27036 for UDP

You could try to find the ip-address using the netstat command.

First: open a power shell or CLI window
start TFD
alt-tab to the command window
Use the command:
netstat -a -f -n | FINDSTR 270
check which ip address is displayed having the port according to the listed above
tracert -d < the ip address shown in netstat>

check where the delay is coming from.
If it is the last hop then it’s a TFD server issue

Maybe you see something you can fix (e.g. local router delay, bad/slow DNS server etc.)
Last edited by HaloSign; 15 Aug @ 10:27pm
Vekkaro 16 Aug @ 7:42am 
Originally posted by HaloSign:
Originally posted by Vekkaro:
I did a clean W11 install, I debloated my sysyem after the first boot and im still having the same problem.

I still don't understand why this is the only game that do that.

I actually wrote what the most probably root cause of this issue is.
Reinstallation of the local OS on your PC will never fix such issues…

Anyhow, in order to find the delay, you need to use the “tracert" command.
usage: tracert -d <ip-address>

IP-adress: how to identify
TFD uses these ports:
27015, 27036 for TCP, and 27015, 27031-27036 for UDP

You could try to find the ip-address using the netstat command.

First: open a power shell or CLI window
start TFD
alt-tab to the command window
Use the command:
netstat -a -f -n | FINDSTR 270
check which ip address is displayed having the port according to the listed above
tracert -d < the ip address shown in netstat>

check where the delay is coming from.
If it is the last hop then it’s a TFD server issue

Maybe you see something you can fix (e.g. local router delay, bad/slow DNS server etc.)

No luck. I don't know what else to try. I want to play the game but it's becoming impossible for me.
Aw3tastic 16 Aug @ 10:17am 
I had the same issue, I have a monster rig, but any time I put the settings to "cinematic" I get the same issue.

I can even have ray tracing on cinematic, but if the game itself is set to cinematic it just doesn't run.

I changed the game to Ultra, with Cinematic ray tracing and AMD FSR on the highest settings and the problem just went away.

I also had a bug where my settings wouldn't save until I logged in, so every time I booted up it was stuck in cinematic, but I fixed that.

So try a lower base game setting, and make sure it's saving the next time you boot.

Don't know if that helps, but before the patch there was 0 issue running everything on cinematic. :/
Last edited by Aw3tastic; 16 Aug @ 10:19am
Echo2Omega 16 Aug @ 11:35am 
Originally posted by Vekkaro:
I did a clean W11 install, I debloated my sysyem after the first boot and im still having the same problem.

I still don't understand why this is the only game that do that.

There are several changes to windows settings that you should make (internet search is your friend) for gaming that are not default windows settings.

Update your bios.

You may also have improper settings for your system in your bios. Consult your board mfg's guide for settings.
< >
Showing 1-15 of 35 comments
Per page: 1530 50