Nhawks17

Oh well look at that... It does seem to be happening even with EVE removed... Lemme grab a fresh copy and make sure this one didn't break or something. Edit: Should've done more troubleshooting before reporting.... Fresh copy fixed it. Sorry about that blackrack

Oh oh oh... I haven't checked that yet, I'll be able to in about 30 or so minutes.

If you read the last couple of posts on the thread, the issue is already reported It's an issue with the version of EVE I have put in with the current release. I haven't been able to test to see if the the latest development versions of EVE have fixed this because I've run into another issue that needs to be fixed first. Unfortunately it just has to be dealt with until I can get a new release out.

I believe they're set to default so, yes? But yeah, it's on my SVE development KSP so it's just EVE and Scatterer... The issue went away once I removed Scatterer and just had EVE but came back as soon as I added it back.

Yeah it took me about an hour to port SVE over to the new config system... wasn't all that bad just time consuming, now I just need this issue to get fixed

Tried that, it obviously goes away when you reach that fade out altitude but as soon as you go back into it, it returns.

Hiya blackrack, I know your not able to do anything with Scatterer right now but I'm having an issue with Scatterer's feature of applying the black skybox until you reach a certain altitude and it fades to the skybox. With the latest development releases of EVE that feature seems to be applied over EVE's stuff because the sky is showing as black on the ground. I don't know if this is something conflicting in Scatterer or EVE so I'm just letting both you and rbray know about this Here are the logs of when it happens if you need to look at them (when you can). Thanks blackrack KSP.log output_log.txt

Okay, I don't know if this is EVE or Scatterer's doing (I'm going to let blackrack know as well) but with the latest dev versions of EVE it seems to be conflicting with Scatter's feature of applying a black sky until you get past a certain altitude (fades to the skybox). The black sky is showing through the atmosphere so it causes the sky to be black... Like I said, don't know if this is something that Scatterer or EVE needs to fix so I'm going to let you both know Here's some logs if you need to look at it Issue solved

Ohh, you downloaded EVE through Github.. Yeah that explains it. I haven't been able to look into it yet but the most recent versions of EVE has caused the black sky, it's best to just use what is given in my SVE download on my Github. The clouds disappearing is caused by EVE. The latest dev versions of EVE might have that issue fixed but like I said above, that causes the black sky with the current build so it'll have to wait until I can get around to getting everything working properly with the latest EVE versions. I'm trying to decide if my next version will be the release version of SVE or if I release an update sooner and just keep it in the pre-release stage (will lack things I've been working on and will focus mainly on updating configs and EVE), if the next IS the release version I wouldn't expect an update for a little while but we will see.

.... I think I know what's happening, did you install SVE through CKAN or just EVE? Because it looks like my SVE clouds and the "stock" EVE clouds are getting applied, it'd make sense for that to happen if installing through CKAN because I think they made it so that SVE requires EVE which would download both the plugin material and the clouds that come with it.... If that's the case then I might have to remove SVE from CKAN until I can come up with official CKAN support. Edit: I'm still a little confused by your post but I think I'm getting it now In your Gamedata folder if you have a BoulderCo folder you can delete that completely, you only need EnviromentalVisualEnhancements and StockVisualEnhancements.

I'm getting some exceptions as well... Tried the release version as well as the recompiled version sarbian posted a few posts up but here's what I'm getting. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.DirectX.Direct3D, Version=1.0.2902.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. File name: 'Microsoft.DirectX.Direct3D, Version=1.0.2902.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' at DDS4KSP.IMGManager.init() at DDS4KSP.FRM_main.FRM_main_Load(Object sender, EventArgs e) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.6.1063.1 built by: NETFXREL3STAGE CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- DDS4KSP Assembly Version: 0.0.0.1 Win32 Version: 0.0.0.1 CodeBase: file:///E:/Downloads/DDS4KSP/DDS4KSP.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.6.1038.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.6.1038.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.6.1038.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.6.1038.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 4.0.0.0 Win32 Version: 4.6.1038.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.6.1038.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.6.1038.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.6.1038.0 built by: NETFXREL2 CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Ahh gotcha gotcha. Didn't know that about the Linux version!

I get this sometimes when going into the Joolian system, I think it's an issue due to Scatterer loading Laythe and Jool at the same time which just makes the FPS tank, reloading the scene usually fixed it for me.

I'm currently working on reworking Jool to look better than it does now (as well as the layers), what does everyone think of this?

output_log provides more information than the KSP.log most of the time

Is there a crash report or do you see anything in the output_log.txt file that could tell you what happened?

Access Violation in your mono.dll it looks like? Are you running the 64-bit hack?

Check the output log in the crash folder, see what happened

I don't know if this is an actual reason but I noticed odd performance impacts on all of the new EVE cloud packs, mine included. Testing with mine and Proot's (those are the only two that I know of on the new EVE besides stock EVE stuff) I get down to 15-20 FPS with a GTX 970 even with a 1 part ship. So, this may be an issue with EVE and how it puts clouds on planets... I don't know, just my personal testing. Should also add I'm running the 64-bit hack and have tested it on DX9 and DX11

What blackrack said, the only difference between the versions is the resolution of the cloud and citylight textures, everything else is the same. So if you want the clouds from the HR or UR version you can just use that, you don't need to use the MR version at all.

Oh, I can't remember if I (or anyone for that matter) have said this yet but on the main menu for whatever reason the clouds only render on the top half of Kerbin... Not a big deal in the slightest just wanted to point that out

Rbray, just a heads up. I updated my pqs.cfg file and that seemed to fixed the issues I was having with Jool... Now I just need to figure out what is causing my sky to be black

Thanks for helping

Proot, i have to say. I am incredibly upset you released this while my computer is broken But really though, great great work from the pictures I've seen in the thread and I can't wait to try it out myself, once I figure out my computer issue

I don't see blurriness in any of those