Very cool! Thanks for work! Few notes:
-With the catalog installed SE will take more time to start. One minute or two depending of your computer.
This is true, script engine in SE is very slow. I plan to make an alternative - using CSV files for catalog. Objects like stars, which have small number of parameters (coordinates, stellar class, luminosity, mass, radius and name) can be effectively saved in a text table and quickly loaded in SE. Text table is very easy to edit in CSV editors (or even in notepad), so you can quickly fix incorrect data or add new stars. No more binary star catalog will be required.
-Unfortunatly SE cant generate procedural planets around objects in external catalogs like this one.
I added manually a few procedural planets in the nearest browns.
Not correct. SE do generate procedural planets for any catalog stars, if you did not describe any object in planet catalog for this star. But you described many brown dwarves there as stellar objects orbiting barycenter. You can fix that at least for solitary brown dwarves by describing them only in stars catalog, but this also disables custom mass and radius (currently SE didn't read Mass and Radius data in stars catalog, they simply ignored).
Also, I noticed that you used RemoveStar command in the planet catalog (BrownsMain.sc). This have no sense, this command is for stars catalog only.
and change their values to
This is too hard values! They disables procedural star generation in entire Milky Way galaxy! And even in Magellanic clouds!
and change the values of this lines:
all of them to 0, the final result should be this:
And this disables generation of multiple stars and stellar remnants in entire Universe! If you want to disable procedural bifurcation of catalog stars, you must use StarProcBifurcation false instead of.
Also, did you set StarSilentLoading false when you made your catalog? This helps to track any catalog errors.