Search the Community

Showing results for tags 'eve'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • 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


  • Developer Articles

Found 65 results

  1. (Note, this is still in v 1.04) Proving that what goes to Eve does not have to stay on Eve, I set about to make a not-entirely-stock Eve lander for my developing fleet of interplanetary ships. It may not be the best design, but I did successfully make and test a (rocket) vehicle that can leave the Purple Ball O' Doom, without being too big or tall. This is a "final" revision of my third design, meant to take a Mk 1 lander can down and back up. To make EVA easier without putting a zillion ladders on, I put a Mk 2 lander can at the very bottom to act as an EVA "elevator", i.e.transfer the Kerbal down and up. Could have used another Mk 1, but I wanted a bigger attachment node for the 5m stack separator. It also meant that the main stage is purely radial engines, with no central one; the central and outer tanks feed the inner engines. The pics combine two separate tests (used HyperEdit), the entry phase from the previous revision and the landing/launch from the final version. The only things different between the two ships was that the four Kiwi retro-burn engines (from Space Y) were replaced with a single Mainsail below the heat shield, a Mainsail replaced the 8 Swivels in the middle stage, plus 8 active winglets were added, and more fuel was added to the main stage. I had thought the Kiwis could perform as descent engines to slow down the final few meters, but they did nothing and still ended up using 4 of the main engines, so I ditched them. I made the changes to the middle stage after it kept flipping out after staging. I wanted to keep both the middle and upper stage short, so either the Mainsail and/or winglets proved to be the solution. The main engines are 8 Ratites from Space Y, a 2.5m engine with more thrust than a Rhino, especially at low altitudes (Rhinos proved to be useless on Eve). Less efficient too, but that's not I needed for the first stage of an Eve ascent vehicle. Most of the main stage tanks are from Fuel Tanks Plus, the 3/4 and 1.5x versions of the standard orange tank. Added some stock Rockomax tanks as needed. Main chutes are 2.5m Mk16 XLs plus 8 radial drogue ones. The big radial decouplers with built-in sepratons are also from Space Y (those things are so cool and useful!). And the heat shield is a Tweakscaled 5m one from Space Y (not sure if it mattered) up to 20m size--no problems with heat there! Middle stage as noted is a Mainsail on a Rockomax -32 tank with 8 radial FL-T400 tanks. Upper stage is a FL-T400 with 4 -200s and 4 1.25m Poodles (used Tweakscale), they have a mass of .377 and 45 kN of thrust. Thought about using aerospikes but wanted something with thrust vectoring and lower mass. The upper stage has an RCS fuel tank from FTP and 4 quad thrusters. And of course I put MechJeb on it, though I only used it to hold pro/retrograde, not to land or launch. The landing struts are LT-2s upsized 300% mounted on 200% pocket I-beams. Several 2.5m reaction wheels are in the ship, with main power from 4 200% size RTGs Not sure what was going on with the landing struts on the landing (broken? glitch?) but the ship was stable and took off fine. Went into a polar orbit since that was how it came in--wanted to land on, well, land and not in the sea. Started at relatively low altitude too, 654m ASL (heh, the previous test landed in the Highlands ). Ended up with over 1150 m/s DV left after the circularization burn. The first version of the lander included a top-docked rover, my latest "mega mini" type, the plan being to transfer the scientist Kerbal from the ship to the rover after then pop off the rover before landing and have it drive back to the ship, visiting several biomes on the way That proved to be successful, so I stopped bothering to include it on later versions. I might even change the plan to land the rover separately, or even several rovers...but that would require a 2 or 3-Kerbal version of the ship...guess what will be next?
  2. Explodium Breathing Engines "Jet" engines that (actually!) use Eve's atmosphere and Oxidizer. License: MIT License except for re-coloured textures, which were derived from art belonging to Squad / Deported B.V. Download from SpaceDock or from GitHub. Requires Module Manager 2.8.0 for KSP 1.3. Supports RealPlume Stock. It had to happen. After good success with @GregroxMun's Alien Space Programs and @OhioBob's Eve Optimized Engines, along with an old discussion about atmospheric engines using oxidizer instead of liquid fuel, I just had to ask how hard it would be to make jet engines that would breathe "explodium vapour" likely found in Eve's atmosphere and burn it with oxidizer to produce efficient thrust. @JadeOfMaar and @wasml pointed me in the right direction, @DStaal filled in a few blanks, and I hacked together some parts. Introducing Explodium Breathing Engines. A set of cloned configuration files from stock jet engine parts that use oxidizer only, and a new resource configuration found hypothetically in Eve's atmosphere: "Explodium Vapour" evaporated from Eve's Explodium Sea. This vapour may also be present on other planets in popular planet packs. Further rebalancing has happened based on resource abundance and a pure ethane (C2H6) reaction with oxygen. Resource abundance now has a direct impact on engine performance. This is turning from proof-of-concept into something realistic, while still being fun to use. There really is some science behind this that I explain at the project's Wiki, and hammered out in a more recent add-on discussion thread. Modified parts include explodium versions of all intakes, oxidizer + explodium versions of nacelles, oxidizer only tanks and wet wings, and underworld-themed engines: J-21 "Hades" J-34 "Zephyrus" J-91 "Atlas" J-405 "Sphinx" J-X5 "Beelzebub" and let's not forget our favourite: CR-8 L.U.C.I.F.E.R. (Large Unkerbal Cycle-Interchanging Fueled Explodium Rocket) All parts should have a distinct appearance to separate them from stock parts. I put all of the modified parts and ExpVapour resource configurations in a new GitHub repository. MIT license to match OhioBob's choice for the Eve Optimized Engines. I'd be glad to let others into the project who know better than I do. The to-do list includes: (The to-do list is finished!) Rewrite parts as Module Manager patches to remove dependency on Squad art (Done!) Fix the intakes to work on Eve only, somehow (Done! Intakes are now zero EC harvesters.) Fix the resource config if needed, integrate with Community Resource Pack (Not necessary as it turns out.) Rebalance engine performance based on tester feedback (we might be almost done!) Produce different artwork to identify the explodium-based parts (I'm just missing some tricky parts.) Create RealPlume configurations; I'd like to do a different colour plume for these like the blue from an ethane flame (This was quite easy, as it turned out.) Maybe get some help with CKAN, publish to Space Dock (SpaceDock done, CKAN should be done) Known problems, should not impact play: Harvesters need manual activation because of how ModuleResourceHarvester behaves. Workaround: Assign "Deploy Filter" and "Start ExV Filter" to action groups. Ore mining contracts will appear in Career mode when you unlock tech nodes with harvester parts. This might be a game design problem with contracts lumping all resource harvesters together. Pay attention to contract requirements, because there might be a "Gather 2000 units of Explodium Vapour" contract that won't make sense because there are no containers for it. No colourized textures are available for the Atlas engine or Big-OX wings. The wings don't take well to colourization, and the Atlas causes null reference exceptions if using an alternate texture. Harvesters have a small amount of ExpVapour loaded by default. This means engines will work for a few seconds at launch from Kerbin, but will quickly run out of vapour. This may be needed in KSP 1.3 though. Slow frame rates may happen if using the RealPlume configurations. Update SmokeScreen to 2.7.4 or later to address this. (KSP 1.3) Stationary harvesters will harvest zero ExV, such as craft on launch clamps or with wheel brakes engaged. Once motion starts, harvesters will start harvesting. (KSP 1.3) Engine resource shows up as "Ex V" instead of "Explodium Vapour" in VAB or SPH. Other resource name strings not affected for some reason. To use this part pack, grab a release from GitHub or SpaceDock, and put the "GameData\ExplodiumBreathingEngines" folder into your GameData folder. Also copy a supported edition of the Module Manager DLL to your GameData folder. I tested this with Module Manager 2.7.5 on KSP 1.2.2 and 2.8.0 on KSP 1.3. To use an ExpVapour intake / harvester, first deploy the harvester's filter (Deploy Filter), then start it (Start ExV Filter). You might want to use the Brakes action group to deploy the filters and then the Stage action group to start them. To use a RealPlume configuration, install RealPlume-Stock and update its SmokeScreen installation to 2.7.4. If you don't install RealPlume, you'll still get a different engine plume for some engines but most will use the stock jet plumes. Note that GitHub's release ZIP puts the folder into "ExplodiumBreathingEngines-v0.3.1\GameData\ExplodiumBreathingEngines" so you only need the last folder copied to your GameData folder. Now with more words! Change log:
  3. Hello, Can someone please help me make eve/scaterer compatible atmospheres for my planets? Also, how do I make oceans? Thanks in advance
  4. Tutorial: Setting Up EVE Cube Maps In this tutorial we will be looking at how to take advantage of EVE's Cube Map system to layer up to 4 textures onto a single cube map to reduce file size within mod distributions. This method will be outlining the process of taking 4 Equirectangular Cloud Maps, converting them to a single image by putting them into the Red, Green, Blue and Alpha channels, converting it to a Cube Map and setting it up for use in-game with EVE. ***Please Note: All the images below are clickable thumbnails to 1080p images*** ---- 1. Source your Cloud Map (or whatever you want to use) images from wherever. Google Images, NASA, your own creations etc. and ensure that they are all sized correctly in an Equirectangular format; as what has always previously been used in EVE & KSP i.e. Width = 2 x Height. You can use up to 4 image maps at this stage. Below, I have shown a 8192px x 4096px cloud map that has a transparent background. 2. Your images will need to be converted to Greyscale, flat images where the light portions will be the clouds and the dark portions of your image will be the transparent parts in game on your cloud layer i.e. the opacity of the pixel scales with brightness. Therefore, at this stage just edit your cloud map to have a black background with your cloud map layer over the top. 3. Do this for all 4 of your textures and save them as .bmp. For ease of use, I'd recommend naming them something simple like red.bmp, green.bmp, blue.bmp and alpha.bmp or 1.bmp, 2.bmp etc. 4. Open your Equirectangular to Cube Map conversion software, I recommend CubeTheSphere or Hugin (I will be using CubeTheSphere in this tutorial), and load in and convert your images to Cube Maps. In CubeTheSphere open your Equirectangular .bmp image and then select the individual cube face image size to be 2048px x 2048px under the Options toolbar. This will result in the output Cube Map to roughly equate to the same resolution as the 8k Equirectangular image. 5. Extract all the faces of the Cube Map to give you your 6 individual images being the Front, Back, Left, Right, Top and Bottom sides of the map. Do this for all of your 4 cloud maps. This may take some time as your computer is rendering out the images for each face of the cube. Be patient. 6. Now you need to rename the faces to correlate with EVE's naming conventions. In EVE the following sides of the Cube are given as X Positive, X Negative, Y Positive, Y Negative, Z Positive and Z Negative. Seeing as we will finally be outputting the textures for KSP in .dds format, we will need to name the sides of the faces upside down as .dds flips the image vertically when saving. For ease of use, use the following guide to help you rename the files: Xp : Right Xn : Left Yp : Bottom Yn : Top Zp : Front Zn : Back So you should end up with something like the following list of files for each of your cloud maps: redXp.bmp (Right Image) redXn.bmp (Left Image) redYp.bmp (Bottom Image) redYn.bmp (Top Image) redZp.bmp (Front Image) redZn.bmp (Back Image) 7. Once you have your cube maps for all your 4 cloud map textures, go back into Photoshop and load the first 3 X-Positive face images. i.e. redXp.bmp, greenXp.bmp & blueXp.bmp 8. Convert each of the images to Greyscale. Confirm to 'Discard' when asked. 9. Ensure that each of the images is flattened. 10. Navigate to the Channels panel and select the 'Merge Channels' button from the drop down menu. 11. The Merge Channels menu should pop up where you can select the RGB option from the drop down menu, select the 'RGB' option and 3 channels and click 'OK'. 12. In the next menu select the appropriate image for each of the corresponding colour channels. Click 'OK' to merge the images into one image. 13. As a result you will end up with something similar to what is shown below. By toggling the visibility of each of the colour channels you can see you individual textures appear on their separated colour channels. 14. To add the 4th cloud map, cube map face texture to the image, we will be putting it into the Alpha Channel. To do this, in the Channels panel click 'Create New Channel' to add another channel to the image. This will by default apply a solid black mask to this channel which will act as the alpha channel. 15. Open up the 4th appropriate cube map face in Photoshop (in this examples case the alphaXp.bmp), convert it to Greyscale as before and select all the image and cut/copy it. 16. In the Channels panel with the new Alpha channel selected as the Active Channel, paste the image into this channel. You should see it appear similarly to what is shown below when only the Alpha channel is toggled visible. 17. At this stage, toggle the RGB channels on and the Alpha channel off and save the resulting texture as a DXT5 .dds texture. I have shown my nVidia dds configs below during the saving process. When saving the .dds texture, make sure to name them '******' for ease of use later i.e. 18. Repeat steps 7 through 17 another 5 times for each side of the Cube Map and you should end up with 6 .dds textures with your 4 cloud maps appearing on the 4 separate channels named: ******** ******** ******** ******** ******** ******** These are the final textures that will be used in-game. Copy them to your Textures directory inside your mod directory. 19. EVE requires a separate config to know how to handle cube maps. This file can be located anywhere in your mod directory but must be named 'textures.cfg. I always recommend the use of the EVE GUI to edit the configs as no syntax or parameter errors can be made but for this demonstration I will be listing the config structure below as I assume the knowledge and familiarity with EVE's GUI. The Textures config can be found in the TextureConfig panel in the GUI. In this config, you will be required to list the following information: Cube Map = True and paths to each of the cube map faces. i.e. EVE_TEXTURE_CONFIG { OBJECT { name = Mod/Textures/imageName isCubeMap = True texXn = Mod/Textures/imageNameXn texYn = Mod/Textures/imageNameYn texZn = Mod/Textures/imageNameZn texXp = Mod/Textures/imageNameXp texYp = Mod/Textures/imageNameYp texZp = Mod/Textures/imageNameZp } } 20. Once EVE knows to recognise the 6 images as a Cube Map, you can navigate to your Celestial Body's Cloud Manager in the CloudManager Panel in the GUI and add a cloud layer. You can name this layer whatever you wish and input your specific settings for altitude, speed etc. 21. Toggle the MainTex option and input the path to your texture; this will be as specified in the Texture Config section i.e. Mod/Textures/imageName 22. Change the RGBA setting by default to AlphaCubeMap. If done correctly up until this stage, the image path should be displaying as white text. 23. Scroll down the GUI and toggle the 'layer2D' option so that it renders the cloud texture as a graphic in ScaledSpace/PQS. 24. At this stage you can hit Save and Apply and EVE should now render, by default, the cloud map you specified to be in the Alpha channel of your Cube Map. If following my instructions above with regards to the alignment of the cube faces using CubeTheSphere it should be aligned correctly. If using other software or this is not the case, you may need to play around with the sides of which your textures are appearing on the Cube Map. 25. To change the rendering of the cloud map to that of the Red, Green or Blue channels, cycle through the 'alphaMask' option to switch between your 4 cloud map textures. 26. At this stage you should be finished and able to choose between 4 different cloud maps by using only 6 cube map textures. Hooray! From here you can go back into your cloud layers and edit the parameters of them to how you wish to configure your EVE Cloud Layer to appear. ---- For reference, if you were to use 4 separate 8k DXT5 .dds textures for the 4 cloud maps, the resultant total file size would be 170MB. By combining these 4 maps into a single 2k DXT5 .dds Cube Map the resultant total file size is only 24MB... more than a 700% saving! Imgur Album of the above Tutorial Images for your reference: A big thank you and shout out to @rbray89 for making all of this possible with EVE and the continous support that he has given when we badger him with questions. EVE Forum link: I hope that you found this helpful and will be an aid in your endeavour to create better and more efficient visual packs for EVE. If you have any queries, feel free to ask by pinging me with an @Poodmund tag in this thread.
  5. PARA-SCI HIGH-PERFORMANCE ATMOSPHERE PACK For use with KSP 1.2 and the EnvironmentalVisualEnhancements mod Since many of us are sometimes, or always, forced to play KSP on laptops and other devices with weak GPUs or otherwise not optimized for gaming, I present the Para-Sci High-Performance Atmosphere Pack, wherein I have done my best to combine good visuals with minimal graphics demand. FULL PREVIEW ALBUM: Notes: - Most bodies, with the exception of Kerbol and the particularly lumpy minor moons, include a "glow" layer that enhances their appearance at long distances and fades away on approach. - Many of the glow layers make use of the original KSP planet textures; naturally credit goes to SQUAD for these and I advise against attempting to redistribute them or use them for things other than KSP, KSP mods, or KSP fanart. - None of the cloud layers have a "layer3D" (volumetric clouds) component. While this does cause us to miss out on that feature, the numerous large particles it involved rendering tend to be a major performance drain and thus they have been left out. - None of the cloud layers cast shadows either. - All bodies have a maximum of three cloud layers; most have only one. - The pack currently does not include aurorae, noctilucent clouds, or dust storms, although some of these may be added in the future if I feel up to it. - Some textures are the original textures packaged alongside the main EVE installation. Like the SQUAD textures, I advise against violating their licensing terms, etc. - Jool's glow layer uses the beautiful Jool texture painted by @Felsmak. Naturally credit goes to him for that, don't steal it, etc. etc. etc. DOWNLOAD
  6. Pood's OPM-VO (Outer Planets Mod - Visual Overhaul) Latest Release - v.0.3.4 Pre-Release Beta - 08th April. 17 Due to some users having issues with compatibility, please find below a list of the dependencies and the current builds used to run OPM-VO. Please ensure that you are running at least these versions of the dependencies or later releases: Dependencies: EVE: (Release build 1.2-2) Scatterer: (Release build 0.0300) Kopernicus: (Release build 1.2.2-5) Kopernicus.Components.dll:!vUowhKgB!PAIeK8M1KlBOXhcBNglxGTq6MzSiqFxF27fAXYOD8_w (development plugin not included in 1.2.2-5 release) Module Manager: (Get latest release build) Outer Planets Mod: Planets Mod/download/2.1 (Release build 2.1) Suggested Mods: Stock Visual Enhancements: (Release build 1.1.6) - Galileo and I work together to ensure our mods are compatible and SVE gives the stock planets great atmospheric and visual effects. Stock Visual Terrain: (Release build 2.0.2) - The texture pack that's built alongside SVE to make the stock bodies look amazing. -------------------------------------------------------- For all information regarding downloading/installing/using/licensing etc. for this mod, please refer to the Readme. This mod includes version checking using MiniAVC. If you opt-in, it will use the internet to check whether there is a new version available. Data is only read from the internet and no personal information is sent. For a more comprehensive version checking experience, please download the KSP-AVC Plugin. Changelog: v0.3.4 - 08th Apr. 17 - Edited Tekto's & Urlums EVE cloud layers slightly, amended SVE integration due to SVE's new file structure and added in Kopernicus' new Ring Shader effects for all bodies (if Jool rings are present, they are maintained). Kopernicus' Ring Shader update is not incorporated in the latest Kopernicus release yet, however, the patch can be downloaded here to be installed into your Kopernicus directory:!vUowhKgB!PAIeK8M1KlBOXhcBNglxGTq6MzSiqFxF27fAXYOD8_w v0.3.3 - 02nd Apr. 17 - Added Sigma OPM-Tilt support, slight change to Urlum's rim exposure and now leveraging SVE's cloud detail textures if SVE is installed, if not, uses own placeholder texture as before. v0.3.2 - 01st Apr. 17 - Forgot to render Tekto's oceans... doh! Ocean shaders on Tekto have been enabled by adjusting Ocean Alpha values. v0.3.1 - 01st Apr. 17 - Fixed scatterer's configs so they play well with other mods and don't repeatedly add OPM body configs to other body's ones. v0.3.0 - 30th Mar. 17 - KSP 1.2.2 Compatibility update. v0.2.0 - 8th May. 16 - Rebuilt from ground up for KSP 1.1.2; Thatmo work has not been included. v0.1.2 - 11th Jan. 16 - Included support for OPM Tilt and Kopernicus Expansion. Compatibility with KSPRC has been fixed by including updated pqs.cfg file for KSPRC (bundled in distribution). v0.1.1 - 8th Jan. 16 - Forgot to include Scatterer files within .zip (Doh!) v0.1.0 - 6th Jan. 16 - Initial Release - First GitHub commit & beta release --------------------- Original Initial Post: With the release of EVE for 1.0.5 and Scatterer gaining multi-planet support I decided to jump right in and start messing around with configs for OPM as I rarely play KSP without it. As the two mods are still very much in their infancy really with respect to 1.0.5 and their latest releases I am learning as I go and have never shown any of my previous tinkerings with EVE in the past on these forums (I used to run a modified AVP-I, AVP-EoO and KSPRC mashup in previous versions of KSP). I initally started working on Tekto as it has a pretty crazy atmosphere in OPM canon. Current progress can be seen here: I also have very hazy mist clouds rumbling over the lowlands that look a lot like heat haze up close. These are very much still WIP and I am still learning new tricks/techniques with EVE's new volumetric cloud options. The look I have gone for is a very chaotic, dense atmosphere that is suffering from a sever over abundance of a toxic gas that could be generated from underwater plant life or similar. After visiting MatoroIgnika's Twitch stream he commented to me that he loves Thatmo and how it should look like a Triton analog, so... next on to Thatmo! Like Triton, Thatmo has a very think atmosphere but it can be visualised from orbit. It is very hard to convey through screenshots but a very thin, wispy cloud cover has been added, viewable from orbit. Down on the moon's surface, clouds are visible somewhat more than they are from orbit purely for the fun aspect of actually seeing the atmosphere present. Triton's albedo coefficient is one of the highest in our whole solar system and so I decided to make Thatmo very reflective and bright to convey the shiny, ice like nature of the moon. Its pretty blinding down on the surface. As the surface of the moon is refracting light through its ice layers I have also introduced a chromatic aberration-like quality, visible when in orbit. Finally at this point I have been tinkering heavily with texture generation for Gas Giants (as OPM has 3 of them!) using curling noise for procedural fluid flow to try and create some really interesting base texture maps for the gas planets. It has been pretty laborious switching between Linux running the generations and Windows for Photoshop texturing (I don't like GIMP at all) but its getting a lot easier to manage now I am use to the process. I should be able to utilise this technique to also create completely procedural cloud texture maps also with a bit of work that could range from thick stormy stuff ala Venus down to very light, high atmo wisps. As you can see there are a lot of different style outcomes using the same texture by changing the input parameters. Let me know what you like and what you think would suit each gas planet as I can create a variety of effects. Generation takes around 20 minutes and then I have to wrap a cubemap back into an rectilinear texture for use within KSP. All of this is really in its infancy and I created this thread as a place to store my ongoing efforts whilst also being able to receive some feedback. Progress may come in fits and spurts around work; I get two weeks off over the Christmas period I may be able to cram a load of texturing in. Depending on how far I continue the final piece of the long-term puzzle would be re-texturing the base moon textures to hi-res variants. Feedback is greatly appreciated and any thoughts or critiques are appreciated, even though at the moment all you are able to look at is screenshots. Once things become more substantial I will upload configs and textures in a pack for testing out within KSP. At this point I will apply a suitable license. Update 12th Dec. 15 - Been doing a little tinkering to test some different variables in the texture generation and thought... "why not upload some short clips on Steamable?" So: Sarnus - Test WIP Neidon - Test WIP Update 3rd Jan. 16 - Porting Tekto to new EVE syntax. Fog on Tekto 1 - Showing fog and dust clouds at low level. Fog on Tekto 2 - Showing the post processing depth buffer level at low level. Update: 6th Jan. 16 - v0.1.0 Beta Release - Initial Release Update: 8th Jan.16 - v0.1.1 Beta Release - Included forgotten Scatterer files and bundled MiniAVC plugin for automated update checking. Update: 11th Jan. 16 - v0.1.2 Beta Release - Added support for OPM Tilt and Kopernicus Expansion and bundled an updated file for KSPRC to allow for EVE Cloud Layers on Gas Giants. Update: 8th May. 16 - v0.2.0 Beta Release - Rebuilt from ground up for KSP 1.1.2; Thatmo work has not been included and Sigma OPM-Tilt compatibility needs to be added. Also work needs to be done on Tekto's Scatterer effects and so changes to the stock Gas Giant's normal map texture that all the OPM Giants use. Update: 27th Aug. 16 - Updated dependency mod links. Mod will be updated to KSP 1.2 post release. Update: 30th Mar. 17 - v0.3.0 Beta Release - KSP 1.2.2 Compatibility update. Update: 01st Apr. 17 - v0.3.2 Beta Release - Fixed scatterer's configs so they play well with other mods and don't repeatedly add OPM body configs to other body's ones & forgot to render Tekto's oceans... doh! Ocean shaders on Tekto have been enabled by adjusting Ocean Alpha values. Update: 02nd Apr. 17 - v0.3.3 Beta Release - Added Sigma OPM-Tilt support, slight change to Urlum's rim exposure and now leveraging SVE's cloud detail textures if SVE is installed, if not, uses own placeholder texture as before. Update: 08th Apr. 17 - v0.3.4 Beta Release - Edited Tekto's & Urlums EVE cloud layers slightly, amended SVE integration due to SVE's new file structure and added in Kopernicus' new Ring Shader effects for all bodies (if Jool rings are present, they are maintained). Kopernicus' Ring Shader update is not incorporated in the latest Kopernicus release yet, however, the patch can be downloaded here to be installed into your Kopernicus directory:!vUowhKgB!PAIeK8M1KlBOXhcBNglxGTq6MzSiqFxF27fAXYOD8_w Whad'ya think?
  7. Good morning everyone. I have started a new 1.22 game (going to wait for teething trouble observations before 1.3) and as expected EVE just slogs my potato PC to a crawl, so I am playing without clouds. However, before I try to get to Eve I thought I would ask; has anyone heard of a mod for ONLY Eve? Landing on Eve (the OPM Triton analog too I guess [name escapes me]) would be so much more mysterious and exciting if there were dense clouds there, but I can't abide the slow down for Kerbin operations that come from EVE, Is there a possibility for an Only Eve EVE?...
  8. Wiki and Kerbalmaps say the peak is at 7526 m, but I've managed to land a rover there and got to 7541 m, 15 m higher than the official value. I'm using full terrain details. I wasn't aware of these changes, are they new? I'm using Realistic Atmospheres and pressure on top was 0.943 atm.
  9. Hi I'm not quite new to the forums, but haven't been active a lot. Now I decided to share some of my epic missions with you. I'm playing this almost vanilla, just with some minor mods for precise planning, better visuals and of course, to make it more plausible: life support. An (almost) complete mod list: Distant Object Enhancement Environmental Visual Enhancements Kerbal Alarm Clock KAS KIS Persistent Rotation PlaneShine SCANSat scatterer Stock Visual Enhancements TAC Life Support MechJeb The pale blue dot, circling the green giant has captivated generations of Kerbals since the beginning of astronomy. With the beginning of the space age, Kerbalkind got to taste what it could be to visit it's mysterious twin for the first time. But to find out, what it would look like to visit the beaches of this far off world, there was alot lot learn, a lot of progress to be made, and a lot of mistakes that were awaiting brave pioneers. The KSP, the Kerbal Space Program, as it was officially named had quite some successful missions: Landing a unmanned UAV on Duna: Duna Direct: The Ravenstar: The Rolling Thunder: But all these missions served only one purpose: the get to Laythe one day. Finally, KSC accumulated enough bright minds, technology and of course funds to start with this humongous undertaking. Part I: The construction of the DSV Hermes
  10. Hi, I'm not new to KSP, but I'm still having troubles. I want my planets to look like in Matt Lowne's videos. But it's obviously not as simple as just enabling EVE, Scatterer, etc on CKAN. The mods I'd like to use are: EVE, SVE, SVT, and Scatterer. I don't really care about any other mods, I simply want my universe to be moar realistic that the lame stock planet graphics. So, when I enable EVE followed by Scatterer, I get the realistic atmosphere look I wanted. But when I go to enable SVE, the "Apply changes" button is grayed out. If I enable SVE first, it says it includes EVE, however when I do this I get SVE but still have the lame atmo-less look to Kerbin, Eve, and Jool. This is just one example. Then we have stuff like: "SVT (for Windows)", and "SVT-High Res". No indication of what the differences are, what dependencies they have, if they are compatible with SVE, etc. I have Windows, and I want High res. But it won't let me pick both! How on earth do I know which to use? And what does it mean when one of the mods in the list turns red for a second? For each mod, it seems there are several secondary "config" and "component" mods with them, and others I have to select from. I have no clue which of them to pick! This is probably part of my problem. This is all very annoying because every time I have to update KSP or build a new install, I have to remember all the same stuff I did last time... before I realize it looks totally different than last time! (Why can't they just make standard things like good visual mods stock?) Now before you suggest it, yes, I know I can just download the individual mods and apply them one by one. Problem is, I can't get the mods to work out correctly seeing as some parts of them override each other. I also don't have the time to be re-doing this all over again for every update. So I use CKAN, for no other reason than that! Can someone help me understand what all these little mods alongside SVE, Scatterer, EVE, etc are, and tell me what I need to do in order to enable all the main mods at the same time? Thanks
  11. This mod adds cloud configs for OPM, you can get it here,'s OPM configs for Sci-Fi Visual Enhancements It requires Sci-Fi Visual Enhancements,You can get it here vvvvvvvvvvvv
  12. Okay, I'm having a issue with SVE and EVE. I've installed everything your supposed to, (even the recommended mods), and the EVE clouds won't show up. Only the scatterer atmosphere. I've installed the regular SVE itself and the textures itself. I have reinstalled modulmanager. I have installed EVE on it's own without SVE. The EVE I installed is also NOT the config one, as stated in the github. I have a Dell XPS 8700, with a Intel i5-4460 core, and I have a Nvidia GeForce GTX 1060 6GB, if that information will help at all. Does anybody know what's going on, or what am I doing wrong?
  13. My newest videos of a Moho transit and a simultaneous Eve and Mun transit. Used Tarsier Space Tech.
  14. I finally managed to build a reasonable craft for Eve Space Program that can get to Eve orbit with about 1300-1400 m/s dV left. In career mode, with only Tier 3 and 4 parts. Craft file here, uses OhioBob's Eve Optimized Engines. After several attempts, my best effort is in this video here. The biggest challenges of the current incarnation of the Eve Space Program mod are the lack of biomes outside of the KSC, and the distance of most survey contracts; the KSC is a quarter of a world away from where the game puts those surveys. This leaves part tests, science grinding around KSC, and a full fundraising campaign strategy (25% of reputation going to funds) to pay for building upgrades. Otherwise I'd be using a lot better parts for this craft. As it stands, the only remaining source of decent science is Gilly, and I can't reach that and get back on 1400 m/s. I didn't do any dV math really; just tried plotting to Gilly's orbit needing 1425 or so m/s, and came up short just by 20+ m/s. That being said, I remember someone saying that ascending from Eve's surface to orbit needs a launch profile that goes straight up for a large part of the ascent, then starts the gravity turn very high up. With this craft I find I can start my turn just around 20 km, and also before staging away the last of the Adam engines and going to my first non-EoE; the Swivel, close to 35-40 km. Then some careful throttling and I can get to about 1400 m/s orbit speed before staging away the Swivel and going to my Terrier, finally closing my orbit with maybe 2/5th of my fuel. What would be a better ascent profile for launching into Eve orbit? Where to start turning away from vertical? At what altitude and at what speed should I have a pitch of 45 degrees? If you try this craft, note that Eve Space Program's launch pad is only at 450 m altitude, and I'm using tank priorities and decoupler fuel crossfeed to use a hybrid of onion staging and asparagus staging, so watch the tank levels on ascent. [Update 15 APR] There's so much good advice here I can't mark any one answer as correct. I upvoted all of the good answers and gave out likes.
  15. Here is pics: (Mechjeb hates me and doesn' tell me my Dv stats)
  16. I am about to land on Eve and want to make it extremely efficient!
  17. I might be getting a new graphics card soon, so in the mean time, or if I don't get it, are there any tips to have a higher FPS when you're using EVE and scatterer?
  18. Does anyone remember a really old Scott Manley video explaining why specific impulse is measured in seconds? Or remember a follow-up making fun of YouTube's caption generator? Seeing as it's now April First UTC, I can now publish the story of the Purple Space Program. Inspired by YouTube's caption creator and raised by @GregroxMun's Alien Space Programs, the brave purples of Eve take their first faltering steps into space. Barely. I'm Not Manley.1 Fly Safe! [1] No matter how you interpret that, I think it's funny!
  19. So I've just downloaded my first Graphic mods - EVE + Scatterer. They work but.. look a bit glitchy. Is it just me and it looks absolutely normal or..?
  20. Anyone want to take on the tough challenge of making an Eve lander for 1.1.x? We had a thread around 2 years ago that came up with some excellent designs for Eve landers and I thought it was time to revive this for the current version of the game. Challenge description - Build the lightest Eve Lander possible! Category 1) Take off from anywhere on Eve and reach a stable orbit. Category 2) Take off from an altitude of under 100 meters and reach a stable orbit. Challenge rules: You need Kerbal on board who can exit and enter the vehicle prior to take off. What would be the point of landing on Eve if you couldn't have a walk around on the surface. No external command seats! That rules out using a seat in a service bay. You'll need to use a lander can or command pod or something similar. I may add an extra category if there is a demand for the use of a chair in a service bay method later. Stock parts and physics only. Exceptions are Autopilot and navigation aids like Mechjeb, Kerbal Engineer etc and any building mods like Editor Extension, Hanger Extension, Infinite offset limits etc. These are allowed. You do not have to transport your lander to Eve. you may use Hyperedit to reach an Eve orbit and the Vessel Mover mod to move your vessel once it has landed, (useful if you want to take off from a specific altitude!) Post screenshots of proof as well as the lander prior to take off. Craft files would be most welcome and videos are optional. Why this challenge? Well, in some ways an Eve Lander is easier to build in this version since v0.9 as you probably only need around 9000 DeltaV to reach orbit from sea level compared to the 12000 DeltaV. However, the journey to Eve is harder compared to earlier versions. Aerobraking is difficult due to the heating effects of the atmosphere and Eve is inclined so it take more DeltaV to get there. This makes building the lightest craft possible an important factor in enabling inter-planetary transfer stages to be of reasonable sizes, especially if you plan on using engine thrust to achieve orbit. Obviously you do not need to build one of these for this challenge but a light lander will help anyone who wants to use a submitted lander to build a craft that is fully capable of a mission to Eve and back from Kerbin. Here is what I have come up with myself: With de-orbiting, re-entry and landing parts attached. With above parts removed, (that are jettisoned at lift off). This weighs 74.220 tons, 86 parts and completes Category 2. It can reach a 100 km orbit from under 100m with 444 DeltaV left over so I think there is a lot of margin left over for better designs! It's a simple asparagus design however the first 2 stages are just fuel tanks with the 3 Aerospikes and 2 vectors all firing from launch. Mixing the engines like this gave me the best balance between TWR and DeltaV. The biggest challenge was ensuring the craft could survive entry into Eve's atmosphere without flipping out as the inflatable heatshield has so much drag it tends to flip the craft out. I realise now that I could have just used the Vessel Mover mod to spawn a saved vessel directly on the surface and not worried about re-entry but this makes this design one step closer to a fully functional Eve capable craft anyway. Download > Good luck!
  21. At this time, i'm almost ready to succeed the reddit w30*2017 challenge in hard mode - launch a ship from Kerbin, land on Eve, mine Ore, take off and bring 300 Ore to Gilly. Still struggling to bring the ship from Kerbin orbit to Eve orbit (in one launch)
  22. Hello, guys! On the older versions of Kerbal Space Program it always worked to install Environmental Visual Enhancements. Now it somehow doesn't work. I see no clouds showing up or anything related to that and I did the same thing like you always do. Please help!
  23. May Someone In The Community Volunteer To Create The Badges Please! Thanks! Hello everyone! I'm Rebooting the old Eve's Rock Challenge. If you want to see the original thread, Click HERE Landing on Eve is simple. Landing a Kerbal on Eve and returning him safely back to Kerbin, however, is the closest you can get to the challenges NASA was facing in the real-world Moon landings. Your rocket need not only be big (though it necessarily will be), but it has to be well-designed to boot: you need to strike the right balance between enough thrust and enough fuel. The surface of Eve is littered with the debris of launchers that were almost good enough. Trying to include any kind of safety margin will quickly inflate the project to ridiculous levels -- and keep in mind that you somehow need to get your lander up from Kerbin and to Eve in the first place, and put it down in Eve's high gravity without creating a debris field then and there. There will be no scoring system and no leaderboard because really, returning from Eve is quite a feat of itself. However, there will be a badge for you to keep once you have completed the challenge. (Badge in Process) And to spice things up a little, there will be several levels of achievement: Level 1, I can do this: retrieve a soil sample from Eve and return it safely back to Kerbin. Level 2, Let's get serious: return a sample from Eve's oceans as well. Level 3, Going all the way: land at (and launch from) an altitude of less than 500m. Jebediah's Level: all of the above, without parachutes, wings, or control surfaces. For Science!: ignore all of the above, but strip-mine at least three biomes for their science and return the results to Kerbin -- in duplicate! Rules & Restrictions: - stock physics - no glitch exploits (do I even have to say this?) - only stock parts, except where I don't care (see below). - part clipping: be conservative. - there have to be pods/hitchhikers for all Kerbals involved. No seat-only lifters. -Multiple Launches are allowed (Please show pictures of every single launch) There will be 2 modes. A stock one and a Modded one. The aerodynamics on Eve has changed quite alot since the old thread, I will enable Part Mods(Info Mods such as Mechjeb/KER counts as stock. I should be able to access your craft file without installing any mods). You MUST Clearly State What Parts Mod You Are Using. Mining on Gilly will be alright, but ramscoops will be not. Mining on Eve itself is not OK. Talking about refueling: in LKO, I will be content if you showcase your solution once. After that, you may resort to magic. No need to actually fly a dozen boring milk runs. However, I do want to see a solution that seems halfways adequate. Don't tell me you'd deliver the fuel a spoonful at a time. About the "For Science!" level: Basically, you have to return two command pods full of experimental results (science containers are explicitly forbidden for this one). Overachievers may also land at sea level without parachutes, but there's no extra points for that: this level isn't about the biggest baddest lander, it's about making a sensible mission. Submission Guidelines: I want to see a well-lit money shot of every vessel involved (ideally, one should be able to recreate your craft from screenshots), and enough material to give me a good impression of what your mission looked like and how it played out. I don't need to see every single maneuver node and all of your twenty asparagus stages in action, but you should provide one picture every thirty seconds or so. Leave the altimeter, navball and resource panel open during ascents, and if you use MechJeb/KER, also keep the delta-V and orbital info stuff on the screen. Launches from Kerbin need not be as detailed, but I want to see that you launched and didn't just teleport into orbit. I reserve the right to request stockified craft files of your vessel as it is awaiting liftoff on Kerbin and/or Eve before accepting your entry. If you use rovers / planes / whatever, please don't go over the top with pictures of your vehicle in action. Of course I want to see how it works (especially how it reaches the ground, and any specialties like entering the water or sumsuch), but for purposes of what you did, a single map view with a few annotations easily beats one hundred pics of a rover between dunes. Please be kind to other people's bandwidth: use a gallery if possible. If you absolutely have to spam a dozen pics in a forum post, have the decency to convert them to JPEG. Short videos of key events may be helpful, but the emphasis is on "short": seconds, not minutes. Provide the following data: - weight and part count of the vessel on the launchpad - weight and part count awaiting liftoff on Eve - the approximate price tag of your entire mission, if at all possible - game version - mods used (Please include info mods such as Mechjeb) - tell me how you found your landing site. "I tried until I got lucky" is perfectly alright, but inquiring minds want to know. - if there's anything that your are especially proud of, be sure to point it out (provide a direct link to a picture if applicable). - please also mention the things that didn't work out so well / required a lot of saveloading / you would do different next time. PEOPLE WHO MADE IT Stock: Modded:
  24. Reach orbit in high gravity environment! Basically, this challange is just about getting orbit efficiently on Kerbin. However, with gravity multiplier cheat, it won't be easy! In these harsh environment, haul fuel/payload to orbit as much as you can! Rules: 1. No cheats allowed, aside from the gravity multiplier cheat. - Entrants should keep the gravity cheat on throughout the entry, with the multiplier given by each level. 2. No kraken drives, no clipping of functional parts. 3. The orbiter can either be manned or unmanned, refuel it in any way if you can. (Docking is allowed as well) 4. Reach stable orbit out of the atmosphere, using any ways fitting in the rules. 5. Mods allowed: - Part mods with reasonable chemical tanks/engines only. (No OP tanks/engines or other propulsion concepts) - Visual mods like Scatter, SVE and such. - Piloting mods like Mechjeb, kOS and such. - Editor mods like Part Angle Display, Editor Extension Redux and such. (Finished product should be stock craft with it) Any other mods aside from these are not allowed. Entry Submission Rules: 1. An entry should contain screenshots or videos to prove the completion. Imgur or Mission Reports is recommenfed. 2. At least one of the screenshot should contain debug screen indicating that only gravity cheat with appropriate multiplier is on. More than once is recommended. For video submissions, show it once and capture continuous process to orbit in the video. 3. Screenshots should include craft in VAB(for total mass), on LaunchPad, liftoff, subsonic flight, gravity turn, supersonic flight, high atmosphere flight, reaching apoapsis, finishing orbit and craft on orbit and more if you want. Scoring Scheme: 1. Score is given by (Payload mass) / (Total mass) - 'Payload' means parts got to orbit which is neither fuel tank nor engine, and fuels left on the orbit. Crew cabins count as payload, but not any other multipurpose fuel tanks like wet wings. - 'Total' means every parts launched for this mission. This includes pre-launched refueling ships in orbit. Levels: I. Moderate gravity (1.7g): Reach orbit on Kerbin with gravity multiplier of 1.7. (Range of 1.68g~1.7g is allowed, due to the sensitivity of the scroll bar) I1. Spaceplanes (too) Powerful Reach orbit, using jet engines. Every bits you launched should reach stable orbit. I2. Heavy Rocketry Reach orbit without jet engines. Isp. Heavily Usable Rocketry Reach orbit without jet engines, with every bits you launched reaching stable orbit! (Yes, this one is specially aimed for conquering a *punishing* body) II. High gravity (3g): Reach orbit on Kerbin, with gravity of 3g! 2.88g~3.0g is allowed. III. Super gravity (5g): Reach orbit on Kerbin with gravity of 5g! 4.98~5g is allowed. V. Hyper gravity (10g): Use any possible way, to reach orbit with Hyper gravity of 10g! (Only 10g is allowed, since it's at the end of the scroll bar) (This should be impossible, though let's see if I'm wrong) Results: I. Moderate gravity (1.7g) I1. Spaceplanes Powerful I2. Heavy Rocketry Isp. Heavily Usable Rocketry II. High Gravity (3g) 1. MarvinKitFox - Asparagus-staged Mammoth Rockets to 11k X 14k orbit. (Score pending) III. Super Gravity (5g) V. Hyper Gravity (10g) + My entry will be up soon! (Though I doubt I need one)
  25. Hello! I'm designing a mission to eve, and it'd be great if I have a SSTO for this. I know that there were several SSTOs, but I want one which doesn't need any precision manuever and fuel mining time. It'd be better to have long range for science purpose. Is there ANY way to do that? EDIT: I mean, completely stock SSTO without debug-cheating in flight. Other than that anything is okay.