I found that it ignores attributes during merging

it does, i have no idea how to fix that properly

the globalmerge_auto command calls nav_analyze at the end, that should fix any auto-generatable attributes
means its a nonissue really

Might as well post this here, but I used gm_fork or the map to change & I've literally set it on auto all night & its still analyzing, is it meant to take THAT long?

引用自 NinjaNate898：

Might as well post this here, but I used gm_fork or the map to change & I've literally set it on auto all night & its still analyzing, is it meant to take THAT long?

nav_analyze is the reason nav_generate takes so damn long

引用自 Zeb：

引用自 NinjaNate898：

Might as well post this here, but I used gm_fork or the map to change & I've literally set it on auto all night & its still analyzing, is it meant to take THAT long?

nav_analyze is the reason nav_generate takes so damn long

damn, but is it meant to take all night though? (8-10 hours)

引用自 NinjaNate898：

引用自 Zeb：

nav_analyze is the reason nav_generate takes so damn long

damn, but is it meant to take all night though? (8-10 hours)

It ranges from seconds (classic flatgrass) to hours (gm_bigcity or other huge maps) so it might be as simple of an answer as yes I'm afraid

It highlights the nav_mesh blocks and i can't get rid of it, unless it's because of sv_cheats.

引用自 NinjaNate898：

引用自 Zeb：

nav_analyze is the reason nav_generate takes so damn long

damn, but is it meant to take all night though? (8-10 hours)

fork ends up with tens of thousands of navareas
each one has to have accurate visibility data with every nearby area
it's a time consuming process for computers

I've been looking everywhere on this page about disabling the visual mesh once its fully completed a navmesh_globalmerge_auto, Nukeface has the same Issue

Visual mesh? Never heard that terminology used before

But many, many nexbots need the calculated visibility data, it's essential if you're publishing a navmesh to the workshop.

So far working good although I have noticed from time to time slops seem to end up going through the floor on some maps which is probably a bad thing. Maybe not though i'll have to test more and see.

Never seen that cause any big problems for bots.
Knock on wood lol

ConVarRef host_thread_mode doesn't point to an existing ConVar
ConVarRef sb_perf_collect doesn't point to an existing ConVar

some stuff that popped up when I did the command