Meadville Space Center
Welcome, Guest. Please login or register.
October 24, 2020, 10:01:34 PM

Login with username, password and session length
Search:     Advanced search
25068 Posts in 2094 Topics by 2266 Members
Latest Member: twa517
* Home Help Search Login Register
+  Meadville Space Center
|-+  Project Apollo - NASSP
| |-+  Project Apollo - NASSP Development (Moderators: movieman, Tschachim, Swatch, lassombra)
| | |-+  OrbiterSim2016
« previous next »
Pages: [1] Print
Author Topic: OrbiterSim2016  (Read 2027 times)
vrouleau
Project Team Member
Full Member
****
Posts: 153


View Profile Email
« on: September 06, 2016, 09:17:47 AM »

OrbiterSim2016 is out and 2010 is no longer downloadable from the orbitersim page. Is this time we migrate to 2016. I've been using/merging without check-in the Orbiter2015 branch. I think it is a good time to do it.
Logged
dseagrav
Project Admin
Hero Member
*****
Posts: 1118


View Profile
« Reply #1 on: September 06, 2016, 09:47:50 AM »

I have to update the build environment before anyone does anything. It's still using eariler sdk files.
Logged
indy91
Hero Member
*****
Posts: 1316


View Profile
« Reply #2 on: September 06, 2016, 09:53:06 AM »

As fun as it is working on the lunar landing, what I think we should do is focus on a Apollo 7+8 release. It doesn't have to be perfection, but there is still work to do on documentation and bug fixes. If we have a completely working version for Orbiter 2010 that can fly the Apollo 7+8 missions with LVDC, Virtual AGC and optionally the MCC functionality, then we call that the last Orbiter 2010 release and start work on Apollo 7-10 for Orbiter 2016. What do you think?
« Last Edit: September 06, 2016, 09:56:16 AM by indy91 » Logged
dseagrav
Project Admin
Hero Member
*****
Posts: 1118


View Profile
« Reply #3 on: September 06, 2016, 11:51:06 AM »

Yeah, we can call it a swan song for Orbiter 2010. There's LOTS of room for potential improvement in 2016, and lots of work that can be done. For example, staging can be completely thrown away and the stack split into vessels. This would be a major chore at first but once done it will greatly simplify later modification (like when we start handling the post-13 differences)

Logged
vrouleau
Project Team Member
Full Member
****
Posts: 153


View Profile Email
« Reply #4 on: September 06, 2016, 12:40:44 PM »

I haven't commited anything myself in over 1 year, I have been merging the Orbiter2015 branch from the master branch and running with the SVN on OrbiterSim2015 (2016 now...) since then. But as of today, the Orbiter2015 branch works on OrbiterSim2016. I don't know the full impacts of the new earth models of the LVDC, but at least it compiles and runs. My main problem is that I do not have a Orbiter2010 setup to test on and cannot test on it. Its might be confusing to generate a new build of the 2010 master branch for a version of the sim that is not available anymore. My 10 cents...
Logged
indy91
Hero Member
*****
Posts: 1316


View Profile
« Reply #5 on: September 06, 2016, 12:54:38 PM »

I don't think dropping the Orbiter 2010 version right now is the right approach. First of all, Orbiter 2010 is still very much available: http://orbithangar.com/orbiter.php

The Orbiter2015 branch is way behind, although I guess most changes since the last update can be easily merged. But if we are jumping straight to Orbiter 2016 we are giving up so much. We can't launch with the LVDC, our accelerometers seem to be broken so we can't perform maneuvers  (and the EMS is freaking out on reentry). Let's make this a more gentle move to Orbiter 2016 and not suddenly abandon a version that is working very well right now. Of course you and/or dsgeagrav can focus on making NASSP work in Orbiter 2016, if you want to. Most of what I have done (RTCC MFD, MCC, etc) is applicable to both Orbiter versions and only a few changes will have to be made for Orbiter 2016 anyway.
Logged
dseagrav
Project Admin
Hero Member
*****
Posts: 1118


View Profile
« Reply #6 on: September 06, 2016, 01:49:51 PM »

Please don't make changes to the Orbiter2015 branch (or start an Orbiter2016 branch) for now. As I said, before anything else is done, I have to update the build environment because it uses the SDK from an older release. I'll catch it up to current and then we can start working on it.

For now the "supported" version will be 2010; We are going to issue a 2010 release for Apollo 7-8.
When that release is issued, we will leave the master branch at the 2010 release point and work on Orbiter2015 until it works enough for an Apollo 9-11 release.
This means if any bugfixes need done to the 2010 release we can make them and then carry forward the fixes to 2015 immediately (if applicable).
When we cut the 9-11 release, we will do so by merging Orbiter2015 back into master and releasing master.
That will eliminate the now-dead 2010 stuff and leave us with the Orbiter2015 branch able to be dropped. Development then reverts to master.

Does this make sense?
Logged
indy91
Hero Member
*****
Posts: 1316


View Profile
« Reply #7 on: September 06, 2016, 01:56:42 PM »

Sounds good to me. When the Orbiter 2016 branch is ready for a release it becomes master. I'm not going to do anything about Orbiter 2016 for now, I've only locally tried what works and what doesn't, but nothing else so far. I'll let you handle it until further notice.  Thumbs Up
Logged
vrouleau
Project Team Member
Full Member
****
Posts: 153


View Profile Email
« Reply #8 on: September 06, 2016, 02:40:18 PM »

Yep, sounds good. I'll continue testing on Oribter 2016 and not commit anything until build env and merge back it done.
Logged
kneecaps
Project Team Member
Full Member
****
Posts: 217


36711000 kneecaps@shockpulse.co.uk
View Profile
« Reply #9 on: September 06, 2016, 03:56:41 PM »

Yep, sounds good. I'll continue testing on Oribter 2016 and not commit anything until build env and merge back it done.

To keep your work safe you should create an branch for yourself in Github and ensure your changes are committed back to that branch only. 
Logged

"Okay. As soon as we find the Earth, we will do it."
- Frank Borman, Apollo 8

Current Work: ?? What next??

Future Work:
I know the AGC pretty well so anything need doing there?

On Hold/Completed:
SPS TVC in P40 issues.
P11 FDAI Error Needles (98%) complete. Comitted. Working A7 scenario.
P06 AGC Standby. Concluded. It's done by the AGC PSU.
Got us a complete AOH Volume II
dseagrav
Project Admin
Hero Member
*****
Posts: 1118


View Profile
« Reply #10 on: September 15, 2016, 06:54:40 AM »

The build environment of the Orbiter2015 branch has been updated to the 2016 release SDK, and all pending changes from master have been merged.
Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!