[KSP 1.6.1] Stock Visual Enhancements [v1.4.1] [20 March 2019]

DeadJoe · January 2, 2019

On 1/1/2019 at 8:26 PM, MartGonzo said:

Hi Galileo, just wanted to let you know that SVE is working perfectly in 1.6 (minus kopernicus' Jool ring) so you might want to put that on the title page.

Thanks for creating and continuing to support this awesome mod.

Tested today, everything seems to be working fine (including Jool rings).

Maybe the kopernicus update?

MartGonzo · January 2, 2019

5 hours ago, DeadJoe said:

Tested today, everything seems to be working fine (including Jool rings).

Maybe the kopernicus update?

I just got the Kopernicus update, should all be working now, many thanks DeadJoe.

Benji13 · January 24, 2019

Nevermind

Edited January 24, 2019 by Benji13

MysticDaedra · January 25, 2019

I'm getting the EVE black atmos/clouds problem, which according to the good folks on their thread has to do with missing config files. Does this mean it is a problem with SVE, since SVE is supplying its own configs for EVE? Additionally, any idea when the mod is going to be updated to the latest version? I think it is fantastic that SQUAD is increasing the support of the game, rather than decreasing it over time, but it is problematic I know for modders to keep up with all the changes so frequently.

Pie82 · January 30, 2019

Hi All

Before I begin, I'm not asking for or expecting support from the devs due to the lack of logs for reasons that will become clear. Just asking if any other users have had and overcome the same issues I'm experiencing. Specs at the bottom of this post.

When running SVE+SVT I've been experiencing reboots - something I didn't even think was still a thing on modern OSes and hardware. Not blue screens - not CTD - not graphics driver resets but reboots resulting in no windows core dumps - just a kernel power warning and unexpected reboot message. The crash is so quick KSP doesn't even log anything. It normally occurs somewhere within the cloud layer and is exacerbated by complex actions such as staging or messing with the camera. Temps on the GPU don't top 65 and the CPU hasn't topped 50 (C). I've replaced my PSU as they're only £120ish for a good one but no effect. Memtest runs fine as does Windows memory diagnostics. Prime95 ran for over an hour with the only impact being a minor increase in my electricity bill and fan speed. I've not got any GPU benchmarks but I've put over 80 hours into AC Odyssey (don't judge :-) ) without a single crash at 4k~60 (adaptive). Tomb Raider and Space Engineers also haven't crashed yet. The machine runs noticeably hotter when running the AAAs.

I've tried rolling back to nVidia 417.35 with no luck. I've also updated the BIOS on my mainboard.

I've not run extensive tests yet, but a launch that reliably crashes with SVE/EVE/Scatterer seems to run fine without. SVT seems fine. Has anyone else experienced and overcome this issue? I used to run a similar setup but with a 980Ti instead albeit at a lower resolution and 1.5 or whatever was out back then.

Specs:

CPU: i7 6700k stock clock closed loop water cooler.
Memory - 16Gb DDR4 Corsair Vengeance LPX 3200Mhz (2x8 in the right slots, default settings)
GPU: RTX 2080Ti - Palit
Mainboard - MSI Z170A M5
HDD: Some Samsung M.2 no longer on sale (MZVP512HDGL-00<truncated> according to HWMonitor).

Thanks!

4x4cheesecake · January 30, 2019

@Pie82 I have honestly no clue what's going on there but maybe you can get some more informations from the log file. Since it sounds like you cannot start the game properly: Look for the 'settings.cfg' in you KSP install directory, open it in a text editor, search for the entry 'LOG_INSTANT_FLUSH' and set the value to 'True'. This option allows the log file to be saved immediately on your hard drive so you/we may have a chance to see whats going on there.

Pie82 · January 30, 2019

6 hours ago, 4x4cheesecake said:

@Pie82 I have honestly no clue what's going on there but maybe you can get some more informations from the log file. Since it sounds like you cannot start the game properly: Look for the 'settings.cfg' in you KSP install directory, open it in a text editor, search for the entry 'LOG_INSTANT_FLUSH' and set the value to 'True'. This option allows the log file to be saved immediately on your hard drive so you/we may have a chance to see whats going on there.

Yup - it is a weird one! I turned instant flush on and re-created the crash - happened about 30 seconds in to my second ship launch. Too big for pastebin but full log here:

https://drive.google.com/open?id=19h7YwnuTRPDya9P0GawD7j51_EbUSgei

Nothing untoward in the log I can see - it just seems to stop. Got to head off to work now but I'll strip out non-essential mods one by one and see if I can figure out what it is.

Pie82 · February 2, 2019

Seems it really was the PSU. Swapped the 2nd 8-pin from GPU2 to GPU3 and not only is there slightly less noise, I've not managed to re-create the crash even on my guaranteed reboot ship. Guess you need a far better PSU to deal with KSP style 'render-render-render-render-.......................................take out the trash..................................................................render-render-render' than the more consistent power loads required by other games and benchmarks. Will leave my posts here in case they're useful to anyone else - even if logic rules out hardware - it probably still is.

Tomáš Brada · February 12, 2019

Hi. I installed this mod on KSP 1.6.1 (Linux) along with it's dependencies.

Clouds on Eve, Laythe and Tekto look very much like a surface. Is it supposed to? If I change the detail texture from detailCumulus to DetailLow, the clouds start to look more like clouds.

Screenshot of Laythe

Screenshot of Eve

asaurus1 · February 15, 2019

I Hello, I am having issues with the texture resolution: I have downloaded the high-res texture configs yet my clouds still show up looking like this in both the loading screen and in map view:

The clouds appear very low-res and there are no volumetric clouds to be seen anywhere.

EDIT: upon further investigation it appears that these are the SVE clouds, but the DetailLow layer is not showing, nor are the volumetric particles.

It seems like these are the original EVE cloud configs, rather than SVE ones which, based on my internet searches, should look more like this:

I usually have a lot more mods installed than just SVE but removed them as a test the last time I ran the game just to make sure there weren't any causing these problems. This is just TextureReplacer, SVE, EVE, Scatterer, and Loading Screen Manager.

Log File: https://drive.google.com/open?id=1WTzTzpi0gNe-lKegEDZ58_gfVxga1Vg3

Edited February 15, 2019 by asaurus1

4x4cheesecake · February 15, 2019

13 hours ago, asaurus1 said:

Log File: https://drive.google.com/open?id=1WTzTzpi0gNe-lKegEDZ58_gfVxga1Vg3

The log is not public available, it just prompt a window to send a request for the file via email and I would prefer not to send out my private email address. Please check the settings for the link/file

asaurus1 · February 16, 2019

5 hours ago, 4x4cheesecake said:

The log is not public available, it just prompt a window to send a request for the file via email and I would prefer not to send out my private email address. Please check the settings for the link/file

Should be fixed. Noticed this error message near the bottom of the logs which might explain one of my problems:

[Scatterer] Mapping EVE volumetrics for planet: Kerbin
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[Scatterer] Volumetric clouds error on planet: KerbinSystem.NullReferenceException: Object reference not set to an instance of an object
  at scatterer.SkyNode.mapEVEVolumetrics () [0x00000] in <filename unknown>:0 
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[Scatterer] Detected 1 EVE volumetric layers for planet: Kerbin

Galileo · February 16, 2019

1 hour ago, asaurus1 said:

Should be fixed. Noticed this error message near the bottom of the logs which might explain one of my problems:


[Scatterer] Mapping EVE volumetrics for planet: Kerbin
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[Scatterer] Volumetric clouds error on planet: KerbinSystem.NullReferenceException: Object reference not set to an instance of an object
  at scatterer.SkyNode.mapEVEVolumetrics () [0x00000] in <filename unknown>:0 
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/DebugBindings.gen.cpp Line: 51)

[Scatterer] Detected 1 EVE volumetric layers for planet: Kerbin

Post a screenshot of your gamedata.

also, I’m not sure if the latest Scatterer works with this outdated version of SVE.

I really need to update this mod

Edited February 16, 2019 by Galileo

asaurus1 · February 16, 2019

14 hours ago, Galileo said:

Post a screenshot of your gamedata.

also, I’m not sure if the latest Scatterer works with this outdated version of SVE.

I really need to update this mod

Do you one better:

Spoiler

Folder PATH listing for volume Windows
Volume serial number is AC4B-CADC
C:.
│ Delta-V Map 2.6.ksp
│ KSPModFileLocalizer.dll
│ MiniAVC.dll
│ MiniAVC.xml
│ ModuleManager.4.0.1.dll
│ ModuleManager.ConfigCache
│ ModuleManager.ConfigSHA
│ ModuleManager.Physics
│ ModuleManager.README.md
│ ModuleManager.TechTree
│ toolbar-settings.dat
│
├───EnvironmentalVisualEnhancements
│ │ button.png
│ │ EnvironmentalVisualEnhancements.version
│ │ eveshaders.bundle
│ │ License.txt
│ │
│ └───Plugins
│ Atmosphere.dll
│ CelestialShadows.dll
│ CityLights.dll
│ EVEManager.dll
│ PartFX.dll
│ PQSManager.dll
│ ShaderLoader.dll
│ Terrain.dll
│ TextureConfig.dll
│ Utils.dll
│ _BuildManager.dll
│
├───LoadingScreenManager
│ │ License.txt
│ │ LoadingScreenManager.version
│ │ MiniAVC.dll
│ │ MiniAVC.xml
│ │ README.md
│ │
│ ├───PluginData
│ │ LoadingScreenManager.cfg
│ │
│ ├───Plugins
│ │ LoadingScreenManager.dll
│ │ LoadingScreenManager.dll.mdb
│ │
│ └───Textures
│ back.png
│ drive.png
│ file.png
│ folder.png
│ L1.png
│ L2.png
│ L3.png
│ LoadingScreenIcon.License
│ LoadingScreenManager-38.png
│
├───scatterer
│ │ scatterer.dll
│ │
│ ├───config
│ │ │ config.cfg
│ │ │ planetsList.cfg
│ │ │
│ │ ├───Planets
│ │ │ ├───Duna
│ │ │ │ │ atmo.cfg
│ │ │ │ │
│ │ │ │ └───Atmo
│ │ │ │ inscatter.half
│ │ │ │ irradiance.half
│ │ │ │ transmittance.half
│ │ │ │
│ │ │ ├───Eve
│ │ │ │ │ atmo.cfg
│ │ │ │ │ ocean.cfg
│ │ │ │ │
│ │ │ │ └───Atmo
│ │ │ │ inscatter.half
│ │ │ │ irradiance.half
│ │ │ │ transmittance.half
│ │ │ │
│ │ │ ├───Jool
│ │ │ │ │ atmo.cfg
│ │ │ │ │
│ │ │ │ └───Atmo
│ │ │ │ inscatter.half
│ │ │ │ irradiance.half
│ │ │ │ transmittance.half
│ │ │ │
│ │ │ ├───Kerbin
│ │ │ │ │ atmo.cfg
│ │ │ │ │ ocean.cfg
│ │ │ │ │
│ │ │ │ └───Atmo
│ │ │ │ inscatter.half
│ │ │ │ irradiance.half
│ │ │ │ transmittance.half
│ │ │ │
│ │ │ └───Laythe
│ │ │ │ atmo.cfg
│ │ │ │ ocean.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ └───Sunflares
│ │ │ Sun.cfg
│ │ │
│ │ └───Sun
│ │ Ghost1.png
│ │ Ghost2.png
│ │ Ghost3.png
│ │ sunFlare.png
│ │ sunSpikes.png
│ │
│ ├───icon
│ │ icon.png
│ │
│ └───shaders
│ scatterershaders-linux
│ scatterershaders-macosx
│ scatterershaders-windows
│
├───Squad - REMOVED FOR COMPACTNESS
├───StockVisualEnhancements
│ │ StockVisualEnhancements.version
│ │
│ ├───SVE_Configs
│ │ EVE_AtmoSmoother.cfg
│ │ EVE_Atmospheres.cfg
│ │ EVE_Eclipse.cfg
│ │ EVE_OPMAtmospheres.cfg
│ │ EVE_PQS.cfg
│ │ OPMClouds.cfg
│ │ Scatterer_EVEShadows.cfg
│ │ SVE_CityLights.cfg
│ │ SVE_Clouds.cfg
│ │ SVE_JoolRings.cfg
│ │
│ ├───SVE_Scatterer
│ │ │ planetsList.cfg
│ │ │ Scatterer_Settings.cfg
│ │ │
│ │ └───Planets
│ │ ├───Duna
│ │ │ │ atmo.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ ├───Eve
│ │ │ │ atmo.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ ├───Jool
│ │ │ │ atmo.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ ├───Kerbin
│ │ │ │ atmo.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ ├───Laythe
│ │ │ │ atmo.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ ├───Neidon
│ │ │ │ atmo.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ ├───Sarnus
│ │ │ │ atmo.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ ├───Tekto
│ │ │ │ atmo.cfg
│ │ │ │ ocean.cfg
│ │ │ │
│ │ │ └───Atmo
│ │ │ inscatter.half
│ │ │ irradiance.half
│ │ │ transmittance.half
│ │ │
│ │ └───Urlum
│ │ │ atmo.cfg
│ │ │
│ │ └───Atmo
│ │ inscatter.half
│ │ irradiance.half
│ │ transmittance.half
│ │
│ └───Textures
│ │ atmo1.dds
│ │ atmo2.dds
│ │ Aurora.dds
│ │ AuroraDetail.dds
│ │ detail1.dds
│ │ detailCumulus.dds
│ │ detaildark.dds
│ │ detaillight.dds
│ │ DetailLow.dds
│ │ duststorms.dds
│ │ eve1.dds
│ │ geyser.dds
│ │ geyserdetail.dds
│ │ GGAurora.dds
│ │ GGAuroraDetail.dds
│ │ gradient2.dds
│ │ hadrianClouds00.dds
│ │ Jool_bands.dds
│ │ Jool_ring.dds
│ │ kerbin1.dds
│ │ LaytheClouds.dds
│ │ lightning.dds
│ │ main.dds
│ │ Neidon_bands.dds
│ │ Sarnus_bands.dds
│ │ Urlum_bands.dds
│ │ uvnoise1.dds
│ │
│ └───particle
│ particle_NRM.dds
│ rgb.dds
│ rgb3.dds
│ snow.dds
│
└───SVT
│ StockVisualTerrain.version
│
├───configs
│ Bop.cfg
│ Dres.cfg
│ Duna.cfg
│ Eeloo.cfg
│ EnableColliders.cfg
│ Eve.cfg
│ Gilly.cfg
│ Ike.cfg
│ Jool.cfg
│ Kerbin.cfg
│ Laythe.cfg
│ Minmus.cfg
│ Moho.cfg
│ Mun.cfg
│ Pol.cfg
│ Sun.cfg
│ SVT_KopernicusSettings.cfg
│ Tylo.cfg
│ Vall.cfg
│
└───textures
└───PluginData
bump00.dds
bump01.dds
cactus00.dds
cactus01.dds
cliff00.dds
cliff01.dds
cliff02.dds
cliff03.dds
crack00.dds
crack01.dds
desertplanetmoon00.dds
dirt00.dds
dirt01.dds
Duna5_00.dds
dunes2_00.dds
dunes2_01.dds
dwarfplanet100.dds
Eve2_00.dds
evemoon100.dds
gp1icemoon00.dds
gp1minormoon100.dds
gp1minormoon200.dds
gradient.dds
grass.dds
grass00.dds
grass01.dds
ground00.dds
ground01.dds
ice00.dds
ice01.dds
Jool00.dds
Jool01.dds
Jool_ring.dds
KerbinScaledSpace300.dds
moho00.dds
NewMunSurfaceMap00.dds
NewMunSurfaceMapDiffuse.dds
newoceanmoon00.dds
noise00.dds
noise01.dds
pinetree00.dds
rock00.dds
rock01.dds
rockyMoon00.dds
snowydwarfplanet00.dds
sun.dds
sun_corona.dds

EdwardB3020 · March 1, 2019

Is there a way to get rid of the Module Manager atmospheres?

Galileo · March 1, 2019

34 minutes ago, EdwardB3020 said:

Is there a way to get rid of the Module Manager atmospheres?

What are “module manager atmospheres”?

EdwardB3020 · March 1, 2019

42 minutes ago, Galileo said:

What are “module manager atmospheres”?

If you install Module Manager and don't have Scatterer.

JadeOfMaar · March 2, 2019

3 hours ago, EdwardB3020 said:

If you install Module Manager and don't have Scatterer.

The atmosphere haze effect without scatterer is an EVE effect. The only thing that happens when you install MM is that mods will work.

EdwardB3020 · March 2, 2019

27 minutes ago, JadeOfMaar said:

The atmosphere haze effect without scatterer is an EVE effect. The only thing that happens when you install MM is that mods will work.

How to remove it though?

Galileo · March 2, 2019

2 hours ago, EdwardB3020 said:

How to remove it though?

Don’t install EVE

scottadges · March 2, 2019

On 2/2/2019 at 5:23 PM, Pie82 said:

Seems it really was the PSU.

Probably off-topic for this thread, but I noticed you said you were running other AAA games without problem and thought EVE/SVT/etc. was causing the issue. But then the PSU switch fixed it.

As a partially-literate PC user (I've built 1 computer in the last 4 years) I'm just curious why you think it was doing that? Wondering why KSP vs. other games. How it renders stuff or the mod(s) taxing the system?

Anyway, just curious.

JadeOfMaar · March 3, 2019

@scottadges KSP is a software that is not aging well, and is rather incapable of using the GPU to do graphics-related processing and rendering, and has poor or next-to-no multi-threading. As a result, everyone who brags about their powerful GPU does not know mow much their words become merely hot air. KSP mostly uses the CPU to render EVE's volumetric clouds, dealing an immense performance hit that you tend to not expect in a good-looking game these days. A powerful system that can run KSP needs to have fewer and faster CPU cores and just enough RAM and VRAM to hold textures, and just enough GPU power that KSP can run smoothly alongside a web browser and other things that do need GPU.

Pie82 · March 3, 2019

On 3/2/2019 at 5:08 AM, scottadges said:

Probably off-topic for this thread, but I noticed you said you were running other AAA games without problem and thought EVE/SVT/etc. was causing the issue. But then the PSU switch fixed it.

As a partially-literate PC user (I've built 1 computer in the last 4 years) I'm just curious why you think it was doing that? Wondering why KSP vs. other games. How it renders stuff or the mod(s) taxing the system?

Anyway, just curious.

I originally suspected the mod as I couldn’t recreate the issue without it installed. With it installed it always happened on a reasonably complex ship flying thru the cloud layer. Just to be clear it was not the mod just my crappy hardware :-)

Beats me why the PSU was causing this. Since swapping the PSU and cabling it right it hasn’t happened again. Previously it was easy to recreate. Was a hunch based on the evidence, the machine would power cycle with no log, error or bsod. I’ve not seen a modern OS do that in years so the most logical thing was the power supply. It completely powered off for a few seconds then back on so different from a reboot. Could have been other things but the PSU is the easiest and cheapest thing to change so tried that first.

At the points where it used to reset you now just get the standard short stutter. Since only the PSU changed - no windows update, no driver update, no KSP update or even mod update - the PSU must have been it. The original was a cheap no-name one. I couldn’t begin to tell you why only KSP caused this. It was driving me nuts for over a week.

Edited March 3, 2019 by Pie82
Making it clear it wasn’t the mod

storm6436 · March 3, 2019

13 hours ago, JadeOfMaar said:

@scottadges KSP is a software that is not aging well, and is rather incapable of using the GPU to do graphics-related processing and rendering, and has poor or next-to-no multi-threading. As a result, everyone who brags about their powerful GPU does not know mow much their words become merely hot air. KSP mostly uses the CPU to render EVE's volumetric clouds, dealing an immense performance hit that you tend to not expect in a good-looking game these days. A powerful system that can run KSP needs to have fewer and faster CPU cores and just enough RAM and VRAM to hold textures, and just enough GPU power that KSP can run smoothly alongside a web browser and other things that do need GPU.

That's sadly very true. Call me silly, but one of the things I'd hoped for before we ever hit beta was that they'd spend at least one patch cycle updating rendering engine stuff to better balance what was done where; say, like making something like SVE a stock visual option and having integrated it, pushed more of the heavy lifting over to the GPU.

inopinatus · March 6, 2019

Having trouble with SVE and OPM installed together - Kopernicus is giving me "Kopernicus was not able to load the custom planetary system due to an exception in the loading process" if I have both. Individually each are fine. I've removed all other mods except the dependencies.

Here is my KSP.log, any ideas?

https://inopinatus.org/ksp-20190306.log

[KSP 1.6.1] Stock Visual Enhancements [v1.4.1] [20 March 2019]

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation