OhioBob

I don't think that's a glitch, it's just the way it works. It looks the same for me.

UPDATE Version 2.0.2 Changelog Changed internal name of 48-8S Asp, version 2. Added optional config to optimize engines for even higher atmospheric pressures. See opening post for download link and instructions. The internal name change shouldn't break saves, but any vessels built using the Asp engine since the last release will have the appearance of the engine reverted to the old art style. The optional config decreases engine expansion ratios further to optimize engines for use on planets with atmospheric pressures near 10 atm. The increase in high ambient pressure performance is only marginal, but every little bit helps. This config is designed for use with mods such as Realistic Atmospheres, which increases Eve's sea level pressure to 10 atm, or planets such as Tellumo from GPP.

@lunaris69, you can probably just remove GPP_Renamer from GPP, though I'm not sure what that might mess up if you do it mid-game.

Which is why I really like this mod. You and I seem to have a very similar philosophy when it comes to parts. I'm generally not a big fan of part mods, but there are a few gaps here and there that are just begging to be filled. I think you've done a nice job with this mod addressing those issues. Thanks for that. MissingHistory and BetterSRBs are really the only part mods I use anymore.

Thank you so much. This feature particularly has been something I've been anxiously awaiting.

I didn't know kerbals sank on Tarsiss. I just know that we gave the oceans realistic densities based on the type of liquid it is. Tarsiss is methane, so it has a specific gravity of 0.423, and Hadrian is nitrogen, so it has a specific gravity of 0.807. The lower the specific gravity, the more likely it is an object will sink. The lower density of the liquid along with the low surface gravity also means you should be able to dive much deeper on Tarsiss and Hadrain then you can on Gael (assuming part pressure limits is turned on in the difficulty settings). On Gael the maximum depth is only 408 meters, and on Tellumo it's only 215 meters. But on Tarsiss and Hadrain you should be able to easily dive all the way to the seafloor.

This using Sigma Cartographer: Lowest Point Highest Point Latitude Longitude Elevation Latitude Longitude Elevation Agrippina 26.1425 168.0470 -2 -62.5920 19.0220 628 Argo -44.0335 118.2130 0 -57.3925 -117.1580 2214 Augustus -59.0890 29.6925 0 -34.0680 161.1115 5613 Catullus 69.6815 -5.7505 -27 -75.8450 -15.9685 15883 Ceti -76.8140 -176.1335 0 -17.4700 171.8105 4182 Eta 58.8865 -38.5925 0 41.2845 -96.4080 719 Gael -45.2135 -43.9249 -1699 6.3535 168.0115 6377 Geminus -67.3175 -74.8830 0 14.9415 2.3730 4041 Gratian 79.9805 99.3735 0 -16.4660 159.1700 5792 Hadrian -63.6135 174.3740 -1560 -70.7520 -41.3965 4242 Hephaestus 67.9075 -19.2680 0 40.7390 166.4650 5737 Hox -39.6280 -117.4120 0 27.1425 -133.7675 4866 Icarus 31.4650 144.5200 0 3.0345 50.0265 3039 Iota 38.4975 -73.5625 0 27.0705 87.7150 1778 Jannah 2.3870 -48.9495 0 19.1325 45.2330 3160 Julia -37.5295 -20.0225 -2 45.4390 67.4115 488 Leto -63.5450 2.4055 0 -4.0400 -122.1345 2677 Lili 39.1225 -171.5275 0 -0.4275 89.2975 6005 Loki -16.6510 34.0895 0 59.4385 -118.4765 4934 Minona -39.4240 -109.4135 0 8.9190 -162.8385 4068 Muse 59.7780 32.5420 0 -36.7150 -147.7190 4353 Narisse -54.9405 18.5515 -4 49.1050 -22.6760 1050 Niven -13.5720 100.0195 0 -37.0000 -153.8525 7407 Tarsiss 48.2500 56.8345 -1615 60.2055 -28.2700 3626 Tellumo -38.9985 -71.0275 -3894 -53.3495 125.5075 13428 Thalia -1.3290 -70.6090 0 -43.1540 13.5395 5753 Note that Cartographer scans the surface of celestial bodies in a finite grid pattern, so it could be off a tiny bit in the exact location and magnitude of the highest and lowest points. I have no recollection of what Hadrian use to look like. I do remember that it didn't have an ocean in the very earliest versions of GPP, but it looks like it was changed in v1.0.2. The GitHub release archive only goes back to v1.1, so I know of no way to retrieve the old version of Hadrian.

There's delta-v data included in the download, just look for GEP_deltaV.pdf in the .zip folder. But it's not in the usual subway style. A subway map doesn't work well when GEP is installed as a secondary system, because, in that case, there is no defined starting point. So instead the information is provided in a series of tables. What you need should be there.

Sounds like something is wrong with your installation. But since you've given us absolutely none of the information needed to diagnose your problem, there is really nothing anybody can do to help you.

UPDATE Version 2.0.1 Changelog Added new part (48-8S Asp "version 2") as required for KSP v1.6. See opening post for download link and instructions. Eve Optimized Engines is unchanged for KSP v1.5.1 and earlier. When used with KSP v1.6, the 48-8S "Asp" engine will now have the appearance and variants of the remodeled 48-7S "Spark" engine.

@Cyrus Playz, I see you are trying to use Kittopia with a plant pack. Maybe the problem is with your configs. Does Kittopia work for you in stock?

If you're trying to do it with PQSmods, I'm not sure that's possible. I don't know of any height mods that allows you to target specific latitudes, such as the ice caps. Your best bet might be to add a second height map. The height map should be black all over except for just the areas that you want the change, i.e. the ice caps. Whatever height detail you draw into the height map will be added to the stock height map. So if you draw in hills, or whatever, they'll be added on top of Kerbin's flat ice caps. To get the new height map to execute, you'll need to write a config that adds it in. Probably something like this: @Kopernicus:AFTER[Kopernicus] { @Body[Kerbin] { %PQS { %Mods { VertexHeightMap { map = path/heightmapName offset = 0 deformity = 1000 scaleDeformityByRadius = False order = 20 enabled = True name = _IceCaps } } } } }

As far as I know, we plan to continue version updates. I heard some chatter about releasing a 1.5.1 update weeks ago, but I don't know what the hold up has been. Maybe we put it off long enough that now we're just waiting for 1.6. The current version of GPP works in 1.5.1 just fine. Just ignore any messages about incompatibility.

First question, did you install it? KittopiaTech is a Kopernicus addon that must be downloaded and installed separately. If you did install it, then accessing it is done per the instructions:

I like doing star biome maps. It gives purpose to putting a vessel into a polar orbit around the star to reach new biomes. And there's no reason the spaceAltitudeThreshold has to be placed dangerously close to a star. Place the threshold high enough that it's possible to collect science "in space low" using a vessel with adequate thermal protection. This again gives purpose to a new mission type. That being said, to answer your question, yes, a biome map can have just one biome. Just make the map one solid color. But you're not saving all that much file size by making it a single color versus multi-color. Also, if you make the biomes something simple, like different latitude bands, you don't need much resolution. So just make the biome map small, perhaps something like 512x256 or even smaller. But if you want just one biome, I don't think you even need a biome map. Looking at sun's kittopia dump, it doesn't have biomes. It appears that if there is no biome map or biomes, it behaves like it has just one global biome.

Mun's orbit around Kerbin is perfectly equatorial, but your parking orbit around Kerbin is not. The launch pad is just very slightly south of the equator, which means you'll end up in a very slightly inclined orbit around Kerbin. So a trajectory that takes you to Mun could end up placing you in an inclined orbit around Mun. However, my experience is that the inclination typically isn't all that much; 50 degrees sounds like an awful lot to me. There are a couple solutions. One is to make sure your orbit around Kerbin is perfectly equatorial before performing your transfer burn. You can also perform a midcourse correction as @Plusck describes. Although a midcourse maneuver can correct most error, it still doesn't assure that your orbit at Mun will be perfectly equatorial. The final piece to the puzzle is this: When you perform the midcourse correction, make sure the periapsis of your approach trajectory is located exactly in the plane of the target orbit. This assures that when you reach periapsis and have to perform your orbit insertion burn, you'll be passing through the plane of the orbit of your space station. You can, therefore, add a normal/anti-normal component to your insertion burn and correct the plane at the same time. If properly executed, you should be able to match the orbital plane of the space station with very little error.

I suggest not changing anything in the GEP files themselves. Just make a .cfg file that looks like the following, change the numbers you want to change, and drop it somewhere inside your GameData folder. Before changing the referenceBody to Archangel, make sure that Archangel is indeed the star's internal name and not just the display name.

I know nothing about how After Kerbin is configured, so I can't answer that. But GEP should be able to be inserted into any system that has a star named "Sun" (internal name, not display name). As long as there's a star with that name, Grannus should orbit it. However, that doesn't necessarily assure that GEP will blend nicely with the other planet pack. If you add it to a system that already has multiple stars, Grannus may just get in the way and interfere with other stars. It might still function, but it could destroy the aesthetics. Your best bet it to just try it and see what happens.

Those types of changes are not happening. GPP is already complex enough with all its different installation options. Trying to add anything more is just asking for trouble. Aside from minor updates and bug fixes, GPP is complete. The development team has no further motivation to work on it.

UPDATE Version 1.0.1.3 Changelog Fixed incorrect naming of Nodens in resource configs for GEP_Primary. Increased Sirona's atmosphere to 550 km, added bottom layer of rapidly increasing pressure and temperature. Replaced HazardousOcean with HazardousBody.

I'm not sure what you mean exactly, but we didn't get anything from Duna or any other stock bodies. Pretty much everything about GPP was created from scratch. "Gael" is just a display name. Internally it is named Kerbin. So there could be some places in the game where you might see the internal name Kerbin. It's a minor glitch that's not worth the effort to try to fix.

Yep, that's normal. If we were to do custom science definitions, there are literally thousands of descriptions that have to be written. No one wants to do that, so it hasn't happened and probably won't. Some have tried but all have failed.

I see all the bodies listed except Lili, Agrippina and Julia. I don't know why Lili is not there, maybe too small. Agrippina and Julia were late additions, so we probably just forgot to add them; probably should. Gael is listed as Kerbin. Gael is just a display name, internally it is Kerbin. The NEEDS[!GPP_Secondary] means the configs will work only when GPP_Secondary is not installed. I don't know why Planetshine isn't working for you, unless you have GPP_Secondary installed. The configs are there in the GPP folder, and it's my understanding that Planetshine is working in 1.5.1.

What version are you using? If 1.5.0, there's a bug in Kopernicus that causes this. The only thing you can do to fix it is upgrade to 1.5.1.