gruneisen

For what its worth, if you already have an EXCEL spreadsheet set up for these calcs, there is a very powerful iterative solver built in. You have to enable the SOLVER add-in into EXCEL, and then once that's done, head over to the DATA tab and hit the SOLVER button. This will allow to achieve a target value in a single cell by changing multiple cells and also use constraints to bound the values of other cells. If this applies, you may not need to do too much re-inventing! Cheers!

Ha - I've certainly been accused of worse, so I'll take it! I'm glad you were able to get it to work - cheers!

Hmmm - that's too bad. Like I said, I always able to get it to work eventually...though perhaps when @Arrowstar checks back in he can take a look at your issue.

I've had this problem several times myself. I don't know what makes it finally work, but usually I just try it several times and eventually it will take. Additionally, I've gotten it to work after uploading a maneuver node or reading a spacecraft state in MA prior to scanning for bodies. I hope this helps - let us know if it does! Cheers!

You're the best - thank you!

Hey @Arrowstar - Did you ever release this fix in a Pre-Release? Did I just miss it? Thanks!

Unfortunately I don't think I can be of any help - I tried to use WINE to run KSPTOT some time ago and got a whole lot of nowhere - you can search through this thread for my name and see some of the hilarity I encountered.. Continued playing around with it actually ended up killing my Ubuntu build and pushed me back to using Windows for KSP, which, unfortunately, is what I'd recommend you do if you can - especially now that we have stable 64-bit on Windows. Sorry!

PATH in this case is an environment variable which directs Linux where to look for a binary. In BASH, you can type 'env' into the command line and it it will report all of the environment variables you have set, one of which will be PATH. The value of the PATH will be to a bunch of directories...for example this is my PATH: PATH=/usr/lib64/qt-3.3/bin:/home/kevinmueller/perl5/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/local/apps/Rocketeer/bin:/home/kevinmueller/.local/bin:/home/kevinmueller What the OP directions are telling you to do is verify that the cabextract binaries are in one of these directories - if you use yum or apt-get to install cabextract, then it should reside in a location defined in your PATH. If you do it manually and place it in some other directory (for instance /path/to/your/cabextract/bin, then you either want to put it in one of these directories or add it to you PATH variable. Again, in BASH, the syntax would be: export PATH=${PATH}:/path/to/your/cabextract/bin And it would probably be a good idea to add that line to your ~/.bashrc file so that directory is always included in your PATH. If you are using CSHELL, then the syntax will be different but the ideas are exactly the same. However, with all of this being said, if you use yum or apt-get to install cabextract, then you shouldn't have to worry about it at all. It is always a good idea to check, however. I hope this helps and let me know if you have any other questions. Cheers!

Hey @Arrowstar! This might be a little frivolous, but I was thinking it would nice for the Multi-Flyby Maneuver Sequencer to have a GUI element that tracks each of the 'Best' and 'Mean' score of each run and plots them as a function of run number. I don't know how difficult it would be, but also being able to go back, select a previous run from the batch and propagate the orbital maneuvers for inspection. This is motivated for me in part that sometimes I wonder what the final score a run converged to or, if what appeared to be a good run didn't get selected as the current best, I could go back and understand why. Like I said - I don't think this is something that may be all that helpful, but I thought it might be interesting for me. Thanks as always for your hard work! Cheers!

Nailed it - sorry for the bonehead move and thanks for the help!

I am using the pre-release 5 from yesterday, but I think I forgot to select the gravitational parameter! I'll have to verify tonight, but I'm 99% certain that is the case. I was trying to explore an issue whereupon trying to use KSP TOT in my RSS career that is in year 11, I was getting strange results and had hoped that perhaps the correction made in pre-release 5 would address it. It didn't seem to do anything, so I started a fresh career to test how things behave at year 1 that's made drove me to post last night. But, I most likely did not switch the grav parameter. If this is the case - would there be a way to have KSP TOT, upon reading in a bodies.ini that contains a planet named, say Earth, that it either automatically selects the correct gravitational parameter or prompts the user and asks them is they'd like to apply the RSS parameter? Thanks for getting back to me! Cheers!

Hey @Arrowstar - I've been trying to work with the pre-release you and @Stract worked together on for RSS compatibility (thank you, by the way, for all of the hard work!). I haven't been able to reproduce the success you had with the screenshots you posted a while ago - I'm still not getting the correct rendezvous with KSP TOT. I am using RSS v12.0 and thanks again for all your help and hard work!

I do believe the the demigod @NathanKell has been a bit back into this business over the last week or so. Perhaps he may be able to help answer some of these questions?

Hey @Arrowstar - I can't wait to try this out tonight! Thank you so much for working this!

I agree that TOT is far more precise, but I use MechJeb do to interplanetary transfers that are years out using its porkchop plotter and nail the transfers with no problem whereas for a simple Earth - Moon transfer, in KSP TOT I can load a current vessel into Mission Architect, find a transfer from the earth to the moon, upload the maneuver and it have it be off by as much as 180°. Do a Hohman transfer in MechJeb and bam, spot on. A lot of people have said it before and I'm going to say it again - all signs point to the KSP TOT thinking the bodies in RSS are in a different place then where they are - it is completely inaccurate with RSS over any timescale.