# Spawned at beginning of level and got stuck could not progress with team

**URL:** <https://forums.fatsharkgames.com/t/spawned-at-beginning-of-level-and-got-stuck-could-not-progress-with-team/69693>\
**Category:** Bugs\
**Tags:** acknowledged\
**Created:** [December 17, 2022, 11:37am UTC](https://forums.fatsharkgames.com/t/spawned-at-beginning-of-level-and-got-stuck-could-not-progress-with-team/69693 "2022-12-17T11:37:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![N00DLE](https://dub1.discourse-cdn.com/flex013/user_avatar/forums.fatsharkgames.com/n00dle/32/66144_2.png) [@N00DLE](https://forums.fatsharkgames.com/u/N00DLE)\
**Post date:** [December 17, 2022, 11:37am UTC](https://forums.fatsharkgames.com/t/spawned-at-beginning-of-level-and-got-stuck-could-not-progress-with-team/69693/1 "2022-12-17T11:37:38Z")

</div>

had to run all the way to my team that was behind a airlock and no enemies would spawn so I could be rescued had to leave so they could complete the mission, that absolutely should not have happened please find a fix for that cause it shouldn’t happen and I don’t want others to experience the same thing i want everyone to have fun and not get screwed over due to a major bug such as that

---

<div class="post-metadata">

**Author:** ![FatsharkQuickpaw](https://dub1.discourse-cdn.com/flex013/user_avatar/forums.fatsharkgames.com/fatsharkquickpaw/32/35638_2.png) [@FatsharkQuickpaw](https://forums.fatsharkgames.com/u/FatsharkQuickpaw)\
**Post date:** [December 17, 2022, 11:52am UTC](https://forums.fatsharkgames.com/t/spawned-at-beginning-of-level-and-got-stuck-could-not-progress-with-team/69693/2 "2022-12-17T11:52:28Z")

</div>

Thank you for your report! Could you please provide us with the console logs for the session where this happened?

These may be found by doing the following:

1. Press the Windows key + R
2. Enter %appdata% within the search input and select ‘OK’
3. Navigate to AppData\Roaming\Fatshark\Darktide\console\_logs
4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
5. Upload here
