Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not moving at all in dungeon #4

Closed
KalasB opened this issue Apr 13, 2024 · 4 comments
Closed

Not moving at all in dungeon #4

KalasB opened this issue Apr 13, 2024 · 4 comments

Comments

@KalasB
Copy link

KalasB commented Apr 13, 2024

Hi,

I have vnavmesh, RS, vbm and AutoDuty (36). However, despite loading into the dungeons, it seems to fail already at the first node.

2024-04-14 01:12:03.464 +02:00 [INF] [AutoDuty] Running Copperbell Mines 1 Times
2024-04-14 01:12:03.464 +02:00 [INF] [AutoDuty] Queueing Duty Support: Copperbell Mines
2024-04-14 01:12:06.796 +02:00 [INF] [vnavmesh] Starting transition from 'ffxiv/fst_f1/twn/f1ti/level/f1ti//118BD//0.0.0.0' to ''
2024-04-14 01:12:07.113 +02:00 [INF] [vnavmesh] Starting transition from '' to 'ffxiv/wil_w1/dun/w1d1/level/w1d1//4092F//0.0.0.0'
2024-04-14 01:12:07.130 +02:00 [INF] [vnavmesh] Finishing transition to 'ffxiv/wil_w1/dun/w1d1/level/w1d1//4092F//0.0.0.0'
2024-04-14 01:12:12.845 +02:00 [INF] [Collections] InstanceTab->OnDutyStarted: Received DutyStarted event
2024-04-14 01:12:12.953 +02:00 [INF] [AutoDuty] Starting Navigation
2024-04-14 01:12:12.953 +02:00 [INF] [vnavmesh] Queueing move-to <-22218,000. 2385,000. -20819,000>
2024-04-14 01:12:12.953 +02:00 [ERR] [vnavmesh] Failed to find a path from <-254,4203. 23,845118. -170,7458> (100000040011F) to <-22218. 2385. -20819> (0): failed to find polygon on a mesh
2024-04-14 01:12:12.979 +02:00 [INF] [vnavmesh] Pathfinding complete
2024-04-14 01:12:18.312 +02:00 [INF] [vnavmesh] Queueing move-to <-22218,000. 2385,000. -20819,000>
2024-04-14 01:12:18.312 +02:00 [ERR] [vnavmesh] Failed to find a path from <-254,4203. 23,845118. -170,7458> (100000040011F) to <-22218. 2385. -20819> (0): failed to find polygon on a mesh
2024-04-14 01:12:18.323 +02:00 [INF] [vnavmesh] Pathfinding complete
2024-04-14 01:12:29.008 +02:00 [INF] [vnavmesh] Queueing move-to <-20630,000. 2347,000. -20846,000>
2024-04-14 01:12:29.008 +02:00 [ERR] [vnavmesh] Failed to find a path from <-254,4203. 23,845118. -170,7458> (100000040011F) to <-20630. 2347. -20846> (0): failed to find polygon on a mesh

@KalasB
Copy link
Author

KalasB commented Apr 14, 2024

@adambennett55 curiously, it seems to work with non-testing version (and manually downloaded paths).

@Herculezz55
Copy link
Contributor

Yes the localization patch has not been merged into testing yet, I will do it this evening

@Herculezz55
Copy link
Contributor

pushed localization to test last night, delete and reinstall

@KalasB
Copy link
Author

KalasB commented Apr 15, 2024

Sweet, thanks!

One question though, @adambennett55 : If I create a Path from the UI, does the localization apply to that? Can't seem to get it to work that way.

VeraNala pushed a commit to VeraNala/AutoDuty that referenced this issue Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants