DarthParametric

Modders
  • Content Count

    4,568
  • Joined

  • Last visited

  • Days Won

    514

Everything posted by DarthParametric

  1. You can't do that in K1 anyway. It's possible, yes. How practical it is depends entirely on how conversant you are with the game's models and animations, and importing/exporting them. I'm guessing "not at all"? Probably not the best place to start then. It will require editing one of the supermodels and replacing the existing anim with the TSL version. Before that you'll probably want to transfer it to the K1 rig to make sure it doesn't need any editing.
  2. Might as well throw mine up as well. But I'm not going to bother with their life stories since I'm an altoholic so there are too bloody many. Click for embiggening.
  3. It's simple. You renamed the OdysseyBase to Dia_Nu but didn't change the other instances of the original base name. They are all still linked to PFHA02, which no longer exists. So MDLEdit throws an error.
  4. Here you go. k_fab_enter.nss a_xtracrystals.nss
  5. From k_ai_master: case 1008: //KOTOR_DEFAULT_EVENT_ON_DISTURBED { //NOT USED } break;
  6. Sure, go ahead. Usual deal, credit blah blah blah.
  7. I'd guess it's the fact that that particular mesh (or meshes) has the dirt flag enabled. You'd need to edit the model/s to change it, but you need to flip some of the UVs anyway judging by your first pic.
  8. void main() { object oPC = GetFirstPC(); object oComp = GetItemPossessedBy(oPC, "bao_cmpnts"); DestroyObject(oComp); object oMesh = GetItemPossessedBy(oPC, "bao_mesh"); DestroyObject(oMesh); AddJournalQuestEntry("bao_armor", 50, FALSE); }
  9. Unless you can recalculate the positions of a multi-hundred/thousand vertex point cloud in 3D space in your head, no.
  10. Win 10 with a GTX 1080 Ti. But the thread OP also had a 1080, and I believe we were both running on the same Geforce driver revision at the time, so I have no idea what the root cause is.
  11. I don't have the issue at all. I only ever saw it one time on a single texture on an XP machine.
  12. Yeah nothing special is required. This is just a simple file overwrite, since you can't patch a TLK to replace existing lines with TSLPatcher.
  13. No, there are other issues. For example, problems with compiling condensed models were never resolved. The engine simply can't handle multiple on-screen animated entities, which is why Bioware went with the sprites. That's a non-resolvable issue, at least while still using Odyssey.
  14. Just warp directly to STUNT_55a if all you need is to see the end sequence.
  15. Whether or not you side with Bastila on the temple roof. Check the scripts in that convo.
  16. The game doesn't have any dedicated facial animations aside from the mouth flapping for VO phonemes. Anything else is part of a larger animation for talking or listening. You can try creating a DLG and specifying various conversation anims like TALK_NORMAL and so forth. Otherwise, in TSL you can script any anim in the game (in K1 you can only script a limited selection listed in nwscript.nss).
  17. The walkmeshes in those rooms appear to be sloppily made, so I can maybe see potential for a character ending up inside there (although I'm surprised they didn't get stuck there). It's easy enough to revise the walkmesh. I'll add an issue for it to K2CP.
  18. Whereabouts on Nar Shaddaa is that? We can probably add a fix to K2CP.
  19. Of course not. Steam uses DRM. You can't modify its exe with either this or manual hex editing. You'll need an exe that has had the DRM stripped out, like this one - https://deadlystream.com/files/file/1320-kotor-editable-executable/
  20. Sure, knock yourself out. Just provide credit as per usual.
  21. Both Vulkars are using the Twi'lek male Huttese VO. There aren't really a lot of alternatives unless you swap them out for Rodians or something. And that's really at the point of being outside the scope of the Community Patches.
  22. I'd suggest a different colour than the hot pink, since you appear to be using that elsewhere for barriers. Maybe just a slightly yellowish white rather than a super saturated neon. It also looks like you'll need some custom textures to handle curves/corners/angled sections. The bits where it "steps" look a bit iffy.