TheEngineer
SOC-14 1K
Hi folks,
one week ago I started a new construction site dealing with a solar system renderer (callsign "SystemView). It does NOT generate solar systems. AFAIK there are a few other tools doing this.
At least it was motivated by the last jump/100D limit discussions.
Well, things went well and I have got a working prototype, who accepts solar system data in XML format and displays the stuff graphicaly in a pannable and zoomable map with a user definable grid.
You can save the selected view anytime you want....
Now a question to make thinks more complicate:
I would like to display planetary orbital positions fitting to a special time in MTU/YTU.
Referring to standard data sources we dont have this information.
I could extend the XML scheme in order to provide additional orbital information, but at least this might lead to another problems to keep different TUs compliant..
So, what would you think about using the actual data we have to generate desired information in a reproduceable way ?
This could be done e.g. by some normal hash functions..
E.g. we have offical basic system data (UWP etc...). Combined with hex coordinates and system name I could generate attributes like solar system ecliptic angle.
Doing the same on the level of orbital bodies in a system I could also use body name und UWP to generate orbital starting positions at a virtual time t0.
Then anyone could be able to specify the actual time in his TU and SystemView would be able to show nearly exact orbital positions at a given time.
Any comments,
Mert
one week ago I started a new construction site dealing with a solar system renderer (callsign "SystemView). It does NOT generate solar systems. AFAIK there are a few other tools doing this.
At least it was motivated by the last jump/100D limit discussions.
Well, things went well and I have got a working prototype, who accepts solar system data in XML format and displays the stuff graphicaly in a pannable and zoomable map with a user definable grid.
You can save the selected view anytime you want....
Now a question to make thinks more complicate:
I would like to display planetary orbital positions fitting to a special time in MTU/YTU.
Referring to standard data sources we dont have this information.
I could extend the XML scheme in order to provide additional orbital information, but at least this might lead to another problems to keep different TUs compliant..
So, what would you think about using the actual data we have to generate desired information in a reproduceable way ?
This could be done e.g. by some normal hash functions..
E.g. we have offical basic system data (UWP etc...). Combined with hex coordinates and system name I could generate attributes like solar system ecliptic angle.
Doing the same on the level of orbital bodies in a system I could also use body name und UWP to generate orbital starting positions at a virtual time t0.
Then anyone could be able to specify the actual time in his TU and SystemView would be able to show nearly exact orbital positions at a given time.
Any comments,
Mert