Search the Community

Showing results for tags 'pqs'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • The Daily Kerbal
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website
  • KSP Pre-release
    • 1.2.9 Pre-release Branch
    • 1.2.9 Pre-release Modding Discussions
    • 1.2.9 Pre-release Bug Tracker


  • Developer Articles

Found 7 results

  1. About Kopernicus is a KSP add-on that allows for modification of stock planets and the creation of new planets via modification of the system prefab. Why is this advantageous you might ask? Previous planet adder mods, such as Planet Factory, modified the live planetary system and had to keep multiple hacks actively running to provide these worlds. We strive to provide the least hacky solution by introducing planets into the game in the exact same manner Squad would. The Kopernicus loader is a one step process. It is started before the planetary system is created and rewrites a property called PSystemManager.Instance.systemPrefab. The game itself then creates *our* planetary system as if it were blessed by Squad themselves. The mod's function ends here, and it terminates. Kopernicus introduced worlds require zero maintenance by third party code, as all support is driven entirely by built in functionality. This yields an incredibly stable yet incredibly flexible environment for planetary creation. We provide tools for customizing every aspect of a planet such as biomes, the scaled space model, the surface materials, the structure of the terrain, and much more. Eventually we strive to provide replacement capability for the StarSystems mod. The methods they used to support other stars (reparenting the sun, switching the sun for solar panels, etc.) causes issues. KSP's engine assumes that Sun.Instance.sun is set to the center of the universe. Unfortunately, this also is what the sun light in the sky and the solar panels key off of as well. The solution is likely to include additions to the local space camera system (multiple lens flare and light sources) and custom part component mods for solar panels to replace the stock ones. Current Release Release 1.2.2-6: Kopernicus is licensed under the GNU Lesser General Public License Instructions Copy the contents of the GameData/ folder to KSP's GameData/ folder Launch KSP and enjoy! Please report any bugs you may find at Examples Selectively copy folders inside KopernicusExamples/ into a GameData/KopernicusExamples/ folder. There are a number of examples of how to use Kopernicus. You have to download the examples from their GitHub repository: Note - reparenting Kerbin or the Sun causes the sky to be incorrect in the space center view. It is, however, correct in the flight view and the flight map view. Reparenting the sun causes other stars positions to not update in the tracking station for some reason. How to get support We're always willing to help you with your issues, but however, there are a few things you'll have to do before we can help you: First of all, try to find the issue yourself. Look at the Kopernicus log-files (KSPRoot/Logs/Kopernicus), and compare your config with the examples / other working configs. If you can't fix it yourself, please make sure that all your mods are up to date, and that they are installed correctly Send us the output_log.txt / Player.log, the Kopernicus log-files and one single plain-text config file that causes the issue, including the used textures Final Note: We won't install a full config, or a config that depends on other packs. If you send us something like that, we reserve the right to ignore you. P.S. If you need help with variables or nodes, just post your config. In this case, we don't need log files Expansions and Documentation If you need a graphical UI, you can use our fork of KCreators KittopiaTech: We have an IRC channel on EsperNet: #Kopernicus Team Thomas P. (acting lead developer) NathanKell (knowledge base) KillAshley (examples, testing and official rant director) Sigma88 (monkey, mascot) Contributors Teknoman 117 aka. Nathaniel R. Lewis (co-founder, lead developer, busy right now) Bryce Schroeder (founder of the Kopernicus project) Gravitasi (a lot of useful features + former maintainer of KopernicusTech) KCreator (Creator of KittopiaTech, where some code has been borrowed from) MrHappyFace (Creator of the external loading API and the KopernicusExpansion mod) zengai (code for loading .bins from other paths that Kopernicus/Cache) Majiir (CompatibilityChecker utility that is used to deactivate Kopernicus on unsupported versions) Padishar (ScaledSpace OnDemand optimisations) WazWaz (Scatter Collision fix) Like my mods? Please consider supporting me and my mods on Paypal! I would greatly appreaciate it, since I don't get much money anyways. However note, that this doesn't grant you anything special, but it will help to keep my motivation up. Therefor it's just an extremly nice way to say "thanks". A lot of people helped making this possible, like @Sigma88, @KillAshley and @NathanKell. If you decide to buy me a coffee, please buy them one too.
  2. Welcome to the Kopernicus Procedural Quad Sphere Library Expansion, or KLE for short. So, you're probably wondering, TWG, what IS KLE? Allow me to tell you all about it. KLE is a .dll file containing several scripts that add various new generation options to users. You see, KSP creates planets using something called 'Procedural Quad Sphere Mods'. Minmus, for example, is the product of the PQSMod 'VertexPlanet'. Gilly is the result of 'VertexSimplexHeightAbsolute'. KLE adds several new PQSMods, using the Microsoft C# coding language to give planet creators several new options, things that weren't possible before. Users can also suggest custom PQSMods although, mind you, not everything is possible. No 'planet sculpters'. Current PQSMods included: AltitudeMath CoastlineSmoother FlattenRange HeightColorMap3 (WIP) HybridNoise (after a suggestion by @GregroxMun) MapArtist SimplexNoiseRange SmoothenAltitude VertexCanyons VertexNoiseRange Special mods: ParadiseSpike - an in-dev mod aiming to generate something like this: In-dev PQSMods: - Templator, enter a planet type and it generates a base planet. - And many more that I forgot about... DOWNLOAD SpaceDock
  3. Description This Plugin is a continuation of KCreators "KittopaTech Ingame Terraforming" plugin, that can edit the stats of planets at runtime, via. a Graphical Interface. The original KittopiaTech was mainly developed by KCreator, with some additional content by Kragrathea (Utility code) and Gravitasi (ScaledSpace fixes and more). Their work was modified by BorisBee (initially, he's pretty inactive now) and myself, Thomas P., to be more modular, stable and user-friendly. Because Kopernicus offers us already a fully functional API, we decided to change the goals of this plugin. Instead of a standalone Planet-Editor, this is now an add-on for Kopernicus. This has many additional reasons, for example, the messy config-saver / -loader. What has been changed? Complete rewrite of the UI-Code (Planet_GUI.cs) Replaced the ConfigLoader with a ConfigSaver that can export dumps of the planet in a Kopernicus compatible format Added an option to completely remove a PQSMod. Seperated ScaledSpace export and PQS-Texture export. Made the Instantiation-Button functional, via. hacking PSystemManager to spawn a body that is instantiated from the systemPrefab. It's still hacky, and it can break some mods. Added Support for HeightColorMap-Landclasses Completely new LandClass-Modder Support for editing PQSMod_VertexPlanet.SimplexWrapper and NoiseModWrapper PQSLandControl.LerpRange editing Improved Particle-Editor Reworked the Map-Exporter, so that it uses a Coroutine to generate the maps. That means, that exporting maps no longer freezes your game, but it still takes some time until the generation is finished. But at least, you can do other things in the meantime. We have added Support for editing PQS-Materials. You can now load MapSO's and Textures through a FileBrowser Improved Ring-Editor, you can now edit rings after creation, delete the selected ring. Curve Editor for editing FloatCurves Reworked Star-Fix code, to use StarLightSwitcher Added a ScaledSpace editor, and moved the export buttons to it ScaledSpace and Texture updater save to disk automatically now Added Support for adding / removing oceans, and for adding PQS to gasplanets You can now enter whatever you want into the numeric fields. If the value isn't parseable, you get a warning and Kittopia won't apply it. Removed all apply buttons, Callbacks are used now. To-Do List Readd support for GroundScatter Maybe other things? Suggest something! Screenshots Download Grab the latest KittopiaTech release from the GitHub repository: You can open the Ingame-UI with Ctrl + P License "The KCreator license" KittopiaTech incorporates Kopernicus, which is licensed under LGPL. Source Like my mods? Please consider supporting me and my mods on Paypal! I would greatly appreaciate it, since I don't get much money anyways. However note, that this doesn't grant you anything special, but it will help to keep my motivation up. Therefor it's just an extremly nice way to say "thanks".
  4. This thread is an attempt to document the Kopernicus planet mods various PQS modifiers and how they affect a planet. NOTE: while this will give you information about the pqs mods, it is best to mess around with the values to fully understand what the mod actual does (plus it's more fun that way) people should post information about various PQS mods such as VertexHeightNoise and add information and a picture of it in game there is a list of PQS mods here: (link found in post by killashley) the ultimate goal of this thread is to be a complete dictionary of the various pqs mods so planet makers don't get scared off (though they should still play with the mod on their own) this will also allow more advanced planet makers to find a good PQS mod by looking through this instead of trying to remember them all Kopernicus mod thread: What the values mean AerialPerspectiveMaterial coming soon AltitudeAlpha coming soon BillBoardObject coming soon FlattenArea coming soon FlattenAreaTangential coming soon FlattenOcean HeightColorMap coming soon HeightColorMap2 also coming soon HeightColorMapNoise coming sooner LandControl coming soon MapDecal coming soon MapDecalTangent coming soon MaterialFadeAltitude coming soon MaterialFadeAltitudeDouble coming soon MaterialQuadRelative coming soon QuadEnhanceCoast coming soon SmoothLatitudeRange coming soon TangentTextureRanges coming soon VertexColorMap coming sooner VertexColorNoise coming soon VertexColorNoiseRBG coming soon VertexColorSolid coming soon VertexColorSolidBlend coming soon VertexColorSolidBlend coming soon VertexDefineCoastLine Coming soon VertexHeightMap coming soon VertexHeightMapStep coming soon VertexHeightNoise VertexHeightNoiseHeightMap coming soon VertexHeightNoiseVertHeight coming soon VertexHeightNoiseVertHeightCurve coming soon VertexHeightNoiseVertHeightCurve2 coming soon VertexHeightNoiseVertHeightCurve3 coming soon VertexHeightObolate VertexHeightOffset coming soon VertexNoise coming soon VertexRigedAltitudeCurve coming soon VertexSimplexColorRGB coming soon VertexSimplexHeight coming soon VertexSimplexHeightAbsolute VertexSimplexHeightAbsolute coming soon VertexSimplexHeightFlatten coming soon VertexSimplexMultiChromatic coming soon VertexSimplexNoiseColor VertexVoronoi VoronoiCraters Make object main menu body:
  5. I'm trying to make my LaserDist mod a bit smarter about reporting the kind of thing the laser has hit: ground versus building versus scatter rock (that last one is only for mods have made the scatter rocks have colliders). The current logic is along these lines (this is a simplified version that demonstrates where I'm having a problem with a lot of the extra stuff stripped out): RaycastHit hit = bestLateUpdateHit; // bestLateUpdateHit is populated elsewhere in the mod GameObject hitObject = (hit.transform == null ? null : hit.transform.gameObject); if (hitObject != null) { CelestialBody body = hitObject.GetComponentInParent<CelestialBody>(); if (body != null) { // code that handles the case where the raycast hit terrain } else { // code that handles the case where the raycast hit something other than terrain. } } The problem is that in my testing for whether the raycast hit terrain or something else, testing for CelestialBody generates false positives because in addition to being true for terrain, it's also true for space center buildings, and every other non-vessel object. This makes sense if SQUAD has designed things so that the buildings are children of the CelestialBody just like the terrain polygons are, which of course they have to be so they can stay "glued" to the planet surface and move with it. So what I'm looking for, is what type "T", or what set of "T"'s can I use in the call GetComponentInParent<T>() that will help me distinguish "this thing is the ground" from "this thing isn't the ground"? I've been trying to find experimentally at runtime just what the full parent-chain looks like for my hits all the way up (i.e. this component is a member of this component which is a member of this component, etc) but the problem I'm having is that C# won't allow me to make type T in the various thingy.GetFoo<T>() calls be the open-ended GameObject type or Component type. It insists I use a type a bit more specific than that, and the whole point of the excercise is that I don't actually know what those types are yet and I'm trying to discover them. I haven't found in the Unity API where the call is for "just get the immediate parent, and I don't know yet what type that parent will be. I'd like to print it at runtime." So because I don't know the actual component tree layout SQUAD uses for terrain versus building meshes, and I haven't succeeded at finding that "just get me the parent" call so I can do my own investigation and learn it, I don't know how to discover what kind of thing my raycast has hit. Does anyone know which type T with GetComponentInParent<T>() will find a hit for ground but not for buildings? (or visa-versa).
  6. So I'm trying to make textures with PQS for KSP 1.1! All the colors of my custom planet are still the same and everything about my custom planet looks exactly the same as minmus except for the height. At least the colors have to be different, right? My planet file: I hope there is something I'm doing wrong!
  7. Hello again everyone, I am currently having issues trying to revive one of my old modifications but after compiling to KSP 1.1 I have noticed that the CelestialBody.pqsController function no longer has any attached subroutines for example, CelestialBody.pqsController.GetSurfaceHeight(Vector3d) In KSP 1.0.5 pre Unity 5, was a valid function. However now this does not seem to exist, throwing the following error during compiling: Error 2 'PQS' does not contain a definition for 'GetSurfaceHeight' and no extension method 'GetSurfaceHeight' accepting a first argument of type 'PQS' could be found (are you missing a using directive or an assembly reference?) C:\Users\Marcus\Documents\KSPModding\MaritimeRelease\Source\BackgroundScene.cs 212 52 BoatNavigation I am assuming members of this function have now been changed to Private rather than Public somewhere in the transition to Unity 5 and 1.1? Or that another reference is required from the KSP Managed folder? If there is no apparent solution does anyone know another method of getting surface height from a vector? The vessel in question is Inactive and unloaded due to the nature of the plugin which is why I think I used this function in the first place Whitecat106