Leaderboard

Hello KotOR modding community. It has certainly been a long time since I've posted here. While life has been busy and can get in the way of modding, I have been working on a big project in secret. For the past few years I have been chipping away at my own version of an A.I. Upscale 4x mod for most of the default character files in both games. Because it has been slow going, I didn't want to get distracted by constantly responding to "when is it going to be ready?" prompts when I could be spending time on the files. I also didn't want to get anyone's hopes up about it, only to then keep delaying because I'm often too much of a perfectionist. But after so much time has elapsed, I keep thinking that I need to put something out, even if it is incomplete in my books. To give you an idea of how big a project this is, I have completed 329/475 textures that are common to both games, 71/214 textures for K1, and 184/419 textures for TSL. That makes for a grand total of 584/1108 textures or 52.71%. I'm using the textures as the basis for completion, but there are also 459 models for K1 and 648 models for TSL completed so far. I've attached a spreadsheet with a list of all the files involved. The reason why it is so slow going is that this mod is more than just a simple process of running all the character textures through an A.I. upscaling program. The purpose is to increase the size and fidelity of the character textures while maintaining the painterly style of the original game artists. I have also been attempting to fix many of the UVW mapping errors, lighting errors, and some XYZ errors that the original model .mdl & .mdx files may have had. One problem of upscaling textures that I've found is that the model seams become glaringly obvious at higher resolution, so I've been painstakingly painting those to look seamless. Anyone who is familiar with my previously released mods will know how much I try to fix those pesky model errors. The other thing about A.I. upscaling software, is that I haven't found one that gives perfect results. Instead of relying on one result, I usually run texture files through an A.I. upscaling program multiple times using different settings. Some settings result in "crunchy" textures (high contrast, sharp edges). Some result in "soft" textures (smooth gradients, lower contrast, blurry edges). Some result in better straight/parallel lines. Early tests used Vance AI; Deep Image; ImageUpscaler; or Let's Enhance. Eventually Topaz Labs' Gigapixel AI was chosen and used on the majority of textures. Then I combine textures in a multi layered Photoshop file, using layer masks to isolate the best parts of each upscaled image. This allows for some portions to be smooth (like skin, glass, metal or tubing), others to be sharp (like burlap, skin folds, hair, scratches, etc). Then I manually paint away errors, fix seams, and make additional changes. At any rate, the reason for this WIP post is that I've been out of the loop for so long, that I don't know the best way to package and upload the mod. I usually use 7zip, so that's not the problem. I currently have 378 tga, tpc, & txi files (4.09 GB) that are common to both games; 459 mdl, mdx, tga, tpc, & txi files (1.07 GB) specifically for K1; 648 mdl, mdx, tga, & txi files (2.90 GB) specifically for TSL. I was originally planning on packaging them up all together and letting the user to put them into their respective override folders, making the common files only needing to be downloaded once. The other option is to make two download packages, one for each game, where the common files are included in both packs. This would result in having to download the largest batch of files twice, but it would be easier for installation. To complicate it further, I would also make download packages for a tpc only installation (for smaller file sizes and easier to run in-game). The other questions I have are: which upload method do users prefer: single download for both games (smaller size overall), or two files (one for each game makes installation easier)? how many screenshot images can be uploaded to showcase the contents of the mod? I currently have 197 pngs for a total of 561 MB, and would like to make more. I've attached a few to sample a range of the types of changes the mod tackles. are there any samples for the Read Me file regarding Permissions and Credits? I want to make the tga version into a modder's resource. Where is the best place to put a link to my "Buy me a Coffee" tip jar? I'm hoping to use any funds towards software upgrades for future modding. I don't know if I'll ever actually finish this mod, but I need to share what I've got before the universe jumps in again and makes something impossible for me. Anyway, happy New Year. I hope to continue more of this work in 2025. Screenshot samples: KotOR upscale completed list v0_52.xlsx

I have a few answers: I haven't looked at other other mods/fixes as I've been focused on getting as much of my mod done as I can. I have just taken a quick look at K1 CP, and I will probably tackle the female armour collar clipping on my model versions (since it looks like a simple XYZ fix to me). I haven't looked at any of the rest yet. If any of my models and textures work for the K1 CP, feel free to incorporate them. I am specifically saving the head models until last, since some of them are really messed up (like the one you mentioned). Some day I hope to get to it. I know that in recent years the community has relaxed its view on "porting" between K1 & TSL, but when I started this mod I deliberately decided to keep them separate. My main reason is that I prefer the Taina's replacer method of fixing UVW & XYZ coordinates, since it preserves the smooth groups. However, if anyone else wants to modify some files to work in either game, I'm not opposed to it. It is inevitable that there are going to be incompatible files with other mods. My Revan robes models, for example, make significant changes to the UVW map of the hands and boots, so they will be slightly off when used with a flowing cape mod. As far as I know, in order to add the animations it would require compiling the ascii model using mdlops, which would break the smooth groups (unless that's been fixed in recent years and I don't know). I didn't sweat it because there are so many other HD Revan textures out there that users will pick and choose to mix and match the ones they like best.