Another possible way might be to make a window with a text field and paste the body info into there. Then when you press 'ok', parse it and create the new body.
I just used the XML importer and it seemed to work ok. What I'd do is create a small sector, export it using the xml exporter. Then re-start Astro and use the XML importer to re-import that file. Once you get to that, you can see what the data shoul…
CSV isn't very good for hierarchical data, so that's why only stars (or top level bodies) are supported in that format. There's an XML exporter in the plugsin menu, and also an older XML importer here ( https://www.nbos.com/nox/item/7 ) that may sti…
Yes, for the most part FM8's API is the same. FM9 only introduces a few new functions for working with tabs and packages.
The big difference between the two is FM9 no longer uses the Microsoft VBScript engine for scripting, and instead has its own …
No, there's no API function for that. You'd need to implement that yourself. That can get tricky because there's different types of polygons, and not all area methods work with all of them. I think the method I use in some other programs is to tesse…
I disabled all the options when I exported from inkscape, but you can fiddle around with those to find the best to use. Just one note - FM does not support reading text, I don't believe from emf files.
Ok, svg, now you're talking. You can use Inkscape to convert the svg file to .emf (enhanced windows metafile) and open that directly (ie, File->Open) in FM9. Here's an example from that site.
Not with FM itself. You'd have to use an external tool or write a program to convert the json into something FM can read. FM actually has a text version of its format, so possibly something that could create that.
You can set a sphere of influence around a system using the setting for it in the properties window (on the Position and Display tab). You cannot set a general shape around an arbitrary region though. Best you can do is apply the sphere to each syst…
Yep, this is a good hint. IPP should probably not allow tables with spaces at all, just to prevent the weird confusions they create when its trying to decide if something is meant as a table or table & parameter.
If you select-all it will select all, but only show the first 20 systems in the system data tree (because otherwise you could be getting to hundreds of thousands of items being loaded into it). So you should be able still mass-edit everything. I wo…
If you have existing data, the best approach might be to write an Astro script to rotate the system positions. Then you would not need to transfer anything. You'd iterate the systems and adjust their x/y/z position based on the desired rotation and …
There is no inherent sector orientation in Astro. If you are using real-universe data, you'll need to rotate it to the desired orientation before importing.
In the Advanced Usage section of the help file, under Importing and Merging, there's a section describing a CSV file format that Astro can import. So you'd have to get the data out of this or any other stellar database and reformat it into the forma…
If you want to assign them randomly to all the planets in the sector you'll have to write a script. There's no way to make the built in generator assign these values.
I made a program years ago that took sample text and split words up into syllables, recording the combination frequency. Thats what I used for some of the name generators in IPP and those used by Astro.
I looked into this and the following are what are passed into the generator as variables:
"BodyType": The name, such as Star or Terrestrial
"Habitability": The description (Inhospitable, habitable, hospitable)
"Population": either "Populated" or …
Hmm, no, not in a 3d sense. You can set up a marker that orbits the planet at a particular distance. That will show the circle around the planet in the system viewer.
What's the error you're getting? Usually commenting out lines until the error goes away gets you the cause.
You can check if the BodyType is BODY_TYPE_MULT or BODY_TYPE_CLOSEMULT to detect if its a multiple. Actually what you might want to do is th…
Try iterating systems like this
#plugin Squashdown!
#author NBOS
#desc Compresses system positions along the Y axis
sector = GetCurrentSector()
j = sector.SystemCount
For i = 1 to j
o = sector.GetSystem( i-1)
o.y = o.y / 2
o.M…