Orbiter 2016

[jedidia]

The point here is, that user B can't checkpoint his work at all. He will end up doing ZIP-backups to save his snapshots.

Git to the rescue! ...Or maybe not, because somebody is bound to get annoyed enough to just force-push his changes :lol:

Anyways, maybe we might be optimising prematurely here... How many people are even interested working on this, and what are their skills? In my experience, the number of contributors in any project is rather limited. Might be enough to just open a social group, and appoint somebody to do general coordination. A pull-based system might be overkill for the coordinator, or it might eventually turn out to be necessary, but somehow I doubt it.

 

[boogabooga]

Quick question.
I haven't found any reference to the new atmospheric wind effects in the documentation. How does it work? Are the wind velocities random? Do they change during the mission?

Also, in Surface HUD, is the prograde (circle +) symbol relative to the surface or relative to the wind?

Friendly bump on this question.

Also, I am curious as to the significance of March 2001 as the date for the stock scenarios.

 

[4throck]

How many people are even interested working on this, and what are their skills? I

A few people (2 or 3) with skills but little time :thumbup:

Perhaps there's a simpler solution to the version/updates/coordination problem:

» Consider that we are just correcting altitude errors/noise in selected areas (bases or part of bases), so there will be a defined list of tiles to fix.
» A tile is marked as "fixed" when submitted with the corrections + references (area photos, land surveys, etc)
» "Fixed" tiles will be locked and taken out of the list.
» Once someone selects a tile from the list, it becomes unavailable for others until it's re-submited (there must be a time limit)

It's a different approach but perhaps simpler to manage using a forum thread, some emails, and a webpage somewhere.

 

[Matias Saibene]

I tried the DG 3 points. SDK says minimal 3 points.

static const int ntdvtx = 3;
static TOUCHDOWNVTX tdvtx[ntdvtx] = {
	{ _V(0, -2.166, 10), 1e6, 1e5, 1.6, 0.1 },
	{ _V(-3.5, -2.166, -1), 1e6, 1e5, 3.0, 0.2 },
	{ _V(3.5, -2.166, -1), 1e6, 1e5, 3.0, 0.2 }
};

And I get this:

But when I start forward on the earth I hit a bump and away I go and end upside down.

What a beautiful meshes! It's really a nice job.

 

[Face]

Anyways, maybe we might be optimising prematurely here... How many people are even interested working on this, and what are their skills?

If we start with Martin's initial idea, I don't think that it is premature optimization. It was intended to be open to every base developer. And there are certainly more than 2 or 3 of them.

Or do you think that there should be something like an "elevation crew" that looks around what bases are out there and flattens the runways? IMHO that's too much of an ivory tower approach to me.

 

[reverend]

Have you guys ever thought of doing a free git repo on bitbucket.org ?

I think its like a billion times better than SVN. I have several projects on there. Here's a link about working with large file storage...

https://confluence.atlassian.com/bitbucket/git-large-file-storage-in-bitbucket-829078514.html

I just quickly setup a repo for the orbiter.us mirror HTML codes...

http://bitbucket.org/rpurinton/orbiter.us

 

[Face]

Have you guys ever thought of doing a free git repo on bitbucket.org ?

Well, of course, that was what I'm talking about all the time: using a decentralized version control tool, preferably git on one of the social coding platforms. But there are several problems with this:

1. The Orbiter community is rather traditional in this aspect. It "discovered" version control as collaboration model just some years ago with good old SVN. Why should they switch again? After all it works, right?
2. Trying to push people over to DVCS is hard, because the - to us DVCS users clearly obvious - advantages are hard to communicate to someone not familiar with it ("Blub programmer" paradox). Why should someone learn the much more complicated git system, when he can't understand the plus points of it?
3. Version control might not be the proper tool to approach the problem at hand (common database for elevation data). It could quickly look like you are trying to fix everything with the "hammer" DVCS, when the "screwdriver" database is better suited.

But I guess talking about it all day will not convince anyone, anyway. It is not like an SVN-based system can't be converted over to something better if hits the fan, so I'm all for trying it out. :thumbup:

 

[Ripley]

I don't know if it's a very minor "bug" of the new 2016 webpage (or a feature I don't catch), but when you click the Mirrors' buttons they show different top menus:

Mirror1 (orbiter-radio.co.uk) and Mirror4 (Alteaaerospace.com) only show "Download" and "Help".
Mirror2 and 3 (orbiter.us) also show "High Res Textures" and "Texture Help".

It's the same both for "Orbiter core package download" and "Optional high-resolution texture download".

 

[Nicholas Kang]

Dear members,

I notice that the airbrake of DG could not be deployed with the keyboard shortcut key CTRL+B nor can it be retracted by pressing ALT+B. Can any user reproduce this bug (or anomaly, if you prefer to call it)?

Also, while conducting surface flight on Mars, I notice that the edge of horizon is flickering/blinking with something black occasionally. This happens in both d3d9 client enabled and when using the in-line graphic engine. Can anyone reproduce this?

Thank you.

Nicholas.

 

[Jeast]

Hi all,

When flying the Atlantis mission: launch into sunrise, using the ascent AP it leaves you with just enough fuel to deorbit. Doing an inclination change of more than 1 degree is impossible as you will run out of fuel. Is this a bug?

Thanks.

Jeast

 

[Ripley]

Dear members,

I notice that the airbrake of DG could not be deployed with the keyboard shortcut key CTRL+B nor can it be retracted by pressing ALT+B. Can any user reproduce this bug (or anomaly, if you prefer to call it)?...

Key for deploying airbrake is B, and it works as it should.
Once it is deployed, it retracts with ALT+B.

 

[turtle91]

Also, while conducting surface flight on Mars, I notice that the edge of horizon is flickering/blinking with something black occasionally. This happens in both d3d9 client enabled and when using the in-line graphic engine. Can anyone reproduce this?

I have this flickering only in D3D9 client. (both above and below sealevel altitude).
The inline client works fine for me on Mars.

 

[boogabooga]

Hi all,

When flying the Atlantis mission: launch into sunrise, using the ascent AP it leaves you with just enough fuel to deorbit. Doing an inclination change of more than 1 degree is impossible as you will run out of fuel. Is this a bug?

Thanks.

Jeast

One degree is a lot for a realistic vessel, almost 25% of Atlantis's fuel supply, for example.

 

[turtle91]

Originally Posted by Jeast View Post
Hi all,

When flying the Atlantis mission: launch into sunrise, using the ascent AP it leaves you with just enough fuel to deorbit. Doing an inclination change of more than 1 degree is impossible as you will run out of fuel. Is this a bug?

Thanks.

Jeast
One degree is a lot for a realistic vessel, almost 25% of Atlantis's fuel supply, for example.

I have just done some tests with the new Atlantis.
And...btw..currently I am trying to mix some code from the "Project Outposts" Atlantis.
So far, I have just "implemented" the RMS-kinematic-logic made by Astrosammy.
Just to have a basic-shuttle, which can be more easy used for station-building.
So if somebody has interest...just give me a shout.

Back to topic, my procedure to launch to ISS using the default Sunrise-Scenario:
-using AlignMFD and wait until time-to-ascending-node shows 300 seconds
-AP set to 250 km altitude and heading to 42.8
= after OMS2 I am at about 0.07 RINC (so about 10-15 seconds correction burn on next node).
-when docked to ISS I have about 50-60 percent fuel left.(can be improved....I need more practice...)

 

[Nicholas Kang]

Key for deploying airbrake is B, and it works as it should.
Once it is deployed, it retracts with ALT+B.

Yes, Ripley. The airbrake is deployed and retracted by pressing B and ALT+B. I can now confirm this. Thanks. But please take a look at what the official Delta-Glider manual that comes with your Orbiter 2016 distribution package has to say:

Check the screenshot below:

Notice that manual states that deploy the airbrake by one step by hitting CTRL+B and retract it by hitting ALT+B.

Is the manual wrong? A typo?

Please confirm this.

Thanks.

Nicholas.

 

[boogabooga]

Well, if it doesn't actually work, then it is a typo.

Actually, not a "typo" per se. I suppose tiny "oversight" is a better word.

 

[Jeast]

One degree is a lot for a realistic vessel, almost 25% of Atlantis's fuel supply, for example.

Ok clear, thank you!

 

[JonnyBGoode]

I decided to take my first trip around the globe today... anyone ever seen this artifact before? This is the west coast of South America, in the vicinity of Ecuador.

 

[Abloheet]

Yeah many times. Its just a huge cloud bank martins was unable to remove
from the high res ground textures

I decided to take my first trip around the globe today... anyone ever seen this artifact before? This is the west coast of South America, in the vicinity of Ecuador.

 

[Evil_Onyx]

Much tanks to Martins.

So who else has gone to find out if there local airport is flat, to see if you can land there.