On a side note, stress testing the program myself (basically using it for very much its purpose, but extensively), I found a few bugs easy to play around but which definately must and will be fixed when i figure a new formula for angular motions. Please keep them in mind so far:

1 - The input of mass is interpreted as an integer, so any float values will give an error message.
2 - The angular values output field gives a spelling error that doesn’t quite crash freelancer or even cause a message in the FLSpew, but does affect motion unless corrected: It says “rotation_intertia” instead of “rotation_inertia”.
3 - For some reason in the list of functions under the linear calculation button I inattentively put also one requesting values from angular calculations. Since however the linear values are not affected by angular calculation, the float values in the cockpit offsets and calculation of angular values is merely a formality that by the version uploaded here must be done prior to linear calculations.
4 - Apparently the formula I have been working with for angular motions is imperfect. It takes into account linear accelerations during angular motion or rather motion around a different point. With slow accelerations and high cockpit radii (as on larger ships) the issue is insignificant; however the closer the cockpit gets to the pivot point the more the ship becomes immaneurverable which makes the values more or less useless. Technically there is a div by 0 error when the cockpit has a 0 radius for some axis.

A new build including all the bug fixes will be available once i have combined and implemented a solution to problem #4. If anyone wishes to help me understanding the forces during rotation, their relation to newtonian linear physics and most importantly forces affecting a pilot in angular motion, you are certainly welcome to. Also, I am open to suggestions for additional features to be added in the next version.

Should have sent the Israelis in, they didn’t lose a helicopter at Entebbe.

Last time our US pals copied them, they lost another helicopter or 3 because of non-desert air filters. Someone slipped up.

The video they showed of an old man watching Bin Laden on TV was not Bin Laden, in my opinion. In my brain I can turn the last video of Bin Laden’s face through a few degrees to compare. I don’t doubt that they did shoot Bin Laden, but he is not the man watching TV of himself.

Sad that Pakistan is being paid to support the West but cannot be trusted. Time to cut off their aid payments completely (the UK can’t afford them anyway) and remove all nuclear and space launch capability from them too. If necessary a couple (or hundred) of Exocets should do it. After all Libya was a closer ally a few months ago and yet has suffered incessant attacks.

Spam spam spam spam,… 😉

On the subject of “Liberating” the Arab countries - has anyone noticed my prediction of Egypt in turmoil has materialised? Told you so. And Egypt is not tribal, just multi-religious and used to be tolerant.

Watch out for Libya when this is “all over”. Completely tribal, like Afghanistan…

More spam, spam, spam, spam! 😄

I think this is a good idea and i would play on a server that ran it, but i think i would be lonely.

F!R wrote:

By now I m hoping for a FlHook feature, to set reputation
by npc kills, play time etc.

me too now 🙂

@Chips

The telescope is Celestron AstroMaster 130EQ + 2x barlow and 6mm eyepiece. Camera is my Nokia X6 phone.

But…. this collocation is bad… If i only use the 6mm eyepiece without 2x barlow, i may get more clear image.

@khayman

If you don’t want to delve into astronomy, you can use Stellarium to lead you.

And, you need some knowledge about Equatorial mount and other telescope components to set up and control your telescope.

that’s okay 😉
also, if it might help, i recognised, that the other way, if i keep the byte unpatched, i can see the cargo pods in my inventory, in the commodities section but not at the dealer. so, i cannot buy additional or exchange them, only sell.

guess it is a combination of bytes that makes them visible on both sides somehow.

great, thank you, Adoxa 😄

Yeah that too. I was in Lightwave mode when I wrote that post. I forgot Milkshape supports smoothing groups.

adoxa wrote:
0x0AF90 is for 1.0, 0x0AFC0 is for 1.1 (the format of the new offset list, but code isn’t showing the tabs, which makes it a little clearer). I almost didn’t provide the 1.0 offset, so in future I shan’t (hear that foxUnit01? :)).

Noted. 😉

thanks a lot, to all. can’t express what glad i am to have gotten here finally. a very good moment.