DeltaDizzy

Well the flyby is only to change the inclination, which is why I had wondered about it.

How well does TOT work for planning multistep transfers to very inclined bodies? (like Ulysses if it was rendezvousing with a comet)

The IVAs for it contain props provided by that. They are in a seperate mod because several of Nertea's mods reuse those props.

Finally some good-looking aluminum-powered death sticks!

To do that MKS needs to write the current/predicted power consumption (which one depends on whether you are in flight or the VAB) to a KSPField (that means some code additions are needed) and the rest can be in a config. Edit these values as needed. PARTMODULEHANDLER { // The name of the module name = <the module you want to add to the simulator> // The type of handler - can be Power or Heat type = Power // The name of the handler to use handlerModuleName = GenericFieldDataHandler // Is this shown in the UI at all? visible = true // Do we use solar distance attenuation? solarEfficiencyEffects = false // Is this module a producer by default? producer = false // Is this module a consumer by default? consumer = true // Does this item start off as active in the UI? Should canonically be true for constant sources/draws simulated = true // Does this item count as a continuous power source for the purpose of the UI? continuous = true HANDLER_CONFIG { // Field to poll in editor editorFieldName = <field to ask for power consumption> // Field to poll in flight flightFieldName = <field to ask for power consumption> // Multiply the output by these if you need to. Convention is that a consumer is negative. editorValueScalar = 1.0 flightValueScalar = 1.0 } }

Follow this tutorial, it seems to cover everything: https://www.youtube.com/watch?v=77W2JSL7-r8. When you get to the coning part, using the CollisionFX repo.

How to do which part?

It depends on the mod, but if you can find it, deleting it should work.

@VoidCosmos I couldn't help but notice that the GitHub repo consists of the License, Readme, and a single zip file. This goes against the point of Git, so I submitted a Pull Request to move the files out of the zip. (it also explains just why this is bad and recommends GitHub Desktop to make changing the state of the repo easier)

To disable EVE all you have to do is uninstall it.

It depends on how you want to deal with bug reports, but if you don't want to do it on this thread, activating the GitHub Issues section would help.

Vega is on the left, and Centaur is on the right.

It has been for a while, but it doesn't conflict.

It's free for those who have bought the game.

I have been assuming Mac/Linux support is planned post-release with the dev team focusing on getting all the content in and the game actually out first, but I'd like to make sure that it is eventually coming to those platforms. If it's already been announced then feel free to ignore me.

Back again, this time wondering about Kerbol contracts. In a typical career game, do you go to the Kerbol System? https://www.strawpoll.me/20137259

Normally I don't like bees, but I can see myself really liking this.

Hello everyone! I am currently working on adding some custom contracts to BH (for use with Contract Configurator of course) and was wondering if most people play with unmanned-first tech trees or kerbals-first (like the stock one). Here is the poll: https://www.strawpoll.me/19941401 The current Todo list can be found at https://github.com/Gameslinx/BeyondHomePlanetMod/issues/2 =========================================================================================== @Motokid600 Use Sigma Dimensions. A simple division problem will tell you the scale factor you need, and once you have that just modify Rescale to use it.

Something that I believe few have noticed is the similarity between the Dynetics lander and an older concept floated by General Dynamics...

I can't wait to see all the progress you're sitting on, just waiting to perfect and show us!

rock

I was playing my save with ExplorationPlus when some quirks of the planet pack im using halted my career due to the contract generator. The Brownish-orange planet is the homeworld, and after completing the initial contracts for the moons, NextUnreachedBody() tells me to flyby Destiny (the big/whitish star). This is an issue given how early in the career it happens (the closest you get to the stars before this is "escape kerbin"). I eventually managed to exclude those two stars, but then it gave me Kerbol, which in this pack is very very far away. (blue orbit in the next picture) I then installed ProgressionParser to get the progression list: [LOG 13:27:05.118] [ProgressionParser]: Body 0 is Armstrong [LOG 13:27:05.118] [ProgressionParser]: Body 1 is Lua [LOG 13:27:05.118] [ProgressionParser]: Body 2 is Ash [LOG 13:27:05.118] [ProgressionParser]: Body 3 is Sun [LOG 13:27:05.118] [ProgressionParser]: Body 4 is Destiny [LOG 13:27:05.118] [ProgressionParser]: Body 5 is Fate [LOG 13:27:05.118] [ProgressionParser]: Body 6 is Kerbol [LOG 13:27:05.119] [ProgressionParser]: Body 7 is Verna [LOG 13:27:05.119] [ProgressionParser]: Body 8 is Drohze [LOG 13:27:05.119] [ProgressionParser]: Body 9 is Dynasty [LOG 13:27:05.119] [ProgressionParser]: Body 10 is Janus [LOG 13:27:05.119] [ProgressionParser]: Body 11 is Lond [LOG 13:27:05.119] [ProgressionParser]: Body 12 is Eterna [LOG 13:27:05.119] [ProgressionParser]: Body 13 is Talon [LOG 13:27:05.119] [ProgressionParser]: Body 14 is Tau [LOG 13:27:05.119] [ProgressionParser]: Body 15 is Tribute [LOG 13:27:05.119] [ProgressionParser]: Body 16 is Hydrus [LOG 13:27:05.119] [ProgressionParser]: Body 17 is Hydron [LOG 13:27:05.119] [ProgressionParser]: Body 18 is Scaythe [LOG 13:27:05.119] [ProgressionParser]: Body 19 is Scindo [LOG 13:27:05.119] [ProgressionParser]: Body 20 is Gateway [LOG 13:27:05.119] [ProgressionParser]: Body 21 is Kohm [LOG 13:27:05.119] [ProgressionParser]: Body 22 is Eidos [LOG 13:27:05.119] [ProgressionParser]: Body 23 is Ansia [LOG 13:27:05.119] [ProgressionParser]: Body 24 is Proxim [LOG 13:27:05.119] [ProgressionParser]: Body 25 is Jade [LOG 13:27:05.119] [ProgressionParser]: Body 26 is Vasto [LOG 13:27:05.119] [ProgressionParser]: Body 27 is Voss [LOG 13:27:05.119] [ProgressionParser]: Body 28 is Fury [LOG 13:27:05.119] [ProgressionParser]: Body 29 is Anger [LOG 13:27:05.119] [ProgressionParser]: Body 30 is Rock It seems to do the moons of the homeworld and the two stars before leaving the solar system for the kerbol system. It does not return to the starting system until Body 16. Is there any way to reorder the list of unreached bodies so that I at least visit all the planets in the solar system before leaving it? if not, is there a way to generate a repeating contract for each body in a manually defined list?

Looks like Rutherford Vac