[Black Wolf]

What would be the difficulty in modifying this to apply to waypoints as well?

[WMCoolmon]

*Checks*

virtually none, unless you wanted some sort of gradual transition.

[Flaser]

Could the camera code be used for moving ships as well...
....or forcing ships to do off-table feats (set engines to overdrive, mad-immelman that sorta thigns)?

[Nuke]

is there any way to get that to work with the subspace jump effect so you can make an intra system jump while in mission with it? so the ship will jump from its current position to its new position.

[WMCoolmon]

Yes to the camera code thing, although the camera code only fully supports rotation. Although you'd be limited in SEXPs to moving it towards certain ships or towards a specific position, you'd have to set the rotation manually. Although it'd be done to manually set the ship position, so it'd circumvent the collision detection code for that ship (It'd fly through ships).

Fixing anything besides the first thing would probably take enough work to warrant just adding the thing in itself. The upside would be that if you could override max ship speed on a per-ship instead of per-class basis you could add SEXPs pretty easily to do it too. I think.

With the camera code, you could pretty easily do a poor-man's subspcae jump effect (assuming we have a make-wormhole SEXP of some sort); set the camera to the player's position and make the warp wormhole, fade out, fade in to show the player ship flying away from the wormhole. (setting ship/camera position appropriately while things are completely black)

[Black Wolf]

Originally posted by WMCoolmon
*Checks*

virtually none, unless you wanted some sort of gradual transition.

Nope - I can do any gradual transitions I'll need with every-time and variables.

[SadisticSid]

I asked for this a while ago - suffice to say it's the best possible way to script dynamic capship battles because you have such fine grain control over where you want things to go.

[Flaser]

Originally posted by Black Wolf


Nope - I can do any gradual transitions I'll need with every-time and variables.

IMHO a hardcoded sexp for gradual movement would be better, since anything going through and from the sexp system is bound to be slower and waste resources.

[Black Wolf]

Originally posted by Flaser


IMHO a hardcoded sexp for gradual movement would be better, since anything going through and from the sexp system is bound to be slower and waste resources.

But a hardcoded system would be at best difficult as WM Coolmon suggested, as opposed to the apparently very simple system if it's not hard coded and we achieve the same results through sexping. Why go for a difficult option when a simple one presents itself? It's not like this is a massively high priority request after all - if it gets too difficult or complicated, it'll probably not be done.

Besides - what's the point of gradual waypoint movement? I only said it was possible with sexping because WMC brought it up - I can't think of a single situation where you'd need the kind of split second perfect movement for an object you can't even see.

[Goober5000]

It's possible, but there might be a complication if the code needs to calculate new paths.

Barring any complications, it could be done in less than 30 minutes.

[Lynx]

You might want to contact Kazan about the autopilot he did for us, it sounds mostly similar to what's described here.(Basically, you have some waypoints, and when you press a certain button, time compression kicks in and your ship automatically flies to the selected waypoint/mission area)

[Goober5000]

That has nothing to do with this.

[Lynx]

Was referring to WMC's poor man's warp point idea, with some "show subspace effect" sexp or something this could work.
Should have quoted that.

[WMCoolmon]

Originally posted by Goober5000
It's possible, but there might be a complication if the code needs to calculate new paths.

Barring any complications, it could be done in less than 30 minutes.

That's true, I didn't think of that. Unfortunately, I don't remember seeing the vm_matrix_interpolate in the path finding part of the code.

However, I don't think it would be a problem as long as the waypoint wasn't changed while a ship was in transit to it.

Edit: Oh, and the jump point stuff, if you were clever you could probably do it with the SEXPs and a finished version of the camera code, as well as a SEXP to activate the special clipping that occurs when the ship enters the wormhole. (It might be interesting to map that to a SEXP regardless.)

Anyway, I'm going to be quiet now, until I can actually implement this stuff.

[WMCoolmon]

http://fs2source.warpcore.org/exes/latest/C02092005x.zip

Includes latest CVS (taylor's latest builds) along with high-res fixes (Lockon thingy works now), the camera code (of course).

The SEXP is set-object-position, and is completely untested. It should work with anything though (including wings...if it actually works, changing the position of a wing should be fun to watch. )

[Black Wolf]

Erm... thanks, but typically new sexps need a new FRED

I'll see what I can do with notepad.

[Goober5000]

Originally posted by WMCoolmon
The SEXP is set-object-position, and is completely untested. It should work with anything though (including wings...if it actually works, changing the position of a wing should be fun to watch. )

Er... did you modify set-ship-position or did you add a new sexp?

You should probably rename and change this to set-waypoint-position, since set-ship-position is already implemented and tested.

[WMCoolmon]

I added it as "set-object-position", and it takes an argument of SHIP_WING_POINT plus x, y, and z values.


I lazed out for the team option, It'll just grab the first ship it finds if it's given a team for the value. I may or may not fix that, since I doubt people will have much use for specifying a team.

Edit: Fixing it was easier than I thought, it'll do the same thing if a team is specified as if a wing is specified in my next build.

[Goober5000]

...but I had already added set-ship-position.  Did you use the code I had, or did you create new code?

There shouldn't be a duplicate sexp.  The two sexps should be merged somehow.

[WMCoolmon]

I used get_object_position's code, mostly.

Anyway, if you wanted to, you could just have set-ship-position call the set-object-position SEXP - it'd cause a lil' bit of slowdown though.