That's something I have never quite understood, how to proceed to the 600 ft point on the ISS RBAR starting with that scenario. Anyone more familiar with the RNDZ ops care to post a more comprehensive description of what step or page of the RNDZ FDF it starts on?
Edit:
Mistake on my part. I thought that the ISS docking scenario you were talking about was the Rendezvous test scenario in the Testing scenarios folder. The question is still valid though.
Radar test scenario added. If the scan is started with the OV in the initial orientation the scan spiral ends right away as a target (ISS) is in sight of the antenna, so a pitch and/or roll change before starting the search will show more of the spiral.
About the rendezvous ops, I don't know how SSU stands and I don't know much of the real thing. Now with the radar, I'm sure it would be more realistic from 150Kft (or so) down to whatever distance it is stopped. Currently due to my lack of knowledge of the algorithms/displays/etc used and the incomplete DPS, the radar just outputs to panel A2.
---------- Post added 05-09-16 at 12:38 PM ---------- Previous post was 05-08-16 at 11:49 PM ----------
Finished setting up the second SSU folder and "installing" Orbiter 2016.
My first impression is that SSU seems to run better (more fluid) in MOGE 2016 than MOGE 2010. I started with the upper stages (as they are relatively simple) and both seem to work fine.
Moved to the OV in orbit and the vc works fine except for panel F4 that doesn't seem to be detected. The ASE/CISS both seem to work fine. The new radar seems to work as it tracked the IUS for a while. Didn't test RMS, docking or OMS burns yet. Some work in the CRTMFD/MDU is needed to take advantage of the new MFD limit (this if we are going to stick with the MFDs). There was a problem with time acceleration, where after a period at 1000x and returning to 1x, the vehicle just starts accelerating out of LEO and eventually CTD.... don't know if it's SSU's fault. Also noticed from orbit that VAFB was showing the surface tiles but KSC was white. Particle streams will need to be decreased, as they show up much larger than in the 2010 version.
Then I tried the EDW landing scenario and my early optimism went down the drain. The HUD needs to be re-done as the scale is different. Then I realized that the runway was not where it should (or not where the GPCs were telling me). This includes the vertical position as well.
After touchdown, the OV joined a circus and started doing summersaults and CTD, obviously the result of not having the new touchdown point system. After that I'm somewhat afraid to try the launch scenarios. :lol:
So, IMO it's going to be very very very hard to get a "large-scale" addon (several vessels, surface bases, scenarios, etc) like SSU working on 2010 and 2016. The surface bases probably all need to be changed to accommodate the new stuff, and then the landing site table has to be corrected and changed to add runway altitude. And the scenarios "inside the atmosphere" have to re-done. I'm not fully up-to-date on the new terrain system, but the surface tiles are probably not needed anymore.
So to conclude, IMO to get SSU to run on 2010 and 2016 we need to keep 2 lines of development. The changes needed are just too fundamental to do it all together. So, as we can barely keep one line of development going, the question for me now is: do we take the current state and release a SSU 3.1 for Orbiter 2010 and forget about it, or do we skip the release part and move on to 2016 right away?
