General Question How to specify multiple meshes for a single payload in Multistage 2015?

[CurlSnout]

I'm trying to create a payload that itself contains a payload (a geophysical rocket in which the instrument payload has a recoverable data capsule). According to the Multistage 2015 manual, up to five meshes are allowed for any given payload (and, up to 10 payloads are allowed). Can someone tell me how to list multiple meshes in the *.ini file for a payload?

I understand the payload section should look something like this:

[PAYLOAD_1]
Meshname=abc
Off=(xx,yy,zz)
Height=xx
Diameter=xx
Mass=xx
Module=abc
Name=abc

But I'm not sure how to list more than one meshname. When I create more than one [PAYLOAD_1] section and use different mesh names for each, only the first mesh loads. And, if I create separate payload sections (e.g., [PAYLOAD_1], [PAYLOAD_2]) both meshes load, but they run into/over/through each other upon deployment. I've looked through my collection of Multistage spacecraft and so far haven't found any *.ini file that lists more than one mesh for a given payload.

Any/all help appreciated; thanks in advance.

cs

 

[CurlSnout]

UPDATE: I found what I hoped was a solid hint, looking at Vinka's original 'Multistage launcher support' document (from 2005?):

Mandatory parameters
• MESHNAME : mesh name of payload. It has been found that all payloads must have a
different mesh name or Orbiter will crash. You can define up to 5 meshes for one payload,
they must be declared in the same string, with each mesh name separated by a ; (semicolumn).
Ex: mesh1;mesh2
• OFF : (x,y,z) vector position of payload mesh offset in launcher (meters). If you have
declared more than one mesh for the payload, you must declare the same number of offset
in the same order. Offset positions are separated by ; (semi-columns). Ex: (0,0,25);(0,0,27)

So the answer to the question I posed above appears to be that the mesh names are declared in the same string and separated by a semicolon. Then it's necessary to specify additional offset values.

I tried this; the flight works OK until I try to deploy the first payload - the first payload disappears (i.e., vanishes out of existence) and the second payload deploys. So I might have to use multiple payloads (e.g., [PAYLOAD_1], [PAYLOAD_2]) instead. So far I haven't figured out how to get that to work either. I'll keep trying.

 

[gattispilot]

Here is my SLS with several satellites and the rocket itself

 

[CurlSnout]

Thanks, gattispilot, for sharing this. I'm still trying to work this out. Here is a related question: How do you accurately determine 'z' values for mesh offset in the [PAYLOAD_x] section of the *.ini file?

Off=(xx,yy,zz)

I can get both meshes to show up now when I declare them in the same string and separate the names with a semicolon (according to Vinka's instructions) but get strange behavior when I deploy the 'parent' payload.

 

[gattispilot]

Thanks, gattispilot, for sharing this. I'm still trying to work this out. Here is a related question: How do you accurately determine 'z' values for mesh offset in the [PAYLOAD_x] section of the *.ini file?

Off=(xx,yy,zz)

I can get both meshes to show up now when I declare them in the same string and separate the names with a semicolon (according to Vinka's instructions) but get strange behavior when I deploy the 'parent' payload.

I usually get the values from Meshwizard or trial effort. Can you share your ini in PM(private Message and I can take a look.

In my SLS it was to launch the Cubesat but in real life there were more than MS2015 would allow

 

[CurlSnout]

Thanks for offering to take a look at this. Message sent.

 

[CurlSnout]

OK, I installed Mesh Wizard (with which I have zero familiarity). Where does it give you the mesh offset values?

 

[gattispilot]

With Meshwizard you can measure the top,bottom,....

Sometimes for me it is trial and error.