Jump to content


KSP Team
  • Posts

  • Joined

  • Last visited

Everything posted by JPLRepo

  1. From the video posted above. That is a known issue with Unity Shadows. Usually happens when the sun is at zenith in the sky. We are investigating solutions, but no promises.
  2. I wouldn’t reverse engineer - cause that would be a breach of copyright and T&Cs. but if you raise a bug report on the bug tracker referencing this thread and me. I’ll look into it.
  3. Version 1.5.7 Released for KSP 1.9.x. See Op for details and download links.
  4. Until Contract Configurator is updated for 1.9.x I can't update this mode for 1.9.x Will give it a couple of weeks then consider other options.
  5. Sorry about that, the upload must have failed and I didn't notice. Try again.
  6. Update for KSP 1.9.x. Bunch of changes in the changelog. See the Op.
  7. Everyone at Squad calls it M-uh-n.its pronounced that way and no other.
  8. Ah yes. This shouldn't happen. You can only thaw or freeze one kerbal at a time, otherwise bad things happen. It already does this check in the same part, but it isn't doing it across all parts, I'll add that into the 1.9.x update I'm currently working on.
  9. You are running this mod in KSP 1.9. The current/latest version of this mod does not support KSP 1.9.
  10. That was fixed. Just the bugs have not been updated yet. Our hard working QA team are working on updating the public bug tracker.
  11. Release time for update to my mods to 1.9 = When I have some time over the coming week + a logarithmic multiplier for each person that asks for when it's going to be updated.
  12. The API docs have been updated for 1.9.0. Link in the opening post.
  13. Part Tools has been updated for KSP 1.9.0 This was required to cater for changes make to KSPedia loading. Also removed the second/legacy copy of the part shaders from the bundle. Link in the opening post above. NB: Part Tools now requires Unity 2019.2.2f1
  14. Here’s some notes and details from the team with regards to the changes that come with KSP 1.9.0 Atlas Terrain Shader (Ultra Detail Shader) Quick Guide: I want to use the fancy new shader on a celestial body that doesn't support it. Teach me how! 1. (Offline) Create a texture map detailing the texture indices and strengths of the textures to be shown on the celestial body. (Rules are provided below.) 2. (Runtime) Find the PQS component for the celestial body that you want to change the shader on. Create a new GameObject, attach a PQSMod_TextureAtlas component to it, then parent the new game object to the PQS object. 3. (Runtime) Use ScriptableObject.CreateInstance<CBTextureAtlasSO>() to create a new CBTextureAtlasSO object, then call CBTextureAtlasSO.CreateMap(MapSO.MapDepth.RGB, texture) using the texture created in step 1 to use your texture map. Assign the new CBTextureAtlasSO object to the textureAtlasMap variable of the PQSMod_TextureAtlas component created in step 2. This will ensure that your texture map is used to specify the positions of the textures on the surface of the celestial body. 4. (Runtime) Create Texture2DArray objects of the textures and the normal maps to be used in the material by using KSPUtil.GenerateTexture2DArray(int textureSize, List<Texture2D> textureList, TextureFormat format, bool createMipMaps). Information about the operation can be found here: https://docs.unity3d.com/ScriptReference/Texture2DArray.html 5. (Runtime) Create a new material using the command new Material(Shader.Find("Terrain/PQS/PQS Triplanar Zoom Rotation Texture Array")) and assign the Texture2DArray objects created in step 4 to the _AtlasTex and _NormalTex properties of the material. Fill in the other properties on the material as desired. 6. (Runtime) Assign the new material to both the highQualitySurfaceMaterial and the surfaceMaterial variables of the PQS component for the celestial body. The PQSMod_TextureAtlas component will ensure that all the necessary data is transferred across to the shader when the planetary surface is displayed. I like your textures! I only want to change where they're used on Kerbin! We appreciate the compliment! Just do steps 1 and 3 in that case. I think that you did an excellent job with the way that the textures are mapped to the biomes on Kerbin! I only want to change the actual textures! You're going to make us blush if you keep flattering us! Just do steps 4 to 6. Texture Map Authoring Rules: Two textures per pixel and the strength of each can be specified so that the artist can control blends between the textures. This is done through an RGB texture (the alpha channel isn't used) with the following rules: R: This value corresponds to the texture array index of the first texture. We multiply the texture index value by 10 to avoid errors and make it easier to author, so array index 0 will be 0, array index 1 will be 10, array index 2 will be 20, and so on. G: This value corresponds to the relative strength of each of the textures. So a full value of 255 means that it will only display the texture referenced in R, a value of 127 means that it will display half of the texture referenced in R and half of the texture referenced in B, and a value of 0 means that it'll only display the texture referenced in B, for example. It blends between the values, so use whatever strength makes the most sense for a nice blend between textures! B: This value corresponds to the texture array index of the second texture. We multiply the texture index value by 10 to avoid errors and make it easier to author, so array index 0 will be 0, array index 1 will be 10, array index 2 will be 20, and so on. A: Not used, so don't create an alpha channel. Other Items KSP now uses only one single camera rendering in DX11. Due to improvements done by Unity with regard to rendering using DX11 (Z order reversal amongst other things) KSP now only uses “Camera 00” when rendering in flight, mapview, tracking station and KSC scenes. This improves performance significantly and exponentially depending on what graphics settings you are using. We are unable at this time to do single camera rendering on OpenGL platforms. Added Per Kerbal PhysicMaterial Accessors for Modders so you can adjust each kerbals bounciness using KerbalEVA.SetPhysicMaterial, KerbalEVA.ResetPhysicMaterial. The KSP Assembly version is now set correctly on game start so KSPAssemblyDependency will work for KSP versions. Added events for Action Groups in flight visibility changes so mods can handle any UI changes they need to in each mode. onGUIActionGroupFlightShowing - Fired when the Action Group Editor is about to open in flight. onGUIActionGroupFlightShown - Fired when the Action Group Editor is finished opening in flight. onGUIActionGroupFlightClosed - Fired when the Action Group Editor is closed in flight. Added Pause/UnPause events when the action groups show/hide in flight. Fires OnGamePause and OnGameUnpause. Fix PQS.radiusMax not including some noise PQSMods in its calculations. Should now mean that PQS.radiusMax is no longer below any vertex in most cases. New PartModule called ModuleResourceDrain for the new stock resource drain part can be used like any other PartModule by modders.
  15. Unity Incremental GC has been enabled since KSP 1.8.0
  16. Ah yeah. Sorry that zip file shouldn't be there. will remove it for the next version. A link to the example files Zip I was referring to is in the opening post.
  • Create New...