As of now, we are unable to respawn/go into the ready room once we die. We are stuck in our bodies after we die and can't spectate,

引用自 HighOrpheus：

As of now, we are unable to respawn/go into the ready room once we die. We are stuck in our bodies after we die and can't spectate,

any fix for this yet?

yeah, its working again

We're having the same issues as HighOrpheus, Defiant Skies map, when killed, we just fall facedown and don't pop into spectator, and no option to back into the ready room appears.

EDIT: We can use console to get back into ready room, and that works. Just doesn't have GUI prompt. Is that working as intended?

When I tested it sent me back to the ready room and then I was able to spectate with F6.

Is this a dedicated server or a hosted game?

Try hitting F4 to go to the ready room and then F6 to spectate.

[I've had issues getting the wave respawns to work. This seems to be a byproduct of that with the GUI missing for whatever reason.]

引用自 tjl：

When I tested it sent me back to the ready room and then I was able to spectate with F6.

Is this a dedicated server or a hosted game?

Hosted game with friends, pardon me, F6 does work. Sorry, might be us not ready the manual. EDIT: Sorry, still can't return to ready room from spectate. Still, we have the console command option.
Thanks for the mod regardless, it's nice to have more formal objectives.

Thanks for the update. Will try and see what is happening.

hello first thanks for this mod, i just want to report some bugs in the outpost mission:

AI are spawning into some random building like the one in construction and are preventing the waves to spawn

Between each map i need to restart my hosted game to permit the mission to work

hope this report helps

Thanks for the report. Can you publish a screenshot to steam of what you mean here.

The ai are split into 2 parts - overwatch and the wave.

There are overwatch spawns in the construction building and the overwatch ai will respawn but how they are counted and their respawn in independent of the wave ai entirely.

There is a spawn point for the wave ai in the lower part of the construction building. They should be moving out or are they getting stuck? On occasions I've also seen that part of the wave and other parts of the wave getting stuck on some of the stuff outside the building. I can try to move that spawn point and add in navblockers but that won't take effect until the next point release.

The needing to restart the hosted game between maps etc has been reported to the devs and will be fixed in the next point release.

Intel Retrieval TJL Mod
ABILITY TO CUSTOMIZE THE AI IS A WORK IN PROGRESS

- This currently uses the `search` command which is not really working in the main game. It was working a lot better before Kythera ai. I have some ideas to test out but that is going to take a bit of time.

- If you want a challenge then go loud and max out the ai settings.

Some changes made to the "Chose your OPFOR" system.

- ai with pistols will currently keep them holstered.
- some of the normal ai issues seem to be compounded.

Updates to the random killhouse gamemode put in.

May get significant lag spikes. Cause of this is not known.

This mod is great, however there is an annoying bug or event that takes place periodically.
While playing solo with GB PVE Checkpoint Ranch , sometimes during the first few minutes, a red spawn restriction zone alert will popup and blur the screen. When this happens, I try and back track in an attempt for the blurred screen to return to normal, however in some cases it remains blurred while I attempt to find the path to remove it; many times being killed by enemy while my screen is blurred due to the spawn restriction zone. When viewing the map during these instances, I'm clearly between the red boundary lines of the objective. I've only experienced this with the ranch map.

Thanks for the post.
I've put in spawn restriction when a point gets captured so the opfor ai can spawn in. Something with the spawn protection broke during the 1035 on the BFS side. It has been reported but I do not know if it will be fixed as part of 1035.2.