Jump to content

rbray89

Members
  • Posts

    2,719
  • Joined

  • Last visited

Posts posted by rbray89

  1. 46 minutes ago, VonFrank said:

    I'm a little curious about how the celestial shadows function works.

    With the most recent versions of EVE and RSS, I notice that eclipse shadows on Jupiter seem to work properly when the config file is modified appropriately, but any planet farther than that fails to render the shadows. Is there a limit to the calculated distance from the sun for the celestial shadows to work properly?

    Also, I've noticed that many shadows are comprised of 100% umbra and no visible penumbra at all. Every shadow (regardless of relative size and proximity) should have at least some penumbra, but not all should have an umbra. So is this an issue somehow with RSS conflicting, or is it a feature of realism not possible at the moment?

    Shadow configs are required for them to work. What pack are you using? Logs? Screenshot? (Help me help you)

    The celestial shadows *should* be fairly accurate with regards to umbra and penumbra. Not certain with RSS though. Things that could trip it up would be things like scaling issues and Kopernicus not setting radii correctly.

    As distance increases from the Sun, penumbra becomes less and less. The only reason we have penumbra is due to the size of the light source. So if your sun is only a sliver of light, your penumbra will basically be non-existant. 

    So yeah, in many circumstances (eg. Jool) the size of the sun isn't large enough to create MUCH of a penumbra (it is still  there if you look carefully). Kerbin-mun creates a sizable Penumbra on the other hand. Most of the images online demonstrating Umbra/Penumbra aren't good representations because the scale is WAY off.

    EDIT: Added code for the curious. v is the point of interest, R is the Solar radius, r is the body radius, P is the Sun position p is the body position.

    inline half BodyShadow(float3 v, float R, float r, float3 P, float3 p)
    	{
    		
    		float3 D = P - v;
    
    		float a = PI*(r*r);
    		float3 d = p - v;
    
    		float tc = dot(d, normalize(D));
    		float tc2 = (tc*tc);
    		float L = sqrt(dot(d, d) - tc2);
    
    		float scale = tc / length(D); //Scaled Sun Area to match plane of intersecting body
    		float Rs = R * scale;
    		float A = PI*(Rs*Rs);
    
    		float s = saturate((r + Rs - L) / (2 * min(r, Rs)));
    		s = (INV_PI*asin((2 * s) - 1)) + .5;
    		return lerp(1, saturate((A - (s*a)) / A), step(r, tc)*saturate(a));
    	}

     

  2. 2 hours ago, Axly Kerman said:

    2 CTDs within 6 minutes including restarting KSP. Both happened when exiting VAB. 64 bit.

    rared log directories from the two crashes http://s000.tinyupload.com/index.php?file_id=07083539857338456640

    If I should have included more than the two directories (2016-05-01_172138 and 2016-05-01_172712) I apologize.

    You are running out of memory. Looks like it might actually be caused by Kerbal Alarm Clock: 
     

    5/1/2016 5:26:41 PM,KerbalAlarmClock,API Ready
     
    (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64)
    
    DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 673616.
    DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 673616.
    DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 673616.
    DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 673616.

     

  3. 2 hours ago, Poodmund said:

    I can use the X offset to adjust the Longitude but when adjusting the Z offset is does change the original latitude of the texture but it still rotates around the Y axis pole on the equator so you get a warbling effect.

    Beware the incoming massive .gifs...

    ^ Works fine with no Z offset.

    ^ With a offset at Z the texture rotates around the Y axis pole sitting at 0 Latitude which creates a standing wave like warble.

    Getting confused here. I ideally want the Z axis to work for the the offset but then not apply when the rotation is applied.

    If I were doing this, I'd do it this way:

    1. Texture on Y axis.
    2. Offset of x,z,0
    3. Speed of x,z,0
    4. Rotation Axis0: 1,0,0
    5. Rotation Axis1: 0,0,1
    6. Rotation Axis2: 0,1,0

    You just have to remember that you aren't using the body's axis, you are using the CLOUD axis. You have to imagine the axis being moved around.
    This also means that you could do NON-X/Y/Z axis too... Say you want the clouds to swirl around the planet, you can do so by messing with Axis0 and Axis1 and speed/offset of x and z. 

    EDIT: Thought I'd explain what you are seeing in your second GIF as even I had trouble visualizing it.

    What is happening is that when you rotate on Y, you change where your X and Z axis are. 
    This isn't much of an issue when you only use X to rotate after your Y, but when you think about it, you end up with something like this:

    etVBEoP.png

  4. 1 minute ago, Poodmund said:

    @rbray89 I am trying to replicate a hurricane by using one cube face with the hurricane texture's, storm eye directly in the center of the texture. I apply it in game, say as the Top Face and change the rotationAxis1 to be 1,0,0 so that the texture rotates with its axes through the eye... creating a spinning storm. I can change the speed of the rotation of the storm by increasing the speed parameter as 0,x,0.

    This is all desirable but when it comes to locking down the eye of the storm to a specific place over the planet/moon I am having trouble. I can change the Z value of the offset to change the Latitude of the storm but as I have locked down the other two axis of rotation into the same plane I cannot then change the offset of the X or Y to change the Longitude of the storm so that I could, for example, have two storms 10 degrees South of the equator, but on opposite sides of the sphere.

    Any ideas?

    The axis of rotation are applied in order... As are the offsets. So what you can do:

    1. Place the texture on the Y axis.
    2. Rotate on Z or X using offset
    3. Rotate on Y axis using speed.

    This will get you a spinning texture at wherever you rotated the Y axis to be.

  5. 5 hours ago, Warezcrawler said:

    In space flight I get a lot of null reference errors, which I believe is related to EVE, based on there is a dll called "Utils.dll" in EVE.

    
    [EXC 11:17:01.668] NullReferenceException: Object reference not set to an instance of an object
    	Utils.DeferredRenderer.OnWillRenderObject ()

    It comes many, many, many times in a row. I have had flight where it did not appeare, but I'm unsure of what is causing it.

    Log file

    Can anybody conferm this error?

    This may simply be an old install (there was a quick patch put up shortly after release to address this). 

  6. 2 hours ago, SquaredSpekz said:

    Celestial Shadows? So Mun creates shadow on Kerbin?

    Exactly! Be on the lookout for it. Craft aren't currently affected yet though.

    2 hours ago, Tricky14 said:

    Hi, bit of technical feedback here. Eve is good, but nearby planets and to the ground the textures and light sources kind of tend to scale poorly.

    I was wondering if megatexturing might be a better solution for EVE. It's supported in Unity 5 and allows you to maintain detail at all distances at no significant memory increase. Tradeoff is a larger download size, but I don't think that will hold many people back from EVE at this point.

    http://docs.unity3d.com/Manual/SparseTextures.html

    I actually do something similar in the shader (the large equirectangular format has been replaced with a multi-map system. Textures can now be represented as 6 (or 2) textures where RGB components equate to the different sides of the cubemap, or one channel in the 6 textures is used for one alpha mask). The problem isn't actually the mechanism, it is my awful textures (programmer not an artist) If you open up the textures in GIMP or PS you'll see what I mean. Other pack authors actually know what they are doing in graphics packages. I just supply the backend :) Right now my textures are 2k (actually scaled from 1k without any detailing), but they could easily be bumped up to 8k (for machines that can handle it)

  7. 9 minutes ago, MetaframeNL said:

    I guess its the volumetric clouds, so i have to disable that because i can run it in high after the clouds. So the search to find the keys for the GUI begins here! :D

    (alt-N?)

    ALT+0. Navigate to the clouds config, and either disable the volume clouds (radio button) or lower the Area values. Don't forget to hit apply and save.

  8. 3 minutes ago, Cooly568 said:

    Heya, so apparently what I've been doing recently is going around asking mods about little, issues.

    So uh, derp, sorry. Anyways...

    I've been trying to run a lot on my laptop, and the volumetrics really kill the FPS, by kill, I mean, 20 FPS, and without the volumetrics I'm looking at a steady 34. But my question is if theres a way to, say, lower the volumetric density? To still to get the volumetrics without a ton of FPS hit? I swear you could do it in much older versions of EVE, but, not sure.

    ALT+0 and navigate to the clouds config. There you'll see in the volumetrics section two config items for IIRC Area and Division. Area controls the size of the spread, and division controls density.

  9. 1 hour ago, blackrack said:

    So... I got a real job with a major software company, I didn't do great in all the technical questions but apparently making and maintaining a mod like this is a huge selling point.

    Thanks for everyone who supported me and supported scatterer over the past year, it means a lot to me.

    I will be back with more neat stuff once things settle down.

    Congrats! I hope this doesn't cut into your modding time *too* much :wink:

  10. 8 minutes ago, Ser said:

    I have a huge performance hit on 1.1. Mainly when looking (or getting into) volumetric clouds FPS drops from 30+ to 7. This starts once the view is just over the horizon. Removing Scatterer doesn't help. Tried all quality variants with no much difference.

    Nothing like that happens when using plain EVE so I tend to blame volumetric clouds.

    KSP x64, game settings maxed out (except for lighting and shadow cascades). Core i5, 8Gb Ram, GeForce GTX550Ti w.1024Mb RAM.

    What could be done to improve performance?

    I'm working on a few small tweaks that may help performance.

×
×
  • Create New...