OhioBob

Going 3x wouldn't make much of a difference. The increase in delta-v is roughly equal to the square root of the resize factor. JNSQ is about 2.66x bigger than stock, so if you went to 3x, the delta-v would increase by only about SQRT(3/2.66) = 1.06 times. One way to think about it is, how much more delta-v do you want it to require? Say that instead of JNSQ's 4900 m/s to orbit, you want it to be about 6000 m/s. Then you would need a resize factor of, 6000 / 4900 = SQRT (ResizeFactor / 2.66) ResizeFactor = 2.66 * (6000 / 4900)2 = 4x

@LNugget315, first off, you shouldn't have two versions of ModuleManager installed. Secondly, if you have a problem with a planet pack not loading, you should take that up with the maker of the planet pack. Problems are much more likely to be with the planet pack or how you installed it than with Kopenicus. And neither of those problems are the responsibility of the Kopernicus developers. If the planet pack maker determines the problem is with Kopernicus, then they should be the ones to report the problem.

JNSQ vs. Stock @ 2.5x with SD are very similar, though JNSQ should actually be a little harder. Both Kerbins have the same surface gravity, but JNSQ's Kerbin is slightly bigger and more massive - 1600 km radius vs. 1500 km. Getting to low Kerbin orbit in JNSQ typically takes about 4900 m/s delta-v. Here's more information about how JNSQ is sized if you are interested (warning !- math stuff):

All the planets are just made bigger, there is no resizing going on. Check the planet information in the Tracking Station - the radius of Kerbin should be 1600 km. You're not still getting stock Kerbin are you? If it looks like stock Kerbin, then it's stock. If so, you've installed something incorrectly.

@N3N, you can do either - edit the config or use the patch - the result should be the same. But as you say, you must remember to delete the patch should we release an update that includes the fix.

No, it is not intentional, nor is it normal. Do you perhaps have Distant Object Enhancement installed? It can pretty much blot out the stars depending on your settings.

I was not aware of all the problems you outline, so thank you for explaining so clearly. The changes you suggest look good to me. I will likely implement them, though I don't know when an update will be released. In the meantime, the following patch should work. @PART:HAS[@MODULE[ModuleAsteroid]]:AFTER[JNSQ] { @MODULE[ModuleAsteroid] { @density *= 9.8637 //JNSQ already multiplies by 3.3456, so together we have 3.3456 * 9.8637 = 33 @maxRadiusMultiplier = 1.67 @minRadiusMultiplier = 1 } }

Based on your estimated JNSQ masses and radii, the densities are really low -- about 200 kg/m3 or less. For the masses given, the radii should probably be about 40% of the shown values for the densities to be realistic. Given how much uncertainty there is in these numbers, it might not be worth changing anything. After all, even if we did decrease radius to increase density (while leave mass unchanged), the asteroids wouldn't be any easier to move.

The reason I'm asking is because I'd like asteroids in JNSQ to fall within a realistic range of densities.

Do you happen to know what the range of radii are?

JNSQ is not updated for any scatterer versions 0.08+. You should use scatterer 0.0772.* * Unless the most recent version(s) of scatterer has been updated to be backwards compatible with older configs, but the last time I checked this wasn't the case.

We don't officially provide support for KSP versions older than 1.12.1. That being said, it could be that your terrain detail needs to be reset. Delete the file settings.cfg in you root KSP folder, restart the game, and reselect all your settings. I suggest using terrain detail GPP_High.

That's not the way we'd like it to be, but it is the way it is. The file you reference does include the line JNSQTag = True, so I'm not sure what the problem is. I've never noticed the atmosphere being deleted.

I don't know what that means. By "eve" do you mean Environmental Visual Enhancements? And what do you mean that it is saying this? As far as I know, EVE doesn't talk. JNSQ comes with all the EVE configs and textures that it needs. That's why I suspect either an installation error or something else conflicting with it. A clean install with just JNSQ, its dependencies, and EVE should work if installed correctly.

I have no idea. There are too many mods out there to keep track of. The usual procedure is to remove all mods except JNSQ and its dependencies, then check and see if it works. If so, then start adding mods back one at a time until you find the one that causes the conflict.

I don't know how asteroid mass is determined. I only wrote the part of the config that determines where and how many asteroids appear. I believe the changes to the asteroid module were done by @JadeOfMaar. Perhaps he can explain it. Sounds to me like you may have an installation error or some type of mod conflict.

Using the wrong scatterer most likely.

If you decide that you want to give the real scale version of RSS a try, I've made a very slimmed down config that rebalances the stock parts to work with it. It changes part masses, propellant densities, and a few other things so you can build realistically sized rockets at real scale using stock parts. You don't need all the realism mods, so it's very easy on your computer. I made it originally for a 10x version of JNSQ, but it should with any real scale planet pack. If you want to give it a try, here it is: https://www.dropbox.com/s/ro5zb12tszg905r/PartRebalancer10x.zip?dl=0 (edit) I also recommend using BetterSRBs in combination with the part rebalancer, though it's not needed.

Freezing and crashing problems have been reported frequently since the last release of GPP. But I've only heard from those that have had problems, not from those who haven't. Therefore, I have no idea how widespread the problem is. My own personal experience is that I've never had a problem and have been unable to recreate the bug. Though, granted, I have not played extensively. If there is anybody who has been playing GPP successfully without the reported freezes and crashes, I'd like to hear from you. Please post a reply.

Neither GEP nor GPP have been tested with AVP. With EVE and scatterer configs it's pretty easy for one mod to mess up another, so I'm guessing there's likely a conflict of some sort. Try removing AVP and see if that fixes the problem. If so, then you're probably just not going to be able to use GEP, GPP and AVP in combination. It's something I might be able to fix for a future release, but it will time to diagnose and correct. Instead of AVP, you might consider using Stock Visual Enhancements. GEP and GPP were both made to work with SVE.

Why not just use what comes with JNSQ?

You don't have to write anything. The stuff in the ReadMe is for those who want to install GPP_Secondary with some unique primary star system that requires Ciro's orbit to be modified. Since you want to install GPP with the stock sun, then none of that applies. GPP_Secondary should work fine as is, you just have to install it correctly. Since you want the stock sun as primary, then you need to install GPP, GPP_Secondary and GEP, and, of course, you also need GPP_Textures. If done correctly, you should have the stock solar system as primary, Ciro orbiting the Sun, and Grannus orbiting Ciro. No star should orbit Grannus. Since it's not working you, it's likely something was installed incorrectly. The folder structure for GPP and GEP can be a little confusing. For instance, in the GPP download the folder structure for GPP_Secondary is as follows: OptionalMods GPP_Secondary GameData GPP_Secondary It is the second GPP_Secondary folder that gets installed into your GameData folder, not the first. The best thing to do is drill down until you find a "GameData" folder. Then drag and drop the GameData folder from the GPP download to your root KSP folder. This should correctly merge all the necessary folders and files into your KSP installation.

No, but there is third-party support. Somewhere in this thread is a link.

I'll have to look and see if I still have it. I don't remember how user friendly it is, because it was never made to share. If I find it, I'll send you a private message.

I rewrote the spreadsheet that I use to create atmospheres. And when I added the configs to make it possible for JNSQ, GPP and GEP to all be used together, I just thought the time was right to redo the atmospheres in all three planet packs so that they're all made to the same standard. The surface conditions are unchanged, but the temperature and pressure curves at altitude are a bit different. In most cases probably not enough to really notice a difference. But many of the heights changed.