Source of the post Right now I'm slowly going through main belt confirmed binaries from Johnson's Archive, then there are still tons of confirmed NEOs and TNOs that will have to be added to the script. Then there are more which are probable binaries, some of them are already in the catalog. Lot of work in spare time.

Source of the post Space Engine seems to be fine with showing the number of moons for the largest object in the barycenter system. Take the multiple TNO Pluto for example. In this system SE shows the barycenter "Pluto-Charon" having 6 satellites and Pluto having 5. Also as another example, the binary asteroid Antiope is shown having 1 moon and barycenter "Antiope system" is shown with 2 satellites.

This is fixed for the next version. SE now "collects" satellites from the children and parent barycenters and adds them to the primary's satellites counter. Primary is the most massive object in the system.

Permian Therapsid wrote:

Source of the post Could I ask how the diameters of asteroids and other objects shown in the game are calculated? Is this equatorial diameter, mean diameter or what?

Equatorial. Yes I added Solar System myself manually, but processed asteroids and comets from the MPC data files (there are thousands of them).

Permian Therapsid wrote:

Source of the post Sorry if I ask this here, was just wondering the asteroid diameter calculation in the game engine as many asteroids are not very regular shaped.

SE does not calculates radius of asteroids - vice versa, it reads it from catalog script and generates model roughly of the same size. If there is no radius data provided, SE tries to calculate it from photometric parameters (absolute magnitude and slope factor) - this is the case of majority of asteroids. Of course if you trying to measure an average radius of a procedural model, it will not coincide with the catalog value, due to random nature of procedural terrain.

Source of the post Space Engine seems to be fine with showing the number of moons for the largest object in the barycenter system. Take the multiple TNO Pluto for example. In this system SE shows the barycenter "Pluto-Charon" having 6 satellites and Pluto having 5. Also as another example, the binary asteroid Antiope is shown having 1 moon and barycenter "Antiope system" is shown with 2 satellites.

This is fixed for the next version. SE now "collects" satellites from the children and parent barycenters and adds them to the primary's satellites counter. Primary is the most massive object in the system.

Thanks SpaceEngineer, this would fix was vey much need.

SpaceEngineer wrote:

Permian Therapsid wrote:

Source of the post Could I ask how the diameters of asteroids and other objects shown in the game are calculated? Is this equatorial diameter, mean diameter or what?

Equatorial. Yes I added Solar System myself manually, but processed asteroids and comets from the MPC data files (there are thousands of them).

Thanks. I was just curious. I wonder is there any possibility that the next SE version would fix several errors and missing Solar System data I have found, or have you already finished it?

SpaceEngineer wrote:

Permian Therapsid wrote:

Source of the post Sorry if I ask this here, was just wondering the asteroid diameter calculation in the game engine as many asteroids are not very regular shaped.

SE does not calculates radius of asteroids - vice versa, it reads it from catalog script and generates model roughly of the same size. If there is no radius data provided, SE tries to calculate it from photometric parameters (absolute magnitude and slope factor) - this is the case of majority of asteroids. Of course if you trying to measure an average radius of a procedural model, it will not coincide with the catalog value, due to random nature of procedural terrain.

Is there any possibility that you could be able to add non procedural models for those asteroids we have light curve data on their possible shape? Or if you do not think that is accurate enough to add, would there be any possibility that you could add accurate shape for those asteroids, dwarf moons and comets that have been imaged close enough that we have accurate data on their shape and surface features. Would there be any possibility that there would be accurate surface maps for these asteroids, comets and dwarf moons of asteroids, TNO:s and gas giants that we have accurate data on their surface features.

Vesta, Ceres and Pluto, do already have real maps included in SE, but what about Gaspra, Ida & Dactyl, Lutetia, Eros, Toutatis, Plutos dwarf moons and some of the dwarf moons of Gas giants. Also asteroids Steins, Itokawa, Braille, Mathilde and Annefrank do have close observations on their shape and surface but are not included in SE yet. Also comets 1P, 9P, 19P, 81P, 67P and 103P have accurate data on their shape and surface. Is there any possibility you could implement correct shape and /or surface maps for at least these asteroids, comets and dwarf moons that do have accurate data on them.

Permian Therapsid, adding everything is possible, if there are 3d models and/or elevation maps of these objects exists. I saw custom 3D models of asteroids and dwarf moons in Celestia and other planetarium software, but they cannot be used directly in SE, also, there are copyright issues. If you or someone else could somehow create an elevation maps for these bodies, including them into SE would be just few clicks.

Permian Therapsid, adding everything is possible, if there are 3d models and/or elevation maps of these objects exists. I saw custom 3D models of asteroids and dwarf moons in Celestia and other planetarium software, but they cannot be used directly in SE, also, there are copyright issues. If you or someone else could somehow create an elevation maps for these bodies, including them into SE would be just few clicks.

I have discovered possible source for 3D models of several asteroids, comets and some moons. It does also have maps for some of them. I can post that on catalog fixes thread. I also have found some other sources for surface features of several asteroids and some comets that may be useful.

You are welcome Mosfet, It seems that many unnamed moons lack the | symbol in the SE catalogs (examples "DwarfMoon "S2000 J 11", DwarfMoon "S2003 J 18", DwarfMoon "S2003 J 4", Asteroid "S2016 (107) 1", and Asteroid "S2006 (9617) 1""). Only 18 moons in Asteroids-bin.sc have name with | like "Asteroid "S|2004 (1313) 1"" for example), could you, or I remove that symbol from the asteroid moons and we would just catalog them like this "Asteroid "S2004 (1313) 1""? That would be more consistent with the rest of the catalog of SE.

Oops, that symbol will be used starting from SE 0981 version. Probably it slipped in some substitution I did, for now I'll remove it to restore name conventions for SE 0980.

Hey, would you be able to add the | = / symbol to the names of all unnamed moons of asteroids after the SpaceEngine 0.981 is officially released? I did also find some odd error with the TNO "2007 UK126/(229762) 2007 UK126" and its moon. The asteroid and its moon will not appear in game for some reason. This happened in 0.981 version.

Source of the post Hey, would you be able to add the | = / symbol to the names of all unnamed moons of asteroids after the SpaceEngine 0.981 is officially released?

Sure, even if for current beta builds SpaceEngineer took care of this. Also, given that the issue with Greek letters/Constellations name parser will probably lead to small changes in syntax, I would wait to see what happens with SE 0981 final release.

I see that 2007 UK126 and its moon are included in Asteroid-bin.sc for build 8 with those orbital parameters and I'm seeing them just fine. Did you check your se.log? Maybe there's some script that is merging with the existing code?

Seems good, but PeriodDays and SemimajorAxisKm will work only for 0981 release and following, so to maintain compatibility with 0980 they should be converted in years and AU. Per other naming conventions I think the name should have the discovery date in it, so unless it's otherwise specified in papers I would change it with something like:

Sure, even if for current beta builds SpaceEngineer took care of this. Also, given that the issue with Greek letters/Constellations name parser will probably lead to small changes in syntax, I would wait to see what happens with SE 0981 final release.

Ok, thanks. I did download the 0.981 some time ago so maybe I do not have everything as the latest update.

Mosfet wrote wrote:

I see that 2007 UK126 and its moon are included in Asteroid-bin.sc for build 8 with those orbital parameters and I'm seeing them just fine. Did you check your se.log? Maybe there's some script that is merging with the existing code?

[color=#aaaaaa]Seems good, but PeriodDays and SemimajorAxisKm will work only for 0981 release and following, so to maintain compatibility with 0980 they should be converted in years and AU. Per other naming conventions I think the name should have the discovery date in it, so unless it's otherwise specified in papers I would change it with something like:

Since 2007 OR10 main body right now is included in KuiperBelt.sc, I would transfer its parameters in Asteroids-bin.sc as well.

For Sisyphus it's about the same.You're working hard! [img=24x24]http://forum.spaceengine.org/images/smilies/icon_e_smile.png[/img] I hope to have some time to update the script this weekend.

Ok, thanks! I have tested the 0.981 version and it looks nice, I also did some addons that include 220 new Sol System asteroids and I did some changes for comets file. I did post them on 0.981 beta test thread. This is because I did base the comets.sc update on 0.981 version.

For some reason my SE will not have 2003 QW111, 2007 TY430, 2007 UK126. They are missing. What could that be?

I did also find problem with Kandrup. The info text when having the system map mode is flashing so fast that its hard to read.

(EDIT: I do have in fact 2003 QW111, 2007 TY430. They are now named objects Manwe and Mors. But the third object (2007 UK126) is missing.

(EDIT2: I did modify Asteroids-Rem.sc by removing the command for removing 2007 UK126 and now it is fine. Would it be good idea to remove this command from the original file if it is not needed and can cause these kind of problems?)