NASSP V7.0 Beta 20150804 Released

[dseagrav]

As promised, we are issuing beta releases again. This is the first in three years.

Most of the recent work has been around the new "LVDC++" autopilot for the Saturn, which more closely approximates the original LVDC flight software. We also switched to OrbiterSound 4.0.

Our focus on the moment is getting Apollo 7 and Apollo 8 working enough to issue a 7.0 release, after which we will move on to the LM and Apollo 11. If you are desperate to see the LM, it's there, but it's not at all usable.

The release is available via GitHub or SourceForge. It was compiled with VS 2010, so the appropriate redistributable package from MS is required if you don't have it already.

 

[JJJacksonTyler]

Great!

I just started using NASSP yesterday. It took me a good part of the entire day to simply get familiarized with a much more in depth CSM (I had burned though AMSO like tinder beforehand). At the end of yesterday, I realized the last release of the sim was in July of 2012.

I then discover this, this morning, that after 3 years of development hell, a new version came out less than 24 hours after I had begun playing in the first place.

 

[Marg]

It would be good to see NASSP for Orbiter 2015...

 

[fort]

Hello,


I have a problem with the latest releases of Orbiter ( beta 2010 -face-4c4b2e467413-121223 patch-rev 20 - ...or beta 2015 rev 13 ) with the launchers, here in Apollo-Saturn, but also in other addons, as, if i remember, Voyager (BrianJ) or Cassini for example...these launchers are not vertical but leaning on their pads. Touchdownpoints ?

This may be a problem to post in the topics devoted to the latest betas ( if others have it ) ? Is it only me ?

good day.

 

[Marg]

Yes, that is what I observe with most addons in Orbiter 2015 BETA.
Seems that spacecraft3 does not have this problem. Also BrianJ updated falcon add-on so it works (although it did not lean in new Orbiter!).
Add-on X-15 works pretty well though, I spent a lot of time in Nevada, California, etc. because with realistic terrain it was great to land X-15 not only in Edwards but some other "valleys".

 

[STS]

And yesterday (July third) I was recording a timelapse about the prelaunch checklists.

Good, great news that NASSP 7 got updated!

 

[kuddel]

Is it only me ?

No, same here. In Orbiter BETA the launchers are not vertical.

 

[n72.75]

This is good news. I was over on the Medeville Space Center forums reading decade old threads and hoping this project wasn't dead about a month ago. Glad to see development.

 

[dseagrav]

Shows how far out of the loop I am, I didn't even know there WAS an orbiter beta. How far is it from release, and how drastic are the changes?

 

[n72.75]

 

[fort]

Yes, that is what I observe with most addons in Orbiter 2015 BETA.

No, same here. In Orbiter BETA the launchers are not vertical.

I know four betas for the 2010 edition ( and one, the 121223, from face repository ):

orbiter111105-100830diff.7z
http://www.orbithangar.com/orbDownload.php?file=orbiter111105-100830diff.7z
orbiter121021-100830diff.7z
http://www.orbithangar.com/orbDownload.php?file=orbiter121021-100830diff.7z
orbiter121023-100830diff.7z
http://www.orbithangar.com/orbDownload.php?file=orbiter121023-100830diff.7z
orbiter121129-100830diff.7z
http://www.orbithangar.com/orbDownload.php?file=orbiter121129-100830diff.7z


The problem seems to begins with the: orbiter121021-100830diff, and is also in the 2015 beta.

I think that an explanation is there:

http://www.orbiter-forum.com/showthread.php?t=29346

"A few notes to this beta:...

This allowed to provide support for dynamic surface interactions, and replacement of the old 3-point touchdown definitions with "impact hulls"...."


Another example with the Falcon9R - falcon9r_150612 - by brianj, in orbiter 2010 - patched 121021:

[ame="http://www.orbithangar.com/searchid.php?ID=6593"]Falcon9R[/ame]

 

[Face]

I have a problem with the latest releases of Orbiter ( beta 2010 -face-4c4b2e467413-121223 patch-rev 20 - ...or beta 2015 rev 13 )...

(emphasis mine)

This is rather old. 4c4b2 is SVN trunk revision 20, which is also the last revision from the old SVN repository before Xyon kind of lost the repo.

The newest mirrored version in my repo is always this: https://bitbucket.org/face/orbiter/get/tip.zip . Currently, it corresponds to the newest SVN trunk revision 13 of the new area repo. As of this moment, there is no newer version in the SVN repo.

 

[fort]

Hello

(emphasis mine)

This is rather old. 4c4b2 is SVN trunk revision 20, which is also the last revision from the old SVN repository before Xyon kind of lost the repo.

Rather old but the latest for Orbiter 2010 ( rev 20 -standard 2D terrain; classic style for textures and support for D3D9, as the beta 2015 )

The newest mirrored version in my repo is always this: https://bitbucket.org/face/orbiter/get/tip.zip . Currently, it corresponds to the newest SVN trunk revision 13 of the new area repo.

Yes, the latest for the "beta 2015" version with 3D terrain.

Thank you and good day.

 

[Face]

Rather old but the latest for Orbiter 2010 ( rev 20 -standard 2D terrain; classic style for textures and support for D3D9, as the beta 2015 )

Hm. Beta is beta, there is no distinction between beta for Orbiter 2010 and beta for Orbiter 2015, because Orbiter 2015 doesn't exist yet, because the beta is Orbiter 2015.

If we talk about latest versions in this context, we really only have the latest official release (Orbiter 2010-P1) and the latest beta ("codenamed" Orbiter 2015). Everything else is an intermittent version that has no relevance anymore IMHO.

Or is there a plan to release another patch to the 2010-P1 version?

 

[kuddel]

Hi there,

I've tried to get into NASSP (again) after a long time and found the "Orbiter2015" branch at github.
As I am a complete noob with git (I'm a svn boy ) I have not yet mastered the vocabulary and procedures with git...but

Here's my changes to
"Orbitersdk\samples\ProjectApollo\src_saturn\sat1bmesh.cpp"
dealing with the 'new' touchdown points:
With this changes I was able to run the "Scenarios\Project Apollo - NASSP\Apollo 7 Quickstart - Launch.scn" Scenario with the current Orbiter BEAT (r55) and current D3D9Client (23.1)

@@ -180,10 +180,17 @@ static PARTICLESTREAMSPEC prelaunchvent_spec = {
 	PARTICLESTREAMSPEC::EMISSIVE,
 	PARTICLESTREAMSPEC::LVL_FLAT, 0.1, 0.1,
 	PARTICLESTREAMSPEC::ATM_FLAT, 0.1, 0.1
 };
 
+// touchdown point vertices
+static TOUCHDOWNVTX tdvtx[] = {
+	{ _V(  0,-1.0, 0), 1e9, 1e7, 0.3, 0.3 },
+	{ _V(-.5,.5  , 0), 1e9, 1e7, 0.3, 0.3 },
+	{ _V( .5,.5  , 0), 1e9, 1e7, 0.3, 0.3 }
+};
+
 
 void Saturn1b::SetFirstStage ()
 {
 	SetSize (45);
 	SetEmptyMass (Stage1Mass);
@@ -210,43 +217,25 @@ void Saturn1b::SetFirstStage ()
 
 	InitNavRadios (4);
 }
 
 void Saturn1b::SetFirstStageMeshes(double offset)
-
 {
-	double TCP=-54.485-TCPO;//STG0O;
-	TOUCHDOWNVTX tdpoints[4];
-
-	tdpoints[0].pos = _V(0,-1.0,TCP);
-	tdpoints[0].damping = 1;
-	tdpoints[0].mu = 1;
-	tdpoints[0].mu_lng = 1;
-	tdpoints[0].stiffness = 1;
-	tdpoints[1].pos = _V(-.5,.5,TCP);
-	tdpoints[1].damping = 1;
-	tdpoints[1].mu = 1;
-	tdpoints[1].mu_lng = 1;
-	tdpoints[1].stiffness = 1;
-	tdpoints[2].pos = _V(.5,.5,TCP);
-	tdpoints[2].damping = 1;
-	tdpoints[2].mu = 1;
-	tdpoints[2].mu_lng = 1;
-	tdpoints[2].stiffness = 1;
-
-	// SetTouchdownPoints (_V(0,-1.0,TCP), _V(-.7,.7,TCP), _V(.7,.7,TCP));
-	SetTouchdownPoints (_V(0,-1.0,TCP), _V(-.5,.5,TCP), _V(.5,.5,TCP));
-	// SetTouchdownPoints(tdpoints,3);
+	double TCP = -54.485 - TCPO;//STG0O;
+	for (int i = 0; i < ARRAYSIZE(tdvtx); ++i) {
+		tdvtx[i].pos.z = TCP;
+	}
+	SetTouchdownPoints(tdvtx, ARRAYSIZE(tdvtx));
+
 	VECTOR3 mesh_dir=_V(0,0,offset);
 
 	AddMesh (hStage1Mesh, &mesh_dir);
 	mesh_dir=_V(0,0,16.2 + offset);
 	AddMesh (hInterstageMesh, &mesh_dir);
 }
 
 void Saturn1b::SetFirstStageEngines()
-
 {
 	ClearThrusters();
     ClearExhaustRefs();
     ClearAttExhaustRefs();

I will try to learn a bit more git and hopefully be able to present 'pull-requests' (or whatever they are named) in the future :thumbup:

/Kuddel

 

[n72.75]

Hi there,

I've tried to get into NASSP (again) after a long time and found the "Orbiter2015" branch at github.
As I am a complete noob with git (I'm a svn boy ) I have not yet mastered the vocabulary and procedures with git...but

Here's my changes to
"Orbitersdk\samples\ProjectApollo\src_saturn\sat1bmesh.cpp"
dealing with the 'new' touchdown points:
With this changes I was able to run the "Scenarios\Project Apollo - NASSP\Apollo 7 Quickstart - Launch.scn" Scenario with the current Orbiter BEAT (r55) and current D3D9Client (23.1)

@@ -180,10 +180,17 @@ static PARTICLESTREAMSPEC prelaunchvent_spec = {
 	PARTICLESTREAMSPEC::EMISSIVE,
 	PARTICLESTREAMSPEC::LVL_FLAT, 0.1, 0.1,
 	PARTICLESTREAMSPEC::ATM_FLAT, 0.1, 0.1
 };
 
+// touchdown point vertices
+static TOUCHDOWNVTX tdvtx[] = {
+	{ _V(  0,-1.0, 0), 1e9, 1e7, 0.3, 0.3 },
+	{ _V(-.5,.5  , 0), 1e9, 1e7, 0.3, 0.3 },
+	{ _V( .5,.5  , 0), 1e9, 1e7, 0.3, 0.3 }
+};
+
 
 void Saturn1b::SetFirstStage ()
 {
 	SetSize (45);
 	SetEmptyMass (Stage1Mass);
@@ -210,43 +217,25 @@ void Saturn1b::SetFirstStage ()
 
 	InitNavRadios (4);
 }
 
 void Saturn1b::SetFirstStageMeshes(double offset)
-
 {
-	double TCP=-54.485-TCPO;//STG0O;
-	TOUCHDOWNVTX tdpoints[4];
-
-	tdpoints[0].pos = _V(0,-1.0,TCP);
-	tdpoints[0].damping = 1;
-	tdpoints[0].mu = 1;
-	tdpoints[0].mu_lng = 1;
-	tdpoints[0].stiffness = 1;
-	tdpoints[1].pos = _V(-.5,.5,TCP);
-	tdpoints[1].damping = 1;
-	tdpoints[1].mu = 1;
-	tdpoints[1].mu_lng = 1;
-	tdpoints[1].stiffness = 1;
-	tdpoints[2].pos = _V(.5,.5,TCP);
-	tdpoints[2].damping = 1;
-	tdpoints[2].mu = 1;
-	tdpoints[2].mu_lng = 1;
-	tdpoints[2].stiffness = 1;
-
-	// SetTouchdownPoints (_V(0,-1.0,TCP), _V(-.7,.7,TCP), _V(.7,.7,TCP));
-	SetTouchdownPoints (_V(0,-1.0,TCP), _V(-.5,.5,TCP), _V(.5,.5,TCP));
-	// SetTouchdownPoints(tdpoints,3);
+	double TCP = -54.485 - TCPO;//STG0O;
+	for (int i = 0; i < ARRAYSIZE(tdvtx); ++i) {
+		tdvtx[i].pos.z = TCP;
+	}
+	SetTouchdownPoints(tdvtx, ARRAYSIZE(tdvtx));
+
 	VECTOR3 mesh_dir=_V(0,0,offset);
 
 	AddMesh (hStage1Mesh, &mesh_dir);
 	mesh_dir=_V(0,0,16.2 + offset);
 	AddMesh (hInterstageMesh, &mesh_dir);
 }
 
 void Saturn1b::SetFirstStageEngines()
-
 {
 	ClearThrusters();
     ClearExhaustRefs();
     ClearAttExhaustRefs();

I will try to learn a bit more git and hopefully be able to present 'pull-requests' (or whatever they are named) in the future :thumbup:

/Kuddel

Is there a better way we could coordinate between this form and Rob's forum.

 

[kuddel]

Is there a better way we could coordinate between this form and Rob's forum.

Sure!
I really think I have to create an Meadville Space Center account when *really* starting to do things.
But because I am not sure whether there will be any further changes by me, it might be too much effort for just one little change.

"Officially" I think this has to be done (by me):
- have an Meadville Space Center account
- have an github account
- discuss @ Meadville Space Center
- create pull-requests @ github

But as you see, much effort for just *one* simple patch.
It only pays off when I plan to do a little more.

 

[indy91]

The Orbiter 2015 branch is a few months behind, but there weren't any changes done in the master branch for Orbiter 2010 that would be different for Orbiter 2015 so the most recent updates could be simply merged. I haven't worked on any Orbiter 2015 related stuff, so I have always let dseagrav handle keeping it up to date. He will probably be very interested in your touchdown point solution.

If you want to create a MSC account you have to do a little procedure to get your account approved: http://www.ibiblio.org/mscorbit/mscforum/index.php?topic=2666 It's an outdated forum and not much else than NASSP dev talk is happening there.

Helping hands are always welcome. I am not very experienced with git myself, but the pull request feature seems pretty good for encouraging people to help with the project.

 

[kuddel]

Thanks for the info.
I found out, that I already have an gihub account :blush: (just haven't used it much, though).
If I fork from "master", I could try to create a pull request for any changes I do.
It might not be much, but I can contribute to some issues (#15 e.g.) easily when I'm back from work.
Let's see what happens :thumbup: