Jump to content

Postron

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by Postron

  1. Hi there,

    I vaguely remember a mod that changed all the main story line progression contracts (such as "Explore the Mun" etc.) to work like these small speed and altitude record auto-contracts. So you could just play the game and would get the appropriate reward whenever you fulfilled the conditions. I do not however remember what the mod was called.

    Can anyone maybe tell me the name of the mod?

    Thank you very much in advance.

  2. Granted. There will be 3 new gas-giants with complex moon systems. However due to the additional textures KSP loads now to 3.3Mb in the main menu so whenever you try to launch a rocket ksp crashes after 2 minutes, reaching the memory limit. Also these new planets and moons use a file-format that is completely incompatible with any form of 64 bit processing.

    I wish for cake.

  3. I'd have to go back and check my notes to see how much the atmospheric pressure of Kerbin's atmosphere changes with height and how it compares to Earth's atmosphere in that regard. I do know that on average the atmospheric pressure on Earth at 10 kilometers up is roughly 100 hPa (roughly 0.1 atm). There may be a difference there that also contributes to differences in how the atmosphere behaves.

    Actually atmospheric pressure at 10 km is roughly 26 kPa. As a rule of the thumb you can say atmospheric pressure halves roughly every 5500m.

  4. It already is available via CKAN. It's called "Trajectories" there. If you don't see it make sure you have ksp updated to .90 and try refreshing your repository. If you still don't see it then you should post this in the CKAN thread.

  5. I think it should be possible to extract any stage during flight, by looking at the staging actions, and cutting parts of the vessel graph where things are going to decouple. I think Kronal Vessel Viewer does exactly this. The user could then be proposed a field to type the stage number than will reenter (by default the last stage?). But that would not help for manual things you are planning to do (such as decoupling docking ports before reentry, etc.)

    Once this is done, the mod could simulate only the remaining parts. This could be slightly wrong for FAR that makes more complicated things (parts interact with each other, wing cross winds, etc.), but I don't know how inaccurate (or not) it would be.

    In my opinion, such an automatic system would be better than adding more user interactions towith the mod. Otherwise, each time you change your ship design, you would have to click the "Save aerodynamic profile" again, which means you'd have to remove the staged parts first, click the button, and re-attach the parts. Also, if you forget to do it, you may get inaccurate results, not be able to fix it while in flight, and don't know if you have to blame the mod or yourself for forgetting an update. The developpers who get bug reports wouldn't know either ;-)

    Having the player plan ahead was actually part of my intention, since it would be unrealistic to be able to simulate even for configurations that weren't even intended for reentry, that being said right now the mod can simulate for any possible configuration as well as long as that configuration is actually physically (in game) present, so it would make sense to be able to simulate any stage from how the mod works right now.

    That being said I believe FAR actually needs a craft to be physically present in the game in order to determine its aerodynamic behavior so if we wanted to auto predict for every stage we'd probably need to replicate the part of ksp.exe that turns a craftfile into an 3d KSP-ingame model, which is probably against the rules. Therefore it'd be far easier to save this aerodynamic behavior at that point of time when the configuration is actually present in game which will usually be while building the craft. (Usually you start to build your crafts from the top stage, don't you) Also regarding reattaching everything after stripping it of, you can just reload the finished craft provided you saved it earlier.

    - - - Updated - - -

    For the amazing shrinking predicted orbits on aerobraking on FAR issue:

    Just switched to NEAR from FAR. Using NEAR the prediction is spot on. So, whatever is causing more drag to be experienced than expected is something that FAR is calculating that NEAR is not. No idea what that might be, but if predictions were working well for people in FAR pre .90, then it's one of the new features that's not being read in or accounted for.

    In one of the last updates Ferram introduced an concept called Reynolds-Numbers which drastically increases drag in low pressure, high velocity situations. Therefore skimming through the upper atmosphere now alters the orbit far more than before.

  6. A puller design is definitely superior to a pusher design because the pusher tends to make your ship bend (and break) while the puller pulls your ship straight (imagine trying to push/pull a spaghetti from its ends).

    Regarding SAS modules, I'd try to use as few of them as possible, sure it's gonna make turning excruciating but at least you won't have to worry about your falling apart due to too much torque applied from digital on/off buttons (maybe that's a different story if you use a stick to fly).

  7. I love this idea, but I have no clue how to implement that. I don't think it would be impossible though. Feel free to poke your noses in the code! ;) There's a new section in the OP, called "Contributing", you might want to flick through it. First sentence: "This mod is a community project!"

    I feel that this is not something a user should "work around" ;)

    TBH, I think that's the smallest problem of all ;) Teaching FAR to temporarily calculate only one stage however, ...

    To my understanding FAR is able to see the aerodynamic properties of any craft in the editor. So it should be possible to take these readouts for any given physical construction and save them as in file somewhere. Now I think (hope) it should be possible to tell FAR later on to do it's simulation not based of the readout from your current craft but instead based upon the file you created earlier.

    The way I imagine it to work is, that while building my rocket I strip everything that's supposed to be decoupled before reentry from my capsule and hit a button "Save aerodynamic profile". Later on in flight then I would be able to tell the mod to use this saved profile instead of the profile FAR is currently reading, so the trajectory would actually match that of my next stage instead of the current one.

×
×
  • Create New...