bead-v

Premium Member
  • Content Count

    551
  • Joined

  • Last visited

  • Days Won

    17

bead-v last won the day on December 17 2019

bead-v had the most liked content!

Community Reputation

218 Jedi Grand Master

7 Followers

About bead-v

  • Rank
    Evil Malachor Overlord

Profile Information

  • Gender
    Male
  • Location
    Slovenia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for reporting that! It's because those scenes use the same scripts (and so do Sion's scenes at least on Malachor and possibly elsewhere, it would have broken them to). I was supposed to use the TSLPatcher to install them but I wasn't thinking, sorry! Anyway, this will happen with both versions of the mod. If anyone else is experiencing this, your options are: put the files into the override folder only after Sion's kolto tank scene and remove them after you escape the Harbinger OR remove the files and install v1.1 that will use the TSLPatcher and be up very soon! EDIT: The mod is updated! Sorry for the inconvenience!
  2. I think giving the named Quarrens unique appearances would already be a big improvement. Maybe what is needed more are Quarrens in non-exhange-boss roles. Who's the fourth named Quarren btw? Besides Slusk, Saquesh and Visquis ...
  3. Yeah, thought about that and tried it too. In the end I opted for a single-bladed lightsaber for the release version, but you can always take the .uti of a double-bladed one, stick it in the override as "lsbkresion.uti" and it will work. Yes.
  4. View File Kreia's Lightsaber / Long sword This mod modifies the scene on the Harbinger where Kreia leaves the party to face Darth Sion. There are two versions of the mod. In the Lightsaber option, Kreia will pull out a lightsaber instead of a vibroblade (a green single-bladed lightsaber by default) and will face Sion with that. After he cuts her hand off, the lightsaber is not seen again. If you want her to use a different lightsaber, copy the .uti file of the lightsaber you want, name it lsbkresion.uti and replace the one in the override folder. In the Long sword option, there will be a Republic Officer corpse near Kreia. Kreia will now pick up a Long sword from the corpse and use it to fight Sion. It could also have been a vibroblade, but I liked the Long sword better. (In this case it is not possible to change the sword, because it is baked in the corpse placeable model. I tried to do it using a character model and an equipped item, but it is impossible to control the creature's death animation if they are dead and it is impossible to make a creature non-selectable when they're not dead and are just using a death animation.) In addition, both versions of the mod give all of Kreia's weapons to the player as she leaves the party. The cameras have not been adjusted in any way. I tried to refrain from editing .dlg and .git files to keep this mod compatible with other mods editing this scene. I may address such issues in a future mod. Installation: Run TSLPatcher.exe. Uninstallation: (1) Use the 153har.mod file in the backup folder to replace the existing one in the Modules folder inside the game folder. (2) Delete lsbkresion.uti from the override folder (Lightsaber version only). If you installed mods after this one that affected the 153har.mod, this will undo their changes. To prevent this, you may use ERFedit to manually edit the existing 153har.mod instead of replacing it. Extract the following files from the backup 153har.mod, then add them to the 153har.mod in use: 153har.are (Long Sword version only) a_sioncut.ncs a_sioncut2.ncs Additionally delete the following files (Long Sword version only): k_153har_enter.ncs plc_rsldcrps.mdl plc_rsldcrps.mdx plc_rsldcrps.pwk plc_rsldcrpssw.utp This will remove this mod while preserving changes to any other files in 153har.mod from any other mods. Thanks: Fred Tetra: Kotor Tool tk102: DLGEditor, K-GFF GFF Editor JdNoa & Dashus: DeNCS @Sam Fisher: bringing the mod request to my attention. Permissions: You may do whatever you want with this mod, however if you redistribute it, please mention the original author somewhere. THIS MODIFICATION IS PROVIDED AS-IS AND IS NOT SUPPORTED BY BIOWARE/OBSIDIAN ENTERTAINMENT OR LUCASARTS OR ANY LICENSERS/SPONSORS OF THE MENTIONED COMPANIES. USE OF THIS FILE IS AT YOUR OWN RISK AND THE ABOVE MENTIONED COMPANIES OR THE AUTHOR IS NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR COMPUTER FOR THE USAGE OF THESE FILES. Submitter bead-v Submitted 12/17/2019 Category Mods TSLRCM Compatible Yes  
  5. Version 1.1.0

    137 downloads

    This mod modifies the scene on the Harbinger where Kreia leaves the party to face Darth Sion. There are two versions of the mod. In the Lightsaber option, Kreia will pull out a lightsaber instead of a vibroblade (a green single-bladed lightsaber by default) and will face Sion with that. After he cuts her hand off, the lightsaber is not seen again. If you want her to use a different lightsaber, copy the .uti file of the lightsaber you want, name it lsbkresion.uti and replace the one in the override folder. In the Long sword option, there will be a Republic Officer corpse near Kreia. Kreia will now pick up a Long sword from the corpse and use it to fight Sion. It could also have been a vibroblade, but I liked the Long sword better. (In this case it is not possible to change the sword, because it is baked in the corpse placeable model. I tried to do it using a character model and an equipped item, but it is impossible to control the creature's death animation if they are dead and it is impossible to make a creature non-selectable when they're not dead and are just using a death animation.) In addition, both versions of the mod give all of Kreia's weapons to the player as she leaves the party. The cameras have not been adjusted in any way. I tried to refrain from editing .dlg and .git files to keep this mod compatible with other mods editing this scene. I may address such issues in a future mod. Installation: Run TSLPatcher.exe. Uninstallation: (1) Use the 153har.mod file in the backup folder to replace the existing one in the Modules folder inside the game folder. (2) Delete lsbkresion.uti from the override folder (Lightsaber version only). If you installed mods after this one that affected the 153har.mod, this will undo their changes. To prevent this, you may use ERFedit to manually edit the existing 153har.mod instead of replacing it. Extract the following files from the backup 153har.mod, then add them to the 153har.mod in use: 153har.are (Long Sword version only) a_sioncut.ncs a_sioncut2.ncs Additionally delete the following files (Long Sword version only): k_153har_enter.ncs plc_rsldcrps.mdl plc_rsldcrps.mdx plc_rsldcrps.pwk plc_rsldcrpssw.utp This will remove this mod while preserving changes to any other files in 153har.mod from any other mods. Thanks: Fred Tetra: Kotor Tool tk102: DLGEditor, K-GFF GFF Editor JdNoa & Dashus: DeNCS @Sam Fisher: bringing the mod request to my attention. Permissions: You may do whatever you want with this mod, however if you redistribute it, please mention the original author somewhere. THIS MODIFICATION IS PROVIDED AS-IS AND IS NOT SUPPORTED BY BIOWARE/OBSIDIAN ENTERTAINMENT OR LUCASARTS OR ANY LICENSERS/SPONSORS OF THE MENTIONED COMPANIES. USE OF THIS FILE IS AT YOUR OWN RISK AND THE ABOVE MENTIONED COMPANIES OR THE AUTHOR IS NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO YOUR COMPUTER FOR THE USAGE OF THESE FILES.
  6. I'll get it to you when I have a moment That was a hint to the mods Maybe this will help:
  7. What have you done so far? Some time ago I started working on a "dlgedit" (for the same reasons you listed) in C++. ATM it can open/save dialog files, display them in a tree (which I wrote from scratch to maximize speed), it allows for copy/paste/cut/delete/create tree operations and most of the fields work, although not all are fully implemented yet. With it I made a GFF and a TLK library. If you're interested I can show you the code, either to use parts from it in your own work or to continue work on this tool (since I don't have the time right now. It is written using WINAPI, however... I can imagine that's not something you're interested in..). (this topic should probably be moved to the modding tools section?)
  8. If you get this, right click on the binary code and select View decompiled code in DeNCS. Now you can save the script. Good luck!
  9. If anyone is looking for information about how baseitems.2da and appearance.2da are tied together and what model and icon names the game expects, this is a useful post:
  10. All this would require is dialog editing. Since you seem to have a pretty clear idea about what you want, why not edit the dialog yourself? You do need to know where to find the right dialog, which can sometimes be a little tricky for a beginner, but then you can ask here (the above part is in k_hbas_dialog.dlg). Once you have the file, editing it is simple. Then just drop the file into your override folder.
  11. I'm guessing your talking about the state of affairs after importing with KOTORmax? Anyway, the animations aren't hardcoded, you can add additional keyframes that exceed the 16600 as you say. It's max that has the limitation of just one timeline, KOTORmax therefore loads the animations onto it in sequence. It has an animation editor through which you can keep track of which keyframes belong to which animations. You can simply add a new animation and assign the keyframes you want to it. Although, using the new animations in the game is a different story. I think in K2 it should suffice to list it in animations.2da and then it's possible to call it via script. But I'm not sure it's as simple in K1. You may delete the animations in the animation editor if you want. This means they won't be exported from KOTORmax. Once the model is exported, first you need to compile it back to binary. After that you either place it in the override folder or you put it in a .mod file (which represents a module). Modders generally never edit .bif, .rim and .erf files, we leave those as a source of the original files. For just a character model, you'll be fine putting it in the override folder. Also note that K2 will recognize files in the subfolders of the override folder, while K1 won't. Not sure what you mean with the training dummy.
  12. No idea what could be wrong, but you could try ERFedit.
  13. Newbies picking up giant projects, it never works out (statistically, no offense meant). I'd suggest you set your goals lower and do some smaller mods first, and then ask yourself again if you're willing to do it when you have more experience. I also doubt one person alone could do it without getting overwhelmed.
  14. I've been preparing a known issues list, because I want to get an official MDLedit update out as soon as possible. Posting it here in case there is something I missed. 1. MDLedit is not capable of processing some very large models (eg. the K1 DS endgame scene area models). I may be able to solve this in the future. 2. When converting area models from K1 to K2, some models lack an aabb node in the MDL. Without the aabb node, the model will not be displayed in the game (unless the VIS file is missing, but this shouldn't be the solution). In this case, first decompile the model to ASCII, then edit the file with a text editor and add the following lines in an appropriate place: node aabb NEW_AABB parent BASE_NAME endnode 3. There have been reports of smoothing not working properly if the model was converted with the batch convert function. I haven't been able to reproduce the issue so far and would be grateful if I could receive all the relevant files to examine them if it happens to you. 4. In some area models, the aabb mesh isn't properly modeled to be used for the creation of the walkmesh, which causes the compilation to fail. If that happens you have two options. You can either inspect the aabb mesh and delete all the offending faces or you can enable the 'Export WOK file' option in MDLedit, then use that mesh to replace the aabb mesh, just make sure it has all the right options afterwards. In the future, I will add an option for the WOK file to be handeled separately, so this issue won't arise anymore. 5. Smoothing will sometimes not work across boundaries where the UV is mapped in different directions. This requires an update to the vertex normal calculation and will hopefully be solved in the future.