hello the problem is the KSC is floating and the ground is not visible, well I dont know what to say more but I hope someone can help me out

Gamedata Folder:

Curious as to why you removed the AVC support?
Are you still including the .version file?

As such, the mod must be manually installed for the modern version, while CKAN will keep attempting to "update" the mod down to 0.9.8.

Hi everyone!
You have already done a brilliant work.
I am very grateful for it.
I am playing KSP 1.4.2 on a Windows 10.
I am using the last version of sigma dimensions
I am trying to play on an Earth size Kerbin
I have had no problen moving the Mun.
I have a little issue rescaling Kerbin. When I set Kerbin radius to 6500000 then KSC appears floating over the sea.
I presume landscape is not adjusting properly.
I have tried to include a parameter &landscape = 10 in the Settings.cfg file but it does not appear to work
Any tip?

Thank you very much!
Ignacio

KSP.log

ModuleManager(configcache).txt

Kopernicus.log

and the Moho log
Moho.Body.log

I am using KSP 1.7.0
Mod List:
Kopernicus 1.7.0-1
ModularFlightIntegrator 1.2.6
SigmaDimensions 0.10.3
ModuleManager 4.0.2

I had uninstalled KSP through steam, then deleted the entire KSP folder in /Steamapps/common, then reinstalled KSP 1.7.0. I am using the most up to date mod versions I can find for 1.7.0. The game is fully operational with just Kopernicus and its prerequisites. When I add Sigma Dimensions with stock config, I can get to choosing a save file, however It will not stop loading, although it plays the ambient noise for the KSC.

I have little to no knowledge of coding or making mods in general; but I can pick out where I think its going wrong in the kopernicus log (linked above):

[LOG 22:19:32]: [Kopernicus]: Configuration.Loader: Loaded Body: Sun
[LOG 22:19:32]: [Kopernicus]: Configuration.Loader: Failed to load Body: Squad/Moho: Argument cannot be null.
Parameter name: type

A similar few lines are found toward the end of the moho.body log (also linked above). It is worth noting the ModularFlightIntegrator.version file says the maximum ksp version is 1.6.9; but Modularflightintegrator still works without sigma dimensions.

If I missed anything important, I can provide files on request.

Not sure if this will work,

so use with caution

Sigma-Dimensions.v0.10.2.unofficial.zip

Reproduce:

1. fresh 1.4.3. install
2. install Making History (without it everything seems to be ok)
3. install Kopernicus and Sigma Dimensions 0.10.1
4. set 6.4 resize and rescale (without rescale everything seems to be ok).
5. create new vessel with engine shroud.

https://imgur.com/g7HaNaL

Please update Sigma to work with KSP 1.7.1.2539 and Kopernicus 1.7.1.3

This message pops up during game launch:

1 error related to GameData/Dimensions/Configs/ReDimension/newCacheFiles.cfg

Here are my log files: https://www.dropbox.com/sh/3ahnlcciy0ltcsd/AAAwJ2fKzCG7vj-BqOM5aGLra?dl=0

Requested by: davidy12

Link to the mod: Kerbal Konstructs

KK now changes the altitude of statics based on the planet size.

This will result in the altitude of buildings being resized twice, once by KK and another time by SD.

To avoid this I will add an option to tag certain PQSCity so that they are "Ignored" by SD

This will allow KK to handle its statics without needing to worry about SD messing up their position afterwards.

@GER-Space could you confirm you didn't revert the changes you described in this post?

tagging @Galileo88 since he manages Rescale!

I am so sorry to ask you so that the steps you say are really detailed...

I just can not understand them...My English is too bad...(T^T)

I write what you say(I must have made a mistake), but it does not take effect. T_T

It is not possible to on-rails timewarp even above 180km, due to the ship being under pseudo acceleration.

A few weeks ago I mentioned a problem I was having with PQSCity2 and SigmaDimensions, and felt like posting it here as well, so you can keep track of it. I hope you don't mind.

The issue is with PQSCity2 (And possibly PQSCity) objects with snapToSurface set to false, and this results in them being repositioned several hundred kilometers above their intended position by SigmaDimensions.
(ie 600km above the intended point at 2x scale)

I believe the code in question starts at line 108 in SigmaDimensions.cs and appears to set the alt value of the PQSCity2 to account for the planet being rescaled, but it would seem PQSCity2 accounts for it already.

If you need any more information, I'll be happy to provide it.

edit: Just tested without the .dll, and everything's in the right place (other than KSC), and the planet is still scaled up.

I think treating pqsCity2.alt the same way as pqsCity2.snapHeightOffset might fix it, but then again, I know almost nothing about this.

Hi @Sigma88 ,
I assume that Dimensions is not compatible with the latest Kopernicus.
I'm just popping in to offer help with any testing or config related aspects of this project.
Thanks for your contributions to KSP.

• resize the light at ksc when resizing buildings
• fix tangents in elongation of atmospheres

It isn't particularly important, but when playing with SigmaDim and GPP, both of their loading screens show up. The SigmaDim loading screens kind of clash with the oil painting styles of GPP's, and they also show the stock planets which don't exist in GPP. I have fixed it in my own install by deleting the pictures, but I think there is probably some code which could be written to detect GPP and hide the SigmaDim loading screens if it is found.

I've noticed this is a similar issue to what some other people have been experiencing, but with a seemingly different cause, so I thought I'd open a new thread rather than flood old ones. By the way, this issue occurs on all versions, as far as I could tell - I suspect it's something to do with the config files or cache, although deleting the cache did not help.

As the title implies, the land underneath the KSC disappears and is jaggedly cut off in a square. This happens when you launch a vessel and unload the initial land textures. It's hard to explain in text form, but I will include screenshots.

As you can see here, the land is there and intact most of the way up. However, as I'm sure you're familiar, the terrain makes way for a lower-res version.

This is on the descent. You can start to see the issue, there is a faint outline of the ocean cut out of the land.

Here the bug is very pronounced.

And this is just a zoom out of the area after I had crashed into the "ocean".

I'm not entirely sure how to fix the issue, but I've been troubleshooting all day with no luck. I've tried:

-The fixes here: #97

-Using an older version of Sigma Dimensions, since I am using the newest

-Deleting all mods but Sigma Dimensions and Rescale (and dependencies)

-Using multiple Rescale mods

-Fresh install of Sigma

-Deleting the cache folder

-Fresh install of KSP

-Fresh install of Kopernicus (Redundancy sake)

-Older version of Module Manager (see below)

I'll probably try a factory reset later in the week if it still isn't working.

Through process of elimination I have reduced the possibilities to this mod or Rescale, but I suspect it is this mod looking at some of the other issues, and the fact that both Rescale mods reproduce this issue.

Below is an image of my GameData folder:

That's all I can think of adding. If you need any other information I'd be happy to provide, but that's all I've got.

Update:
I rolled the game back to 1.8, with strange results. The same issue is occurring
but not to the same extent. I don't really have much of an explanation but a screenshot. (Note - This is with GPP, although I am sure this isn't the issue because this still happens on stock Kerbin)

Update:
Version in stock. Much more clear here

Update:
Found the potential issue. Your mod removes "minDetailDistance" from the latest version to fix this bug, but ModuleManager appears to write this value to the cache anyway. I'm not entirely sure though, just a guess.

Here's the section in question, found in ModuleManager.ConfigCache:

PQS
{
minLevel = 2
maxLevel = 8
minDetailDistance = 6
maxQuadLengthsPerFrame = 0.03
fadeStart = 30000
fadeEnd = 90000
deactivateAltitude = 110000
materialType = AtmosphericTriplanarZoomRotation
allowFootprints = True
Material
{
factor = 8
factorBlendWidth = 0.05
factorRotation = 135
saturation = 1.1
contrast = 1.2
tintColor = 1,1,1,0
specularColor = 0.1,0.1,0.1,1
albedoBrightness = 1.3
steepPower = 2
steepTexStart = 10000
steepTexEnd = 200000
steepTex = BUILTIN/ikeSteep_diffuse
steepTexScale = 1,1
steepTexOffset = 0,0
steepBumpMap = BUILTIN/ikeSteep_nrm
steepBumpMapScale = 1,1
steepBumpMapOffset = 0,0
steepNearTiling = 50
steepTiling = 50
midTex = BUILTIN/MunFloor [Diffuse]
midTexScale = 1,1
midTexOffset = 0,0
midTiling = 90000
midBumpMap = BUILTIN/MunFloor [Normal]
midBumpMapScale = 1,1
midBumpMapOffset = 0,0
midBumpTiling = 90000
lowStart = -1
lowEnd = -1
highStart = 2
highEnd = 2
globalDensity = 1
planetOpacity = 1
oceanFogDistance = 1000

And here's the whole cache:

ModuleManager - Copy.txt

If this is the issue I have no idea how to fix it.

Update:
I'm not really sure what happened here, but I landed on the ground with a Kerbal and this resulted. This was 1.8 KSP with the original rescale mod.

Requested by: MrMeeb

Link to the mod: KSC Floodlight

How do I calculate a Geostationary orbit for Kerbin at 2x stock?

Also, I am having an issue calculating the new DeltaV needed for LKO. I've been guesstimating but maybe you can help me. I have everything (resize, rescale, day length) set to 2x stock, but I changed the atmosphere setting to 1.5x.

Any help is appreciated.

Thanks!

When I quit to main menu and reload, it seems to be applying that atmoTopLayer thing all over again. Here's what it looks like after 4 and 5 reloads with the following settings (based on original KScale64 and improved for the latest SigDim version):

SigmaDimensions
{
	// Base Settings

	Resize = 6.4
	Rescale = 6.4
	Atmosphere = 1.33
	dayLengthMultiplier = 4


	// Advanced Settings

	landscape = .50
	geeASLmultiplier = 1

	resizeScatter = 1
	resizeBuildings = 2

	CustomSoISize = 0
	CustomRingSize = 0

	atmoASL = 1
	tempASL = 1
	atmoTopLayer = 1.4
	atmoVisualEffect = 1

	scanAltitude = 1
}

This makes things difficult and requires the full game restart to make everything work properly again.

Hi Sigma88, in trying to come up with a modded 1.3.1 install in which to start a new career and I came across some performance issues that when narrowed down seem to point towards Dimensions.

I understand that there could be other factors in the modded install that contribute to the fps drop so I guess I am asking about the clean install that drops from 244 to 166 fps. Is that normal for dimensions to behave like this?

As you can see from the pictures, the modded install drops from 203 to 40 fps. The only thing I'm doing is adding or removing Dimensions for each of these tests.

Also notice the GPU seems to be limited some how when Dimensions is installed.

Pictures

@Galileo88 I am working to add scatterer compatibility to SD

could you test out this version of SD? link

this version should do automatically what you define here

it also adds an option to bypass the "Rescale" parameter by adding a "customRescale" inside the star node (in case you need a different rescale factor)

NOTE

KK now handles the altitude by itself

This means that now SD will not move those statics as long as you install KKtoSD alongisde KK and SD

Original Issue

I'm testing with 1.3.1 and the base mods for KK, SD, SVT and your KKtoSD mod. Looking to make KerbinSide work with RESCALE! 3.2x. I'm hoping to get all the bases working in the rescale and fix any floating buildings problems. I've made alot of progress to getting it done, but am having an issue as described below.

This code was posted in the forum thread as a fix for the floating radar tower near KSC.

PQSCity_Groups
{
    GROUP
    {
		name = KSCUpgrades2
		body = Kerbin
		
		MODS
		{
		PQSCity = KSCUpgrades_ksideradar3_0
		}
    }
}

It works perfect and from my understanding this is creating a new group called KSCUpgrades2 and giving it one static. Since no center is defined then the first static in the group is used as the center. This has the effect of moving the tower back to the hilltop because the lon/lat of the terrain feature is the same.

This code does not work however.

PQSCity_Groups
{
   GROUP
    {
		name = DeadkerbalPit2
		body = Kerbin

		MODS
		{
			PQSCity = DeadkerbalPit_ksidecontroltower4_0
		}

    }	
}

Looking at the static definition for both the floating radar towers I can not figure out why one works and the other does not. Literally the only difference I see is how the parent group is defined. KSCUpgrades uses CentralPQSCity = KSC and DeadkerbalPit is using CentralLAT and CentralLON

Relevant lines:

If a celestial body has the internal name "Kerbin" (which the homeworld of a system replacer would likely have) and has an atmosphere, then Sig Dim sets its sea level pressure to a hard-coded value of 101.325 kPa (equal to stock Kerbin's sea level pressure), regardless of what the sea level pressure for that homeworld as defined by its atmospherePressureCurve is, while leaving the rest of the body's atmosphere pressure curve untouched. This can lead to the following behaviors:

• If the body's atmosphere is normally thinner than Kerbin's, this results in the sea level pressure being higher (sometimes much higher) than it should be, while the rest of the atmosphere is unaffected.
• If the body's atmosphere is normally thicker than Kerbin's, it can create a situation where atmospheric pressure initially increases with altitude before reaching a peak and dropping off like it normally would for that body.

Fig. 1: Kcalbeloh System's Efil at 2.5x rescale, showing the normal sea level pressure of 75.9938kPa.
https://media.discordapp.net/attachments/939249946027245587/1232387089719365683/image.png?ex=6629456a&is=6627f3ea&hm=024e89cd57550b2c8c224db1f71feef8489ca01b21275c2068ffbb6661e1fec0&=&format=webp&quality=lossless&width=1202&height=676

Fig. 2: Kcalbeloh System's Efil at 2.5x rescale, this time with the planet pack's homeswitch setting set to "Efil", which sets Efil's internal name to "Kerbin". Its sea-level pressure has been changed by Sig Dim to the aforementioned hard-coded value of 101.325kPa.
https://media.discordapp.net/attachments/939249946027245587/1232390962517381251/image.png?ex=66294906&is=6627f786&hm=2ad8d0abc8594abbbe4e62adcefb0f73e671cf7587b47f2c05e9f76c74a3e1c4&=&format=webp&quality=lossless&width=1200&height=676

Requested by: Armageddon

Link to the mod: ScanSat

@GregroxMun proposed on #Kopernicus to add textures to the kittopia exports.

While I think this is a good idea I don't think SD is the right repository to dump all that data on

@StollD do you think a new repository could be added to the Kopernicus organization to hold all Kittopia Exports? (cfgs and textures)

yes? no? bad idea? self advertising? m8 i r8 8?

let me know :D

Hi, when I use Sigma Dimensions it doesn't work. When I play KSP it plays just fine but resizing/rescaling doesn't do anything, all the planets still have their default size. I tried it with the Rescale mod as well but that also didn't do anything. I'm running a clean install of KSP 1.6.1 (1.6.1.2401 to be exact) and Sigma Dimensions and Kopernicus are the only mods I have installed. Link to zip file with logs etc. https://drive.google.com/file/d/1XWvbNj9aLcF6LB0IaHuK1EzXel74N2Ao/view?usp=sharing. Any help is greatly appreciated

When loading sigma dimensions and KSP 1.1.3 and stock (rescaled for 6.4k) - everything loads normally.

When loading with all the planet packs of my install KSP hangs - with logs spews from sig dimensions and has template eeloo.

Some planet packs are not affected - OPM, trans-keptunian, PluronKhato. I haven't spent the exact time to determine which ones are affected, and which ones are not.

However I was able to replicate the hang by adding KDS (Kumar's Dwarf Planets) to the install.

I have attached a zip with the working "stock install" - Rescale config, Squad, MM, and Kopernicus, OPM+TK+PK, and with a hang situtation.

I'm using SD with RESCALEx10 and OPM on KSP 1.9.1.

Every OPM body I try to land on I fall through the surface and explode. It doesn't happen with stock planets or OPM without SD>

Requested by: MrMeeb

Link to the mod: KSC++

Hi!

Been struggling with this issue for a while, not really gameplay intrusive but annoying visual bug/glitch/whatever.

Appears most of the time at the beginning of the launch and will "spawn" multiple times throughout the flight in a new position. Multiple can be spawned at one time but it's hard to get a screenshot of them all in one shot. Happens both when launching from the Runway and Launchpad.

Happens with and without the KSC Extended/Tundra Space Center mods.

Happens with and without Galileo's ReScale configs being used.

It took me a while to actually narrow it down to it being Sigma Dimensions related?

KSP.log

error.log

Mods
KSP: 1.7.3 (Win64) - Unity: 2017.1.3p1 - OS: Windows 10 (10.0.0) 64bit
ClickThroughBlocker - 0.1.7.2
Toolbar - 1.7.22.2
ToolbarControl - 0.1.8.2
CommunityPartsTitles - 0.5.1
BAM - 1.3.2.6
Chatterer Extended - 0.6.2
Chatterer - 0.9.96.2332
CommNetAntennasExtension - 2.1
CommNetAntennasInfo - 2.1.2
Connected Living Space - 1.2.6.2
CorrectCOL - 1.6.4.4
CrewRandR - 1.1.9.2
Community Terrain Texture Pack - 1.0.4
CustomBarnKit - 1.1.19
AdvancedTextures - 1.7.3
DistantObjectEnhancement - 1.9.1
Easy Vessel Switch - 1.11.7052.36539
EditorExtensionsRedux - 3.3.22
Engine Lighting Relit - 1.6.1.1
Environmental Visual Enhancements - 1.7.3
FShangarExtender - 3.5.5
JanitorsCloset - 0.3.6.1
Kerbal Engineer Redux - 1.1.6
Kerbal Joint Reinforcement - 4.1.15
KerbalKonstructs - 1.7.3.4
Kopernicus - 1.7.3.2
Sigma Dimensions - 0.10.5 (w/ 0.10.6's resizePQSMods.cfg for the MM error fix)
Sigma Binary - 1.7.2
ReScale 3.2x - 1.0.2.8
Kronometer - 1.7.1.1
KSC Extended - 1.1
KSP-AVC Plugin - 1.3.1
LoadingScreenManager - 1.2.5.3
MechJebForAll - 1.3.0.6
ModularFlightIntegrator - 1.2.6
NavBallDockingAlignmentIndicatorCE - 1.0.5
OuterPlanetsMod - 2.2.5
PlanetShine - 0.2.6.1
Precise Node - 1.2.10.3
QuickCursorHider - 1.0.7.2
RealPlume - Stock - 2.0
RemoteTechRedevAntennas - 0.1.1
ReStock - 0.1.4
ReStockPlus - 0.1.4
Ship Effects Continued - 1.0.9.1
ShipManifest - 5.2.1
StationKeeping - 0.2.1.1
Stock Visual Enhancements - 1.4
Stock Visual Terrain - 2.2
TextureReplacer - 3.7
ToadicusToolsContinued - 0.22.3.3
TooManyOrbits - 1.1.5.1
Tracking Station Evolved - 1.0.4.1
TrimIndicators - 0.0.1
Tundra Space Center - 1.1
TweakableEverything - 0.1.26
TweakScale - 2.4.3.9
World Stabilizer - 0.9.5
ZeroMiniAVC - 1.0.6

I'm using Rescale 2.5x and GPP. When in orbit above planets and moons I'm seeing a "ghosted" image of a second terrain surface. On some bodies the height between the visible surface and the ghost images are more pronounced than others, but it's happening to all of them. The effect almost looks like a cloud layer but the clouds are in the shape of mountains. Of note, it looks like the ghost texture isn't aligned with the underlying hard surface - you may see a ghost mountain above a flat plain.

Hard to capture on screen shot, but here are a few examples:
Note the lighter band of grey on the right edge where the light is shining through the ghost terrain:

Here's another - note the lighter color that looks like an atmosphere, but it's terrain shapes

I'm using:

• KSP 1.4.5
• GPP 1.6.3.1
• Kopernicus 1.4.5-4
• Rescale 2.5 1.0.2.8
• Sigma Dimensions 0.9.8 (I've also tried 0.10.1)

Thanks

Disclaimer by Sigma88

This is not an issue with SD itself, but rather an issue with the idea of rescaling in general. SD offers different ways to solve the issues of rescaling planets and PQSCity mods, but an automatic solution is impossible. In this thread you will find some suggestions on how to approach these issues using proper SD syntax

Original message by @Joker58th :

I looked over some forum posts and eberkain's issue which seemed similar but I am unable to get a config that fixes the floating issue with the 3.2 or 6.4 rescale.

https://i.imgur.com/49RDsGa.png

I have a fresh 1.3.1 install with the following:

Mods
https://i.imgur.com/5dgUAZI.png

Gamedata
https://i.imgur.com/WQvukTg.png

Config
https://i.imgur.com/DsTYIcw.png

Any help would be appreciated. Thanks.

Version: 1.10.1 w/ SD 0.10.7 and Galileo88's RESCALE mod at 10.625x, clean install. But see below...

This seems to be a popular theme with the open issues, no?

I'm seeing the same thing as #77 and #95 - a ghostly surface that only appears when you zoom out enough. If I try to land on where the surface should be, I end up exploding as I pass through terrain that isn't there. Interestingly, MechJeb seems to know where the surface is supposed to be (i.e. the true altitude reads roughly what I'd expect it to be, and goes negative as I sink into the terrain. At ground level, KSC appears to be floating above the ocean - presumably ~328m above it.

Now, I KNEW I was using the SD + RESCALE mods on KSP1.10.0 with an accidentally de-nyancatted version of Kopernicus for 1.9.1 (1.9.1 release 3, assuming it hasn't been fixed,) so I dug around in my old folders and found it. Indeed, it looks like something changed between KSP 1.10.0 and 1.10.1 to cause these issues.

I'll mention this to @R-T-B (who I guess I can't actually @, darn it,) but I figured I'd also drop you a bug report just in case.

Obviously I'm stacking old versions of mods on old versions of mods on new versions of KSP here, so I don't expect a whole bunch of support - I feel like I make a decent case that something went weird between the versions, at least.

There's just no way I can play with a stock-size KSP.
SD is just the one mod I would always appreciate.
The game is dead for me without SD

The thing is, I've encountered a issue with performance, but unlike #72, it seems to be related to the resize, the larger I rescale to, the laggier. I'm using 4X resize on planet pack JNSQ, and I can only get 50 fps with a 40 part vessel on 640km sized minmus. The weirder thing is that I can get smooth 60 fps on a 6400km sized kerbin with 100 parts, which doesn't make any sense?
This bug seems to be present on 1.7.0 and 1.7.1, and regardless of what shader I'm using.
Sorry if I sound rude or something, for some reason I'm fairly bad at expressing politeness when using English. I absolutely love this mod and it has become one of my essential mods that I can't get rid of.

Max allowable timewarp seems to only be 100000x on a 10.625x GPP save. Going into Kerbal Construction Time's settings and trying to increase max timewarp there doesn't work past 100000x

As the title describes it.
As you modified the resizePQSMods.cfg file a few days ago, I thought maybe a little bug may have crept inside of it.

KSP.log:
https://gist.github.com/maushacks/4f2c301ce81b3897ec62633395454232

Edit: I tried it with module manager 4.0.3 as well. Same error message.

I hope the title explains my issue in short - when using Sigma Dimensions in conjunction with any Kopernicus planet pack I have yet tried, Module Manager throws these errors during the loading process:

And spams exceptions into KSP.log (which I would add here, but the file size has made uploading it difficult - will do so when I figure that out,)

with Kopernicus stating this error once main menu opens: