GaryCourt

Done.

I removed it as I wasn't certain that atmospheric thrust was being calculated properly since KSP v1.0 changed how thrust is calculated. I'm hoping someone can get me the new equations.

Tool has been updated for v1.0! Also, according to the KSP v1.0 changelog, thrust is now calculated differently. If anyone could provide me the new equations, that would be awesome. Thanks!

Interesting idea... I'll play around with this. You could just run a simulation with one stage and X dV. Then open a new tab and run again for the launcher. Different fuel types would require a complete rewrite - something I don't have the time for at the moment. I had thought about doing that, but didn't want to have that one guy who's like "your suggestions are too small/big and X would be better" or "I can't get to X with with this tool; it must be broken". This too would be nice to have. The tool would only be able to do a best guess as to the size of the rocket, as the payload size is undefined. Already on the TODO list. Most part configs are badly written or just plain wrong, and a lot of hand editing is required to get the part list as it is already. But yes, something I would like to have as well. Might actually be a good idea. I'll add it to the list. Modern browser's JS engines are pretty fast these days (as close as half the speed as native). I think the convenience of an online tool outweighs speed, but feel free to create your own. I'll even consider linking to it from the first post.

By popular request: Just added a new option to force the last stage to have an engine that can be throttled (on by default).

It's just for making my life easier in maintaining the app. A lot of parts have inaccurate or missing data, so some hand editing of the results is still required.

Just added a new option to the calculator which allows you to force each stage to have a gimbaling engine (on by default).

The calculator makes no guarantee that the optimal configuration is buildable or flyable. That's an exercise left to the user. Yes. This would be ideal. But like you said, it's much easier just to include the most common mods. Now this is actually a really good suggestion. I'll add it to the list of things todo.

The calculator has been updated to include the new parts and costs in KW Rocketry 2.6c. In addition, I have written a small program for auto-generating the list of parts based on the config files in a mod. This greatly simplifies the process of adding new and maintaining existing parts from part packs.

The calculator has been updated for the new part costs in KSP 0.24.2. Thanks to pee8379 for going over all the parts! Please note that the O-10 MonoPropellant Engine is not included as the calculator only works with Liquid Fuel/Oxygen tanks.

Yes, I will be updating the app for 0.24 (hopefully) in a week or two. I'm away on vacation at the moment, but will get to it when im back. Looking forward to trying the new release.

Just updated the tool with the new parts in KSP 0.23.5. Please note that the LFB KR-1x2 is not enabled until I've had a chance to refactor the code to support liquid fuel engines with attached fuel. I'm still in disbelief that they shipped a part like this, as it goes against the whole modularity theme of KSP. But, who am I to judge. >:/

At that weight, the solution would involve just too many parts. The program limits itself to 8-16 tanks and 4 engines per stack per stage. You're going to have to break that bad boy into smaller pieces.

In my mind, that's a bug in KSP. But yea, I'll fix that. The LV-T30 doesn't have thrust vectoring, so you can't control your angle with it like some of the other engines. You need another control mechanism such as winglets or SAS.

Man, that's embarrassing. I've had it wrong all this time.

The one thing this tool does not do is ensure the design is structurally sound. That is an exercise left up to the user (since, as you mentioned, there are multiple ways of building it). Since FL-T800's are the same mass and fuel as the X200-8, you could swap them out for more stability. Turning off the "tank size must be the same as the engine size" (last option) would likely have done that for you. That is a good idea, I'll add it to the list.

If you'd like to make a donation to the project, I could get that done right away.</shamelessplug> You can set the number of stacks to 1 to prevent radial stack from being created.

Just pushed out another big update: * Added engine clustering to search. * Added min/max burn time restriction. * Added maximum mass restriction. * Added maximum part count restriction. * Added branch parts from Stock. * Added KSPX 0.2.5 pack. * Added KW Rocketry 2.5.6 pack. * Now outputs just the parts in a stack, with a separate multiplier on how many stacks are required. * Fixed bug with decoupler size matching. * Now displays payload fraction. * Changed max symmetry to maximum number of stacks. Enjoy!

That's a good idea. I'll add it to the list.

In stage 1, they would all be attached to your payload. In stage 2, each stack would be attached to a stack in stage 1. All 7 stacks would drop at the same time.

I'm not quite sure how this could be implemented without making the interface too complicated. In the mean time, you can open the app into multiple tabs and transfer the data (mass) manually.

Yea, the tool currently doesn't support clustering. Something to add to the todo list. It's likely trying to maintain the TWR in this case. I imagine that had you given the program enough time, it would have eventually weeded this one out for a design with one less stage. Well, you do use most of your fuel in the first few seconds of flight. However, it's likely a TWR thing. Thanks! Happy rocketing!

Just pushed out a big update to KORC tonight: * Added Part Count optimization, with a secondary optimization criteria. * Added field for changing the maximum amount of symmetry allowed per stack. * Added option for forcing the last stage to be a single stack. * Added option for forcing all tanks & stack decouplers in a stage to be the same size. * Added option for forcing all tanks & stack decouplers in a stage to be the same size as the engines (except radial engines). * Added additional summary fields to the header of search results. * Small visual change to search results. * Added part sizes to Stock parts data. * Fixed symmetry issues with multiple stages of radial parts. Makes rockets much easier to build. Enjoy!

I've changed it so that the valid and invalid counts are now separate. No worries.

That's already on the roadmap (in the first post). Actually, it's an intended feature. For a particularly hard problem (such as Eve), a lot of the "solutions" don't work or fail to meet your specified restrictions, even though it was generated as "the best I could do". When I had it such that the number only updated when it found a valid solution, it looked like the app had frozen. So instead, it now increments the number (to show that it's doing work), even if it's not finding valid solutions.