Jump to content

Arrowstar

Members
 View Profile  See their activity

  • Posts

    2,557

  • Joined

  • Last visited

 Content Type 

Everything posted by Arrowstar

  1. Arrowstar
    Hey everyone, just a heads up. In the forum crisis of the past two weeks I released KSPTOT v1.6.10! However, because the forums were down, and because I'm not really trusting them to stay up in the future, I've decided to move hosting of KSPTOT to SpaceDock. You can grab it here: https://spacedock.info/mod/3737/KSP Trajectory Optimization Tool The Google Drive links I had before will still work, but they only contain the v1.6.9 release I'm not planning on updating them. I'll continue to post change log and similar type stuff here for releases and especially pre-releases. In the mean time, go check out the v1.6.10 release. It's really quite a jump forward. I hope you enjoy it! Happy orbiting!
  2. Arrowstar
    Glad to see the forums are back!
  3. Arrowstar
    Unfortunately no, anything that involves changing sphere of influence must be done in Launch Vehicle Designer (or MA).
  4. Arrowstar
    Hi all, After a bit of a hiatus I've built KSPTOT v1.6.10 pre-release 8. Here's the change log! LVD: Plotting ground track with contour should be slightly faster now. LVD: Removed the camera pos/tgt/va text on the status bar. LVD: Fixed bug with the sun vector and general lighting position in 3D view frame. LVD: Added new surface textures for Earth, Jupiter, Moon, Neptune, Saturn, and Uranus. LVD: Added explanatory notes about the body x and z axis definitions in the bodies.ini file. New jupiter texture, higher res LVD: Fix bug with skybox disabling grid lines after enable/disable skybox. LVD: Provided ability for ground track display to be disabled. LVD: Performance improvements LVD: Added open loop kerbin launch example LVD: Added utility for finding best integrator for each event. LVD: Added more output to findBestIntegrator function. NOMAD optimizer now works better with consoleOptimize(). LVD: Removed warning about force models not being active if only gravity is active if nonspeherical gravity is on with the central body. LVD: Fix for planets with tilted axis not viewing correctly. Please let me know if you find any bugs. Happy orbiting! Hey there! Sorry for the long delay in getting back to you. In the porkchop tool, positions are always computed by solving Lambert's problem. This is the only technically feasible way to design a tool like that, so I'm afraid it can't be changed. Numerically propagating the orbit and altering initial velocity to hit the target point would take forever if you had to do it with an optimizer thousands of times to fill in the porkchop grid. Sorry!
  5. Arrowstar
    You can just open up the relevant bodies.ini file (so for you, the one related to RSS) and change the orbit parameters to match whatever it is need them to be. There's also a way to generate a bodies.ini file if you have KSP running and have the KSPTOT Connect plugin installed. From the main UI, you just go File -> Create New Bodies File From KSP. If you do this, you won't need to modify the bodies.ini file directly.
  6. Arrowstar
    That's due to the way RSS models Earth tilt in KSP. You can update the parameters in the configuration files as needed though!
  7. Arrowstar
    The easiest way to do what you want is to just open up the Porkchop plot generator and paste the UT time into the Earliest Departure Time box. It'll show the Year, Day, etc immediately below that box when you do.
  8. Arrowstar
    Usually if you right click a time related text box, you'll see an option menu that has an option for converting a KSP date to universal time. If you don't see anything, can you share which text box it is that you're looking at? Yes, it absolutely can. You would use Launch Vehicle Designer (LVD) for this work. Please let me know if you have any questions, and sorry for the delay in getting back to you, it's been a busy few months.
  9. Arrowstar
    I've recreated the bug and I believe I've got it figured out. I reuploaded the PR7 ZIP file. Please go ahead and redownload that and let me know if you have any issues going forward. Thanks!
  10. Arrowstar
    Today I've built KSPTOT v1.6.10 pre-release 7. This pre-release adds a bunch of new functionality and includes some bug fixes and minor performance improvements, all of which are in LVD. Here's the change log: Noticeable performance improvement when using numerically propagated celestial bodies. LVD: Added new ground track tab to main LVD UI's display area. LVD: Added sky box code for more "cinematic" display of 3D trajectories. Set option to enable in View Settings. LVD: Added additional camera controls functionality (Dolly horizontally/vertically camera). LVD: New steering model: tabular quaternion interpolation. LVD: New throttle model: tabular throttle interpolation. LVD: Update version of IPOPT optimizer to v1.1.6. LVD: Add new SQP optimizer algorithm. LVD: Bug fixes and performance improvements. Please let me know if you find any bugs. Thanks! Happy orbiting!
  11. Arrowstar
    No, this is a new one certainly. Can't say I've seen this before. I'm going to push a PR7 out pretty soon (maybe even tomorrow), so can you let me know if the issue persists with the new build? If it does, I'll investigate further. Thanks!
  12. Arrowstar
    Ah, I didn't realize you were using Principia. In that case, yes, you can turn on the n-body calculations for the celestial bodies as you had it. Just realize that it's going to be very slow. Sorry about that.
  13. Arrowstar
    Correct, that should work just fine!
  14. Arrowstar
    Ah, no, sorry, I think I see the confusion. Numerically propagating the orbits of the celestial bodies is NOT the same as using n-body gravity on your spacecraft. To enable n-body gravity, you need to do the following: In your initial state, set the bodies you want to use for 3rd body gravity. For each event, set the Force Model to use 3rd body gravity. That should be all you need!
  15. Arrowstar
    Honestly, just leave the numerical propagation to two body for everything. Your simulations will run much faster. You typically want to scale your objective function so that the value is between -1 and 1. Since final vehicle mass is the objective function, and the final vehicle mass is around 4, a scale factor of 10 is appropriate since it'll make it 0.4, which is between -1 and 1.
  16. Arrowstar
    You had a couple of issues that I was able to resolve: 1) You had numerical propagation turned on for all your celestial bodies. That's much slower than the two-body analytic solutions and was causing the propagator to take forever. I had to change things back to analytic two body propagation. 2) I scaled the constraints by their current value (Optimization menu -> Scale Constraints -> Current Value). 3) I scaled the objective function by 10. Once I did all of these, the optimizer brought the solution in easier and quickly. Here's the file. Please let me know if you have any questions with anything I did! Happy orbiting! https://drive.google.com/file/d/1t9DxXgP46S7R3gHbPCPeSpExvdcHQHFy/view?usp=sharing
  17. Arrowstar
    I have access but when I try to load your MAT file I'm told that it's not a binary MAT file. Can you try again? EDIT: Nevermind, seems like it works now.
  18. Arrowstar
    It can, but I'd still highly recommend using LVD. Did you try scaling the constraints as the text box message that pops up describes? Can you share your MFMS output with me so I can take a look at it and see what's going on? In other news, work on the new optional sky box functionality for LVD is progressing nicely. No more grey axes boxes if you don't want them!
  19. Arrowstar
    I've been working on a new display for Launch Vehicle Designer (LVD). This is a new ground track display that can show the following on a 2D map of a celestial body. This display is located on a new tab in the Display area of the main LVD GUI. Vehicle trajectory Ground object location and trajectory Celestial body location and trajectory Terminator line between lit and shadow (day and night) portions of the celestial body Terrain contours (may be turned off and off in View Settings) Here's a great image of Duna that illustrates these new functionalities. You'll also notice that the tool tips on this display are much richer and show more useful data. This is true for the 3D orbit display as well! This will show up in the next v1.6.10 pre-release. Let me know what you think! Happy orbiting.
  20. Arrowstar
    Hi everyone, I'm happy to announce that after a fairly lengthy hiatus, I've built KSPTOT v1.6.10 pre-release 6. This new build moves KSPTOT to a new MATLAB version, MATLAB R2023b. You will need to download and install the MATLAB Compiler Runtime version for R2023b to run this build. Please do so before attempting to run KSPTOT v1.6.10 PR6. Here's the change log: New MATLAB Version: R2023b LVD: Update NOMAD solver to v4.4 and removed v4.3.1. LVD: Enabled DiscoMADS option for NOMAD solver. MA/LVD: Updated the optimization variable plot mouseover label background color to be not transparent. LVD: Run Case Matrix workers now record diary as they run to a "running" log file. LVD: Updated tab order for initial state and set kinematic state UIs. LVD: New example: lvdExample_MunarFreeReturn MA/LVD: Many bug fixes. Please let me know if you find any issues. Thank you and happy orbiting!
  21. Arrowstar
    Got it. I found the issue and resolved it for the next release.
  22. Arrowstar
    Just a heads up to everyone, the next pre-release will probably update MATLAB to R2023b (the latest version). It'll also have an updated version of the NOMAD optimizer (v4.4) in LVD, along with some other changes.
  23. Arrowstar
    I actually couldn't reproduce this error. Does it still happen for you? Propagating to certain "events", like true anomaly or whatnot, doesn't work as well in the integrator based system that LVD uses. This is why everything is time based. Set up constraints to the target you want at the end of an event and then optimize the propagation time of that event to meet those constraints. This should work out pretty well most of the time.
  24. Arrowstar
    Hey, sorry about taking forever to get back to you. Between Christmas and New Year's Day I've been pretty busy recently. You've basically got the idea on point 3 about updating the state. Once you're in between major bits of the mission and you're just coasting along, you can remove the previous segments and update the initial state to match your current state in the game via importing it (right click in the Initial State dialog box). At that point you can add maneuvers for corrections and stuff like that. I think there's an "advance to segment" option in the right click menu of the script listbox that helps make some of this easier! Does this help any?
  25. Arrowstar
    I don't have the skills for that, but if anyone would like to give it a go, they are welcome to let me know and I'll help with info as I can.
×
×
  • Create New...