Simple Waypoint System

• 

  Release Notes
  • Baroni  

  16
  0
  Votes
  16
  Posts
  7588
  Views

  

  v5.4.5 DOTween updated to 1.2.305 added missing startPoint indicator on navMove movement script fixed startPoint indicator at wrong position if reverse is checked fixed Pause() coroutine not getting cancelled on subsequent calls fixed some warnings about invalid/already killed tweens v5.4.6 added BezierPathManager method, converting waypoint index to path point added CTRL+click de/selecting for moving multiple waypoints at once fixed events not being called on reverse paths due to wrong index fixed reversing on bezier paths by returning new path copy each time minimum required Unity version: 2017.4.16
• H

  A simple way to round path corners?
  • Hyunsik  

  11
  0
  Votes
  11
  Posts
  14
  Views

  

  Your questions are confusing :-D As you can see in the scripting reference, "bPoints" is a list of "BezierPoint" classes. Each bezier point has a "wp" waypoint transform (yellow dot in the above screenshot) as well as a "cp" transform array for two control point transforms (blue dots in the above screenshot), shaping the curves for that waypoint. When creating bezier paths you need both. One Waypoint transform and two control point transforms. How are you setting the handle values? (cp[transform]) Via code, just like you do it for a regular path. Create a transform and assign it to bPoints[index].cp[0 or 1]. Which one is left or right is written in the scripting documentation for BezierPoint. You always need to set both, left and right. In the editor, you just click on a waypoint (yellow dot) to make the blue handles appear. If they are not shown you probably have "Show Handles" disabled on the BezierPathManager. I've played with cp for a bit now and I'm not getting the result I want at all the curve looks so awkward If you create and modify the bezier path at runtime, you probably missed calling CalculatePath() on the BezierPathManager to recalculate the path.
• H

  Moving multiple objects along [bezier] path
  • Hyunsik  

  2
  0
  Votes
  2
  Posts
  7
  Views

  

  The script in the other thread uses tweenPath.PathGetPoint(perc) //for instantiating an object at a Vector3 position on the path objMove.tween.fullPosition //for setting the current movement position on the path, on the object's splineMove script Both methods are DOTween methods, which have not changed. Have a look at its scripting reference: http://dotween.demigiant.com/documentation.php#gettingData A bezier path in SWS is different from a "regular path" in regards to its waypoint array. When spawning objects at waypoints, for a bezier path you obviously have to change the "waypoints" variable in that code, since it does not exist on a BezierPathManager. This would be bPoints instead. The rest of it still looks like it would work.
• H

  Dynamically adding and removing multiple events for multiple waypoints on runtime
  • Hyunsik  

  4
  0
  Votes
  4
  Posts
  13
  Views

  

  What is mentioned in the other thread is just adding some additional C# delegates (3) to the movement scripts, so it is easier to react onto specific movement changes via code. Currently it is not high priority to release an update for this only though.
• H

  Is there an option to add stop point?
  • Himanshuchahar  

  4
  0
  Votes
  4
  Posts
  8
  Views

  

  You have to add your own logic in order to "detect" an object in front of the moving object, i.e. by raycasting. This is highly game-specific so there is no one-fits-them-all solution built-in. Your logic can then trigger the Pause/Resume methods.
• K

  Playmaker Actions missing (scripts could not be loaded)
  • Kodagames  

  10
  0
  Votes
  10
  Posts
  17
  Views

  

  Well, thank you for still using it after the years :)
• H

  Diff between Instantiate() and path.Create() when drawing paths
  • Hyunsik  

  15
  0
  Votes
  15
  Posts
  36
  Views

  H

  Ahh how'd I just found out about waypoint events this works beautifully thank you!
• H

  Issue with Vehicle AI
  • Himanshuchahar  

  3
  0
  Votes
  3
  Posts
  9
  Views

  H

  Awesome, worked perfect. Thanks Baroni.
• F

  GameObject with Box Collider and Rigidbody
  • Faketa  

  2
  0
  Votes
  2
  Posts
  5
  Views

  

  Your Rigidbody component likely has gravity enabled. An object can not be affected by gravity and an animation tween (from Simple Waypoint System) at the same time. If you would like to move via an animation tween, you need to disable gravity on it. In the same way, if you would like it to react to physics, you need to disable the movement tween.
• H

  Modifying and Extending
  • Hyunsik  

  3
  0
  Votes
  3
  Posts
  20
  Views

  H

  @Baroni That actually sounds very promising.. thanks!!
• H

  SetPath at runtime does not move object
  • Hyunsik  

  11
  0
  Votes
  11
  Posts
  17
  Views

  H

  Ah yeah I just figured out it's Spline Move > Size To Add I had it 1.1 just like the example and apparently that moved the object. Thanks for responding so quickly! Cheers
• D

  Unexpected extra (first) waypoint node when creating path during runtime
  • doublecubed  

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  Hi, could you please post your runtime path creation code as well? It's difficult for me to find the cause when looking at the screenshots, but it seems like there is an offset on the first waypoint, resulting in the addition of another path point. Is your first waypoint located at (0,0,0) relative to the parent path game object?
• M

  [Bugfix] Editor draws extra path lines for paths that no longer exist when you change the points on a path
  • megamiley  

  4
  0
  Votes
  4
  Posts
  7
  Views

  

  Reproduced with "Enter Play Mode Settings" > "Enter Play Mode Options (Experimental)" enabled, but "Reload Domain" disabled. Won't fix in SWS, this should go into DOTween.
• M

  Disable the default Tools for the main GameObject on a (Bezier)PathManager
  • megamiley  

  2
  0
  Votes
  2
  Posts
  9
  Views

  

  Keeping the first waypoint at (0,0,0) / path origin is actually on purpose, because some time ago, there were bugs with the tweening libraries caused by position offsets on the path and waypoint transforms. They existed in HOTween (DOTween's predecessor) and iTween (removed). Introducing a toggle for disabling transform tools, in order to move the first waypoint, seems a bit overkill to me. Since all waypoints are transforms, you could just select the first waypoint in the hierarchy to add some offset, and then continue with the path tools.
• M

  Add script events to the splineMove and navMove components
  • megamiley  

  2
  0
  Votes
  2
  Posts
  14
  Views

  

  Adding events to the movement classes is something I am going to implement in a future update. The current UnityEvents list is convenient to populate in the editor, but comes short during runtime and also when switching paths often, like you and others have pointed out. In addition to this, something that was requested before was: separate "MovementStarted" (first waypoint) event separate "MovementFinished" (last waypoint) event "PathSwitched" event, so it is possible to un/subscribe to the "onWaypointReached" event For completeness and other users: currently, what I recommend to use is either populating the UnityEvent on a movement script via code at runtime, or use collision triggers along the path instead. Both of these methods allow for the path or collided object to be checked before invoking additional code, therefore supporting path switching. They are demonstrated in the "Events" sample scene.
• M

  Make individual waypoints select-able by click and drag in the editor
  • megamiley  

  3
  0
  Votes
  3
  Posts
  7
  Views

  M

  Cool! FYI, Ctrl+click = toggle select, Shift+click = additive (no selecting), having both wouldn't be too difficult once you get the other working :)
• M

  (Bezier)PathManager doesn't have a visual ability to show that a path is a closed loop
  • megamiley  

  3
  0
  Votes
  3
  Posts
  6
  Views

  M

  Aha, that sounds reasonable then yeah. Thanks for the reply :)
• M

  First waypoint to point in a Bezier Path reacts differently than the rest of the path
  • megamiley  

  3
  0
  Votes
  3
  Posts
  8
  Views

  M

  I see, after doing a bit more testing I now understand the issue and it's exactly as you described it. I would have expected the entire path to be changed until the first Waypoint insead of the first point but it makes sense that it's like this. It's indeed a closed loop path here which was causing this unexpected behavior. I think this should now be a part of my other topic on visually showing closed loop paths on a path level as that would more easily show what the final path would look like in such a case :)
• T

  Issue with events and reversing bezier path
  • TomMP  

  17
  1
  Votes
  17
  Posts
  72
  Views

  M

  I don't see those in my repro scene, maybe you have another object with a movement script in the scene? Difficult to tell. The extra lines seem to be quite random, on one run they're there and on the other their gone. Can't seem to get a grip on why it might happen but it seems to be only visual so I can basically ignore it. I was able to reproduce this, and it is a result of calling "splineMove.Reverse()" at the last waypoint, which invokes the waypointChange event twice - once for each direction. This results in firing off the next PathConnection in the SplineEventHandler instantly. Honestly I'm not sure how to avoid this at the moment, I may have to contact the developer of DOTween for that. You can just avoid calling Reverse though in your SplineEventHandler, and add the turn manually: Yes! That fixed the issue! There was a small bug still where it would jump back 1 point and then teleport to the end again when the path got reversed but I was able to fix that by changing the moveToPath to _splineMove.moveToPath = connection.StartPath != connection.NewPath; If moveToPath was always true then it would again double fire the event which would cause issues, if the two connected paths are the same then it's same to assume that the cube doesn't need to move to the new location Thanks! Going to add that, with the other fixes, to the next version. Yay! "GetFirstPoint" would just return 0 every time, as there is nothing to calculate :) Haha true, it would be more about consistency in that case if a GetLastPoint method was added, but I can create those two myself as an extension method when needed :) As an asset developer I'm forced to use the first cycle version (2019.3.0) for uploading, due to supporting all versions above that. Personally, it's not about the stability of the editor itself, but because of the various Package Manager products, with most of them in preview - or not working well in combination with other packages. Basically since the Package Manager was released, we've had a guideline to avoid all packages shipping with it (except UI). That's why I'm still developing with one of the last versions without it (2017 LTS) or soon 2018 LTS. Aha, never knew that, sounds reasonable Thanks for all the help with this, now I need to create the paths for my entire island and also create a cleaner UI for this system :P
• B

  MovetoPath and Reverse
  • Brunob  

  2
  0
  Votes
  2
  Posts
  11
  Views

  

  Hello, calling the Reverse() method on the movement script can be done at any time, even between waypoints. It is specifically designed for restarting movement at the current position, but in the opposite direction. It also works on bezier paths. What exactly do you mean by "transported to another point"? Setting "reverse = true" during movement does not result in any change, because this would need the movement to restart. I'm not sure what you mean by your second question, could you elaborate? You could either: move the object to the path via your own movement method set a different "startPoint" before calling StartMove(), so it will walk to a waypoint on the path instead of its beginning or have a look at our "PathInput" sample scene which uses absolute positioning on the current path by input. You could also use this to move the character to the target path by input, and then start moving on it automatically.