Search the Community

Showing results for tags 'atmosphere'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • The Daily Kerbal
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website
  • KSP Pre-release
    • 1.2.9 Pre-release Branch
    • 1.2.9 Pre-release Modding Discussions
    • 1.2.9 Pre-release Bug Tracker

Categories

  • Developer Articles

Found 17 results

  1. I noticed in KSP 1.3 that parts using ModuleResourceHarvester type = 2 (atmospheric) no longer appear to harvest any resource if surface speed is exactly zero, such as if the craft is attached to a launch clamp or has wheel brakes engaged. If there's any motion, such as a heavy craft wobbling on its clamps, or with brakes engaged but can still be tilted side to side, then it'll harvest the resource. This seems to happen regardless of abundance. This differs from air intakes that can still take in a fixed amount of IntakeAir if perfectly stationary. I originally tuned my harvesters to match whatever the corresponding air intake would harvest in IntakeAir while stationary, then re-tuned that to match the IntakeAir rate times whatever MinAbundance was (assuming MinAbundance and MaxAbundance were equal). Now it seems I'll have to re-tune that based on a fixed non-zero speed. Or maybe there's an option for a stationary atmospheric harvester to still work. Where can I find changes to ModuleResourceHarvester?
  2. Hello KSP players, here is an interesting mod that adds atmospheres to those planets and moons which don't have atmospheres of the kerbol system (and also in the future WITH YOUR PERMISSION that adds atmospheres to your planets and moons that have no atmosphere ) Picture : Album gallery/iLCUW will appear when post is submitted Projects : (Not complete) Have good non-existent pressure for the planet and moon (Not complete) Add more color for atmospheres to those planets and moons which don't have atmospheres (Only black and white) (Not complete) (WITH YOUR PERMISSION) Adds atmospheres to your planets and moons that have no atmosphere (at least one mod please ) Download : Github Spacedock Curse Dropbox Source : Github README : 1. Download the mods Kopernicus (1.3.0 2 IMPORTANT !!) and the mods ModuleManager (2.8.0 IMPORTANT !!) 2. Put the mods files in the GameData folder 3. Start the game (KSP) 4. Have fun Essentials mods : Kopernicus by @Thomas P., This mod is the core to manage stars, planets and moons. ModuleManager by @sarbian, This mod that allows you to write a patch file that modifies another part at the time of loading. Recommends mods : HyperEdit by @Ezriilc, This mod will allow you to cheat even more! BetterTimeWarpContinued by @linuxgurugamer (@MrHappyFace), This mod allows you to have a better time warp. KerbalHistoricalInstitute by @blspblackdeath, This mod allow you to have the old parts. HypotheticalWorlds by @ModerndayLink64, This mod adds two hypothetical planets (Planet K and Kyche). KSP-AVC by @cybutek, This mod allows you to have updates without going on the internet browser. Compatible mods : Sorry, there are no mods for the category LICENSE : MIT Log : Special thanks : @Gaarst Because it added my mod in Community Mods and Plugins Library continued for 1.2.2 & 1.3! And if you have a suggestion or find bugs or errors, contact us (pikmin-123@hotmail.com or make a private message in the forum of KSP) Thank you very much!
  3. Download Here (1.2 is most recent update) EVE is bundled, but be sure to check EVE page for updates as i dont expect to update this more often then every few weeks. And for those of you that want to run this with OPM, check out the following: Pics: Features: *Minimalistic design and lack of scatterer requirement (feel free to run it alongside this mod if you like to, just isnt required for this to look good) allows this to run on potato computers. *All planets but Gilly and Bop have atmospheric scatter or glow effects rendered via EVE cloud layers. Colors are generally highly saturated to give a more sci-fi universe feel compared to the more white and washed out realistic style used in most other mods. *Kerbin, Duna, Eve, and Laythe have light volumetric clouds. They are a good balance between thickness and performance, should not cause any real lag. *Most airless bodies have fog/dust effects. Color choice is fairly varied, with some planets having highly colorful fog while others use a more greyish color. Duna has dust storms and Eeloo has blizzards. Particle density is kept to an absolute minimum to keep performance up. While i cannot speak for everyone, my mid range laptop is capable of handling this mod as well as 2 1000 part warships in low orbit around any planet. *Lite edition has no clouds and does not come with the respective textures (use this if you want more performance or prefer to not have clouds like stock scatterer would). Changelog: V-1.2 *New custom cloud maps in 4096x2048 (8192x4096 for Kerbin), unique to every planet. Styles vary from purely sci-fi to semi-realistic depending on the planet for variety's sake. *Three new higher resolution detail textures which are both high res and do not give tiling issues when viewed from far away. Currently textures are for cumulus, cirrus, and a sci-fi one. *Seven new particle textures. Three are for clouds, all of which are wispy in nature and optimized to look good with very low particle density. Four are for the surface effects which vary from some particulates floating around to full blown dust storms. *Few minor color adjustments to improve looks with the new cloud textures. V-1.1 *Improved detail textures. *Minor changes to atmosphere and glow colors. V-1.0 *Initial release. Planned: *Lava eruption fx for Moho (cryovolcanoes on Eeloo afterwards as an option instead of/alongside the blizzards) *Unique fx for Gilly and Bop. *Requests are welcome (although i may have to say no if it cant be physically done or will end up being a performance concern). Support: For suggestions and issues please post in this thread. I play tested this for 2 days, but there is always the possibility i missed something (or could change something for the better). Also, for all EVE related bugs or questions please go to the EVE thread and do not post here. I repeat, i will not be troubleshooting EVE itself on this thread, just stuff related to my effects pack. Check the readme in the files for credits and licensing information.
  4. Before posting feature requests or bug reports, please read the FAQ. FAQ Works with stock aerodynamics and FAR Reportedly works with deadly reentry real solar system Rescaled Kerbin Compatible with Blizzy's toolbar If you see weird spirals or other crazy lines everywhere, double-check you didn't enable "body-fixed mode" by mistake If the predicted trajectory seems inaccurate, check that you set the correct orientation in the Descent profile (or checked Prograde or Retrograde), and that you keep that orientation all the time It's not possible to predict a trajectory for a future stage. We know this is a highly requested feature, but unless we duplicate big parts of the KSP-internal code, we are limited to simulating the current state of the vessel. Parachutes are not simulated (that's usually not a problem if you open it near the ground) Download On SpaceDock On GitHub Description The mod displays trajectory predictions, accounting for atmospheric drag and lift. Works with the stock aerodynamic model, and with Ferram Aerospace Research (FAR). With this mod, you can choose precisely the location where you'll crash. The typical precision is about 6km. Plan Aerobraking maneuvers that can, for example, put you on intersection trajectory with another body (see point 1 about what you can do from there) Keep in mind that this software comes without warranty of any kind, and in particular that it may or may not help you survive, reach a specific target, or anything at all. But it usually helps User manual See your predicted trajectory Open the map view This is it ; trajectory display is enabled by default, you have nothing else to do White is the trajectory in space, red is the trajectory in atmosphere, the red cross is your impact point (that takes the body rotation into account to show the impact point on the terrain, this is useful both for bodies with and without atmosphere) Disable the trajectory display Click on the Trajectories icon in the stock KSP toolbar (or Blizzy's toolbar if it's installed) to display the main UI Click "Display trajectory" to toggle it on/off Click "complete" to toggle display of the complete trajectory (including parts where it is superimposed with the stock KSP trajectory) Set a target point (nav ball guidance) Adjust your velocity so that the red cross is located where you want to go Click "Set current impact as target" to enable the green cross Alternatively, there is a button to set the target on the KSC (works on Kerbin only obviously), or you can enter longitude/latitude Go back in flight view, and notice the two new indicators on the nav ball The square indicator shows where you need to point your craft at if you were exactly following the predicted trajectory The circle indicator is a hint about the direction you should go to adjust your actual trajectory to reach the target (this is not necessarily where you need to point, what's important is the direction between the square and the circle, and the distance between them indicates how far you are from the perfect trajectory) Body-fixed mode Use this toggle to switch between the regular mode (similar to stock KSP orbits), or body-fixed mode. In body-fixed mode, the trajectory is displayed relatively to the body frame, following the body rotation. This mode makes sense for atmospheric or low terrain fly-by, and also to adjust a geostationary orbit. However, for most high orbits, it will just look funny. This can help you keep occupied for those 2-year-long planetary transfers, but try not to burn up all the fuel to see how it can make funny curved lines. Manoeuver nodes You can plan aerobraking or re-entry after manoeuvers, just place your nodes as usual and see the predicted trajectory. Keep in mind that you always place nodes on the stock trajectory, that might be very different from the predicted one, so you may have to place nodes at a point that have an effect somewhere else on the predicted trajectory (especially when planning landing on a body without atmosphere with body-fixed mode). Also, atmospheric prediction can happen only for the body you are currently orbiting, so you can't plan a Kerbin re-entry while you're still arround the Mun. Support and Bugs If you have questions and feedback regarding a current release, feel free to post in this thread. Please post bug reports on the GitHub bug tracker. If you don't know how, don't want to learn or are unsure it's a bug, you can ask in this thread. Contributions This mod is a community project! It was originally written by @Youen and is currently maintained by @Kobymaru. The following people have already contributed to this project (in approximative order of commits): Youen (Github neuoy) Kobymaru (Github fat-lobyte) PiezPiedPy atomicfury (Github sawyerap) And many others. You want to be part of this list? Contributions are very welcome! Read our Introduction for Contributors, fork the Repository on Github and have a go at the code! When you feel that your changes are mature enough to be included, send me a pull request! Also, please let us know what you are working on in the development thread. It's always best if you work on your "pet problem" - a bug that needs to be fixed or that you personally want to see implemented. Or you could just grab an issue from our Issue Tracker! For discussions about Mod internals and Development, please head over to the development thread. Change log The changelog started with release v1.6.7. For the changes in versions older than that, please visit the GitHub releases page. License This mod is under MIT license, feel free to look at the source code: https://github.com/neuoy/KSPTrajectories
  5. Hey everyone, I recently have been sucked into this game, and I'm loving the math. My question is this simple, determine the altitude a rocket will achieve on full fuel burn of a single stage. I've done a lot of research and have come up with the following example problem to test my algorithm/process of calculation. Let me know what you guys think of below and what I'm missing or potentially a force I haven't considered into the calculation such as lift, as you'll see my answer is off by nearly 3,300m. (For the sake of simplicity the rocket travels straight up in a vertical dimension only.) Known Values of my Rocket: Full Mass [MFull] (Entire Rocket) : 7.5t (7,500kg) Empty Mass [MEmpty] (First Stage Depleted) : 4.5t (4,500kg) Fuel Mass [MFuel] (Both LQ and OX) : 3.0t (3,000kg) Isp [Isp] (Reliant Engine) : 265 sec Thrust [FT] (Thrust Force Atm.) : 205.2kN (205,200N) LQ Rate [BLQ] (Burn Rate of LQ) : 7.105 u/sec OX Rate [BOX] (Burn Rate of OX) : 8.684 u/sec LQ Volume [VLQ] (LQ Fuel 45% Mix) : 270 u OX Volume [VOX] (OX Fuel 55% Mix) : 330 u Known Values of Kerbin: Accel. Kerbin [g] (Accel. of Gravity) : 9.81 m/sec^2 First I will calculate the time required to burn through the fuel mixture. This time will be needed in the final calculation. Tburn =VLQ /BLQ =VOX / BOX << >> 270u / (7.105u/sec) = 38.0 sec Next I convert burn rate units from volume/sec to units of kg/sec. (I assume 1u = 5kg of both LQ and OX) BLQ_M = BLQ * (5kg/u) << >> (7.105u/sec) * (5kg/u) = 35.525 kg/sec BOX_M = BOX * (5kg/u) << >> (8.684u/sec) * (5kg/u) = 43.42 kg/sec BTOTAL= BLQ + BOX << >> 35.525kg/sec + 43.42kg/sec = 78.945 kg/sec (M *Dot = Mass Flow Rate) Determine effective exhaust velocity of rocket motor related to Specific Impulse and Gravity. (NASA Formula) Ve= Isp * g << >> 265sec * 9.81m/sec^2 = 2,599.65 m/s Determine acceleration of rocket (Found this formula on a physics forum, not sure if valid) a = Ve ( BTOTAL / MFULL ) - g << >> 2,599.65 m/s * (78.945kg/sec / 7,500kg) - 9.81m/s^2 = 17.554 m/s^2 Apply classical kinematic physics equation for displacement with acceleration. (Vertical Axis only...) deltaX = 0.5 * a * (Tburn^2) << >> 0.5 * 17.554m/s^2 * (38sec ^ 2) = 12,673.988m So in the end this calculation results in an effective altitude of 12,673.98 meters. If anything, I expect drag (if simulated) among other forces to take away from this value. Instead the opposite occurred, my actual test flight while holding steady to the center of the NavBall resulted in roughly 16,000 meters altitude at 38 seconds into flight (after stage finished burning). Any ideas?
  6. Good evening to you all. Hopefully I have a simple question here. I have built an early tech plane, and, in order to make it long range I added a Terrier rocket engine to it so I could get it off the ground with all the extra fuel it's carrying for the Juno engines that are on it. I set the thrust limiter on the Terrier to 20, just enough to get the plane off the ground, and then I shut it down once I have enough speed to keep the plane in the air. My question is, does the oxidizer burn at the same rate no matter what you have the thrust set at? When I do activate the Terrier in flight it seems that the oxidizer is still burning at the same rate it would if the Terrier was at full power. If it does, is there any way to limit the oxidizer so I can maximize the effectiveness of the Terrier?
  7. Once Galileo probe entered the atmosphere of Jupiter we made a lot of dicoveries and conclusions about Jupiter and all gas giants in solar system. But in ksp we can much more than in real life The idea is - you dive deeply into jool atmosphere as deep you can can and then return . For this task you beter use a plane/glider. Rules :Dont use cheats to prevent overheating nor cheats for infinite fue (just dont use cheats at all !) . Dont use mods except the the mods that add balloons . You need stay at the low altitide for 55 sec. That is your guide Easy: 70 000 m Normal: 40 000 m Hard: 35 000 m .
  8. It seems that the ksp atmosphere(stock) has some visual artifacts with the brightness and contrast. Which makes me curious about: How's it rendered? Is it intended to be physically accurate (in some degree), or just artificially constructed to look good? Also, I've heard that Tylo and Eeloo supposed to have very thin atmosphere, but it is discarded due to the rendering method of ksp being incapable of those rendering. Can I be given a short description of the cause of the incapability?
  9. Revamped Kerbol System Atmospheres This is an EnvironmentalVisualEnhancements and Scatterer configuration for use with @GregroxMun's Revamped Stock Kerbol System mod. Greg asked me to help him create this for his mod, and I was happy to help. He and I discussed the changes to be made for the Revamp, and I've done my best to implement his vision for this mod. EnvironmentalVisualEnhancements 1.1-3 or later is required! Scatterer v0.0246 or later is required! To install, first download and install EVE and the standard EVE configs, and install Scatterer and any additional Scatterer sunflare as you desire. Then download and extract the RevampedKerbolAtmos.zip file. Copy the GameData folder into your KSP install, and overwrite the existing Scatterer configs. Currently it is not possible to implement Scatterer configs via a ModuleManager patch, and custom textures for Scatterer are in use with this mod. However, the MM patch in the "Cetera" folder will make the necessary changes to the BoulderCo > Atmosphere >clouds.cfg. This file must exist for module manager to update in order for this mod to work. Download License: GPLv3, primarily due to using the Scatterer config tool to create the textures and the configurations, and that is the license Scatterer is released under. Special thanks to @GregroxMun for making the Revamped Stock Kerbol System mod, @rbray89 for creating and supporting EVE all these years, and @blackrack for the Scatter mod. KSP just wouldn't look nearly as good without the efforts of those two gentleman, and you should each thank them personally. A huge thank you to @Raptor831 for coaching me through writing the ModuleManager patch, and explaining to me like I'm five how module manager works. His patience was instrumental in making this mod happen. Details: Jool has a more yellow cloud color, and a very pale green atmosphere in Scatterer. Lathe has a more blue-ish gray atmosphere, adding an additional cloud layer. Duna has very light, wispy, high-altitude clouds. The clouds are a light brownish-orange. Eve has been reworked to keep the stock EVE textures, but turn them a very nice pink, almost salmon, color. The atmosphere in Scatterer still has a purple highlight. Moho has a very thin, gray atmosphere. At higher elevations on the planet, it will not show up at all, as you are above the majority of the atmosphere. At lower elevations, it will provide a gray highlight to the horizon.
  10. I know clouds have been brought up a lot on this forum, but I think clouds are only half the story. Weather is often a determining factor in the success or failure of space missions or aircraft flights, be it on Earth, or at the destination. 1. Wind - Wind plays a big factor when taking off or landing with aircraft. High wind speeds and storms also cause hazard for re-entering spacecraft, and for spacecraft wishing to launch. 2. Clouds - Clouds add a layer of uncertainty to approaches, as it is more difficult to judge where your spacecraft will touch down, (especially on a planet like eve where there would be very thick clouds). It'd also add nice aesthetics. 3. Rain - Again, mostly cosmetic, but adding another level of depth to the planets you are visiting. Every day is the same on the moon, but Laythe storms would add a different perspective to the mostly barren moon. 4. Storms - Storms would combine all of the above, not freak hurricanes which destroy ground bases (although poorly built ground bases or top-heavy landers might topple) but still a deterrence from landing. Weather is something which is closely tied to aeronautics and space, and I think I'd be a loss if KSP didn't implement some form of weather system. PS: No mod I've seen has successfully combined all of the above. I've seen Kerbal Wind: And I've seen EVE: But these two do not represent a fully functioning weather system.
  11. How to get atmosphere and tempterature curve values without writing them? Or a generator maybe?
  12. Hi there, I've accepted a contract asking me to enter the atmosphere of Jool. I decided to send a very simple probe in a deadly trip to the Green Planet. (Periapsis 4 km...) I was thinking that "Enter the atmosphere of Jool to achieve this goal" was pretty clear. But my probe exploded a few hundred meters below the surface of Jool, and the contract is still there... https://drive.google.com/folderview?id=0B1cJn_NG58YYSGRSdm1KQXpDSDQ&usp=sharing Do you think I need wings to achieve this contract, or is this just a bug? Thanks for reading
  13. I have a very small pod (about 1 ton) in an elliptical orbit around Kerbin. The Pe is around 68km, the Ap around 330km. I am mostly watching the thing orbit in realtime. When I am not timewarping, both the Ap and the Pe fall. (In 1.0, it used to be true that when the Ap fell, the Pe would rise, and vise versa.) The funny thing is that it's acting like a drag that's decreasing with altitude. Like the 70km atmosphere cutoff no longer applies. Is anyone else seeing something like this?
  14. Hellooow everyone ! Today I come up with a weird question : Okay, so I wish to start exploring other planets in the game now, but I like to do things properly and well, because the most amazing part of the gameto me is when excrements works and you succeed in actually going somewhere. My first target will obviously be Duna and I have this program idea, that's kind of inspired by the Mars Semi-direct Mission, with a hab module, a Duna Ascent Vehicle and a Kerbin Return Vehicle. Now I know Duna has a different atmosphere and gravity pull than Kerbin... So how do I test properly my crafts ? How am I going to know if they'll actually work waaaay over there ? That's the kind of mission I don't want to have to restart from the beginning if something doesn't work.. I mean, I enjoy problems that are interesting and spectacular, like when everything goes south or when you forgot a step and the result is just too funny to be reverted etc... Not the annoying stuff that makes you start again 60 times and takes you 7hours to get right. So yeah, thanks in advance for all the help and have a nice Odyssey
  15. As the title says: we have listed values for vacuum and ASL thrust, but how is the Isp/thrust interpolated from there (or extrapolated for higher atmospheric pressures)?
  16. So, I am making a planet pack with Kopernicus for KSP. And I have a problem. I want to create a brown dwarf, using Jool as template. I want to create an atmosphere for it (so you can't land on it), but I don't understand those complicated numbers: key = 137500 100.8216733 -2.71949803636364E-03 -2.71949803636364E-03 key = 151250 68.1071 -2.13953963636364E-03 -2.13953963636364E-03 key = 165000 41.98433333 -1.65774109090909E-03 -1.65774109090909E-03 key = 178750 22.51922 -1.00126501090909E-03 -1.00126501090909E-03 key = 192500 14.44954667 -4.06759432727273E-04 -4.06759432727273E-04 key = 206250 11.33333333 -2.27824727272727E-04 -2.27824727272727E-04 key = 220000 8.184366667 -2.25669374545455E-04 -2.25669374545455E-04 key = 233750 5.127426667 -2.06283192727273E-04 -2.06283192727273E-04 key = 247500 2.51158 -1.61502101818182E-04 -1.61502101818182E-04 key = 261250 0.68612 -9.13301818181818E-05 -9.13301818181818E-05 key = 275000 0 -4.98996363636364E-05 -4.98996363636364E-05 (They're about atmosphere pressure and temperature curve) Is there a program or site to make these, or is there a simpler way?
  17. As I was performing an aerobrake, my ablator died and went completely black. Then it made me wonder: how fast can you kill an ablator? ---RULES--- No Alt F12, keep it stock, don't mess with game files, etc. Keep it pure and genuine. I want to see how fast you can kill an ablator. I'm not sure if the size matters, but I'm going to try and keep it on even ground. The size of your base, starting engines determines the size ablator you can use. For instance, a 3.5m starting engine only allows you to use no smaller than a 3.5m ablator, and a 2.5 m starting engine allows a 2.5m ablator, and so forth. However, you can stick on a larger ablator with a smaller starting engine (The Vector engine can carry a 2 or 3 m ablator). If you use a cluster of starting engines of varying sizes, you can use an ablator no smaller than the largest starting engine. You may use stages as you see fit, but you may not use an engine in any stage larger than your blator payload. I will keep ablator burn up times each respective to their sizes. You gain bonus points if your vehicle doesn't blow up after killing the ablator, and especially if you come to a complete stop. This also means you can't have any parts destroyed while attempting to fry your blator. ----- Also, I hope this is a reasonable challenge... feel free to critique my challenge, but please don't be a wiseguy. As long as you are nice about pointing out any potential loopsholes, etc. Have fun.