Search the Community

Showing results for tags 'postprocessing'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • The Daily Kerbal
  • Kerbal Space Program 2
    • KSP 2 Discussion
  • 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
  • Making History Expansion
    • Making History Missions
    • Making History Discussion
    • Making History Support
  • Breaking Ground Expansion
    • Breaking Ground Discussion
    • Breaking Ground Support
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Twitter


Location


Interests

Found 2 results

  1. KERBAL SPACE PROGRAM POST PROCESSING MOD Introducing KS3P (KSP Post Processing -> KSPPP -> KS3P), a mod that aims to bring post-processing effects to Kerbal Space Program. Ever wondered 'how come Unreal Engine games always look so smooth compared to Unity Engine? Well, that's the result of post-processing. See an example below: Here's another demonstration from my own computer. Without post-processing: With post-processing: Screenshots They say an image speaks a thousand words. Thanks to KS3P, they may even speak more than that. Here are a couple of side-by-side comparisons. Features - Make KSP look better than ever, with post-processing effects! - Low CPU and GPU cost! - Works with and alongside all your favorite mods! (Including CameraTools!) But it gets better... - KS3P is fully configurable, meaning that every post-processing effect can be fine-tuned. Modders can even set up effect configurations to be scene-specific - KS3P has several features to play with: - Anti-Aliasing (FXAA or TAA) - Ambient Occlusion (Note: does not work right in Unity 5.4.0, but should work like a charm with KSP 1.4) - Screen Space Reflection - Depth of field - Motion blur - Eye adaptation - Bloom & lens dirt - Color grading - Tonemapping (Make the colors pop by harnessing the ACES Filmic and the Neutral tonemappers) - User Lut - Chromatic abberation - Procedural grain - Vignette - Dithering DOWNLOAD Mod: SpaceDock [V6.1 for KSP 1.7.X] Source code: GitHub Documentation: https://docs.unity3d.com/Packages/com.unity.postprocessing@2.1/manual/index.html In-Game editor: Open-close with Left-Alt + 3. Documentation on the way.
  2. TUFX - Textures Unlimited Special Effects This is a mod for Kerbal Space Program that makes the Unity Post Process (v2) package available for use within the game. All supported effects from the package are available for use within KSP. The goal of this mod is to add the ability to use industry-standard image post-processing effects during realtime rendering of the game world, allowing for increased visual fidelity in general use, or for specific effects for cinematic purposes through specially configured profiles. TUFX allows for users to select a specific 'profile' to be used for each game scene. These profiles specify which effects will be enabled for the scene, and specify the values for each of the parameters for the effects. The included default profiles in the comparison images below have been setup to be low-impact, both visually and performance-wise. More aggressive post-processing is available through the creation of custom profiles, using the in-game profile editing tools. Before After Cinematic Effects (not default profile) Before After Requirements: Windows / DirectX11, required for single-camera setup in KSP ShaderModel 3.5 or later graphics hardware support (5.0+ recommended) KSP 1.9.0 or later, required for single-camera setup No exceptions. No OpenGL. No DirectX12. Definitely not DirectX9. Any other requirements of the Unity Post Process package (look them up if interested) KS3P will cause conflicts. Choose one or the other. Scatterer currently unsupported (it is not yet available for KSP 1.9+) EVE currently unsupported (it is not yet available for KSP 1.9+) Installation Releases of the mod will be available from GitHub: https://github.com/shadowmage45/TUFX/releases Download the most recent release for your version of KSP, open the .zip file, and extract the contents of the GameData/ subfolder from the package into your KSP installations' GameData/ folder (e.g. Your/KSP/Path/GameData/TUFX). Make sure to include any other dependencies and folders (e.g. ModuleManager) that were included in the release package. Pre-Release Note: Anything marked as a 'Pre-Release' on the GitHub page is exactly that -- a pre-release intended for testing purposes; if you install one of these releases, you are accepting the risks that come with its use (it may not work, may conflict with other mods, may have unfinished features, etc). Configuration The mod includes a default profile for each supported game-scene, and these profiles are included in the standard installation. Additional profiles can be added as KSP-CFG files anywhere in the GameData folder; the loading system will locate all installed TUFX_PROFILE configs, and load all detected profiles into memory for selection and use in-game. Configuration of the mod is best accomplished through the in-game configuration UI. Click the 'TUfx' app-launcher button to open or close the UI; this button should be available in all supported game scenes (except for main-menu, where app-launcher is not supported). From within the configuration UI, select a profile for the current scene/to be edited (only the active profile can be edited). Once a profile has been selected, press the 'Change to Edit Mode' button on the top of the configuration UI. This will prompt the UI to display the current configuration of the profile. Press the 'Enable'/'Disable' toggle by an effect title to toggle that effect on or off. When an effect is enabled the UI will list each of its adjustable properties directly below the effect header row. Each of these properties will have a toggle to enable specifying a custom value; when this is enabled further controls will be displayed to edit the property depending upon the type of property being edited; integer and decimal values show a text input box and slider, color values provide four component input boxes, boolean values provide a simple toggle, etc. The property list for a currently enabled effect can be hidden/shown by toggling the 'Show Props'/'Hide Props' button on the effect header row. This does not disable the parameters, merely collapses them to help clean up the UI view. When finished editing a profile, press the 'Export Selected' button at the top of the UI to export the current configuration into the KSP.log file. From there, you can copy the profile out of the log and rename it to create a new profile, or use the data to overwrite the contents of an existing profile config file. TUFX does not support direct-to-file exporting, as no 'Save File Dialog' has been provided by either Unity or KSP, and I have no desire to create one myself, nor deal with the security issues that would arise from its use. See the included readme.md document for information on config file syntax, and how to manually edit/create profiles. Performance Comparison Comparison data gathered on the following hardware (your results may differ): i5-2500k @ 4.5ghz 24g DDR3 GTX970 Scene <KS3P> <TUFX> <TUFX-Disabled> <Stock> KSC NA 142 170 180 Kerbin-Ground NA 105 118 128 Kerbin-Orbit NA 125 150 165 KS3P was unavailable at the time the testing was performed, so no data was gathered. Dependencies ModuleManager - TUFX depends directly on ModuleManager for its 'Database Reloaded' callback, and will not function unless ModuleManager is installed. ModuleManager has been included in the release packages, and is redistributed under the terms of its own license. Further information on Module Manager can be found on the KSP Forums at: ( https://forum.kerbalspaceprogram.com/index.php?/topic/50533-18x-19x-module-manager-413-november-30th-2019-right-to-ludicrous-speed/ ), and the license and source-code may be found on the ModuleManager GitHub repository: ( https://github.com/sarbian/ModuleManager ). Known Issues and Bug Reports See the github issues repository: https://github.com/shadowmage45/TUFX/issues The change to use HDR rendering can cause occasional artifacts. If these are present, you can turn off HDR in the profiles by setting the hdr flag to 'False'. Licensing/Legal Full source code for the TUFX assembly is available on github: https://github.com/shadowmage45/TUFX Source code for Unity post processing shaders are available on github: https://github.com/Unity-Technologies/PostProcessing Custom code and classes (everything outside of the PostProcessing source folder) is under GPL3.0 or later license, the full text of this license may be found included in the release packages and on the GitHub repository: https://github.com/shadowmage45/TUFX/blob/master/LICENSE.txt Unity developed classes, shaders, and textures are provided under Unity companion license, with source and license references available from: https://github.com/Unity-Technologies/PostProcessing Modifications to Unity classes (adding ConfigNode load/save methods) are released under public domain or as close as possible under US law. ModuleManager (fork by Sarbian) is included and redistributed under its license: https://github.com/sarbian/ModuleManager/blob/master/README.md Credits @Shadowmage - Coding and development. @SQUAD - For creating and publishing KSP. @sarbian - Forking and maintaining ModuleManager @The White Guardian - For creating KS3P, without which I would have never known about the Unity Post Process packages.