Yes I do, I just wasn't sure if I needed to include it.
The bug could have been in the StarBarycenter. If there had been a bug.
First of all, to get your 'se.log' a little cleaner.
Set 'CatalogLogLevel 2' in the 'main-user.cfg'.
// Logging settings
Log
{
LogTimeStamp false // print time stamp into log file
LogThreadStamp true // print thread ID into log file
// Level of logging while loading catalogs:
// 0 - do not log
// 1 - log errors and warnings, using min("CatalogLogLevel" in this config, "LogLevel" in the catalog file)
// 2 - log everything, using min("CatalogLogLevel" in this config, "LogLevel" in the catalog file)
// 3 - log errors and warnings, ignoring "LogLevel" in the catalog file
// 4 - log everything, ignoring "LogLevel" in the catalog file
CatalogLogLevel 2
Otherwise, a lot of superfluous error messages are generated!
For example, something like this:
[MT] "data/catalogs/Catalogs0980.pak/stars/BrownDwarfs.sc" line 32320: ERROR: Star "WISEA 00471-37103/WISEA J004713.81-371033.7" can't compute distance, random value 555.056 assigned
These errors are caused by missing data, but are not a problem because SpaceEngine generates a random value.
If you want all error messages to be output for a particular script, you can put 'LogLevel 2' at the beginning. (But you know that.)
(Excerpt from the manual :
It is recommended to specify LogLevel 2 in your sc files and CatalogLogLevel 2 in main-user.cfg while you are working on catalogs so you will have all information about star solver work in the log file (see Creating a star for details). If you need to see only possible errors, specify LogLevel 1. If some errors or warnings are still visible in the release version of your catalog (for example, no RA/Dec data are provided for a star, and star solver generates them procedurally), it’s recommended to specify LogLevel 0, so other users will have their log files clean of errors related to your catalog.
)
After doing this, there will still be a lot of error messages in your log. You really should try to get rid of these error messages.
Your 'Serudina' script does not generate an error message for me and works fine.
The only warning I receive concerns IC 1101! BUT this warning has nothing to do with your script. It also appears without your script.
But you actually have too many planetary objects! The limit is 32767. (Approx.)
[MT] sc cat planets: 32862
[MT] sc del planets: 62
[MT] Merged planets: 36
[MT] Deleted planets: 50
[MT] Failed planets: 0
[MT] Final planets: 32776
DONE
(I post my 'se.log' to show what a log looks like without any error messages!
)