wasml

I believe these are other planets. I think (take with a grain of salt) KSP uses some tricks to make it appear there's a star out there but the illusion breaks down if there's a planet behind the star - it will appear in font and break the illusion. And you do see the planets as you should if they're between you and the star.

I had a very similar idea some time ago and made a list of the various things I wanted to track for each profession. Got as far as locating some of the variables I would need but it never went beyond that I afraid.

Community tech tree adds a bunch of nodes that mods can use but doesn't fill any of them - this is so mods don't step all over each other adding duplicate or very similar nodes but it does leave empty nodes. There's another mod Hide Empty Tech Tree Nodes that will remove the empty nodes - not sure if it works in 1.8.0 yet.

Did you add a thrust transform to your engine? I have a dim recollection of needing a FX transform for the plume too - though I think you can use the thrust transform for that if you want. I think the rationale for using a separate transform was that changes to the plume were easier to make without changing the thrust transform. I had put together a number of part "Reminders" with notes, Blender and Unity files for myself and anyone else that might find them useful here: Best of luck with your parts

@P Express Space & Sky Dept I believe biohazard15 is referring to the robotic parts (F-12 servo) in the Breaking Ground DLC.

Tried the new 2.4.3.7 and it looks good. As Gregory Kerman said "Everybody borks" (been there, done that (more time than I like to admit)) And again thank you for maintaining and improving this mod.

@linuxgurugamer using this r4mon's curve editor - click on the "Click to edit ->" in the upper let corner and the graph appears. Left click on a key in the graph and two handles appear that you can manipulate. Right click on the key and you have a popup menu to change how the handles act among other things. Looks like it defaults to a smooth transition but select "Broken" (with right click) and the handles on either side move independently.

Per Azic Minar's note I scanned the GameData directory and InterstellarFuelSwitch has a GameData\InterstellarFuelSwitch\Plugins\Scale_Redist.dll. Here's a link to the log file and the zip I installed TweakScale from. Thanks

I'm guessing here but I would look into making assets like the scanable items Breaking Ground added - I haven't seen anyone doing anything like that - though GregroxMun has had scatterers on some of his planets (probably requires Kopernicus). You'd need to figure if you could create single instances like the monoliths. Like a flight recorder? That would be neat.

The only (simple) way I see would be to include the VARIANT section. The part under "GAMEOBJECTS" tells the game which model to display - in your cfg example the 45 = true says that the model named "45" should be visible when that variant is selected. A non-simple way would involve loading the .mu file into a 3D model editor and pulling apart the different models and reexporting/running through Unity and creating individual parts.

First thanks for maintaining this mod - sorry about all the headaches you've inherited I'm getting an error message with the 2.4.3.7 release and think it may be in error (but it's early here - not a morning person). I've double and triple checked but don't see a problem with my install. I installed the latest 2.4.3.7 and got the "Houston..." message about Tweakscale installed in the wrong place. It said I had installed TweakScale in GameData\TweakScale\Plugins and should have put it in GameData\TweakScale but the plug in directory is where the dll's are located in the distribution zip (Manual install - drag and drop TweakScale-2.4.3.7.zip\GameData\TweakScale into my GameData folder) and where (I believe) they should be. This is the directory structure: KSP GameData ModuleManager.4.0.3.dll (Installed latest MM rather than TweakScale included one - shouldn't have anything to do with TS installed in the wrong spot) TweakScale patches ...Lots of cfg's... Plugins KSPe.Light.TweakScale.dll Scale.dll Scale_Resdist.dll Am I missing something? Thanks

I've always liked the make your own custom menus - I've made ones containing just the info I want for building, launching, landing, intercept/docking.

I've collected information on various parts as I've attempted to make them and I put them into a package that will hopefully remind me how to make the part when I try to do it a second time. They are start to finish (includes Blender, Gimp, Unity files plus notes) but may leave out details I thought I would remember. Models and textures are very rough - these are just reminders - and my modeling and texturing skills are a work in progress. After starting this it occurred to me they might be of help to others so I made a post for them here:

The scan arms have a ModuleRobotArmScanner and a ModuleScienceExperiment - the ModuleRobotArmScanner being the one unique to the DLC. Edit: Just removed the stock ModuleScienceExperiment from an arm so ModuleRobotArmScanner was the only module - problem remain.

Made a new install and added the Breaking Ground DCL and Vessel Mover. Made a vessel consisting of a large probe core, a fuel tank and a OP-E Large scanning arm. Launched and picked up with Vessel Mover. Vessel continued to rise until I hit escape. No errors in the log between launch and return.

You might try looking in ModuleManager.ConfigCache - should be in the same directory as the MM dll - this contains the patched cfg files so you should be able to see what KSP is using for the TechRequired field.

As this is just a part (no code/dll behind it) it shouldn't be particular about the Unity version - though I'm not sure how parttools would respond if installed on a version of Unity it wasn't meant for. If you have a bit of time I'd like to try and figure out why its not working - if it's something with what I've done that only works on some systems or if an addition to the instructions might be in order. If your willing could you explain what's not working - what you were doing and what made you realize it wasn't working. Example: when you dropped the blender dae file in the Unity assets folder did the part icon show up properly or did it show up as a blue box?

So you got it working? If you do find a mistake in any of those parts please let me know so I can fix it and not mislead/confuse anyone else.

Stack nodes can be done in multiple ways. You can add in your modeling software before exporting to Unity, you can add in Unity or you can add in the config. The config method uses the "node_stack_top =" in the config while the Unity and before method uses the NODE {} method. As far as the collider is concerned you don't need a material on it and in fact you'll want to remove the mesh nodes after you add the collider in Unity, otherwise the collider will show up in game. But don't remove the collider mesh before adding the Unity collider - Unity uses the mesh to create the collider (in the add mesh collider case).

I haven't looked this over closely but it may be what your looking for: Last part of the OP talks about creating a plume. Edit: One note - the plume in Unity often (always?) looks quite different than it does in game

@Mittence I haven't made many planets (actually only one and it stopped working for unknown reasons) so I can't help you there but I do know that some of the parameters in cfg files can be very picky - sometimes capitalization is important, sometimes not. I would suggest you us in the same directory structure White Guardian had (from GameData on down) just to eliminate one of the differences.If that doesn't work you might try posting on one of White Guardians tutorial threads - there will be more modders that know about making planets hanging around those threads.

If the example part was from the template parts - they were working on my system when I uploaded them - what errors/indications did you get?

The interesting thing about making plugins for KSP is that there is very little official documentation. Fortunately there is a requirement that addon's have source code available so your best bet would be to look at some of the mods that do something similar. Two IVA interfaces that I know of are: The KSP API is listed here though mostly uncommented This project (a hardware interface) may be of some help too: Good luck with this!

@gamerscircle A minimally tested patch: @PART[*]:HAS[@RESOURCE[LiquidFuel]&!MODULE[ModuleFuelJettison]] { MODULE { name = ModuleFuelJettison } } should add the module to any LF containing tank that doesn't already have the jettison module (doesn't touch Xeon or mono prop tanks).

Nice models - look forward to seeing where this goes. I notice you add the resources Deuterium and Tritium - be aware these collide with the same def's from CommunityResourcePack - not sure what will happen but would guess one or the other would get overwritten and you may find the balance way off if both are installed (CRP has significantly different values).