Author Topic: Stupid Question  (Read 3308 times)

0 Members and 1 Guest are viewing this topic.

Offline ryanchealth

  • 25
  • Why did I want a job at 16?
How do I make a Convoy move to a Jumpoint.  I have created my first mission and working on the 2nd that deals with a convoy escort.  I created the Jump Node and created Waypoint but the ship stand still.  Do I need to do this in the Events editor or is there a simpler way?

 

Offline Shivan Hunter

  • 210
  • FRED needs lambdas!
Typically, you give your ships an order to follow the waypoint (ship dialog -> "Initial orders" -> "Waypoints"; note that FRED will hide the "Waypoints" goal unless there is an actual waypoint in the mission).

The best/most robust way to do this is to create a waypoint for each ship in the convoy, tell each ship to go to its own waypoint "Waypoints" or "Waypoints Once", doesn't matter) and set each ship's departure cue to check for when it's within a certain distance of its waypoint.

If you use a single waypoint for an entire convoy, the ships' paths will converge on that point and they'll start bumping into each other. Worse, they may never actually reach the waypoint, if two ships are colliding with each other trying to occupy the same space. This is another good reason to use a departure cue that checks for a distance, rather than a "Warp" order with lower priority than a "Waypoints once" order (which is the simple way to do it).

Note that ships in a wing will get into a formation automatically, and will all depart at once (you can only set a departure cue for the wing, not for individual ships that are in a wing).

Good luck! Glad to see more people making missions :D

 

Offline Colonol Dekker

  • HLP is my mistress
  • 213
  • Aken Tigh Dekker- you've probably heard me
    • My old squad sub-domain
Freespace comes with a comprehensive Fred tutorial, we also have one in detail in the modding wiki if memory serves.  Finish both to learn most of the features you'll need to make an entire campaign :)
« Last Edit: April 22, 2023, 03:18:37 am by Colonol Dekker »
Campaigns I've added my distinctiveness to-
- Blue Planet: Battle Captains
-Battle of Neptune
-Between the Ashes 2
-Blue planet: Age of Aquarius
-FOTG?
-Inferno R1
-Ribos: The aftermath / -Retreat from Deneb
-Sol: A History
-TBP EACW teaser
-Earth Brakiri war
-TBP Fortune Hunters (I think?)
-TBP Relic
-Trancsend (Possibly?)
-Uncharted Territory
-Vassagos Dirge
-War Machine
(Others lost to the mists of time and no discernible audit trail)

Your friendly Orestes tactical controller.

Secret bomb God.
That one time I got permabanned and got to read who was being bitxhy about me :p....
GO GO DEKKER RANGERSSSS!!!!!!!!!!!!!!!!!
President of the Scooby Doo Model Appreciation Society
The only good Zod is a dead Zod
NEWGROUNDS COMEDY GOLD, UPDATED DAILY
http://badges.steamprofile.com/profile/default/steam/76561198011784807.png

 

Offline 0rph3u5

  • 211
  • Oceans rise. Empires fall.
"Waypoints" or "Waypoints Once", doesn't matter

There is a difference that does matter between these two AI goals
- "Waypoints" means that a ship will loop on the waypoint path, meaning when it reaches the final waypoint it will head back to the first and start again. As a result the ship will not deccelerate when approaching a waypoint. "Waypoints" will never be true if checked with "are-waypoints-done-delay"
- "Waypoints Once" means that the ship will stop on the final waypoint, as logic dicatates it will reduce speed on approach to the final waypoint. "Waypoints Once" can be checked with "are-waypoints-done-delay".

set each ship's departure cue to check for when it's within a certain distance of its waypoint.

While this is roibust and avoids a bug where an impromperly configured ship has problems "hitting" a waypoint, it also means that waypoint clock visible on a targeted friendly ship will be off. Considering this waypoint clock is dynamic (i.e. it responds to the ship's speed), it is the most accurate representation for the player when trying to check for a time estimate on task completion.
"As you sought to steal a kingdom for yourself, so must you do again, a thousand times over. For a theft, a true theft, must be practiced to be earned." - The terms of Nyrissa's curse, Pathfinder: Kingmaker

==================

"I am Curiosity, and I've always wondered what would become of you, here at the end of the world." - The Guide/The Curious Other, Othercide

"When you work with water, you have to know and respect it. When you labour to subdue it, you have to understand that one day it may rise up and turn all your labours into nothing. For what is water, which seeks to make all things level, which has no taste or colour of its own, but a liquid form of Nothing?" - Graham Swift, Waterland

"...because they are not Dragons."

 

Offline Shivan Hunter

  • 210
  • FRED needs lambdas!
There is a difference that does matter between these two AI goals
- "Waypoints" means that a ship will loop on the waypoint path, meaning when it reaches the final waypoint it will head back to the first and start again. As a result the ship will not deccelerate when approaching a waypoint. "Waypoints" will never be true if checked with "are-waypoints-done-delay"
- "Waypoints Once" means that the ship will stop on the final waypoint, as logic dicatates it will reduce speed on approach to the final waypoint. "Waypoints Once" can be checked with "are-waypoints-done-delay".

True 'nuff! I was hasty in my explanation there, but I meant that in my case - where the ships get close and are told to depart via departure cue - it doesn't matter which is used, since the goal should get "interrupted" by the departure cue anyway. (Departure cues override all goals and other AI behavior as far as I'm aware)

You can see the effect of a "Waypoints" (looping) goal, used on a waypoint path with only one waypoint, in some [V] missions - the one that comes to mind is the one with the Parracombe and Jooyun and the asteroid field. The ships reach their waypoints and start senselessly dancing around that one spot, since they're effectively being told to "patrol" a "path" consisting of a single point. So yeah, 0rph3u5 is right, don't do that :P

While this is roibust and avoids a bug where an impromperly configured ship has problems "hitting" a waypoint, it also means that waypoint clock visible on a targeted friendly ship will be off. Considering this waypoint clock is dynamic (i.e. it responds to the ship's speed), it is the most accurate representation for the player when trying to check for a time estimate on task completion.

Also true. But the distance check doesn't have to be large - checking if the ship is within ~100 meters or so would make the discrepancy only a few seconds, and IIRC would still avoid most problems (depending on the mission, of course. It won't help if two Collosi are trying to occupy the same space!)

Although there may be new best-practices for waypoints that FREDders have come up with in the last decade, in which case ignore me :nervous: