If I understood how RTU works, the Iron Hill scenario (whatever the name is) must have in the end:
BEGIN_RealTime
TIME=same MJD from "ENVIRONMENT" section
END
I did run some tests, and the difference between the environment MJD and the MJD saved in RealTime section is minimal (less than one second). You can simply copy the MJD from environment to RealTime if
ultra precision matters. But, if the scn file has this section in the end and the MJD is correct, it has to work.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
PS: you must have to activate RealTime module in launchpad.
---------- Post added at 02:30 AM ---------- Previous post was at 02:21 AM ----------
Example: I have a scenario with
BEGIN_ENVIRONMENT
System Sol
Date MJD 56305.8418328994
END_ENVIRONMENT
(...)
BEGIN_RealTime
TIME=56305.841831
END
Both MJDs correspond to Jan 13 2013, 20:12:14 UT. If I open the scenario now, it will accelerate time until now. If I open next year, it will accelerate until next year.
---------- Post added at 02:31 AM ---------- Previous post was at 02:30 AM ----------
If you have RealTime module activated, Orbiter will put the RealTime section in any scn file you create.
---------- Post added at 02:38 AM ---------- Previous post was at 02:31 AM ----------
Also, the file .../Config/realtime.cfg must have the following:
If not, it won't use time acceleration.
---------- Post added at 02:47 AM ---------- Previous post was at 02:38 AM ----------
I got the last IHP state posted by Felipi and added in the end
BEGIN_RealTime
TIME=56299.1226944559
END
(the same MJD from environment)
It worked very well. But we must be careful to not save a state with focus defined to a ship in LEO or in an orbit close to a massive body: acceleration rates higher than 100x are not recomended in these cases. Look for a vessel in solar orbit or landed befor saving state.