For information and discussion about Oolite.
https://bb.oolite.space/
and there was me thinking you were a fellow Flogging Molly fan.Thargoid wrote:The speed of Dark.
No matter how fast light is, it always gets there first...
Thargoid wrote:And it's also read-only. The only one writable by scripting is desiredSpeed.
On a similar track, do I remember that there was some thoughts about a desiredThrust as well? I can't see anything about it actually appearing in the wiki though?
Speed can not be set directly, because it would look ridiculous when a ship changed speed drastically in a split second. Therefor we have a desiredSpeed. When set, the engine increases/decreases speed according to the thrust value until the desiredSpeed is reached. Thrust in instantaneously, therefor a desiredThrust would seem a strange thing. Thrust can be set directly by script.but that's what happens when you hit the torus jump drive.Eric Walch wrote:Speedcan not be set directly, because it would look ridiculous when a ship changed speed drastically in a split second.
Not exactly. The ship accelerates very quickly to torus speed and deccelerates quickly when torus switches off, but it does not jump instantly between speed values from one frame to the next, which is what would happen if we were able to set actual speed by script.TGHC wrote:but that's what happens when you hit the torus jump drive.Eric Walch wrote:Speedcan not be set directly, because it would look ridiculous when a ship changed speed drastically in a split second.
As Another_Commander writes: Also for the player acceleration goes by thrust. However, Oolite is cheating here because it multiplies the thrust in shipdata with 7 for the player. I assume is was to enhance playing for the player. (try flying an Annaconda and you know what I mean). But it means that a player accelerates always faster than the identical npc variant of the same ship.TGHC wrote:but that's what happens when you hit the torus jump drive.
I have to admit though I have wondered about the effect of momentum when coming out of the jump drive.
My meaning was to have variable thrust for different scenarios. I hadn't spotted that it's R/W for NPCs though, which as you say covers what I was thinking about for desiredThrust.Eric Walch wrote:Thrust in instantaneously, therefor adesiredThrustwould seem a strange thing.Thrustcan be set directly by script.
I had a problem with an earlier version of my mod doing that for the NPC ships, since I was using performTumble as a "dodge" routine when they were getting hit. In initial tests, it worked great because I also had a set speed in the same line. But when I later pulled the 2 separate, because I didn't always want them to tumble when I wanted them to increase speed (such as attacking instead of fleeing)...things went awry. It was stop-on-a-dime behavior even if the set speed should be called at roughly the same instant as performTumble.Thargoid wrote:As for changing speed instantaneously, watch what an NPC ship which is flying along does when it's AI suddenly hits a performTumble. They fairly much instantaneously stop and then start tumbling (my hired guns are prone to that one). I don't disagree it looks wrong though.
Yes, performTumble is the only command that bypasses the thrust and immediately sets speed to zero.Thargoid wrote:As for changing speed instantaneously, watch what an NPC ship which is flying along does when it's AI suddenly hits a performTumble. They fairly much instantaneously stop and then start tumbling (my hired guns are prone to that one). I don't disagree it looks wrong though.
velocity. e.g. if you target a floating cargopod without any speed, you can target it and type 'PS.target.velocity = [0,0,20]" in the console. Than it will start moving immediately in that direction [0,0,1] with a speed of 20. During game it looks stupid when setting an explicit velocty, but it is very useful when spawning stuff with an initial momentum. And this is probably what you want.
) and they all still had speed zero, despite moving at around 2500m/s.