Maintenance for the week of November 10:
• PC/Mac: NA and EU megaservers for patch maintenance – November 10, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – November 12, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – November 12, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PC/Mac: NA and EU megaservers for patch maintenance – November 10, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – November 12, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – November 12, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
[REQUEST] First path knot waiting time should be performed
AnduinTryggva
✭✭✭✭✭
✭✭
✭✭
I tend to place paths and give the first path knot a certain waiting time before the movement to the second knot happens so as to have visitors first appreciate the initial scenery or other objectives.
Unfortunately, during the first initialization this waiting time is not at all performed and the actor is immediately proceeding to the second knot.
Can we please implement that the waiting time on knot 1 is actually performed? Thank you!
Edited by ZOS_Kevin on November 7, 2024 10:13AM Unfortunately, during the first initialization this waiting time is not at all performed and the actor is immediately proceeding to the second knot.
Can we please implement that the waiting time on knot 1 is actually performed? Thank you!
1
-
MoonPile✭✭✭✭✭I noticed this as well, had to add a second one for it to work as expected. This is weird, is it bugged?0 -
Malkorga✭✭✭Can you not just edit the route and adjust the first node? I have no issues adjusting the time on my path nodes.0 -
AnduinTryggva✭✭✭✭✭
✭✭It is about the very first loop. It does not matter how much waiting time you edit into the first node. When the path starts the actor will just ignore the waiting time of the first knot. Current work around is to place a second node immediately there with the desired waiting time. But that is just a workaround and not convenient as you loose one node position (maximum number is 30 irc).2