OhioBob

UPDATE Version 1.6.7.0 Changelog Adjusted scatterer to reduce gas giant brightness. Adjusted time warp limits for new atmosphere heights. Fixed problems with launch & tracking sites: Added map decal for Nye Island. Repositioned GSC map decal to unbury west end of runway. Woomerang no longer underground. GSC no longer underground at 10x scale. Flattened area around Island Runway at 10x scale. Updated MechJeb runway elevations. Revisons to KerbalKonstructs: Updated all KK configs and fixed problems. Resized & repositioned GSC map decal for KSC++. Disabled KK launch sites for GPP_Rescale. Revisons to terrain detail presets: Fixed typos and added missing presets. Fixed conflict with JNSQ (JNSQ now includes GPP when both installed). Added preset names to localization. This update is mostly bug fixes from the previous release. When upgrading to v1.6.7.0, you should: If using v1.6.6.0 with GPPpatch1660-2, delete the patch from the GameData folder. If using KerbalKonstructs, delete the contents of the folder, GameData/KerbalKonstructs/NewInstances/. You should be able to safely upgrade from v1.6.6.0 to v1.6.7.0 without breaking existing saves. Note that the expanded and alternate launch sites (created using KerbalKonstructs) are disabled when using GPP_Rescale. The reason for this is that the sites aren't properly rescaling, and it's simply not worth our time and effort to fix them at this time. We're currently working on GPP v2.0 in which the alternate sites are being redesigned. We're therefore putting our energy into making sure v2.0 works rather than fixing something that is going to be replaced anyway. KerbalKonstructs can still be used with GPP_Rescale for the placement of anomalies. Be advised that this version of GPP is compatible with scatterer only through v0.0772. Newer versions of scatterer may not work. DOWNLOAD

If Space Dust works like other resource mods I'm familiar with, then it likely distributes resources randomly if no specialized support is provided. Perhaps @Nertea can verify for us.

I don't know what SpaceDust is, so at this point in time I'd have to say I'm not aiming for that.

Thanks for bringing this to my attention. There was a problem in which the west end of the runway was buried, so I corrected this in the last patch by raising GSC several meters. Unfortunately I failed to notice that this raised much of GSC above the terrain. I've updated the patch to fix this. GSC has been returned to its original elevation and instead the problem of the buried runway has been fixed by moving GSC slightly east. As far as the KK stuff goes, I know nothing about that. All the KK stuff is by @JadeOfMaar.

Neither GPP nor GEP have been tested with JNSQ while Ad Astra is installed. Ad Astra is not by Team Galileo, so we have no idea what problems might arise by having it installed. It is our current position that no accommodation will be made for the use of Astra. If anyone tries Ad Astra and discovers problems, please don't bring them to us. Report your problems to the maker of Ad Astra and allow him the option to make the necessary fixes. If he does not, then the official position is that the mods are incompatible and should not be used together.

A memory leak was reported for JNSQ + GPP + KK + dependencies. Nothing has been done yet to resolve it on our end. What is the screen shot trying to show me, floating scatter? If so, that's a Kopernicus problem, not JNSQ.

Are you using the Rescale mods to make sure everything is at the same scale? For instance, if you are playing JNSQ at its native 1/4 real scale, then you need to resize GPP and GEP by 2.5x using the optional Rescale mods that come with GPP and GEP. If not, JNSQ will break scatterer for anything that is installed with it. The fix for this is included in the Rescale mods, as it is presumed Rescale will always be used when either GPP or GEP is installed with JNSQ.

I have not been able to reproduce this problem.

JNSQ uses Universal Time, which is centered on the prime meridian (0 degrees longitude). That is, noon (6:00 UT) occurs when the sun is directly over the prime meridian. Since KSC is located at 91.8° W longitude, this means that when a game starts at the traditional time of 0:00 UT, it is sunset at KSC. What this mod use to do, and what JNSQ now does on its own, is adds a 1/2 rotation to Kerbin and advances the clock 6 hours so a new game starts at 6:00 UT. This means that when beginning a new game it is sunrise at KSC, giving the player a full day of sunlight to get things started.

@Gordon Fecyk, congratulations on finishing the series. Thanks for making it, I thoroughly enjoyed it.

@CookieBorg, your description sounds strange, I don't know what's going on. Doesn't really sound like GPP problem. If you're in a 79x124 km orbit around Tellumo you shouldn't be able to time warp past 50x. And there's no such thing as orbital decay in KSP (though there may be a mod for it). Once above the atmosphere limit there should be no drag whatsoever.

@manbearpig44, that looks pretty normal to me. At least I'm seeing it the same way in my game.

First of all, when you say you have low quality textures, I don't even know what that means because it could refer to several different things. I need a better description of exactly what you're looking at an under what circumstances. Give me some screenshots so I can see for myself. Also, it is important that we rule out the possibility that some other mod is interacting with GPP to cause the problem. So if you haven't already done so, either create a fresh install with just GPP and its dependencies, or uninstalled everything from your current installation that is not necessary to run GPP. Also verify if the problem occurs just at 10x scale or if it occurs at 1x as well. That should be enough to get us pointed in the right direction. May need more information later. Also bare in mind that GPP was designed to play at 1x, not 10x. What you're seeing may be a natural and unavoidable consequence of stretching the textures to fit something 10 times the intended size.

@manbearpig44, the GPP specific terrain detail options only appear first time after deleting setting.cfg. Thereafter you won't see the GPP options, but the setting will remain set what you picked the first time. If you ever have a need to change it, you need to delete settings.cfg again and start over. As to why you are getting poor quality textures, I have no idea. I don't have enough information to even make a guess.

The only thing I can suggest is to make sure your station is in a high enough orbit that there is room below it for smaller and faster orbits. You don't want to make the mistake of having your station in such a low orbit that it becomes difficult for shuttle flights to the station to catch up with it and rendezvous.

It is very doubtful that Rescale and KerbalKonstructs are compatible. Rescale was never tested with the KK sites enabled. If you're using Rescale, I recommend against using KK.

GPP Patch Many of the problems that have been discussed in this thread have been fixed, though we're still working on others. We hope to release an update in about a week. In the meantime, the following patch fixes some of the easier to correct issues. Just download this file and place it anywhere inside your KSP/GameData/ folder. https://www.dropbox.com/s/c1k6sxm5jmlbq7t/GPPpatch1660-2.cfg?dl=0 If anyone has trouble downloading the file, just copy and paste the following text into Notepad (or equivalent) and save it as a .cfg file. This patch is no longer required if using GPP v1.6.7.0.

I don't think this is a GPP/GEP issue. I believe it is something inherent to scatterer. If it bothers you enough, you can always play without scatterer. I have not been able to reproduce this problem. Everything looks normal to me. I don't know what causes that. If it's a config setting then it might be fixable, but it could be a scatterer bug that I can't do anything about. The problem kicks in below the PQS deactivation altitude, which for 10x Gael is 150 km. Strangely it only seems to happen at 10x scale. I'm not sure there's anything that can be done about it. GPP was never built to be played at 10x scale so there are bound to be some artifacts introduced when resizing it. If it bothers you enough, you can always play without scatterer. You might try deleting the Kopernicus cache, which are the *.bin files in the GPP Cache folder, though I'm not sure how much that will help.

I have no idea what's going on. I first created these Rescale configs back in May and at that time I tested all this and it was working fine. Now I'm getting reports of stuff being buried or floating. Obviously I need to investigate and figured out the problem. There are definitely going to be some patches released, not only for GPP but also JNSQ and maybe GEP. Perhaps next week.

It is part of the GPP download, inside a folder titled "Optional Mods".

In my post I included a link to my dropbox where you can download the revised icons. You can then replace the icons in your KSP install with the new ones.

I don't have the ability to edit the OP, but I added it to the second post, which supplements the OP.

The Rescale configs haven't been fully tested so there are bound to be problems. I made sure that all the planets loaded up correctly and that scatterer and EVE were working. I also had a short check list of other things to look at and verify, but I never checked any of the KK stuff. I'm not sure what's required to make that stuff work, we'll have to look into it. If any other bugs turn up, please let us know. Rescale is still largely a work in progress.

Kronometer 1.12.0.1? Release 1.12.0.1 · linuxgurugamer/Kronometer (github.com)

KKtoSD hasn't been a thing for quite some time. I think what it use to do is now built into SD. But since we're not using Sigma Dimensions anyway, it's not applicable. I don't know. It's been that way for quite awhile and I've made no attempt yet to figure out what's causing it or how to fix it. (edit) I've figured it out and will fix it in an upcoming patch. That doesn't really sound like an issue related to GPP. You might have a problem somewhere else. You probably need to go through the usual debugging steps to figure out what's causing it.