Galland1998

So I have a strange issue that I think is KCT related but I am not sure. I am running KSP 1.7.3 with RSS/RO RP-1 play through and am making use of the new airlaunch feature for my rocket planes. I launched a rocket plane via air launch and that all worked great (thanks for adding that option by the way). I use a parachute during the landing phase and then then recover the aircraft to the SPH. The plane then shows up in the KCT build list as its being "reconditioned" and once that is complete options to launch or air launch pop back up again as you would expect. I click the button to do another air launch and this time it tells me that the aircraft that I just got done air launching is too big to air launch. I then edit the aircraft via the KCT menu but when I am in the SPH editor the aircraft is effectively spawned outside the editor. I turn on the HangerExtender mod and find that the aircraft was spawned in the editor very high and the right in the scene. I then drag the aircraft back down to a normal position in the editor save the "edits" and go back and look at the main KCT GUI. There it is saying that it needs effectively 25-30% of the build time for a new airplane to effect the changes. When the changes are done I can Air Launch again without a problem. Its still faster than building a new airplane, and we get the air launch option but is this working as intended or am I doing something wrong?

I'm using KCT in a 1.7.3 RP-1 playthrough and you have the option to recover aircraft to the SPH for quicker turn around. When you do that are the parachutes used on that flight reset or do you need to edit the craft and replace the "used" items prior to the next flight?

I am running in KSP 1.7.3 right now on a RSS/RP-1 play through and found that rolling back to 3.6 from 3.6.1 seemed to fix the problem and I am once again able to hide/delete parts. Maybe the 3.6.1 patch broke something while fixing something else.

I am having the same problem with my 1.7.3 RSS/RP-1 Install.

Can the MechJeb modules handle Ullage of the engines that is required in realism overhaul

If you follow the link to the GitHub there in the releases section there is a 1.10 version of the mod from back in October. The notes say that it was a 1.8 update.

Ad Astra is built for the JNSQ planet pack and leverages some of the AVP assets and but is version locked to 1.7.3 due to Kopernicus mod dependencies. Astronomer Visual Pack works pretty well in 1.8.1 as best as I can tell from my experimentation. Spectra is another one that should work in 1.8.1 as well. Spectra is similar to AVP but a little friendlier to your computer and should result in slightly higher FPS. According to its mod page it removed a previous dependency on Kopernicus and should work in 1.8. However, I have not tested that mod personally so I can't confirm its performance in 1.8.

Thanks

Am I doing something wrong with the horizontal test stand cradle. All of the attachment points seem to only connect in the vertical position with when I try to put a tank and engine in it. The vertical stands work just fine.

Do the new antennas in the exploration mod work with RemoteTech?

Does this work in Stock at all or does it require RO to function?

I just started playing with RSS/RO and RP-1. Other than the recommended mod list in the RP-1 Install wiki is there a list of known compatible mods with RSS/RO?

Well according to that config file, while the runway is a North/South aligned runway the heading is not quite north/south. That 0.4 heading deviation might be enough to through the coordinates off. Generally speaking for a north/south runway you would expect to see the longitude to be the same for all of the defined points with different latitudes. While for East/West runways like at the KSC you would expect to see a common latitude and different longitudes. In this case I would guess that either the cfg coordinates and headings are a little wrong or the runway isn't aligned with a longitude line. The accuracy of those points kinda depends on the manner in which the coordinates were derived in the first place. You can also compare these coordinates with the config file that feeds mechjeb and its autoland module.

In real life localizer and glideslope transmitters are not in the same location. Localizers are typically located at the far end of the runway. This means that you can get valid centerline info all the way through the landing or even takeoff operation. The glideslope transmitter is usually abeam the desired touchdown point. You can go here: http://code7700.com/ils.htm for more info about how ILSs work in practice.

So the bit about PlanetShine is news to me. So if you have Scatterer for 1.6.1 or later than PlanetShine is redundant? if they are doing the same thing do they conflict if you have both? I ask because I have been in the habit of having all of those visual mods every time I build a new KSP setup to play with and since I probably use too many mods as it is, I am looking for places to trim down my install.

Installed it last night... It looks so good. Thanks for all the hard work.

Does Tundra 1.7 work in KSP 1.7.3 or do I need to stay with 1.6 until then? My main save is dependent on Koperinicus and I am stuck at KSP 1.7.3 until they update that mod. Also has anyone tried using the Tundra Exploration craft file vehicles in JNSQ? JNSQ is a 2.7x scale system and I was wondering if the intended vehicles in via the craft files are even viable in that scale or if they were balanced just for the stock KSP system.

unless they changed something when I wasn't looking. It was my understanding that Constellation is not compatible with RemoteTech. RemoteTech is largely incompatible with any mod that tweaks the Commnunication Network features of the base game.

Is there an updated list somewhere of supported mods to use in conjunction with Kerbalism 3.1 running in KSP 1.8.1? What I found on the Kerbalism Wiki seems to be a bit seemed to be more in line with pre-1.8.1/3.1 combinations. Also the wiki says to check inside the support folder but every time I click on that link I get a 404 error message.

Thanks! I figured something like that was going on because of some oddities of actually trying to find the parts that were used in the craft file. By the way @Friznit does impressive work. His wiki is super helpful when trying to recreate the craft that you intended with all of your mod parts. Kudos to both of you. As a side note, do any of your parts make use TexturesUnlimited to turn any of the metallic parts shiny?

I've been enjoying the mod pack(... sooo many parts). Anyways, I was working on building out some of the historical launchers and using the included craft files as well. However, With the titan-gemini craft file the part models are a not so attractive splotchy rust brown looking color. Was that intentional or am I missing some graphical setting/mod to make that ship look as intended.

Does anyone know if there is a way to keep the Restock parachute textures while using this mod. I love this mod but I also really like the restock parachute aesthetic.

I figured it was something like that. On of my last saves had PBC tech tree and KW Rocketry and most of the parts seemed to show up when there similar stock parts show up.

Just out of curiosity how does this mod pack treat "unsupported" parts mods? For example I make a lot of use out of the KW Rocketry mod but it isn't officially supported yet.

Anyone test this one in 1.8.1 yet?