Outerra forum
Anteworld - Outerra Game => Modding: Importer, Tools & Utilities => Topic started by: zzz on June 29, 2014, 08:21:16 am
-
Is it possible to get the Vehicle's speed method to return individual xyz vectors instead of overall velocity?
-
We'll expose a velocity method that returns both the linear and angular vector speeds.
-
Thanks. Is there a timeline on that?
-
It will get into the next update which could be out soon, just some issues at exit need to be addressed.
-
- script: velocity method for getting speed vectors in vehicle physics
great! what's the syntax on that?
and videomaker.exe gives some errors on quitting although I'm not using it.
-
I've added it to the wiki. Returns an object with linear and angular member variables in world space.
-
I've added it to the wiki. Returns an object with linear and angular member variables in world space.
Could you give me an example line? I tried this (and variations)
this.velocity('angular').y
for pitch velocity but got nowhere.
-
Try
var v=this.velocity();
v.angular.x ...
-
I think the vectors might be relative to the world instead of the model. Asking it not to go over "50 velocity" limits its speed to numbers that don't match any units and change depending on the heading. Also if you turn the vehicle 180 degrees it does not change the velocity function's outputs.
edit: yeah, seems 250ish heading positive x, 160ish positive y.
-
Yes, they are in world space. Can be converted to model space via the quaternion, but there's no easily usable math lib in JS for it, so it will be probably better to provide transformation functions.
-
so it will be probably better to provide transformation functions.
So the function won't get much use until those are created? I read up on quaternions and the maths is... dense.
-
Depends on how you mean to use it. You may want to implement a stabilizer that controls the vehicle in tangential plane, and for that you'll need world space vectors.
I have added a bool flag to instruct the method that you want model space vectors.
-
Thanks. The linear speeds work perfectly, but with angular is the conversion correct? After some bugs I logged the changing angular.z speed and it cycled between -8 to 8 as I was in an increasingly fast 360 degree spin along that axis.
-
Thanks. The linear speeds work perfectly, but with angular is the conversion correct? After some bugs I logged the changing angular.z speed and it cycled between -8 to 8 as I was in an increasingly fast 360 degree spin along that axis.
Was my interpretation of this correct?
-
Hm I didn't notice any issues with the angular speed in local frame; it's used, for example, on boats for stabilization.
-
hmm, this a screen of the angular readouts of the x-axis as the ship rolls left about 180 degrees/s.
http://s9.postimg.org/u2y3pesb3/screen_1404426459.jpg (http://s9.postimg.org/u2y3pesb3/screen_1404426459.jpg)
Just in case my axis was wrong I tried the same whilst logging the y and z axis. They all stayed at very low numbers and none of them increased proportionately with the roll speed.
What turned me onto it was to stop my models sliding out of control I use this code to autocompensate:
var velo = this.velocity(1);
if (velo.linear.x > 0) {
this.extra_force({y:0,z:0},{y:0,x:-latForce});
}
if (velo.linear.x < 0) {
this.extra_force({y:0,z:0},{y:0,x:latForce});
}
and it works perfectly. When I use something similar to stop yawing or pitching it overshoots the zero point by some margin until it reverses speed, overshoots even more and eventually oscillates out of control, no matter how low the forces, speed and acceleration are.
if (velo.angular.x > 0) {
this.extra_force({y:100,z:0},{z:0,x:-angForce});
this.extra_force({y:-100,z:0},{z:0,x:angForce});
}
if (velo.angular.x < 0) {
this.extra_force({y:100,z:0},{z:0,x:angForce});
this.extra_force({y:-100,z:0},{z:0,x:-angForce});
}
edit: here's a screen with all 3 axis being logged.
http://s28.postimg.org/uhiaxd76l/screen_1404427168.jpg (http://s28.postimg.org/uhiaxd76l/screen_1404427168.jpg)
at that time it was yawing right so fast it was a blur, with a slight pitch up and barely no roll.
-
To me it seems you are detecting pitch (x axis), but acting on yaw.
-
Seems you were right. That on top of working in m/s instead of rad/s and the compensators not working unless all 3 were active meant it couldn't do anything but oscillate out of control. Sorry for bothering you. :-[
But if it's any consolation the updated js file may save you having to make that UFO flight model.