BMot360

I'm having some problems with the Inon Decouplers since the last dev release. The attachment points aren't the same as they used to be/don't work and neither do the engine fairings. I noticed the problem when trying to attach to the Inon Engine Mounting Plate/Inon-75 engine (either one engine or two). Previously, an engine fairing was generated that lined up correctly with the fuel tank. Here are some screenshots.

Wow, that looks awesome. Just downloading now. Can't wait to give them a whirl.

Awesome. I look forward to it! Thanks.

Awesome looking parts there. Any plans to add TweakScale?

Looks awesome. What settings are you using, may I ask? Looks nothing like my Scatterer/EVE.

I think the LR-87 could be called "Bwoooop".

Awesome. Which docking port are you using on the Agena?

Hey Cobalt, just thought I'd let you know that this problem is no longer happening with the 0.08a release. Loving the Agena, it's great! Beats my stock/Tantares Agena I was using with your Atlas parts. On a side-note - and seen as though you mentioned a while ago about your interest in "older rockets" - I thought you (and everyone else), might like Breaking the Chains of Gravity: The Story of Spaceflight Before NASA written by Amy Shira Teitel.

Bug report for the RMA-D-30 The RMA-D-30 consists of 2 nozzles. When firing the engine, one nozzle thrusts backwards, i.e. the correct direction, the other nozzle thrusts forwards (at least the animation does) and my craft enters a wild spin due to the opposing directions of thrust.

Looks awesome. What part(s) are you using for the upper half of the first stage - after the Muo-2585? I wonder how much of a loss Orbital ATK are making if they're having to use an Atlas V instead of the Antares; seen as though the lowest spec Atlas V has 50% more payload capacity than the Antares.

I believe it's supposed to arrive on 9th December.

I'm having a problem with the G-143A Orientation Parachute and the G245A Docking Unit. When deploying the parachute, when coming into land, the docking unit detaches and the parachute deploys.The docking unit then flies up and destroys the deployed parachute. This has never happened before and my design and staging haven't changed. Has anyone else experienced this?

[quote name='trooperMNG']Question for everyone: where to find alternate textures? I saw a lot of imgur albums with green Soyuz[/QUOTE] There's an Alternate Texture folder in the Tantares download. I'm not at home, so can't check the file structure, but I imagine you replace the default files, e.g. in the SOYUZ folder, with the file from the Alternate Texture folder

Just a query: Is there a reason for the why the [I]G-750A Orbital Rocket Motor[/I] can only be decoupled via Action group and not via Staging? I've been having a look around the CFG file and can see... [QUOTE]MODULE { name = ModuleDecouple ejectionForce = 40 explosiveNodeID = top staged = false }[/QUOTE] I'm not a modder, but I assume changing [I]staged[/I] to [I]true[/I] will enable this, but will it break anything else (not at home to test out)?

[quote name='CobaltWolf']Wasn't necessarily planning on doing ATV, just Agena.[/QUOTE] An Agena would be really sweet. It would definitely make my [URL="http://imgur.com/a/aia56"]Mariner 2 recreation[/URL] look a lot cooler! Any plans for a Titan II in the future?

[quote name='malkuth']Huh? Potatoe? Man something must of been really screwy in that last update.. I will check it out thanks. [COLOR=silver][SIZE=1]- - - Updated - - -[/SIZE][/COLOR] I promise that this was not an intentional thing.. Not even sure why or how at this point. AS for the APA PEA problem remember default Error of margin for those are only 1000 meters. You can change it in the Config file if its to low. I will set it higher in next update since I keep forgetting to do this. [COLOR=silver][SIZE=1]- - - Updated - - -[/SIZE][/COLOR] [B][SIZE=5]Version 1.25[/SIZE][/B] 1. Fixed the Great potatoes Bug mystery. Satellite contracts had a strange requirement for a Potato? This was not an intentional feature. What happened was that I have always used a default mission objective from default KSP contracts. That is the satellite has Power and is new.. This was from the fineprint contracts that ship with the game now. When 1.05 for KSP came out the contract. Parameters for fine print were MOVED to a new location and some renamed. I found what I though was the new name for Satellite has power and is new.. But I guess it is not the case. Sorry for lack of checking on that one, that part is my fault. 2. I raised the default error of margin for APA and PEA from 1000 to 5000. 3. Shipped the up-to-date config file with new version. The older version had an older config file.. Was not a big deal the config file rewrites itself if its not correct, but still rather have the right one for you can edit the config file before starting for the first time.[/QUOTE] Thanks for the update, malkuth. Also, I do agree with Apollo13 that the wording of the ApA/PeA criteria does seem to imply that anything about the altitude will work.

[quote name='VenomousRequiem']Oh the topic of neat things, have some screenshots. I feel naked without EVE enabled, but I'm having trouble with it lately... Anywho- [URL]http://imgur.com/a/noTR9[/URL][/QUOTE] This might be a stupid question, but which fairings are you using? They're nice and round!

So I've just installed this mod and had a few problems with my first contract. Here are the objectives: Enter KeoStationary Orbit Around Kerbin with an ApA of 2886000m - DONE Enter KeoStationary Orbit Around Kerbin with an PeA of 2886000m - DONE Have line of sight of Heart Station with Frequencey 33.5 - DONE Send Data Stream and connect satellite to customers - I clicked Start Data linkup and it completed, but this task didn't become ticked Have part type Repair Panel - DONE Ensure the potato - What?

I tried merging with my previous version and removing then installing. Which option would you recommend? I'd download both zip files again and reinstall, tomorrow.

For clarity, I've had the previous version of EVE installed and running fine - well, as fine as I can expect with KSP being 32-bit and having quite a few mods installed. System Specs are: Windows 7 Premium 64-bit Intel Core i5 2500K 8.00GB Dual-Channel DDR3 2047MB NVIDIA GeForce GTX 770 The mods I have are: ActiveTextureManagement Bluedog Design Bureau Chatterer FASA Towers Kerbal Engineer Kerbal Joint Reinforcement KW Rocketry (with community fixes) MechJeb Scatterer Tantares + Tantares LV

I've just installed the rebooted version for 1.0.5 and the Space Centre is just a black screen; the HUD is there, but the rest is black -

Perhaps a stupid question, but are you running the Kerbal Space Agency save, or do you have another save that you could be using by mistake?

This might be a stupid question but: what do I do with the KWPatch.cfg file? Do I paste it into my KWRocketry folder in GameData, or do I update each part CFG file with the amendment in the KWPatch.cfg file?

Hey kaoz. To quote another reply, you'll need to edit the config file for the petal adapter. The location of this file might be different for you, but it should be something similar to C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\KWRocketry\Parts\Structural\KWPetalAdapter3m

So, I'm having a little problem with interstage adapters, engines and auto-shrouds; specifically the 5m-3.75m Adapter Interstage and the Wildcat-XR. I've summarised the problem in this album. I'm probably missing something really obvious, but I'm stuck!