PrivateFlip

ModuleEnginesFX is a class which inherits from ModuleEngines. This means ModuleEnginesFX expands on the functionality of ModuleEngines, but can still do the same stuff. When ModuleEnginesFX were introduced I didn't know this and wrote all these separate sections of code to interact with either ModuleEngines or ModuleEnginesFX. Later when I was also a little more familiar with C#, I noticed this. Since all of these separate block were unnecessary I corrected this everywhere in the mod, since ModuleEnginesFX can be treated as ModuleEngines so there was never a reason do duplicate all this code. To answer your question, the mod works equally with both ModuleEngines and ModuleEnginesFX. Don't know why your getting this error. Don't see your issue when using the rapier engine. Which multi mode engine are you using? Is this from a mod? Update: -compiled against 1.6.0 libraries

Update: -compiled against 1.5.1 libraries -added functionality to show the cost of the delivery when pressing "Check delivery" before making an actual delivery. This functionality was requested by a user. As I uploaded this unto spacedock I found out there is already a new version of KSP... Update update: -compiled against 1.6.0 libraries. version 025

The window in which you can configure the throttle controls does not allow you to enter keys besides the once which produce a character. I will check if there is some way to do so. In the main mod window there is a button "Deactivate module" this will deactivate the mod completely and return functionality back to regular operation. It is however possible the thrust limiter has been set by the mod to some other value then the regular 100%, for example zero. This might prevent engines from working after the mod is deactivated. The "All Normal" button can be pressed, before deactivating the module with "Deactivate module", which will set the engines to their default settings, to fix this latter issue. This shouldn't be needed when deactivating the mode like i described above. Some testing did not show similar issues. As far as I can tell this script would add the module "DifferentialThrust" which is indeed the module you should add. This module adds other modules to the engines when activated and removes them again when deactivated. When I click the blue TC-button in the cockpit the mod activates, clicking again deactivates it, just like it does outside of the craft, so I'm not able to reproduce the behaviour you report. If other mods hide their windows on F2 I gues I can't stay behind. Will look into this. In believe I understand what you would like to happen for point number 2. You would like to use this mod to configure a particular engine mix which would then be used proportionally by MechJeb. Besides the integration with MechJeb this would also change what these throttles mean in this particular scenario. Since the throttle settings act not like throttles but engine mix settings. What you want can however be relatively easily achieved by lowering the "Thrust Limiter" on the engines which should run a little slower in proportion to the other engines. This is part of the vanilla game. (This can be a little bit annoying if you have many engines which you have to set; this mod however supplies an extra option in the engine settings "Sync all <enginename>" which should sync all engines of the same type to the same settings, which also includes the thrust limiter setting.) My apologies for the late reply, I'm not very active. Great to hear you have been using this mod a lot!

You're welcome, glad to hear it is of use! ===================== General update: currently working on some new features. Have added functionality so kerbals which are scheduled for a mission, are actually reserved on the astronaut roster from the moment of Launch. Currently in testing. This will enable longer mission, to destinations outside Kerbin and its moons to be supported in a more realistic manner. Also just started working on some things to eventually make routine missions to and from the surface of other planets possible, but this is still in early phases of development.

Update revised version of routine mission manager -improved UI --in game manual --detailed information of tracked missions --ordering forms gives more info on the to be ordered mission and gives feedback on any not met requirements. --overview of all ordered missions -no longer nessecary to be away from a destination station for a mission to complete. (this comes at the cost of missions no longer completing when there is other traffic in the area of the destination) -support for missions which have reusable stages which return for kerbin for recovery. Example: a rocket with reusable boosters which parachute down to be recovered. Make sure each booster has a command part, like a probe core. Save the game before launch. Launch the rocket. Seperate the boosters when depleted and immediatly create another savegame. Fly the rocket on to it's destination. Jump back to the seperation savegame and switch vessel to one of the boosters. "Fly" the booster safely to the surface, repeat the same procedure for the other boosters. Jump back to the savegame before launch. Even though the rocket and boosters when tracked to their destination in different timelines the mod will combine the tracked information as if it was one mission. A new version of the mod is out. The mod has been greatly overhauled. I'll try to watch this thread more closely in the coming weeks for feedback and issues.

Hi Atis, To make these type of modifications to the mod I would really encourage you to take a look at the revised version of the mod I've been working on. Code has restructured and is a lot cleaner than the current version of the mod. See this post for download of this version. I've also pushed the last code changes to github and added a link to github in the opening post of this thread. With this version in hand solving the problems you have will be somewhat more straightforward. The current mod already has code to store vessels. Storing of a vessel happens in the tracking code within method TakeVesselSnapShot(). It currently does so outside of the save game in the 'vesselfile' of the mission. This is the file form which the vessel is loaded when the mission is repeated. So there is no need to delete the vessel in order to store it. In the new version I'm storing data for ordered missions in a scenario. Although it currently does not support it, this functionality could be expanded to also store a vessel as part of the order information. This way you can save the departing vessel before deleting it and then reload it to have it dock on the destination station. In the revised version the code for arriving and departing is moved to the ArrivalWorker and DepartureWorker classes. These classes currently are still specific for arrivals and departures which the current mod supports, but they could be changed to support other functionality as well. (You already mentioned you would have to make changes to dockingstage code. This is now all in the ArrivalWorker) In the DepartureWorker class you will also find the code which deals with removing kerbals and setting their status. For automated return missions to kerbin in which the vessel does not safely return, I set the crew status to Missing or Dead depending on the campaign setting on whether lost crew should go missing. When crew go missing the game has them return later. This functionality is however never used because the current mod probably prevents the player from automating a return mission which would lead to the dead of kerbals. For the functionality you are trying to add, I suspect you could keep the crew set to assigned. This way the crew will not be available for other mission while the vessel is supposed to be underway from station to station. The mod should register this in some way and have a way to return those kerbals to available in case the mission is canceled. This is necessary to make sure kerbals are not stuck on their assigned status in case the mission cannot be completed. This last functionality is next on my own wish list because it would allow me to make routine missions to other planets realistic. Currently kerbals are plucked from the roster just as the vessel arrives. For relatively short missions to kerbin and it's moons this isn't a very visible to the player, but it would be for year long missions. The revised version could relatively easily store such data in the aforementioned scenario. The revised mod also already has functionality to compare a docked structure to a stored structure. I suspect you would need this as well to check if a docking port currently holds a vessel which is identical to the one on the original mission. Hope the above makes some sense to you. Let me know if you have any questions. The mod is released under a BSD license, so you are completely free to create your own expanded version of this mod and release it yourself. Also, although there have been numerous questions for additional functionality, I haven't been able to spend a lot of time on adding new features to this mod, so if someone comes along and makes a new mod based on this one with added functionality I would encourage it. I want to be a little bit more cautious on whether I would be interested in adapting your changes in this mod. Surely, if the functionality you added is robust I would have no issues in adding it. However, based on my own experience in making the mod so far, there are a lot of little things you have to take care and deal with to make the functionality somewhat robust. This has always made creating and improving this mod a lot more arduous then what I expected on the start. I would be more than happy to link any code changes here, to allow other people to further update the mod.

The behaviour you describe is indeed what the mod would do if the crew you request are already assigned, so this is not a mod conflict. The code changes you propose would correct this behaviour. However this particular behaviour was intentional. It allowing the player to select astronauts which are currently not available but might be available when the mission starts. This crew is also identified as a preferred crew. When not available for the mission the manager selects any astronaut available to prevent the mission not completing because one astronaut did not report in on time. Currently started with testing of the new version of the mod for KSP 1.4.

Update -compiled for 1.4 -added support for engines which have a minimum thrust which was ignored as soon as this mod was enabled. -making these also some error in center of thrust calculations where found when the engine adjustment hovers around zero percent. This has been improved.

Hi HurrucanKai, how are things going? Is there a development thread where people can track your progress? When writing this post a got an automated warning I was necroing and old thread, this gives some indication how active I am on this forum. Update Compiled the mod for 1.4.

Thanks for the update!

The mod requires a part to be added to your vessel. This part is found under controls. This mod only works for the vanilla engine modules, not sure how fire spitter factor into this, which is what the A7 Aerosport Engine uses. Best is to test if the same happen for stock engines. Could well be I don't take this into account, will add this for the next release for the next KSP version, assuming it's feasible.

Thanks for the info: the save itself shouldn't effect the fix I made in 027, so I'm probably still missing something.

Released an update for revised version of the mod: see this post for dropbox link. -found and fixed where vessel give error when docking to complex station. -added ability to delete mission trackings. During testing I ended up with all these uncompleted trackings which cluttered up the overview screen. These can now be deleted. -times in tracking detail window now given in a more readable format. -under the hood how the arrival and departure logic is called was changed. Arrival and departure take far less time to complete and are expected to be more stable. -a few UI tweaks.

This issue has been reported a few months ago (post). Although I could not reproduce the issue, I believed I had fixed the way it could happen in version 027. Have you tried this version? It is the third update for the mod for KSP 1.3.0. If you're already using version 027 and this is still happening, I would love to know.