OK, I see. Referring to the manual I see that I can have a single booster, so I'll have a [BOOSTER_1] and a [Booster_2]? Awesome!
Gotta go play around with an .ini file now, Thanks K_Jameson!!
---------- Post added at 10:04 PM ---------- Previous post was at 07:19 PM ----------
Hmm, there is something that I'm missing out on. I've got the look I want now, my references put the boosters on a 8 degree angle. With that in mind I edited the mesh(s), and renamed them accordingly. When I sat it on the launch platform at SRC Polygon (by Kultch), once I got the lat/long right, it fit like a glove.
But... (there is always a but isn't there), upon burnout, booster_1 ejects like it should, booster_2 also ejects, but in the same direction as booster_1.
Here you can see the port-side booster passing through the core stage. I've read the multistage manual, but I didn't see anything that addressed separation vectors, only translation and rotation speed. If nothing else I can always go back to the way it was with no problems (except the look won't be accurate).
Can anybody point me in the right direction, without me learning a crash course in programming a .dll?
Solved! I got a "I wonder..." moment while getting dinner at Subway (eat fresh!).
The solution was right in from of me, provided by Vinka by way of the demo scenario and rocket. I was more concerned about placement, via the offsets, that I just swapped on number for it's negative on the other side. As I found out, not needed, just the offset from centerline (and -z of course). The angle=x takes care of it for me. I was apparently thinking too hard about it.
Two test flights later and I've got a rocket and booster that look pretty close to right. Test flights will get me the data I need for a guidance file, but I'm going to recommend the UAP, with it there is no need to edit or re-write the guidance file for different inclinations.
So cross number 2 off the list.
Still on the punch-list is a simple tug of some kind, it'll take up space inside the fairing, but it's pretty much a requirement (I think).
Gotta go play around with an .ini file now, Thanks K_Jameson!!
---------- Post added at 10:04 PM ---------- Previous post was at 07:19 PM ----------
Hmm, there is something that I'm missing out on. I've got the look I want now, my references put the boosters on a 8 degree angle. With that in mind I edited the mesh(s), and renamed them accordingly. When I sat it on the launch platform at SRC Polygon (by Kultch), once I got the lat/long right, it fit like a glove.
But... (there is always a but isn't there), upon burnout, booster_1 ejects like it should, booster_2 also ejects, but in the same direction as booster_1.
![Oops.jpg](http://www.orbiter-forum.com/gallery/data/503/Oops.jpg)
Here you can see the port-side booster passing through the core stage. I've read the multistage manual, but I didn't see anything that addressed separation vectors, only translation and rotation speed. If nothing else I can always go back to the way it was with no problems (except the look won't be accurate).
Can anybody point me in the right direction, without me learning a crash course in programming a .dll?
Solved! I got a "I wonder..." moment while getting dinner at Subway (eat fresh!).
The solution was right in from of me, provided by Vinka by way of the demo scenario and rocket. I was more concerned about placement, via the offsets, that I just swapped on number for it's negative on the other side. As I found out, not needed, just the offset from centerline (and -z of course). The angle=x takes care of it for me. I was apparently thinking too hard about it.
Two test flights later and I've got a rocket and booster that look pretty close to right. Test flights will get me the data I need for a guidance file, but I'm going to recommend the UAP, with it there is no need to edit or re-write the guidance file for different inclinations.
So cross number 2 off the list.
![Booster_sep1.jpg](http://www.orbiter-forum.com/gallery/data/568/Booster_sep1.jpg)
Still on the punch-list is a simple tug of some kind, it'll take up space inside the fairing, but it's pretty much a requirement (I think).
Last edited: