Author Topic: Simple Problem, Why Don't I Get It?  (Read 1675 times)

0 Members and 1 Guest are viewing this topic.

Offline Rampage

  • Son Of Rampage
  • 211
  • Urogynaecologist
Simple Problem, Why Don't I Get It?
Okay, I'm going to ask this [hopefully] once... and only once:

How can I configure paths for my model(s)?  Is there a program I can use?  Is there a mathematical operation that I can do to obtain the coordinates?

This is what I see:
Almost all of the models I have opened up to have a look-see have [irrationally] queer numbers as path coordinates and radii.  This is consistent with all original and fan-made Freespace models.  I can't detect a logical pattern in this - façade.

This is what I do:
When I make paths for, lets say, docking bays, I tend to use integers.  For example, I have a docking point at position (45,0,45) in FS2 coordinates with a normal of (0,1,0), I would make my first path at (45,120,45) with a radius of 140.  And I would just decrease "y" and the radius as "y->0".  Afterwards, I would load the model into FS2 and the AI ships would go warp trying to dock.

Please help,



Rampage

 

Offline DTP

  • ImPortant Coder
  • 28
    • http://www.c4-group.dk
Simple Problem, Why Don't I Get It?
use PCS to do paths

use fred2 to see where you put them
just set the model at coordinate 0.0.0
switch on view paths, and each time you want it to update
save the mission under something like modelnamepaths.fs2

thats the way i do paths.
VBB member; reg aug 1999; total posts 600.
War is a lion, on whos back you fall, never to get up.
Think big. Invade Space.

 

Offline karajorma

  • King Louie - Jungle VIP
  • Administrator
  • 214
    • Karajorma's Freespace FAQ
Simple Problem, Why Don't I Get It?
That's probably one of the best pathing tips I`ve heard in a long time. I used to use Modelview to position a subsystem at the points of the path. This is much easier :)
 I`ll probably still need to use modelview to know where to start but at least this way I can see that i`m not screwing up :)
Karajorma's Freespace FAQ. It's almost like asking me yourself.

[ Diaspora ] - [ Seeds Of Rebellion ] - [ Mind Games ]

 

Offline Killfrenzy

  • Slaughter-class cruiser
  • 210
  • Randomly Existing
Simple Problem, Why Don't I Get It?
What do you need paths for anyways? And how many for each function?

I know you need a couple for a docking point for a fighter, but what about other stuff?
Death has more impact than life, for everyone dies, but not everyone lives. [/b]
-Tomoe Hotaru (Sailor Saturn
------------
Founder of Shadows of Lylat

 

Offline karajorma

  • King Louie - Jungle VIP
  • Administrator
  • 214
    • Karajorma's Freespace FAQ
Simple Problem, Why Don't I Get It?
If you want the AI to be able to disable a subsystem or turret you need paths. Otherwise you don`t need them.

EDIT : That said I have heard that unpathed models can cause crashes. This is unsubstanciated however :)

You might also want to look at this thread
« Last Edit: October 18, 2002, 08:55:37 am by 340 »
Karajorma's Freespace FAQ. It's almost like asking me yourself.

[ Diaspora ] - [ Seeds Of Rebellion ] - [ Mind Games ]

  

Offline EdrickV

  • Valued
  • 29
    • http://members.aol.com/HunterComputers
Simple Problem, Why Don't I Get It?
The AI is stupid. Paths tell AI ships where to go to fire at a subsystem/target, where to go for docking, and where to go when heading into/out of a fighterbay. Only path thing I know of that does cause crashes is not having any path info on a fighter and calling in a support ship. (That's a well known problem to people associated with the Robotech MOD, which had (and still has some) pathless models.) I wrote a program specifically to allow people to enable/disable support ships in a mission without having to open it up in FRED2.
Ground - "Let me help you out, you're clear to taxi any way you can, to any runway you see."

Mesh Gallery/Downloads:
http://members.aol.com/ArisKalzar/Gallery.html
Turreting 101:
http://members.aol.com/EdrickV/FS2/Turreting.html

http://members.aol.com/HunterComputers