[Polpolion]

(I'm implementing a Taylor series now)

WHY

incidentally this seems as good a place as any to say taht I've been toying with the idea of trying to create SEXP libraries for FRED. You can do ****tons with SEXPs alone but last time I checked (to be fair it has been a while) there really aren't very many good mechanisms for SEXP abstraction. What you would do is define a bunch of generic SEXPs to do something (eg a minefield) and save it as, I dunno, a `.fred' file and then there would be an options screen in the mission editor for including libraries. Then whenever you wanted a minefield (or whatever) all you would have to do is include your appropriate library and use your custom SEXP. Then when you save the mission a text processor would run through your mission events and expand your custom sexp with its arguments to the actual implementation defined in the library.

only problem is that I haven't had the time to work on it any more than thinking about doing it.

[Droid803]

Time to SEXP up some danmakku...

[Goober5000]

Oh, I see what you mean.  Yes, that would require a get-[pitch/bank/heading]-to-location sexp, which is definitely doable, but not in SCP yet.

Bah, it looks like it's necessarily to make the problem more specific.  It's not possible to get a single pitch/bank/heading from an object to a given set of coordinates, because that problem has multiple solutions.

However, getting the orientation angle of a particular ship, disregarding any external points or destinations, can be done.  Use the get-object-[pitch/bank/heading] sexps.

[Shivan Hunter]

(I'm implementing a Taylor series now)

WHY

I saw where a trig function was not, and said, "no. This will not do."

Besides, it didn't work anyway because of the aforementioned decimal problem.

incidentally this seems as good a place as any to say taht I've been toying with the idea of trying to create SEXP libraries for FRED. You can do ****tons with SEXPs alone but last time I checked (to be fair it has been a while) there really aren't very many good mechanisms for SEXP abstraction. What you would do is define a bunch of generic SEXPs to do something (eg a minefield) and save it as, I dunno, a `.fred' file and then there would be an options screen in the mission editor for including libraries. Then whenever you wanted a minefield (or whatever) all you would have to do is include your appropriate library and use your custom SEXP. Then when you save the mission a text processor would run through your mission events and expand your custom sexp with its arguments to the actual implementation defined in the library.

only problem is that I haven't had the time to work on it any more than thinking about doing it.

That sounds awesome