Leaderboard


Popular Content

Showing content with the highest reputation since 04/21/2024 in Posts

  1. 5 points
    Hi everyone I'm posting this update in part to show you guys some images and the Intro Movie/ crawler mockup. I'm posting the mockup video in hopes to find someone who can do the real intro movie for the mod. The mockup is done in Blender. The person could take this file and make it look better. At the end of the video you see part of the space station break off,. There would be an explosion there. If anyone is interested in doing the actual intro video, please contact me by DS message. Link to video: RoR intro movie mockup
  2. 3 points
  3. 3 points
    It is that time of year again, time for me to reveal another mod for the NPC Overhaul Series! Our latest mod shall enhance everyone's not-so-favorite/infamous Corporation... Amazon Redux, uh... I mean... Czerka Redux! First and foremost, the one thing you'd expect from a Czerka overhaul mod... the Czerka Combat Suit from RedRob41's Modder's Resource! Do note the image above was taken with RC-K1CP, the cut Czerka Guard is in the Tatooine game files unused so Czerka Redux will change cut NPCs meaning you can play the mod with RC-K1CP, though if you don't use RC-K1CP then that's fine too. Most of the Czerka Guards will wear the Combat Suit, however, some Guards have been replaced with brand new NPC variants... like droids: Some of these droids will have droid shields and utility items like flame throwers, turning those redundant Czerka guys in the background of Chuundar's room from a force to be beckoned to a force to be reckoned... with. Of course, not all the new alternative guards are droids... you do have this Gamorrean here: He's from Brotherhood of Shadow: Solomon's Revenge by SilverEdge9. Speaking of BOSSR, the Technician Armor from BOSSR is also worn by the Mechanics of Czerka Corp: The Czerka Muscle Suit from BOSSR also makes an appearance as a rare Czerka item. Whilst the names and descriptions of these BOSSR items are almost unchanged from BOSSR, the stats certainly are. The Muscle Suit in BOSSR has a +5 Strength bonus, it has been severely nerfed in Czerka Redux alongside the rest of BOSSR's items though the Czerka Muscle Suit in particular is now upgradeable making it somewhat good for a rare item instead of overpowered as it was in BOSSR. And the Czerka Mining Suit from BOSSR is also in Czerka Redux. It is worn by the Miners of Tatooine, if you install Czerka Redux on its own it will give the Duros Miners the Czerka Mining Suit, but it won't be shown.... unless you plan on using Duros: Armed & Ready! With Duros: Armed & Ready, the Duros Miners who have the default Czerka outfit will now wear the Czerka Mining Suit for that extra immersion. Future alien mods of mine will do the same thing, the Czerka alien will have the default Czerka Outfit but with Czerka Redux this Czerka alien will wear the Czerka Armor of this mod. The Duros' head from Duros: Armed & Ready is by JCarter426. Speaking of JC, he made a male version of the Czerka Commoner outfit worn by the Czerka Protocol Officer in his JC's Fashion Line B: Commoner Clothing for K2 mod some years back. With his permission, I've added it for the Czerka Scientists and some other Czerka NPCs in the game. As you can see from these screenshots, this mod is compatible with the gloveless commoner clothing from RC-K1CP! There are two versions of the Czerka commoner clothing, the vanilla inspired one and the K1EP one. Whilst I do not have a screenshot of the K1EP clothing yet, I can confirm that I did use JC's male version to convert the once exclusively female K1EP clothing into a male variant. But whilst I lack the screenshot of the clothing, I can confirm I've added the K1EP Czerka Officer texture: Czerka Custom Officers shall now wear that new Czerka Officer outfit. The Czerka Officer outfits have been revamped in Czerka Redux, the green Czerka Officer outfit is traditionally worn by the Czerka Commander with the cap... now it is worn by Liason Officers and the like. You might be wondering, with all these changes... where are the original Czerka Officers? They're right here: Those 4 NPCs on Kashyyyk and Tatooine are now the ONLY Czerka Officers you will encounter in the entire game, the rest have been modified into new NPC variants. To modify most of these NPCs, I have had to change their appearances from Czerka Officers to Commoners to support the armors. As such, all of the NPCs from this mod are based on the NPC Diversity Pack, meaning if you install the NPC Diversity Pack and then Czerka Redux there will be a seamless transition between the two mods with comprising the other. Once I perform the final touches on the Czerka Redux, it won't be released immediately... for I need to make several patches. The 1st patch is a compatibility patch for the NPC Diversity Pack, this is to ensure people who don't use the Diversity Pack can install the main Czerka Redux mod whilst Diversity Pack players will have to install this compatibility patch to finish the installation. The 2nd patch is an addon for the RC-K1CP mod, I don't think this addon is necessary though it will improve the restored Czerka elements of the RC-K1CP quite well. I will share more info on this secretive addon once it is ready. The 3rd patch is an addon for JC's Czerka: Business Attire for K1. It will give the Rodians of that mod new Czerka outfits and new head reskins. The 4th patch is an addon for the main mod. It will add female Czerka Officers to the game. This includes female guards who you can fight and will have a female soundset at death and female NPCs you can speak to. This addon will utilize DarthParametric's Female Czerka Officer's Uniform Modder's Resource for some of these female NPCs.
  4. 3 points
  5. 2 points
    Should be simple enough then, TSLPatcher's ChangeEdit can automatically generate the differences for the 2DA files and from there you can probably just add the dialog and character sheets to the override folder. Just edit her character sheet accordingly after tracking down which level contains the correct character sheet.
  6. 2 points
    I would suggest not using KotOR Tool for much besides extracting files, even then it's usually easier to just use ERFEdit, HolocronToolset is also an option to consider. Though I don't know what it might mess up when it comes to dialog files but it has been known to cause issues when it comes to editing files. Also I would suggest looking into TSLPatcher and HoloPatcher for applying your changes when releasing your mod so that changes can be properly applied to the games files. You're welcome and as I mentioned, there are probably a few other branches within that specific dialog that would need removing. I'm not sure what the issue is here, I always have both installed so I have never encountered this problem.
  7. 2 points
    Ah, well in that case you would have to edit the dialog files in question to remove those options accordingly. This would be for Dorak, which is "dan13_dorak.dlg" that is located within the level file "danm13_s.rim" Though it's highly likely that there might be other entries that you might want to delete.
  8. 2 points
    Here is a preview of the next update to the RC-K1CP. This update shall not only impact the RC-K1CP, it shall also impact the Unofficial K1CP Tweak Pack and the K1 Pre-Release Pack! A number of Tweak Pack features will be removed from the Tweak Pack and will be added to the RC-K1CP: this includes the restored turret soundset, Davik's upgradeable armor, Eli's alternative clothing and the soundset fixes. The Lite NPC restoration shall also be added to the RC-K1CP, but the Lite NPCs shall be made an optional install! In addition, the Lite NPC restoration shall simultaneously remain in the Tweak Pack. Tweak Pack shall have a copy of the Lite NPCs restoration as it undoes the controversial Lite Upgrader feature in the K1CP, hence it fits the description of the "tweak pack". But for Lite NPC restoration in RC-K1CP, there is a unique reason it's being added here. In a future update, there shall be a 3rd install option called "Lite NPC restoration plus" which shall restore all of the Lite NPCs which were not used in the vanilla game. If you install the main RC-K1CP mod, the Lite NPC restoration mod and the Lite NPC restoration plus mod together you'll get to experience the full arsenal of Bioware's original Lite NPCs. Below are some screenshots of the unused Lite NPCs in question, courtesy of A Future Pilot and his Lite Upgrader mod. Now what about the K1 Pre-Release Pack? The K1P-RP mod is similar to the RC-K1CP mod, except this mod restores content shown in official Bioware Pre-Release screenshots. Below is an example: Now, in the game files for Anchorhead are dialogues for cut NPCs such as Chadra-Fans and Ithorians but the Pre-Release screenshots show quite a bit of cut content in Anchorhead. In this screenshot, we have the cut Ithorian Miner NPC. In this screenshot, we have a hover sled with engine in the background and a little drone floating about. In this screenshot, we have a Protocol Droid, a Quarren and two Dewbacks In this screenshot, we have a landspeeder in the background. This creates a problem, do I restore these features in the K1P-RP mod or do I restore them in the RC-K1CP mod? Well, I've made a decision. The NPCs shall be restored in RC-K1CP whilst the placeables will be restored in K1P-RP! RC-K1CP: K1P-RP And to finish this preview off, this update will also fix the syntax errors that have been plaguing the mod since release! So have fun installing it with no guaranteed error messages.
  9. 2 points
    Space for creativity) 1.mp4
  10. 1 point
    View File Thematic The One Thematic The One Premise The One: warlord; conqueror; latent Force-Sensitive. A charismatic leader of the Rakata and a near-supernatural anomaly among their people. As an added bonus, he also dies in about two combat rounds! In fairness, with a good character build there’s very little that doesn’t go down in two rounds or less in the lategame. But The One in particular irks me—he’s presented as special, a natural leader in Revan’s own mold, a warrior-prince leading both armies and the political structure of his people. Yet despite having all the resources of the hundreds of islands he has conquered and dozens of crashed vessels he has looted, indeed despite having a Sith Tremor Sword in a bin literally RIGHT BEHIND HIM, he uses two regular vibroblades; despite being so charismatic he convinced his own former chieftain to willingly sacrifice himself and allow his tribe to cannibalize him while being so brick-headed he’s sat on a single island for half a decade, his WIS is 18 while his CHA is only 12; and despite being latently Force-Sensitive, his Will saves are abysmal. This was a ripe field for a Thematic project. Like my similar mod for KOTOR 2, Thematic The One’s goal is not to make the fight against The One actually challenging—this is not a difficulty mod. The fight will be slightly harder than in vanilla, yes, but for some builds this change will not even be noticeable; indeed, I took him out in two combat rounds just like normal. Instead, the goal is to present The One as the game insists he is: a charismatic warrior with vast resources and the—albeit unconscious—power of the Force behind him. Changes The One’s WIS and CHA stats have been nearly inverted, from 18/12 to 14/18; he has been given a Sith Tremor Sword in his main hand and an Echani Vibroblade in his off-hand (neither droppable); his Will saves have been bumped up to 15, to make him about as difficult as an average Dark Jedi to land Force abilities against; his alignment has been moved from Neutral to moderately DS, so that the Solari crystal will work against him; and, most significantly, he has been scripted to use Force Valor at the start of the fight with him. I felt this was important to represent exactly how close The One is to true Force Sensitivity, and how it’s clear that the Force has been supporting his meteoric rise from the start. Compatibility As is the objective with all Thematic-series mods, this mod should be compatible with every other mod out there. Even mods that edit The One should be compatible, as long as they edit his data in the module rather than with a direct .utc file drop to the override; at worst, such a mod would only replace some of my changes with its own. Permissions & Thanks As with any mod “I” have made or will make in the future, this mod has completely open permissions: modify it, redistribute it, reupload it, do whatever. So long as you give me credit for the idea and for the balance settings if you choose to retain most of mine, go for it. You don’t even need to ask me. Particular thanks to JCarter426, who made this entire mod at my request but then told me it would be funnier if I uploaded it like it was my own. Ok. Submitter Snigaroo Submitted 05/21/2024 Category Mods K1R Compatible Yes  
  11. 1 point
    character.gui from gui.bif Or use this one, you might need to make variants for different resolutions, but this is the default file with the Auto Level Up button moved to -146 which is just off screen. character.gui
  12. 1 point
    Character models typically use supermodels for their animations rather than having animations directly on the model itself. You can see the root supermodel designation in your screenshot in the OdysseyBase properties (just above your circled section). Supermodels exist in a hierarchical chain, with animations being pulled from multiple files. Animations are always pulled from the lowest (i.e. first) instance in the chain, so animations on the model itself will override any animation of the same name in any of the supermodels. This allows males and females to share some anims but have unique variants for others. For example, the base supermodel is S_Female03, which only female characters use. The next one up the chain is S_Female02, which is what males use. That allows for there to be separate walk animations for males and females, for example.
  13. 1 point
    That just means you have a section that isn't being used, so it depends on what the sections are.
  14. 1 point
    Unfortunately it is difficult for people to properly write the documentation while simultaneously writing the programs themselves. That I know of there are a few undocumented features in TSLPatcher, though the only one I can currently recall is the one I used most recently which is the HACKList which is now documented in HoloPatcher's readme.
  15. 1 point
    I think that's an oversight by the writer of the readme so you aren't actually missing anything, you are correct. Place them in a separate folder for now, but after generating your changes.ini file, all of the changes you have made to files should become instructions in the changes.ini file, at that point you will want the original files for the reason it mentions. To be honest I would potentially suggest using HoloPatcher as it has a few new features and is actively being developed at the moment.
  16. 1 point
    Well reinstalled using mod sync and was able to load into the garage. Yay. Hopefully reinstalling and then running the save game doesn't cause any issues but I don't think it should since I had I think most of the same mods installed previously.
  17. 1 point
    That's a pretty awesome looking tool. Thanks for the head's up about it. I somehow installed the Kotor 2 mod build without any issues despite the huge list of mods I installed, but it's entirely possible I made some mistakes with this mod build given how many mods I installed with it. So having a tool to automate that and ensure I'm not messing up is honestly a lifesaver to think about. Very excited to try it.
  18. 1 point
    I figured out the issue, it for some reason did not modify my appearance.2da when I installed the mod. To fix the issue if anyone else has it, I opened my apperance.2da file that was in my override folder and added "P_HK47_01" in the racetex column
  19. 1 point
    Okay, so I'm making a mod for KotOR 1 and one of the changes is that Bastila is becoming a Consular. I need some advice on how to proceed with her build after you re-recruit her on the Unknown World. Here are the options: 1. I could just put her back to level 1 and let the player decide, but this makes the fight with her 4th -wall-breakingly easy. 2. I could just create an optimal build for her so that she shows up strong as hell. Her level 1 stats are going to be 12, 18, 12, 10, 12, 15. Same as normal. At levwl 20 she'll 27 powers (like in KotOR 2) plus Affect Mind. She 'll have Master Two-Weapon plus 4 more feats. How should I build her? What powers should she get?
  20. 1 point
    I decided not to publish. New textures for wounded soldiers. You need to delete the .tpc files of the same name. Diversified_Wounded_Republic_Soldiers_On_Taris_Consoles (textures).rar TOR_MedPanelScr (textures).rar
  21. 1 point
    That's great, I'm glad it's out before the next version of the K2CP is finalized, I'm hoping JC might want to integrate it. It's such a small thing but it's always bugged me.
  22. 1 point
    Yeah, I think I've found it, there's like 6 of them ranging from 15 to 20 in level. I bet I can just edit them all and be fine. Thanks.
  23. 1 point
    Whoa, those Czerka edits look amazing pal, can't wait to try a composite of your appearance overhaul mods.
  24. 1 point
    Thanks for including an addon for JC's Czerka: Business Attire for K1! That's a great mod, too.
  25. 1 point
    That would change every appearance of Traya in the game to Kreia, correct? I don't want her appearance on Malachor changed--much as I think it's likely an artifact of LucasArts mandating there be a big bad at the end, it would be much too significant a thematic alteration for mod build inclusion. If the description of the request wasn't clear enough I apologize, but I only wanted the change for the vision appearance in the tomb.
  26. 1 point
    Specifically, it nukes files that use certain characters in their filenames when it repacks the MOD for the Grove module, meaning that k_pdan_state1-.ncs and k_pdan_state1+.ncs get deleted. These scripts are the starting conditionals that check the value of the DAN_BOLOOK_STATE global, without which the DLG won't function correctly.
  27. 1 point
    I pointed your mod out to brents742 last night. Nice job btw!
  28. 1 point
    View File KotorBlender (for Blender 3.3+) This add-on is a fork of KotorBlender, upgraded to support newer versions of Blender. KotorBlender is in turn based on NeverBlender, forked from version 1.23a. ## Features - Import & export MDL models, including walkmeshes - Import & export LYT files - Import & export PTH files ## Installation 1. Clone this repository or download the latest release of KotorBlender from Deadly Stream 2. If you have cloned the repository, create a ZIP archive containing the **io_scene_kotor** directory 3. From Edit → Preferences → Add-ons in Blender, install the add-on from the ZIP archive and enable it by ticking a box next to "Import-Export: KotorBlender" 4. Alternatively, if you want to contribute to KotorBlender, you may want to create a symbolic link to the local repository in the Blender add-ons directory, typically located at `C:/Users/{user}/AppData/Roaming/Blender Foundation/Blender/{version}/scripts/addons`. 1. `mklink /D io_scene_kotor {repo}/io_scene_kotor` ## Usage ### Data Preparation Extract models, textures, walkmeshes, LYT and PTH files into a working directory, using a tool of your choice, e.g. reone toolkit. Recommended directory structure: - *data* — extract all BIF archives here without subdirectories - *texturepacks* - *swpc_tex_tpa* — extract swpc_tex_tpa ERF archive here If you plan to edit textures, batch-convert TPC to TGA / TXI files using **reone toolkit**, although TPC textures are also supported by KotorBlender. ### Model Import and Export 1. Import via File → Import → KotOR Model (.mdl) 2. Select top-level MDL root object to be exported 3. Export via File → Export → KotOR Model (.mdl) ### Editing Animations To edit list of model animations and corresponding events, select MDL root object and navigate to Object → KotOR Animations. KotorBlender supports both object and armature-based edits. To create an armature from objects, navigate to KotOR Animations → Armature and press Rebuild Armature and Apply Object Keyframes. Before exporting a model, make sure to copy armature keyframes back to objects by pressing Unapply Object Keyframes. ### Lightmapping 1. Select objects for which you want lightmaps to be recreated, or unselect all objects to recreate all lightmaps 2. Press KotOR → Lightmaps → Bake (auto) UV mapping: 1. Select objects having the same lightmap texture and enter Edit mode 2. For every object, ensure that `UVMap_lm` UV layer is active 3. Select all faces and unwrap UVs via UV → Lightmap Pack, increase Margin to avoid face overlapping Fine-tuning: 1. Increase lightmap image size via UV Editing → Image → Resize 2. Tweak ambient color via Scene → World → Surface → Color 3. Manually toggle rendering of objects in Outliner and press KotOR → Lightmaps → Bake (manual) 4. In Scene → Render, set Device to GPU Compute to improve performance, set Render Engine to Cycles if not already 5. In Scene → Render → Sampling → Render increase Max Samples to improve quality ### Minimap Rendering 1. Press KotOR → Minimap → Render (auto) 2. Open "Render Result" image in Image Editor and save it as "lbl_map{modulename}.tga" 3. Open "MinimapCoords" text in Text Editor and copy-paste generated properties into module .ARE file using any GFF editor Fine-tuning: 1. Tweak background color via Scene → World → Surface → Color 2. Manually toggle rendering of objects in Outliner and press KotOR → Minimap → Render (manual) ### Connecting Rooms 1. Select a room walkmesh 2. Enter Edit mode and select two vertices adjacent to another room 3. Determine 0-based index of the other room into the LYT file 4. Enter Vertex Paint mode and set brush color to (0.0, G, 0.0), where G = (200 + room index) / 255 5. Ensure that brush blending mode is set to Mix, and brush strength is set to 1.0 6. Paint over the selected vertices ### Editing Paths 1. Extract PTH file from the module's RIM file, e.g. "modules/danm13_s.rim" (Kotor Tool, reone toolkit, etc.) 2. Import PTH into Blender via File → Import → KotOR Path (.pth) 3. Create/move path points, or modify path connections via Object Properties 4. Export PTH via File → Export → KotOR Path (.pth) ## Compatibility Known to work with Blender versions ranging from 3.3 to 4.0. ## License GPL 3.0 or later Submitter seedhartha Submitted 03/18/2021 Category Modding Tools  
  29. 1 point
    I'm sure many of us play the Kotor 1 Community Patch (K1CP), it's the 4th most downloaded mod on Deadlystream after all! And I'm sure many of us might also know that the K1CP isn't compatible with the Kotor 1 Restoration (K1R mod)... you might be wondering, why is that? K1R is similar to it's K2 cousin, TSLRCM, in that it restores cut content, fixes bugs in the vanilla game and it expects you to install it first and any other mods installed afterwards need to be made compatible with it. But K2 was rushed, Obsidian was forced to leave content unfinished and cut the rest to make way to make way for a release before the 2004 Christmas sales... this not only gutted much of the plot but it also left a plethora of bugs upon release. TSLRCM undoes all of this by restoring much of Obsidian's intended content for early 2005 and fixing many of the game breaking bugs. K1, on the other hand, wasn't like this. What was cut by Bioware was stuff that most players agree was *actually* cut for a good reason, and the bugs in the vanilla game weren't nearly as bad as they were in vanilla K2. In K1R's "prime" from its full release in 2015 until K1CP's first release in 2018, K1R competed with many mods that were incompatible with it such as Kainzorus Prime's NPC Overhaul Mod... and since all K1R had to offer was minor and controversial restored content and minor bug fixes many players, including myself, opted for the much better incompatible mods. With the release of K1R's 1.2 update, there have been a handful of critical bugs in the mod with some capable of breaking the game. This would normally be fixed by the Dev Team behind the mod, but one by one the original K1R Devs left the Kotor Community with only 2 K1R Devs remaining in the community. The mod's leader, ZM90, also vanished... without him, it's impossible to update K1R as he's the one who hosts it, more importantly, we can't obtain permission to update K1R or use assets from K1R. With K1R being seen as undesirable by many and with no hope of it ever being fixed, the developers of the newly emerging K1CP mod abandoned K1R compatibility... just over 5 years later and K1R has become a obsolete relic of the past whilst the K1CP has become the ultimate bug fix mod for K1 standing alongside TSLRCM in importance (Not anywhere near as close, TSLRCM is still King... but its far superior to K1R). Some modders might still make their mods K1R compatible, but I don't bother since K1R has those before mentioned game breaking bugs... why on earth would I put in the effort to make my mods K1R compatible if your game is guaranteed to break because you installed K1R? I'd much rather focus on K1CP compatibility as their dev team is active, are willing to fix bugs with their mod and are still working to this day to fix more vanilla bugs. So this creates a problem... many of us play K1CP, but we can't have Restored Content due to K1CP being incompatible with K1R, and no one can update K1R as the original K1R Devs have abandoned the community... so how do we update K1R? How do we get K1CP compatible with K1R if K1CP Devs refuse to do it? My answer: forget K1R... The K1 Community Patch has already taken the mantle of the "main Kotor mod" from K1R and we can't change that, but we can work with this! This thread is a WIP thread for an upcoming mod, one that you will install after the K1CP mod, one that will restore Kotor 1's cut content whilst having K1CP and it's many, many bug fixes installed! I present to you: Restored Content for the K1 Community Patch or RC-K1CP for short! Now we have to keep our expectations in check... this is currently a one man project, and I alone cannot recreate K1R in its entirety from scratch... though I can, however, restore much of the lesser restored content like impossible difficulty before working my way up to the big leagues like the Vulkar Sublevel. Much of what can be restored is limited to my own modding abilities, so if I can't restore the Vulkar Sublevel constantly requesting it won't make me restore it... it'll be restored when I'm able to restore it, and if that time is not now it'll be some time in the future. You might be wondering; won't this impact the development of my NPC Overhaul mod development? The answer is no... that is because the first release of the RC-K1CP Demo is ready for release! In the coming week or two, I'm planning on releasing some screenshots from the mod to demonstrate what the mod has thus far alongside a YouTube video of an ambitious restoration. Once these are posted here, I shall release the RC-K1CP Demo here on Deadlystream for you to try out! Updates for the RC-K1CP shall be done in two ways; they shall be done in either content updates which adds restorations and bug fix updates which fixes bugs with the mods. As with any other mods, I'd like for players to be ever vigilant for possible bugs and to report any if bugs do arise! RC-K1CP does not follow the same "rules" as K1R and TSLRCM did, so you might see some restored content K1R avoided or never knew existed... so keep that in mind! With release version 0.1.0, you shall enjoy the following restorations from the RC-K1CP. And lastly, there are some things you might consider 'cut content' which might be added to the RC-K1CP. If this cut content was found in pre-release screenshots between 2001-early 2003 before the games release it could be added to the K1 Pre-Release Pack instead and if it's from the XBOX version but was cut from the PC version it might be added to the Knights of the Old XBOX mod (which is due for an update anyway). What do we think? Do you have any suggestions or recommendations? Anything you dislike in K1R you don't want to see in RC-K1CP?
  30. 1 point
    appearance.2da isn't what you're looking for, only the PMBE06, PFBE06 and ia_class6_006 files determine an Exar Kun reskin. They end in ".tga" so "PMBE06.tga" Have you tried K1R? I vaguely remember seeing those files in that mod years ago. If it's not in K1R, and you can't find it in either the NPC Overhaul or Shem's mod, as SH has said already we can't be of much help without images of the armor in question.
  31. 1 point
    Creating tools is my specialty. Let me know if you're finding some task in this project incredibly tedious, that a specialized tool could address. Would love to help out.
  32. 1 point
    @Mesmitos, reach out on Discord to troubleshoot. It's not an issue with the mod builds, your install is either broken in some way or you're just noticing the few imperfections which are still present.
  33. 1 point
    Ads are now disabled for active site members so that should go away.
  34. 1 point
    Other Projects Yes, though progress has been slow lately as I have been busy with another project that aims to automate conversion of old Unreal Engine games to UE4/5. https://github.com/Thor110/UE2-UE4 Currently it's just a series of batch scripts that utilise existing tools to extract and convert the game files in preparation for UE4/5 but I am preparing to go through the source code for each of the tools and re-work them to deal with any issues present at the moment. Expanded Galaxy That aside, the last update to the Main Expanded Galaxy Repository was 16 days ago, a lot of my time has been spent reaching out to other mod authors and looking for people who wish to join the project, as well as testing which consumes quite a lot of my time unfortunately. The project recently overwent a major overhaul to bring it over to the new HoloPatcher installer, which took quite a while to prepare, it is no longer a drag & drop replacement install and is now a dynamically handled installation similar to TSLPatcher installs, which should make the project compatible with other mods, though I give no guarantees on that because mods can easily cause conflicts with one another. Recruiting Currently the project could do with a few more hands on deck, as expected it is far too grandiose for me to handle alone, though I think I have done well getting it this far on my own. Looking for Testers, Modellers, Texture Artists and finally Writers to join the project, though I did plan to do it all on my own I am starting to think finishing it will be unlikely without a team, I am still holding out hope that as a community we can pool our efforts and resources to unify all of the best content into a single canonical overhaul of both games under the Expanded Galaxy branch. End Goals My end goal would be to create a singular install that totally overhauls both games as well as an additional optional install that overhauls the textures and models for both games. Though it might be better that I wait for one of the open source engine re-implementations to be finished in order to better accommodate the needs of this project. Road Blocks Currently there are still a few roadblocks for me to overcome in order to fully realise the goal of this project, primarily forming a team and keeping things better organised, but additionally I need to work out what the best way forward is for the project, recently I have been reminded of the infamous dialog skipping bug that is present in TSL and I feel like it really is something that needs solving in order to make the project the best it possibly can be. This is however a difficult task and a bug or problem that has plagued the game since it's release and has gone unsolved for a long time. I also initially intended to try and finish the Port of KotOR1 to TSL before shifting my focus back to TSL itself, due to the need to incorporate a launcher and save importer that allows players to carry over their choices from the first game into the second game, but this is becoming increasingly difficult for me to swap between the games and playtest as well as work on both of them, for the time being I have set the Brotherhood of Shadow : Solomon's Revenge port aside in order to help reduce the workload, but the reduction is barely noticeable as that was just a side-project or venture to see how quickly I could get the majority of it reworked for TSL. In Conclusion In short, there's lot's to do and the project may never reach a stage where it is to be considered completed, but I very much hope this isn't the case and intend to continue working on it for as long as I can, getting it all this far has been physically and mentally exhausting, while the majority of the work is fairly easy, I started this project back when I was homeless for a short period of time and at times I find it debilitating to be reminded of that part of my life. However, rest assured I will be continuing work on the project indefinitely, it's very much a life-long project which seeks to revitalise the original games as much as physically possible within the constraints of the TSL iteration of the odyssey engine. Initially I had hoped to get a forum section for the project here on DeadlyStream and to raise regular discussions about what needs improving in the game as well as creating polls that the community could vote on in order to try and determine what changes are best, what fixes should or shouldn't be included and allowing the community to guide Expanded Galaxy to it's final destination. However that didn't happen, keeping up with everybody's thoughts, ideas and opinions on the games is difficult enough, let alone everybody's suggestions for improving the game! There is a Discord server for the project where people can discuss things, though it's been a little quiet as of late, it's very easy to discuss the possibilities for these games endlessly and while that can be helpful at times in order to bring forth ideas and suggestions that might help the project, at times it can leave me whiling away hours simply discussing the semantics of why I don't intend to include or add something to the project. My Thanks Thanks for checking in on the project and many thanks to all those who have helped support or contributed to the project so far. Apologies for the super long response, but I felt it would be best to give a proper summary of what's what regarding the status of the project. Thor110
  35. 1 point
    KotorBlender only officially supports MDL format. Technically speaking, material information (textures, colors and transparency) is stored in addon-specific data structures, and is only converted to Blender materials for preview purposes. GLB / GLTF exporters for sure don't have access to KotorBlender data structures, and how they interpret Blender materials is up to them.
  36. 1 point
    Nice job on the document, very organized. One thing I noticed is that you don't have to touch Shader Editor at all, you can just press Rebuild All Materials on the root object or Rebuild Material on individual objects. So the root cause is not normalized bone weights, i.e. total sum of all bone weights per vertex exceeds 1.0 in your model. You can fix that by pressing Weights - Normalize All while in Weight Paint mode: However, that made exported model crash on load, so I had to fix it. Please download version 3.10.1 of KotorBlender from DeadlyStream. Here is your fixed model in-game:
  37. 1 point
    Whether or not you'd consider it a "tutorial", I think it would be useful for people to demonstrate certain things explicitly (meaning in a video most likely).
  38. 1 point
    I do see the value of good documentation / tutorials. I'm sceptical though if it will actually bring more people to use KotorBlender. So to anyone following this thread, do you think a tutorial is necessary here or just a nice-to-have? What topics would you like to have covered? In which format?
  39. 1 point
    More updates: Version 3.9.0 has added support for Bezier-type controllers, compressing quaternions on export and armature-based animations, i.e. it is now possible to animate a character using a Blender armature and then copy keyframes onto regular "bone" objects before exporting the model. More importantly, version 3.10.0 has implemented semi-automated minimap rendering. It works like this: Import a module layout via File → Import → KotOR Layout (*.lyt) Press KotOR → Minimap → Render (auto) Open "Render Result" image in Image Editor area and save it as "lbl_map{modulename}.tga" file Open "MinimapCoords" text in Text Editor area and copy-paste generated properties into module .ARE file using any GFF editor
  40. 1 point
    Hi, Since I could not find a mod that removes the speed blur form the game's effects only, I made my own using kotor tool. I wanted to keep all the other effects by leaving frame buffer effects ON, except the force speed blur. I edited the visualeffects.2da and removed the blur line. Since this is so hard to find I will leave the file here in case anyone else wants it. Just drop it in override. Cheers. visualeffects.zip
  41. 1 point
    Released 3.4.0 with this and a couple of other fixes, but most importantly I have reworked the UI. It now fits Blender 2.8 style alot better. Here are some screenshots:
  42. 1 point
    Published version 3.2.0. Thank you guys for asking and making me look at things more thoroughly. I've fixed some custom meshes related issues, particularly modifiers not being applied on export. More importantly, I've added an option to merge duplicate vertices and mark sharp edges, which is a similar feature to smoothing groups in Max. This is important because KotOR models have a LOT of duplicate vertices, which is exactly how smoothing groups work - they create additional geometry where surface needs not to be smooth. Same result can be achieved with sharp edges and Edge Split modifier in Blender. Some example screenshots: New Import Options Normals Algorithm = None (normals are ignored) Notice sharp edges on the head, despite normals not being imported. That is because of duplicate vertices. Normals Algorithm = Custom (MDL normals are used as is) Notice how smooth edges on the left arm are. There are duplicate vertices there, but custom normals make them look smooth. Normals Algorithm = Sharp Edges, Sharp Edge Angle = 10 degrees (duplicate vertices are merged and sharp edges are marked) Notice how edges on the head are still sharp, despite duplicate vertices being merged. That is the result of these edges being marked as sharp. Unfortunately, edges on the left arm were not marked as sharp, because we could not merge duplicate vertices there - they have different UV coordinates. This happens on more than one model - maybe I'd need to improve the algorithm in the future.
  43. 1 point
    Don't see the diff in the first two pictures. This is what I think is going on: Sharp Edges and Auto Smooth are a display-only thing in Blender. These affect how split normals (vertex normal per polygon) are calculated, but do not result in new geometry. Because split normals are not supported by MDL, what current approach does is it calculates vertex normal as an average of its split normals, effectively cancelling them out, unless all split normals are pointing in a single (imported) direction. What you need to do instead, with custom meshes, is to add Edge Split modifier to your mesh and apply that prior to export (KB doesn't automatically apply modifiers on export, regression on my part). Edge Split generates new geometry based on sharp edges and angles between edges, which is exactly what we need. With Edge Split you no longer need Auto Smooth, Custom Split Normals or Export Custom Normals. P.S. Since you're also using quads, make sure to download KB 3.1.1 (or later) - it fixes export of quads UV.
  44. 1 point
    The only significant workflow change is that you'll be able to drop MDLEdit and the ASCII to/from conversion. Everything else will remain the same. Once the importing of vanilla normals is implemented, that will solve some shading problems that can happen currently due to the smoothing group approach. But it won't fundamentally change anything about how handling models works.
  45. 1 point
    Number of things, including swapping some function pointers and appending additional data to mesh headers. This has everything to do with model format and almost nothing to do with its contents. i.e. you cannot target K1 supermodels from K2 models without some modification of the bone structure. This is by design, and I have no intention to automate these modifications at the moment. Smoothing groups is a 3ds Max concept to influence vertex normal calculation. MDL knows nothing of smoothing groups and so does Odyssey engine. What I meant by lack of smoothing groups is that in version 3.0 of KotorBlender, original normals are not preserved, and shading might get screwed. However, I have since implemented import & export of original normals and will soon release an update.
  46. 1 point
    Just tested this and yeah - we can import and export original normals, no problem.
  47. 1 point
    So does this mean that KBlender will be able to import/export the model's original normals directly rather than dealing with MDLEdit/KMax's hacky conversion to/from Max smoothing groups (which is a legacy of MDLOps/NWMax's ASCII format)? Because that is the single biggest problem with the current Max/GMax workflow, causing all sorts of broken shading issues, especially on head models.
  48. 1 point
    For those interested, version 3.0 of KotorBlender is out. ASCII MDL / PTH workflow has been dropped in favor of binary importer & exporter. Binary MDL support is mostly on par with MDLops/MDLedit, except it lacks smoothing groups and cannot export saber meshes. I will fix these as I go. Other plans include streamlining the editing process, e.g. one-click lightmap baking and working with multi-material objects, armature animation export, advanced shader node setups, etc. Also, an interesting discovery I made about the MDL format - both MDLops and MDLedit expect per-vertex "tangent space" data to have the following layout: Bx By Bz Tx Ty Tz Nx Ny Nz, where B is a bitangent, T is a tangent and N is a normal. However, my experiments show that "tangent space" is actually a transposed TBN matrix, which makes a lot more sense from the engine standpoint: Tx Bx Nx Ty By Ny Tz Bz Nz.
  49. 1 point
    Status update: I've done a couple of beta releases (now at beta 4), where I've improved compatibility with MDLedit and added support for editing PTH files. For those interested in baking lightmaps or editing PTH files in KotorBlender, I've listed the necessary steps in the description.
  50. 1 point
    Fix is in the repository (mesh removal made redundant after upgrade).