Jump to content

[KSP 1.6.1] Stock Visual Terrain [v2.2.0] [20 March 2019]

Galileo

By Galileo
in KSP1 Mod Releases

 Share

Recommended Posts

  • 2 weeks later...
Shoryuken

Shoryuken

Posted
Posted (edited)
On 8/4/2018 at 8:16 AM, JoE Smash said:

NVM, I screwed up.....I think I fixed it....

MpoXfw3.png

 

FTLaULA.png

How did you fix that ? i have the same problem without stock visual terrain ^^

On 7/11/2018 at 2:04 AM, draqsko said:

Delete the :FOR[SVT] in Kerbin's cfg file, it's overwriting SigDim's changes somehow. So far that seems to work for me.

@Galileo Here's some information on this issue, perhaps you can suggest a better fix for now that users could edit into their files until you get a chance to update it (or if you like just suggest how you'd like it fixed and I'll submit a PR on github).

Here's my Mod Manager cache with SVT 2.1.4 as installed (I cut out the bit between Material and Ocean to shorten it a bit, no real difference in that section anyways, just to show that something is being overridden since the position of SpaceCenter changes and loses it's rescaling and I believe that is the culprit for this bug): 


				AtmosphereFromGround
				{
					outerRadiusMult = 1.028571428575
					innerRadiusMult = 0.971527777774318
					transformScale = 1.05714285715,1.05714285715,1.05714285715
				}
			}
			PQS
			{
				Mods
				{
					SigmaDimensions
					{
						Resize = 2.5
						Rescale = 2.5
						Atmosphere = 1.1
						dayLengthMultiplier = 1.5
						landscape = 0.76
						groundTiling = 1
						atmoASL = 1
						tempASL = 1
						atmoTopLayer = 1.038961039
						atmoVisualEffect = 1.142857143
						lightRange = 2.5
						scanAltitude = 1
						geeASLmultiplier = 1
						resizeScatter = 1
						CustomSoISize = 2.5
						CustomRingSize = 2.5
						reEntryHeat = 1
						resizeBuildings = 1
						changeScatterSize = 2.5
						changeScatterDensity = 0.4
					}
				}
				Material

.....

			Ocean
			{
				Mods
				{
					SigmaDimensions
					{
						Resize = 2.5
						Rescale = 2.5
						Atmosphere = 1.1
						dayLengthMultiplier = 1.5
						landscape = 0.76
						groundTiling = 1
						atmoASL = 1
						tempASL = 1
						atmoTopLayer = 1.038961039
						atmoVisualEffect = 1.142857143
						lightRange = 2.5
						scanAltitude = 1
						geeASLmultiplier = 1
						resizeScatter = 1
						CustomSoISize = 2.5
						CustomRingSize = 2.5
						reEntryHeat = 1
						resizeBuildings = 1
						changeScatterSize = 2.5
						changeScatterDensity = 0.4
					}
				}
			}
			SigmaDimensions
			{
				Resize = 2.5
				Rescale = 2.5
				Atmosphere = 1.1
				dayLengthMultiplier = 1.5
				landscape = 0.76
				groundTiling = 1
				atmoASL = 1
				tempASL = 1
				atmoTopLayer = 1.038961039
				atmoVisualEffect = 1.142857143
				lightRange = 2.5
				scanAltitude = 1
				geeASLmultiplier = 1
				resizeScatter = 1
				CustomSoISize = 2.5
				CustomRingSize = 2.5
				reEntryHeat = 1
				resizeBuildings = 1
				changeScatterSize = 2.5
				changeScatterDensity = 0.4
			}
			SpaceCenter
			{
				groundColor = 0.444,0.494,0.294,0.23
				groundTexture = SVT/textures/PluginData/grass00.dds
			}
		}

 

And this is what it is with :FOR[SVT] removed from the Kerbin.cfg file: 


				AtmosphereFromGround
				{
					outerRadiusMult = 1.028571428575
					innerRadiusMult = 0.971527777774318
					transformScale = 1.05714285715,1.05714285715,1.05714285715
				}
			}
			SpaceCenter
			{
				groundColor = 0.444,0.494,0.294,0.23
				groundTexture = SVT/textures/PluginData/grass00.dds
				radius = 18750
				Resize = 2.5
			}
			PQS
			{
				Material

 

As you can see, somehow SVT is overwriting the changes SigDim is making to the radius for the SpaceCenter and likely drawing the textures too low due to that fact. That is literally the only difference I can find so far. This seems to be happening because SVT loads after SigDim, forcing it to load before SigDim resolves the issue.

 

Edit: I think I have a better fix, at least temporarily for this issue. Change all the callbacks from SVT to rSVT in the config folder to maintain loading hierarchy. So, 


Change @Kopernicus:FOR[SVT] to @Kopernicus:FOR[rSVT]

Change @Kopernicus:BEFORE[SVT] to @Kopernicus:BEFORE[rSVT]

Change @Kopernicus:AFTER[SVT] to @Kopernicus:AFTER[rSVT]

That will let it load before SigDim and then SigDim can modify it correctly.

i have the same problem but i dont use scatterer and i have no sigma just eve and eve config, oh and the community terrain pack becouse of outer planets

Fixed both problems through removing whole ckan and backed up the downloads/mods idk what happend but that fixed it

Edited by Shoryuken
Fixed it ^^
Link to comment
Share on other sites
IronDuke

IronDuke

Posted
Posted
On 7/10/2018 at 5:04 PM, draqsko said:

Edit: I think I have a better fix, at least temporarily for this issue. Change all the callbacks from SVT to rSVT in the config folder to maintain loading hierarchy. So, 


Change @Kopernicus:FOR[SVT] to @Kopernicus:FOR[rSVT]

Change @Kopernicus:BEFORE[SVT] to @Kopernicus:BEFORE[rSVT]

Change @Kopernicus:AFTER[SVT] to @Kopernicus:AFTER[rSVT]

That will let it load before SigDim and then SigDim can modify it correctly.

You, kind sir, are a lifesaver. :D Thank you so much! Now when Jeb says "I couldn't see the ground" I can slap his plaster cast and say "WELL I CAN SEE IT.":sticktongue:

Link to comment
Share on other sites
Galileo

Galileo

Posted
  • Author
Posted
1 hour ago, Trekkie148 said:

I have this weird glitch where the KSC's terrain texture won't show and it's normal stock. But after a few missions it's fixed and I can see the terrain again. 

Screenshots and logs

Link to comment
Share on other sites
  • 4 weeks later...
GearsNSuch

GearsNSuch

Posted
Posted (edited)

@Neldonax

No, unfortunately it will not work without Kopernicus. In other words, if Kopernicus doesn't work on your save, this won't either.

Next time, you might want to look at the "Requirements" section on the mod's first page or test it yourself.

Edited by GearsNSuch
Link to comment
Share on other sites
vossiewulf

vossiewulf

Posted
Posted
Just now, 4x4cheesecake said:

That's a know scatterer bug. Switching to the tracking station and back to the KSC should fix it (sometimes it needs a second try).

Ah, thanks for the clarification. Yes, going into pretty much any building and coming back out will reset it to normal, it's mostly amusing. I try to guess how underwater KSC will be whenever I pop back.

Link to comment
Share on other sites
  • 1 month later...
Burning Kan

Burning Kan

Posted
Posted

@Eaten by Black Hole  yes,in "KSP_win64\GameData\SVT\configs" find the "Jool.cfg"open it with editor or notepad  and

delete the red marked text in the cfg:

Spoiler

@Kopernicus:FOR[SVT]
{
    @Body[Jool]
    {
        @ScaledVersion
        {
            Material
            {
                texture = SVT/textures/PluginData/Jool00.dds
                normals = SVT/textures/PluginData/Jool01.dds
                bumpMap = SVT/textures/PluginData/Jool01.dds
                bumpMapScale = 1,1
            }
        }
        Rings:NEEDS[scatterer]
        {
            Ring
            {
                angle = 2
                outerRadius = 2250
                innerRadius = 1250
                texture = SVT/textures/PluginData/Jool_ring.dds
                color = 0.8,0.8,0.8,1
                lockRotation = true
                unlit = false
                useNewShader = true
                penumbraMultipler = 10.0
            }
        }
        Rings:NEEDS[!scatterer]
        {
            Ring
            {
                angle = 2
                outerRadius = 2250
                innerRadius = 1250
                texture = SVT/textures/PluginData/Jool_ring.dds
                color = 0.8,0.8,0.8,1
                lockRotation = true
                unlit = true
                useNewShader = false
                penumbraMultipler = 10.0
            }
        }
    }
}

 

voila- u can also delete the "KSP_win64\GameData\SVT\textures\PluginData\Jool_ring.dds"

welcome on forums )

BK

 

Link to comment
Share on other sites
4x4cheesecake

4x4cheesecake

Posted
Posted (edited)
14 minutes ago, bvsveera said:

Really? I was under the assumption that Kopernicus and SVT are version-locked. I'll try it in a bit. Thanks for your input!

Kopernicus is updated to 1.4.5 and AVC (if you didn't remove it) will display a warning about a incompatible KSP version but SVT will work anyway :)

Edited by 4x4cheesecake
Link to comment
Share on other sites
OhioBob

OhioBob

Posted
Posted
1 hour ago, bvsveera said:

Really? I was under the assumption that Kopernicus and SVT are version-locked. I'll try it in a bit. Thanks for your input!

Kopernicus is version locked, not SVT.  Just make sure you have the right Kopernicus and SVT should work.

Link to comment
Share on other sites
therealcrow999

therealcrow999

Posted
Posted (edited)
3 hours ago, OhioBob said:

Kopernicus is version locked, not SVT.  Just make sure you have the right Kopernicus and SVT should work.

Kopernicus just updated to KSP 1.5, you can manually download it from its forum thread, it hasn't shown up in CKAN. Probably later in the day or tomorrow.

https://forum.kerbalspaceprogram.com/index.php?/topic/140580-150-1-backports-kopernicus-kittopiatech/&

Edited by therealcrow999
Link to comment
Share on other sites
  • 2 weeks later...
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...