Leaderboard

Popular Content

Showing content with the highest reputation on 07/28/2025 in all areas

  1. 2 points
  2. 1 point
    N-DReW25
    This sounds as if there might've been a problem/incompatibility with the Lower City Cantina, tar_m03ae, wherein either the installer didn't add the 4th Vulkar/another mod overwrote the file that added the Vulkar and since that scene's scripts were modified to have the Vulkar move the game crashes as a result. Can you add your tar_m03ae.mod file so I can download it and have a look myself? I might be able to fix it for you.
  3. 1 point
    Kotor_Fanatic1987
    Is it possible to make the appearance of Exar Kun look more canonical? You know like with the burnt sith mark he got from Naga Sadow? And in the tomb is there a way to make the sith look like massassi savages?
  4. 1 point
    Snigaroo
    Good work Drew, thanks a lot! I am still on good schedule for testing, so I should be able to give you feedback by mid-September or thereabouts.
  5. 1 point
    PapaZinos
    You now have total freedom to repair the airspeeder whenever you like, it will just be temporarily immobile for the duration of the Visquis and Goto story. When Visquis contacts you, someone will steal the power cells if they were installed, or rig the speeder to destroy the cells upon installation otherwise. You could wait until after completing the whole planet to start repairing the speeder if you like; the first time you install the power cells they will still be destroyed via sabotage, but if you picked up the extra cells on Goto's yacht then you can just immediately install the new ones. Thus you still have the opportunity to gain influence with both HK-47 and Mira. The "once again" message will appear only after the power cells are installed for the second time, though it just refers to whenever the speeder was usable last, whether that be under your care, or its previous owner's. It just acts as confirmation to the player that the game successfully registers the airspeeder as now in its final stage, one of permanent functionality.
  6. 1 point
    DarthParametric
    TSLRCM does hard overwrites. Install it first. K2CP (and pretty much any TSL mod made since it came out) requires TSLRCM as a basis.
  7. 1 point
    Nimduril
    I just registered, after a long absence from everything KotoR and TSL, because I recently reinstalled it through steam, installed a bunch of mods, reshade and whatnot, to give it another spin. Long story short: I ran into exactly the same problem and I think I found the solution and an explanation as to why this crash seems to appear mainly with the CD- and GoG-Version. There is a commonly known typo in the steam-version of the game which normaly prevents the crash from occuring, which is the absent spacing between words in the games .ini concerning the Vertex Buffer. In the steam-version of the game this reads as "DisableVertexBufferObjects=1" and is corrected by most players who install a bunch of mods, as this line seems to generate bugs with textures - I would the reason for that imagine to be an address-overlap between the VBOs and the Textures of some sort, but what do i know. However. If you own the steam-version and reinstate the line in the "swkotor2.ini" from your manually "corrected" "Disable Vertex Buffer Objects=1" to "DisableVertexBufferObjects=1" it seems to be running fine again. And I've just realized; the last post is nearly a year old - my apologies, but if anyone is still having the problem: this was a working solution (for me).
  8. 1 point