Librelancer 2022.02

Is the drag reversing velocity sign something that happens due to discretion of time or rounding errors or the like? I ask because analytically that shouldn’t ever happen, but of course time intervals between computations are not infinitely small, and so if one takes v0 to be the velocity that was a finite time ago (say, a hardcoded fraction of a second, or a frame), I can see how such unwanted reversals might happen and one would need to clamp like that. Is that why they do?

As for angular motion, the parameters seem to be the same, except now you have one set of torque, inertia, and angular drag for each of your three rotational axis, as counterparts to thrust force, mass, and linear drag, respectively.

Yes, it’s why. It should be fairly obvious that discretization will introduce errors, the most pronounced of which is oscillations.

As far as I could tell, the game only produces roll when the roll key is pressed or the autopilot is engaged. I believe autoleveling will also use it, but I have autolevel disabled so I can’t say for certain.

So I took the time to evaluate my test and here are the results:

My test parameters were:
max_force = 10000
linear_drag = 10
mass = 250

How I performed the test:
I put in reverse thrust until my speed was about -50. At that speed I engaged full thrust and started to gather the data once I went over 0 m/s. I recorded the whole test at constant 30FPS.

I used ffmpeg to dump the videostream as pictures, put the displayed speed of every tenth picture in a table and plotted it.

The calculated speed line was generated by the following equation(v0 is the speed of the previous iteration):
v = v0+(max_force-v0linear_drag)/mass
so
a = (force-vlinear_drag)/mass

The delta curve is just the difference of the other two curves, usually ~3 m/s.

I gotta say, great work! Keep it up

8-[……]
Perfect!
Now it is “atmosphere”

Oh me so want!

Doin’ that download thang @ Librelancer now.

Darn download freezes at 89%. Will try later.

(10 to 1 it’s the flakey 4G here, don’t ask about my desktop internet connection. It got et’ by a backhoe)

Contributing to the existing, full featured UTF Editor wasn’t in the cards?

Getting a dead-lock in attempts to reach asteroid fields. Occurs in both 2017.10 and Daily builds. Screen with procexp/threads: https://i.imgur.com/pglDWeH.png. Not sure what exactly to report.

Offtop, a small question regarding such: https://i.imgur.com/K9qws20.png

( I’m just attempting to render )

The background was painted to the alpha channel of grass, otherwise I wouldn’t see the grass through the glass. What’s causing that: incorrect blending settings or an order of rendering? Because if this is an order’s fault… well, pass, I’ll just start learning Depth Peeling immediately.

I’m sort of with Friendly Fire with this one. As much as I’m dealing with UTF lately and using the an editor that can FINALLY drag and drop and other great advances from the first editors, a bit of support for the hard work within the community might be in order.
Otherwise you’re going to end up reinventing a few wheels and if you run into a brick wall on what wheels you are spinning on it will most likely have already been hit and broken through within the group here.

Without participation in a large group effort I’d be staring at this page on a real magnifying glass instead of a new page zoom and on a newer virtual keypad that doesn’t suffer typing lags. Jefferson001 is indebted to the efforts of groups. For this small miracle and for tools like the UTF editor.

Just because you think your on a different path you still have the skill to walk. I’ll tell you that walking with a group is whole lot better than walking there on you’re own.

“Design is a collaboration. Trying it on your own is masterbation.” Buckminster Fuller.