jholley309
New member
Okay, so I'm thinking the list of "working" add-ons for 2010 seems to depend on your idea of "working"...
For instance: the SpaceX Falcon1/9/Dragon add-on. Okay, the rockets seem to work okay (except for the fact that the payload fairing just winks out of existence when you jettison it on the 9 and 9H, but that's not as bad as the disappearing stages on the Francophone Proton), but the scenarios direct you to use Kev Shanow's highly detailed (and quite beautiful) Canaveral LC40/41 add-on. And that's where the trouble begins...
Now, I haven't loaded any of this to 2006 to see if it functions as designed there, so in all fairness to Mr. Shanow the saga I'm about to describe may not be entirely his fault. And to be honest, I'm a born tweaker so it's really not such a huge big deal; after all, I did successfully hack Mr. Shanow's LC39 add-on to get at least Pad 39B in the correct position for the 2010 surface tiles (which took most of a day, but really...have you seen that thing? It was worth it...). So I faithfully unzipped the LC40/41 archive into the Orbiter folder and fired up a Falcon 9 scenario. Whereupon I found a lonely (but lovely) rocket standing on...nothing. No pad. No tower. No HIF. A quick look around revealed LC 39 still in its place, but LC40? Nowhere to be seen. Let the reverse engineering begin...
Thankfully, I had read part of the Orbiter SDK that mentioned not modifying things like the default earth.cfg and other common files, and instead putting a text file in the distribution that contained the necessary information to merge withthe default files, along with instructions on how to do that. Well, there were no instructions but I did find the supplemental config files, which I promptly merged with the defualt files. Back into the scenario and presto! I had LC40. Only now, some surface tiles seem to have disappeared, and LC39 is way out in the Atlantic. Apparently I have some additional hacking to do...
More on this when I don't have to go to work...
Cheers!
For instance: the SpaceX Falcon1/9/Dragon add-on. Okay, the rockets seem to work okay (except for the fact that the payload fairing just winks out of existence when you jettison it on the 9 and 9H, but that's not as bad as the disappearing stages on the Francophone Proton), but the scenarios direct you to use Kev Shanow's highly detailed (and quite beautiful) Canaveral LC40/41 add-on. And that's where the trouble begins...
Now, I haven't loaded any of this to 2006 to see if it functions as designed there, so in all fairness to Mr. Shanow the saga I'm about to describe may not be entirely his fault. And to be honest, I'm a born tweaker so it's really not such a huge big deal; after all, I did successfully hack Mr. Shanow's LC39 add-on to get at least Pad 39B in the correct position for the 2010 surface tiles (which took most of a day, but really...have you seen that thing? It was worth it...). So I faithfully unzipped the LC40/41 archive into the Orbiter folder and fired up a Falcon 9 scenario. Whereupon I found a lonely (but lovely) rocket standing on...nothing. No pad. No tower. No HIF. A quick look around revealed LC 39 still in its place, but LC40? Nowhere to be seen. Let the reverse engineering begin...
Thankfully, I had read part of the Orbiter SDK that mentioned not modifying things like the default earth.cfg and other common files, and instead putting a text file in the distribution that contained the necessary information to merge withthe default files, along with instructions on how to do that. Well, there were no instructions but I did find the supplemental config files, which I promptly merged with the defualt files. Back into the scenario and presto! I had LC40. Only now, some surface tiles seem to have disappeared, and LC39 is way out in the Atlantic. Apparently I have some additional hacking to do...
More on this when I don't have to go to work...
Cheers!