Mr_Breeze

Thanks!

Do you have any plans to make your antennae remote tech compatible?

Okay. I just wanted to know if it was intended or not. Thanks.

I had tried right and left clicking and sliding the slider with my mouse sensitivity turned way down. It jumped from .125 to 16 no matter what I did.

I can use zip tools.. I am just lazy lol.

AVC is saying there is a new version, but nothing on CKAN. Is CKAN up to date?

I have version 3.2 and the wings go from .125 to 16 length nothing in between. Is this intended? I have been using B9 procedural wings for awhile, just grabbed your fork to check it out. Is there a way you can have all of the sizes in the original fork, or rename the parts so they can be used along side the originals?

Since you can't reproduce it, you're probably right.. how should I send my craft file and mod list?

Yeah, reinstalled both, then reinstalled all of my mods.. no luck. I don't really care if my atomic engines have reactors, I don't. It just worries me that something else may be broken that isn't so obvious. I think I may have found an issue that is actually caused by Mk2X. Have you ever tried front facing spade tails? It breaks physics on the runway. As soon as the wheels hit the ground, the front gear lifts off of the ground. The plane then slowly increases pitch until around 90 degrees. Then it starts levitating into the sky. Engines will not propel the craft forward, even though the are generating thrust. The only thing that appears to have any control over the vessel is SAS. Reverting to the VAB and removing the spade tails returns everything to normal. I made it to 100m in the time it took to write this post.

Okay, it worked thanks.

All of my atomic engines (Stock/Near F/USI) except Mk2 expansion no longer have reactors. They were there on 5-2-16 around 8pm EST. Did you update something since then that might have broken them, or did I do it installing/uninstalling another mod via ckan? I have tried uninstalling and reinstalling NFE & KA, but that didn't solve the issue. Should I go ahead and reinstall all of my mods, or do you have a better suggestion? I have PMed you my mod list, in case it will be any help. BTW Thanks for all of your work. I Use all of your Near Future mods, and I am looking forward to MkIV being ported to 1.1.2!

I can't really tell at this point. It appears I have broken something.. The only atomic engine with a reactor in it now, oddly, is yours.. Let me figure out what happened there, and get back with you. Edit: Still haven't figured out what happened to my reactors.. but Nertea responded to your question, and his answer agrees with yours. I apologize for wasting your time. Having you chasing my problem, which was caused by my not being fully aware of the functions of the mods I have installed.

Any clue why ckan says Pilot Assistant's max compatible version is 1.1.2 and KSP add on vers checker says it's 1.1?

Didn't know they had to be activated via staging, this was not true for the NF or USI engines. They worked fine through action menu activation. I will test this right away, and see if this solves the problem. B9 part switcher has node switching. I could not find anything about IFS supporting node switching. Thanks for the tail boom config! I thought MFT was incompatible with IFS, so I haven't tried installed it on this play through. I have used it in the past though. I will d/l and try it out. Thanks again for the support! Edit: Activation through staging was the issue.. I just want to reiterate that other atomic engines do not have this issue with NFE, and add that other users are likely to run into the same issue. If you don't intend to find a solution, I suggest you add it to the OP in a FAQ.

Just tried it again. I don't know if the reactor is spooling up or not, I can't tell. Still no thrust after more than 15mins of waiting. I threw some nervs on my ssto to test if they had the same issue.. They produce thrust and do not have reactors on them. Another thing that seems off that may be related is that the info for the reactor in the context menu is all blank. This doesn't happen on the near future electric reactors or the USI reactors by rover dude. It seems specific to your reactors, so this is likely going to point us to the cause of the problem. Can you install NFE, if you don't have it, and test it yourself please? Should I post on nertia's thread for support? Edit: While I am posting here, I might as well make some suggestions that come to mind every time I use your parts. Can you please add attachment nodes to the interior of the service bay, so that it is like a 1/4 size cargo bay? I like the size of it for a battery bank, but like to have more options than the included batteries. Can you add fuel and fuel switcher options to the mk2 tail connector like the spade tail has? Can you add fuel switcher options to the stock mk2 liquid fuel tanks like the rocket fuel tanks have but also include the options the service tank has like mono and xenon? The textures on the mono and service tanks bug the crap out of me (yellow lines). I feel like the stick out like a sore thumb on my crafts lol. I guess I am being too much of a perfectionist, because even the rocket fuel tanks black lines make me wince some times. I get the impression adding fuel switcher options isn't very hard. I will probably do it myself, but I hate to have to redo it every time you update. Maybe if I get around to it before you do, you can over look my work and include it in the next update. Also while I am posting here, I might as well say thank you for all of your hard work! I really enjoy your mod! Sincerely, Thank you for sharing your work and supporting it.

You're probably right. I remember turning the reactor on at one point. I think I kept it off to cut down on heat generation, I didn't know it was needed to run the engine. I don't have a lot of experience with Nuclear. I guess I need to devote some time to learning the inns and outs. I expected the pluto to have surface attach enabled since it is in the mk2 housing, and your other engines have it enabled. I am going to edit the .cfg. Thanks for the tip. I want to put radiators directly on the engine housing.

I cannot generate any thrust with the "Pluto" on the runway or in VAC. I am using liquid hydrogen in a mk2 rocket fuel tank via interstellar fuel switch. The engine fires up and there is a plume, but thrust stays at zero. I am using kerbal atomics. Is that the problem? I also cannot surface attach anything to the "Pluto", including radiators . Any help would be appreciated! Thanks!

Awesome. Will update via ckan tomorrow (10hrs or so), to test. Was the Mk2 crew cabin the only one that needed the fix, or did you not have time to check the other crew cabins?

Yes, that is the impression I am getting. Add vesseltype=ship to all crewed parts for a fix. There may be more appropriate tags that work as well though. The discussion is on both page 21 and 22. This is a link directly to the quoted text. Edit: It should be easy enough to test. Add the tag, accept a relevant contract, and then throw the cabin in the relevant location/orbit with hyper edit.

An image album of these parts would be awesome.. A picture is worth a thousand words. Curiosity is going to get the best of me, and I am going to d/l it anyway.. Thanks for your effort and hard work in forking this.

Okay, I'll get right on it. I don't understand how the Mk2 parts are legacy, when the Mk2 b series doesn't have fuel tanks or crew cabins.. it seems the Mk2 series is more complete, and I wouldn't call the older series legacy until the new series is complete. Maybe I overlooked something though. I just like the look of the Mk2 and the B9 procedural wings ( over the procedural wings mod, who wants all of their wings to use one texture and look identical?!?!). I will report back when my research is complete. Please let me know if it is not something you will not have time for, since it was legacy. If needed I may update them myself for personal use, or share them with the team if you'd like. I would hope to get credit as a contributor though Here is what I was referring to. Pages 21 and 22. There is likely also some discussion on this subject around other places. I wouldn't know where to look though, not being a KSP modder. Quotes from that discussion. "I just had that annoying thing happen again with the Kerbals getting no experience. In this case, I took four tourists out to look at the sun in the 2.5m observation dome, but they apparently didn't like the flight because they received no experience and I didn't get paid for the contract. Have we figured out how to fix this yet?" "OK, I just confirmed that if I added that vesselType=Ship line to the observation dome, it now works to accrue experience and tourist contracts. I also noticed that the vesselType for the stock Squad cupola is Lander. I have no idea why it would be Lander, but it is. Does anybody know what the vesselType parameter is for (other than to trigger that Kerbals inside it gain experience)?"

I would like to thank the B9 team for all of their hard work. I also would like to report a bug. I spent a lot of time building a nice Mk2 (the B9 Mk2 with the black bottom) shuttle to ferry tourists into space. When I circularized my orbit, I looked for the notification that I had completed the mission, and received my funds.. surprisingly there was no such notification. I checked my active contracts to make sure it was still active, and that I had indeed completed the requirements, all good there. I checked the crew lists and made sure the tourists were on-board, all good there.. for some reason the four kerbals in my B9 Mk2 crew tank did not want to pay for services rendered. I was reading another mod thread yesterday, and someone was talking about parts (cabins, pods, so on) that did not allow these types of missions to be completed among other problems. If I understand correctly, the part has to be labeled a certain way in the files in order for them to function properly. I don't remember the exact label, and I assume the B9 team is probably familiar with this and can fix it. If I am wrong, let me know and I can do the leg work and search for the discussion I am referencing. Thanks for your time Update, I completed the mission by swapping the stock cabin into the same craft, just to support the idea that it is the B9 cabin causing the problem. I hope it gets fixed, I really like the Mk2 parts, and the stock cabin doesn't fit it well at all.

I can't install the latest update via ckan. It says there is a conflict with Kopernicus Tech http://forum.kerbalspaceprogram.com/threads/109122 I don't recall installing KT, so I am assuming it was installed as a dependency. I did not recieve this error, and had both installed prior to your newest release. Here are the ckan error details See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** The following inconsistencies were found: KopernicusTech conflicts with OuterPlanetsMod. at CKAN.SanityChecker.EnforceConsistency(IEnumerable`1 modules, IEnumerable`1 dlls) at CKAN.RelationshipResolver..ctor(ICollection`1 modules, RelationshipResolverOptions options, Registry registry, KSPVersion kspversion) at CKAN.ModuleInstaller.Upgrade(IEnumerable`1 identifiers, NetAsyncDownloader netAsyncDownloader) at CKAN.Main.InstallMods(Object sender, DoWorkEventArgs e) at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18063 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- ckan Assembly Version: 0.0.0.0 Win32 Version: 0.0.0.0 CodeBase: file:///C:/Users/Thor/Desktop/ckan.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18047 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18021 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18044 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Microsoft.GeneratedCode Assembly Version: 1.0.0.0 Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Microsoft.CSharp Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll ---------------------------------------- System.Numerics Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll ---------------------------------------- System.Dynamic Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll ---------------------------------------- Anonymously Hosted DynamicMethods Assembly Assembly Version: 0.0.0.0 Win32 Version: 4.0.30319.18063 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll ---------------------------------------- System.Transactions Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll ---------------------------------------- System.ComponentModel.DataAnnotations Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.ComponentModel.DataAnnotations/v4.0_4.0.0.0__31bf3856ad364e35/System.ComponentModel.DataAnnotations.dll ---------------------------------------- System.Runtime.Serialization Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18055 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll ---------------------------------------- System.Xml.Linq Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll ---------------------------------------- System.Data Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.18047 built by: FX45RTMGDR CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll ---------------------------------------- Accessibility Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- System.EnterpriseServices Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.17929 built by: FX45RTMREL CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Awesome, Thanks! Update: I have updated the previous version (from the original author) to the new one (by you) via ckan. Everything is working as expected!

Bah, no, I did not return them. They were attached to scanning sats. However, my point remains valid. Vague mission parameters are a pain.