Closed L1ghtman2k closed 3 months ago
Forward base: https://streamable.com/8zqcrw
Given that the only changes between v1.6.4
and v1.7.0
are the following https://github.com/R2Northstar/NorthstarMods/compare/b715a69c711d56490657a3057f3faba8fb26aa48...311affdb844905f5277a9f9a757ac20cdf3995ff and Navmeshes, I feel confident in claiming that issue likely lies with the latter.
@taskinoz any ideas?
@L1ghtman2k maybe try deleting navmeshes and graphs by deleting the following folders on server host:
R2Northstar/mods/Northstar.CustomServers/mod/maps/graphs
R2Northstar/mods/Northstar.CustomServers/mod/maps/navmesh
Then restart game of host and try the same spots again. If you now no longer get teleported, the issue is with navs.
This looks like the game is trying to correct ai positions by teleporting the titan. The titan only navs were cut down to only include geometry reachable by titans, but it seems like it has some problems and oversights. :)
The solution I see as of now is:
A more future-proof solution would be:
if navmeshes are the issue, we could probably just change the disembark scripts to be able to disable the navmesh usage there
this is assuming that it's specifically a disembark issue and not just an ai one
These are definitely navmesh issues. I forgot about the hallway in wargames, and removed that bridge from drydock, because I though titans shouldn't drop up there. And boomtown navs havent been updated to fix titan stuff.
Hey @taskinoz, I was wondering if you could confirm @GeckoEidechse comment
I was wondering if deleting those files would suffice to fix the teleport issues(assuming of course titans lose the capability to move and use navmesh)
Nvm, Seems like it works, I just had it tested, and wargames/drydock don't have the same issues anymore, Thanks @GeckoEidechse
Removing Navs like Gecko said will get rid of the teleporting issues till I can remake them
Closing this as the navmeshes have been rebuilt by me and this issue is pretty much fixed in all maps.
Titans teleport on disembarking, in spots where they typically don't do that
Examples:
We have tested the above on 1.6.4, and these issues DID NOT exist prior to 1.7.0