I suggest you take a look at the video tutorial called Custom Events and Proper Motion, found here.
In the Uniview Theater Run-time Command Syntax guide you can read about more about the stars.time factor:
Prefix
stars.
Command
Arguments
Description
time
factor
<factor>
This command makes the stars,
specifically, interpret the simulationtime differently from all other objects in
Uniview. It makes the stars simulate according to a time that is <factor>
times further away from the epoch of 2000 01 01 12 0 0 than the current
simulationtime is. In other words, if the current simulationtime is
2001-01-01-12-0-0, that's one year away from the epoch. The command stars.time
factor 1000 will then make the stars simulate as if the time was not one year
but 1000 years away from the epoch, i.e. 3000-01-01-12-0-0. This is useful for showing proper
motion of stars.
A useful command together with the above is "system.setsimulatedtime 2000 01 01 12 0 0" as this sets the Uniview time to J2000. From there simply use a significantly large stars.time factor to suit your needs. My preference is to use "stars.time factor 315576000" as that gives each second Uniview time to correspond to appx 10 years, and then just use the timejuggle. The nice thing in scaling from seconds to years is that you don't get any interference from the motions of celestial bodies.
To do what the previous comment suggest, use the default custom events:
To start proper motion:
Run custom event: Time J2000
Run custom event: Star Time 1s per 10yrs
Now if you want to use the GUI to change the time, you can scroll the time in the time widget. Remember you can change the time speed using the time widget which would behave with the scaling on top of the scaling you set with the custom event: Star Time 1s per 10yrs.
Note that you can also run your own time commands (if you don't want to use the time GUI widget). Checkout time.set command reference in the runtime syntax documentation.
I suggest you take a look at the video tutorial called Custom Events and Proper Motion, found here.
In the Uniview Theater Run-time Command Syntax guide you can read about more about the stars.time factor:
Prefix
stars.
Command
Arguments
Description
time factor
<factor>
This command makes the stars, specifically, interpret the simulationtime differently from all other objects in Uniview. It makes the stars simulate according to a time that is <factor> times further away from the epoch of 2000 01 01 12 0 0 than the current simulationtime is. In other words, if the current simulationtime is 2001-01-01-12-0-0, that's one year away from the epoch. The command stars.time factor 1000 will then make the stars simulate as if the time was not one year but 1000 years away from the epoch, i.e. 3000-01-01-12-0-0. This is useful for showing proper motion of stars.
e.g:
stars.time factor 31557600
as this sets the Uniview time to J2000. From there simply use a significantly large stars.time factor to suit your needs. My preference is to use "stars.time factor 315576000" as that gives each second Uniview time to correspond to appx 10 years, and then just use the timejuggle. The nice thing in scaling from seconds to years is that you don't get any interference from the motions of celestial bodies.
To do what the previous comment suggest, use the default custom events:
To start proper motion:
Now if you want to use the GUI to change the time, you can scroll the time in the time widget. Remember you can change the time speed using the time widget which would behave with the scaling on top of the scaling you set with the custom event: Star Time 1s per 10yrs.
Note that you can also run your own time commands (if you don't want to use the time GUI widget). Checkout time.set command reference in the runtime syntax documentation.
When you want to reset to normal time factor: