#Enemies Stuck

1 messages · Page 1 of 1 (latest)

pine cloak
#

Enemies are stuck in the top right corner, making run progression ~5x slower.

Details:

  • 70 hour run, first noticed issue a few hours in
  • Lasts hours at a time, fixes itself, and repeats at seemingly random intervals. Bugged >50% of the time
  • Software: AutoSkip, WaveStreaming, WaveSurge, WaveVortex
  • Modules: Attack Speed, Multishot, Divine Blessing, Advanced Splash, Granite Foundation, Bulwark, Knight's Boost of Power
  • MT9, no buildings except workshop level 1, construction firm level 1, and hq level 1

Theory: Enemies pathfind via NavMesh and carve an area out around them while present on the NavMesh (to allow enemies to pathfind around eachother). If there's a clump of enemies on or near the enemy spawner, it could be carving out a large area of the NavMesh, causing future spawned enemies' pathfinding to break. Clump of enemies on spawner = enemy spawns on part of the nav mesh that's been carved out = it can't pathfind?
This is exaggerated by the burst/aoe/random nature of the blueprint, where kills rely on divine blessing and advanced splash triggering together, and destroying 80+ enemies at once.

Other important notes:

  • All other reports are in the same map and location. It could be something with the mesh or spawner in that area, or even just the coordinate that enemies spawn on/pass over (some kind of NavMesh chunk error, coords rounding error, divide by 0 error, weird unity stuff?)
  • Possibly discovered in previous dicsussions that enemies are trying to pathfind to (infinity, 0, 0) #infinity-phase message
1.png
pine cloak
haughty thistle
#

do the !logs have anything at all?

sweet tideBOT
#
Logfile location

%userprofile%\appdata\locallow\Fire Sword Studios\The Perfect Tower II
Current log: perfect.log
Previous log: perfect.1.log

pine cloak
#

it looks like my last log is from a couple days ago and it doesn't have anything of value

# 
Start of new Log
The Perfect Tower II - v0.51.0  - 388
Unity version: 2020.3.48f1
OS:            Windows 11  (10.0.26100) 64bit
Processor:     13th Gen Intel(R) Core(TM) i5-13600KF
RAM:           32616 MB
Graphics: 
    Renderer:  NVIDIA GeForce RTX 4070 SUPER
    Version:   Direct3D 11.0 [level 11.1]
    VRAM:      11999 MB
12.10.2025 00:13:23 [Info] Server time: 1760228004
12.10.2025 00:13:47 [Info] Finished loading save!
12.10.2025 00:13:47 [Info] Timestamp town: 1760227924
12.10.2025 00:13:47 [Info] Offline Time: 0 Years, 0 Days 0:01:20
haughty thistle
#

yeah that is definitively nothing

pine cloak
#

interestingly >90 of the enemies are normal type. and just a couple archers mixed into the waves that are working

#

according to f2

#

yeah, archer hits 0 once in a while, so it's just the normal enemies that are stuck

pine cloak
#

This bug is still present

1.png
magic dagger
#

Of course it's still present, pretty sure the code regarding that hasn't been touched.

pine cloak
#

It's been a few months without any comments and it seemed like a bug that was worth fixing, I figured it had just been forgotten about or something

woven elk
#

though also why the hell did you spend 70 hours on a run

#

for the most part this kind of bug can be avoided by just using something like super multishot or super bounce, which would kill the enemies that won't move into your tower's range

#

also not sure as to why you found it and were able to reproduce it after so long, but I have never seen it happen or seen anyone else have it happen

#

not really much in your blueprint that would cause enemies to bug out either

pine cloak
#

when it does happen it definitely ruins that run, kill speed drops to 5-10% of the normal

#

it can also happen just a couple minutes into a run, i have a few theories/patterns earlier in the post but PeepoShrug

#

but yes, I probably shouldn't have runs going for 70 hours, lol

woven elk
#

seems like you're cursed or something

#

you angered the gods by spending 70 hours in such a bad run

#

I can't seem to reproduce this at all either

#

enemies just head straight for the tower without any sort of stopping or getting stuck

pine cloak
#

i haven't tried to find a consistent repro yet

#

other than finding it happens more often when you kill enemies in large bursts, i.e. divine blessing + adv splash

woven elk
#

really not much the devs can do if they can't reproduce it themselves somehow

#

next time you get the bug can you take a screenshot of it with the f2 debug menu open?

haughty thistle
#

i guess ill look at that spawner

pine cloak
#

oh hey i just repro'd it

#

Repro: Enemies stuck in Forest

Software:
Autoskip, Wave Streaming, Wave Surge, Wave Vortex

BP:
Attack Speed, Divine Blessing, Adv Splash, Granite Foundation
BcHBDcIwDAXQVaIMkAHIDYkJekQc3Po3WKRuFDtFqGL3vnfGuQ60LuoWb+EZH4rtF6ZGX0UP91Hyug9lctk1lU4qjkzutHySNYDzXGEmWhLLIYpsrZK9E/FBuoDj638B

FPS Limit: 180
Edit: FPS limit not needed

should see enemies get stuck in the first couple splashes, with more getting stuck the longer the run goes

haughty thistle
woven elk
#

all enemies are making it to the tower without any sort of getting stuck

pine cloak
#

interesting

#

should I do anything with it on my end?
could stream maybe if it helps

woven elk
#

I'm trying to think of anything else that could be affecting it

pine cloak
#

wave streaming speed/accel?

#

x2 speed
edit: can be repro'd on x2 and x3 speed

haughty thistle
#

i know ive had infinitely reproducable broken enemy behavior, but that required cheating to happen

pine cloak
#

i haven't run any cheats or otherwise modified the game

haughty thistle
#

though frankly, i highly doubt it is the same thing

#

as the other thing actually had things pop up in logs

pine cloak
#

I'm curious if one of you could load my save?

#

so we can see if it's a town/pc-system difference

haughty thistle
#

maybe, can't load a save i don't have though

pine cloak
#

gonna dm it if that's cool, worked hard on this no buildings save

haughty thistle
#

ok ive even reproduced it without wave vortex, though it might be easier with it just to get more enemies

image.png
pine cloak
#

for sure. the more enemies clumped together the better, and the ones in the corner will naturally pile up as the run goes on

haughty thistle
#

this is also on a save at mt0, just to eliminate as many factors as possible

woven elk
#

and I accidentally left on a run

#

been going for nearly 7 hours and no weird issues

haughty thistle
#

was it with the given blueprint?

#

this only seems to be happening in the top right spawner in forest, which is the third loaded, i may have to try other regions

magic dagger
haughty thistle
#

using advanced techniques (i have no idea how cameras work), i have determined that the broken enemy (circled) is a few meters away from the spawn point

image.png
#

if only i had access to actually useful information during runtime

#

ok in my attempts to see if doing other advanced techniques would affect the situation, ive made like 20 enemies get stuck somehow

woven elk
haughty thistle
#

don't mind me, I'm just going to look through every single thing in forest to see if there is literally anything in that position

woven elk
haughty thistle
#

great because i really don't want to look through the geometry of every object

woven elk
haughty thistle
#

i really need to figure out how unity cameras work so i can get a better view of this

pine cloak
#

I'd be happy to dig into it or help in some way, I have 10+ years of Unity experience
but I also understand if you keep the project files internal

merry lantern
woven elk
#

@tidal pivot

sinful tide
#

for those trying to replicate: all software through mt7, use a reflect-based build (such as basic shield + any elemental barrier)

#

eventually you start to see the waves "pulsing" due to the cluster of enemies stuck on the top-right lane

haughty thistle
#

i think it is fixed on the supporter branch now, but it might need more rigorous testing

woven elk
#

or at least what we thought was the issue behind it

#

was something related to where the different shapes that make up the navmesh lined up

tidal pivot
#

Was anyone able to reproduce it in the latest version?

merry lantern
#

the bug was always hard to reproduce, so I don't think people are gonna experience it again for a while. So technically it could be called patched, we just don't know

tidal pivot
#

we need a "potentially fixed" tag xD

woven elk
#

well clearly @pine cloak was really good at being able to reproduce it