Jump to content

Search the Community

Showing results for tags 'opengl'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Kotor Modding
    • Mod Releases
    • General Kotor/TSL Modding
    • Modding Tools
    • Work In Progress
    • Tutorials
    • Game Saves
  • Mod Projects
    • TSLRCM
    • M4-78 Enhancement Project
    • KotOR1 Restoration (K1R)
    • Revenge of Revan
    • KotOR Toolset
  • Jedi Knight Series
    • General Discussion
    • Mod Releases
  • Other Games
    • Other Games
    • Dantooine Theater Company
  • General
    • News
    • Knights of the Old Republic General
    • Star Wars
    • The Old Republic
    • Site Feedback
    • General Discussion

Blogs

  • Blog 1
  • The memories of Mandalore
  • Blog 63
  • Varsity Puppet's Brain Dump
  • Working Class Hero's Blog
  • mmidnight's Blog
  • Blog-Tastika
  • Darth Malious' Blog
  • The Beta Community's Voice
  • sallyrit's Blog
  • Sith Holocron's Blog
  • Diablo3gold
  • Marginalia
  • Mindwizard's Blog
  • Journal Log Of Penally's Bounties
  • Mudslinger077's Blog
  • starwars1234's Blog
  • Blaaargh.2da
  • Kate The Bionic Uterus' Vibrating Submarine
  • Darth Nuge's Blog
  • The Xuul Report
  • KOTOR Fan Theories
  • Benny Chan style
  • Darth_Sapiens' Blog
  • Neville's Blog
  • Darth_Sapiens' Blog
  • TimmyDean's Blog
  • Malkior's Blog
  • DarthSidious4.2's Blog
  • Darth Pravus' Blog
  • Help
  • Canderis' Blog
  • The Musings of Eauxps
  • xander2077's Blog
  • DeadMan's chest
  • pepoluan Far Far Away
  • Rece's Videos
  • jc2's Journal
  • Kexikus' Blog
  • Kreia's Blog
  • Fair Strides' Blog
  • Pazuzu156's Blog
  • GoldLeader's Blog
  • Steira Shipyards
  • lyuscherbakova1986's Blog
  • superSzym's Blog
  • Leilukin's Blog
  • N-DReW's Datapad
  • magdahalo's Blog
  • Trouble Successfully Using Kotor II TSLRCM 1.8.5 On Windows 7 x64-Bit Laptop
  • DarthTyren's Blog
  • The Holocron of Darth Kyber
  • Darth Varkor's KOTOR Machinima Saga: Production Blog
  • ADG12311990's Blog
  • Unusual's VA Blog
  • Draconian's TSL mod request.
  • darthbdaman's Holocron
  • JC's Blog
  • L0ki's Blog of questions & brief WIP things
  • The Iriaz Archives
  • Breakfast With eb
  • Cathar Handmaiden Skin?
  • Kast's Datapad
  • Having fun with the KotOR maps.
  • AndroidKotOR Modded
  • Starıka's Jedi Academy Machinimas
  • KotOR II Damage Calculator
  • Help Modding
  • A step-by-step guide for widescreen in Star Wars: Knights of the Old Republic
  • 13 gigabytes, 13 brain cells
  • Modding Tools
  • StellarExile Mod Stuff
  • Jedi Knight: Jedi Academy films by Cor
  • Something of a moment of truth
  • Music for Streams
  • LoneWanderer's blog
  • modder 9's blog
  • Community Requests
  • Kotor combined saga blog
  • My Kotor Machinimas
  • How do you stream with your Widescreen fixes?
  • Looking for advice to solve a challenging bug: Eastern Dune Sea is resetting every time upon entering

Categories

  • Knights of The Old Republic
    • Media
    • Mods
    • Skins
    • Modder's Resources
  • The Sith Lords
    • Media
    • Mods
    • Skins
    • Modder's Resources
  • Jedi Knight Series
    • Maps
    • Mods
    • Skins
    • Other
  • Game Saves
  • Other Games
  • Modding Tools

Product Groups

  • Premium Membership
  • Modders Account

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. View File K1 Modern Driver Compatibility Turn off grass. For years that has been the first answer to almost any KOTOR problem, and it was good advice, because on a modern PC the grass really does tear itself across the sky. This patch fixes that, and quite a lot else. KOTOR decides how to light the world once, when it starts, choosing between two methods built for graphics cards of 2003. On most machines today neither is on offer, so the game quietly falls back to a path that was never finished: no proper lighting on walls and floors, no reflections on metal or armour, no fog, no soft shadows, and none of the screen effects. It still runs. It just looks wrong, and a lot of people have never seen it look right. This rebuilds that lighting using something every modern card does support, and puts the game back on the paths the developers actually finished. The grass is one of them. If you play on an NVIDIA card, the lighting has been working for you all along. Those drivers still carry register combiners, one of the two original methods, and it does the job properly. It is also an extension from 2001 that no other vendor implements, surviving on one company's willingness to keep shipping it. This moves every card onto a method that is still current, so there is one path everyone is exercising rather than one propped up by goodwill. What you get back Grass that stays on the ground Lighting on walls and floors, the baked lighting that makes interiors look lit rather than flat Reflections on metal, armour and polished surfaces Fog, in the places the game meant to have it Soft shadows, and the screen effects: bloom, blur, film grain, the distortion around force powers, and the colour wash on some cutscenes Requirements KOTOR 1, version 1.0.3. GOG, Steam and the CD release all work. Install it with the KotOR Patch Manager. Your game files are not modified; the manager applies the patch while the game runs. It replaces the separate cube map fix and soft shadows fix. Both are folded in, so disable those if you have them enabled in the patch manager. Source, releases and issues: https://codeberg.org/Synchro/kotor-modern-driver-compatibility Settings, if you ever need them You do not need any of this to play. The first time you run it, a file called `K1DriverCompat.ini` appears next to `swkotor.exe` with every option listed, explained, and switched off. Open it and delete the `#` in front of anything you want to change. The one worth knowing about is `look`, which chooses between the two ways cards of 2003 drew bright light. `look = nvidia` is the default and the calmer of the two. `look = ati` lets strong lights bleach out what they land on, the way a Radeon did. Neither is a bug, and neither is more correct than the other. Tested on AMD, Intel and NVIDIA hardware, on Windows and on Linux through Proton, across the GOG, Steam and CD releases. If something looks wrong `logs/K1DriverCompat.log` in your game folder holds one session and is overwritten each run, so there is only ever one file to send. Setting `log = debug` in the ini before reproducing the problem makes it far more useful. Thanks @Lane and @J tested this on cards and I don't own. Nearly everything here is based on how some particular drivers behave, and that is worth nothing until somebody with that hardware runs it and reports back. The faults that turned up that way are ones I had no way of finding on my own. @Lane also wrote the KotOR Patch Manager, which is what this ships for. LLM Disclosure This project made use of an LLM during development, in the following capacities: Brainstorming: exploring possible approaches and design directions Decompilation assistance: help interpreting and structuring reverse-engineered code Code comments: refining and clarifying existing comments Skeletons and fixes: generating initial code scaffolding and minor fixes All LLM-assisted output was modified and reviewed by a human before being committed. Submitter Synchro Submitted 08/16/2026 Category Mods K1R Compatible Yes  
  2. Version 1.0.0

    2 downloads

    Turn off grass. For years that has been the first answer to almost any KOTOR problem, and it was good advice, because on a modern PC the grass really does tear itself across the sky. This patch fixes that, and quite a lot else. KOTOR decides how to light the world once, when it starts, choosing between two methods built for graphics cards of 2003. On most machines today neither is on offer, so the game quietly falls back to a path that was never finished: no proper lighting on walls and floors, no reflections on metal or armour, no fog, no soft shadows, and none of the screen effects. It still runs. It just looks wrong, and a lot of people have never seen it look right. This rebuilds that lighting using something every modern card does support, and puts the game back on the paths the developers actually finished. The grass is one of them. If you play on an NVIDIA card, the lighting has been working for you all along. Those drivers still carry register combiners, one of the two original methods, and it does the job properly. It is also an extension from 2001 that no other vendor implements, surviving on one company's willingness to keep shipping it. This moves every card onto a method that is still current, so there is one path everyone is exercising rather than one propped up by goodwill. What you get back Grass that stays on the ground Lighting on walls and floors, the baked lighting that makes interiors look lit rather than flat Reflections on metal, armour and polished surfaces Fog, in the places the game meant to have it Soft shadows, and the screen effects: bloom, blur, film grain, the distortion around force powers, and the colour wash on some cutscenes Requirements KOTOR 1, version 1.0.3. GOG, Steam and the CD release all work. Install it with the KotOR Patch Manager. Your game files are not modified; the manager applies the patch while the game runs. It replaces the separate cube map fix and soft shadows fix. Both are folded in, so disable those if you have them enabled in the patch manager. Source, releases and issues: https://codeberg.org/Synchro/kotor-modern-driver-compatibility Settings, if you ever need them You do not need any of this to play. The first time you run it, a file called `K1DriverCompat.ini` appears next to `swkotor.exe` with every option listed, explained, and switched off. Open it and delete the `#` in front of anything you want to change. The one worth knowing about is `look`, which chooses between the two ways cards of 2003 drew bright light. `look = nvidia` is the default and the calmer of the two. `look = ati` lets strong lights bleach out what they land on, the way a Radeon did. Neither is a bug, and neither is more correct than the other. Tested on AMD, Intel and NVIDIA hardware, on Windows and on Linux through Proton, across the GOG, Steam and CD releases. If something looks wrong `logs/K1DriverCompat.log` in your game folder holds one session and is overwritten each run, so there is only ever one file to send. Setting `log = debug` in the ini before reproducing the problem makes it far more useful. Thanks @Lane and @J tested this on cards and I don't own. Nearly everything here is based on how some particular drivers behave, and that is worth nothing until somebody with that hardware runs it and reports back. The faults that turned up that way are ones I had no way of finding on my own. @Lane also wrote the KotOR Patch Manager, which is what this ships for. LLM Disclosure This project made use of an LLM during development, in the following capacities: Brainstorming: exploring possible approaches and design directions Decompilation assistance: help interpreting and structuring reverse-engineered code Code comments: refining and clarifying existing comments Skeletons and fixes: generating initial code scaffolding and minor fixes All LLM-assisted output was modified and reviewed by a human before being committed.
  3. Guide Updated 10/26/14 This guide requires Nvidia Inspector Currently there are no options to get ENB, SweetFX, etc working in Kotor/Kotor2. These options will give you the highest quality for Antialiasing, Texture Filtering, Screen-Tear, and input delay. 1) Launch Nvidia Inspector, and open "Driver (256+) Profile Settings. 2) Click the drop-down arrow by the Home Icon. Search and Click the Profile for "Star Wars: Knights of the Old Republic 2" Use my settings below as reference, or import my profile. Make sure to apply changes! Antialiasing - Mode - Override any application setting Antialiasing - 8xQ (8x Multisampling) // Or set to 4x Antialiasing - Transparency Supersampling (8x Sparse Grid Supersampling) // Or set to 4x Anisotropic Filtering Mode - User-defined / Off Anisotropic Filtering Setting - 16x Texture Filtering - LOD Bias (OGL) - 0 // Values between 0 and -0.250 improve sharpness but introduce shimmering Texture Filtering - Negative LOD Bias - Clamp Texture Filtering - Quality - High Quality Texture Filtering - Trilinear Optimization - Off Frame Rate Limiter - 58 fps // Change to 118fps if you are using 120Hz Monitor, or offf for 144Hz+ Download Nvidia Inspector Profile Profile for 60Hz Monitor (Locked @ 58fps) *Most common Profile for 120Hz Monitor (Locked @ 118fps) Profile for unlimited FPS Notes / Warnings > Ensure that the Antialiasing modes are matching. For example, 2x/2x, 4x/4x, 8x/8x > Adjust LOD Bias (OGL) to taste. Values between 0 (Soft) and minus -1.500 (Sharper) increase sharpness of textures, although shimmering may occur. Most shimmering I've noticed only on the starting Peragus, although with sharper textures (floor). Therefore you may enjoy settings at 0, -.5000, -1.000, -1.500. My uploaded profile has LOD Bias @ 0 for best stability. What am I working on at the moment? > A confirmed list of non-working OpenGL/DX9 wrappers > Complete Nvidia Inspector Profiles (Different versions, 4x/4x AA for slower GPUs, and some other variants) > Testing any wrappers for OpenGL/DX9 (OpenGL32.dll) > Continuing to explore Nvidia Inspector options, so far nothing working for Ambient Occlusion These OpenGL to DirectX9 Wrappers do NOT work: > gldirect5 // Download > QindieGL.1.0 (rev4 & rev3) // Download > TitaniumGL v2014_01 (All Versions) // Download
  4. Got it working, this is an on-going project: http://deadlystream.com/forum/topic/3002-reshade-for-kotor-tsl/?do=findComment&comment=30622
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines.