Jump to content

scimas

Members
  • Content Count

    201
  • Joined

  • Last visited

Community Reputation

116 Excellent

About scimas

  • Rank
    Spacecraft Engineer

Profile Information

  • Location
    USA
  • Interests
    Physics, programming, reading and, of course, gaming!

Recent Profile Visitors

2,497 profile views
  1. These are initial state files for use with RealSolarSystem https://drive.google.com/drive/folders/1iNlip4K66oaOQgPm7nDnpQxExuDmp6lu Some people like to play or simply want to explore RSS in more recent years, rather than 1951 with which Principia starts by default. And of course you can timewarp to whatever year you want to. But until the devs complete their work on #2400 and related issues, it is going to remain a bit painful the further from 1951 you timewarp. The folder linked above contains initial states every 5 years from 1950 to 2020. So the initial state file for 2010 gives you a
  2. The stock spheres of influence do exist even with Principia, Principia just doesn't care about them. The stock science system uses those same SOIs for determining which experiments are available. In case of other planet packs, those limits are set by the respective planet packs, Principia doesn't meddle with it. And anyway - with or without Principia - altitudes don't depend on the SOIs at all. Altitude is simply (distance from body center minus body radius). Conceptually, an altitude with respect to Mun still exists even if you're in the SOI of Jool.
  3. kOS and Principia don't do anything special for each other. So they are as compatible with each other as any two random mods are. You will need to be more specific than that to get help. What kind of problems?
  4. Download the zip - links are on both the first post of this thread and the README on github. Extract the zip and copy / merge the folder like any other mod. If you have never installed any mod before, read the thread linked by Entropian.
  5. Anyone. One of each INFO, WARNING, ERROR and FATAL log is created for every KSP session. The name contains the date and time when the log was created (alternatively you can also sort the folder by date modified). Also, go through the troubleshooting section of FAQ on github.
  6. Check the history of the README.md file on github, you should be able to get the links there. But note that bug fixes and new features are not ported to older versions, so you won't get them.
  7. Check the ModuleManager documentation, it does allow checking for presence of modules among many many other things.
  8. That's an extremely unhelpful report. It's like saying, "I was walking down the road and now my arm is bruised, what's going on?" I don't know, a hundred different things, maybe you hit a power pole with it or a car drove over it, or it was bruised all along but you just noticed... Nobody can and will help you unless you properly describe what you were trying to do, how that thing didn't happen the way you expected, what went wrong and, if needed, provide the logs.
  9. KSP itself treats asteroids just like vessels. Your rocket can grab onto them and move them around anyway you like, so Principia also needs to treat them like vessels. Actually I didn't even need to type that, I could have just linked this: Principia wiki regarding timewarp
  10. Agreed. So many people have already made their scripts publicly on github. And if people want to contribute more general or utility like code, they are encouraged to contribute to KSLib - a standard library of sorts for kOS. As for the location of the script files, technically they can be anywhere. A Ships/Script/ simlink can then be created. I manage my scripts this way so that updating / deleting a KSP installation doesn't get rid of my scripts. Of course this method has same problems that @kcs123 already described.
  11. The manoeuvre (the current one) can already be accessed through kOS. That issue was about exposing a lot of the FlightPlanner, but as @Butcher said, most of the proposed things can already be accessed through the stock api. He had also written the kOS side of the code for the hypothetical principia interface at the time. I found out the "history only" part about VesselGetPosition when I was working on my modification of his code. The problem I'm trying to address is a lack of future trajectory prediction (both position and velocity) in the presence of N-body gravitation.
  12. I'm writing an addon for kOS. Since the trajectory of the vessel doesn't match patched conics in the presence of N-body gravitation (especially body to body transfer trajectories), automatic accurate execution of manoeuvre nodes becomes impossible. If instead I can get position from Principia, I can code the execution program to seek a certain distance from some body at a certain time (within some margin, not pin point accurate). So it would be helpful if principia could provide the prediction. For my use case it would be enough to get predictions that fit in the constraints provided in t
  13. @pleroy Is VesselGetPosition only supposed to give past positions? I'm extremely new to modding (even using C# at all), so I could be doing something wrong. But passing a time not in the past (eg Planetarium.getUniversalTime() + non_negative_number) throws out of range error. If it isn't supposed to work like this, I will open an issue on github.
  14. In my experience, it's actually the parameters themselves not matching is the problem. When the state of the vessel is such that the "one SOI at a time" is not a good approximation of N-body physics, the magnitudes or anomalies of various nodes differ significantly from the conic approximations. If you turn on the "show patched conics" option in principia, and make that orbit stay in the expected limits for 10 s, the contract will get completed - even if the values change in those 10 s, they just need to remain in limits.
×
×
  • Create New...