Thor110

I will do. This isn't possible to do. I have been trying to do so for a long time now, but the kotor modding community is relatively small, the game has a lot of bugs and requires specific know-how to work with. Early on I had hoped to get the entire community involved in the project, but it just didn't happen. There is also a lot of debate that revolves around which game is better or which version of the games are superior. Some of these things would have to be figured out before moving forward with a large team, though I have tried to support all versions of the game on my own so far. I am more than happy to hear what people have to say, I just wanted to point out the reason why some things haven't been done. Would love to spend every waking moment working on this project sometimes, but I also have a lot of other projects that I work on and not enough time to do so. Here's to hoping that I can indeed one day finish the project, but I wouldn't hold your breath as the scope and scale of it is almost inconceivable.

Interesting that I find myself mentioned directly! For future reference you can @Janetgeorge67 with the @ symbol followed by a name to tag people. While these little fixes can appear to be seemingly simple, they soon cascade into a larger set of problems or grow exponentially in the time required to apply the relevant fixes due to the number of models involved. Usually modders pick and choose what they want to work on/with and this results in other things getting left behind, not so much shrugged off but not being focused on. For example @Salk recently asked me about applying Shadows to the placeable models, which is definitely something that is considered to be simple. What is not simple however, is how many there are, a total of 222 placeables or 232 entries in the placeables.2da file, 10 of which are dud entries or placeables, there are probably a few more and some which don't need shadows at all. So while fixing the shadow for one model, might take three attempts and 15-20 minutes, at 15 minutes each that soon cascades into requiring 55.5 hours of work to apply that same fix to all of the placeable models, based entirely on the assumption that it is the first model I tried it with, this doesn't take into account the extra time it takes to find a good location to view the placeable from to ensure it's shadow looks good or that something hasn't been missed due to the way the model is set up. So for something as simple as ticking a shadow flag on 222 models, it can soon result in requiring between 3 & 4 days ( SOLID ) of work. While I have been trying to persuade everyone to work on one overhaul of the game so that these things are more easily accessible for people, modders are busy with their own lives and they often like to pick and choose what they work on anyway. Up until very recently it has been just me working on the Expanded Galaxy Project and while I would love to include everything, that isn't always possible as first I have to get permission to do so, then I have to properly include it, both tasks can take many hours or days, sometimes even longer with regards to getting permission. And even now, there is only one other person working alongside me that I have also had to tutor to bring up to speed with the project and various intricate details of the game and how it works. There is also the hotly debated topic or issue of what should or shouldn't be included with what mod or project, for example some people like to attain just fixes to the base game, nothing aesthetic in order to maintain the vanilla look and feel, while others like to go for the full overhaul route, there is also mods that seem out of place and are only going to be used by some people, stormtrooper armour for example. Even with my project, there are people that like things one way or want it to be another and I have to try to take that into account while also staying focused on what I think matters. Mod requests aren't always even looked at, it might not have been specifically ignored and even if it was, that would only be because people have their own projects to work on. You also have to remember, modders don't get paid, so while I am considering doing the shadow fixes for KotOR1, the thought of spending 60 or more hours doing so puts me off of the idea, coupled with the fact that I would then need to do exactly the same process to fix them for KotOR2 which I took a look at doing and it seems would require even more time to do so, because the lighting system in the games isn't perfect. For example see the following screenshots. Ignoring the big shadow in the middle which is cast by something else. The star map casts a shadow which can be clearly seen. However! Because of the way the game works, the moment it is off camera, the shadow disappears. Now, it might be possible to fix this by adding a dummy mesh that takes up a large amount of space to ensure it is always visible, but this could again require perhaps hours of tinkering and testing to get perfect, it then would add another 5-10 minutes to the time it would take to apply to each placeable model. Given a conservative estimate of 30 minutes a model, that adds up to 111 hours of work. So for what might seem like some, to be a seemingly simple issue or fix, the scale of applying them to a large number of models, soon becomes troublesome. As showcased with these screenshots, it took me three attempts to get the desk placeable looking right in KotOR1 This is because the model has various parts to it and those parts all interact with the lighting system, as can be seen here the panels prevented the shadow being cast. So I went back and enabled shadows for that part of the model. Only to go back in-game and notice that I had missed a part on the side. Which meant I had to do it again. ( this can be seen in the bottom left of the shadow and is caused by the light on the side ) I hope this illustrates my point and why perhaps not every mod request has been seen to. People also tend to take on mod requests which interest them personally and ignore those that don't which is perfectly understandable and entirely fair.

View File Taris Walkmesh Fixes This is a fix spotted and requested by @Salk I have since spotted and added an extra fix for the door showing through the wall. It seems as if there is either a gap in the walkmesh ( which I couldn't find ) or K1 does not consider both sides of the faces of a walkmesh because this issue is not present in my port of K1 to TSL. Either way, here is a quick fix for that. Installation : Put the following files in your override folder. M02ac_02b.wok M02ac_02k.wok M02ac_02e.wok Uninstallation : Deletefile the following files from your override folder. M02ac_02b.wok M02ac_02k.wok M02ac_02e.wok Thor110 Submitter Thor110 Submitted 12/02/2024 Category Mods K1R Compatible Yes  

As far as I know everyone that has tried this has given up, so no shame there.

Both games are relatively similar, though they have some specific differences. There are a lot of tutorials available for modding the game, for the most part it's just a matter of opening up the files and learning your way around. As I mentioned though, realistically this is the sort of thing that needs to be automated, manually adding an entry for every line spoken by the player character isn't feasible.

No, I don't think so, you would have to generate the lip files yourself, there is information on how to do so around here somewhere. I believe the best tool for generating lips is currently in the reone toolkit, from what I remember reading it is the best anyway. Really doing this is a LOT of work and not something that can realistically be done manually, it would have to be automated otherwise you would have to go through every line of every dialog yourself and make various adjustments, as well as generating the lip files.

There's an entire tutorial and discussion on doing this. As I recall someone was looking to automate the process as well. Long story short, it's a lot of work, but it's possible.

Thanks for the heads up, I expected it to crash in some places which is why I put a warning in place, unfortunately I haven't had the time to get back to testing this as I have been busy with my main project at the moment. But I will take another look at it when I get the chance.

That would be the one, from what I recall it worked fine for me though I didn't play it for long, but going by the OP it still sounds as if they might have done both. I did however forget to add the obligatory advice of try again.

As far as I remember from back when I used it, UniWS does the hex editing itself when the game launches and you don't need to hex edit it at the same time. IE : hex editing it is one way to apply the resolution changes and UniWS is another way. Though I only used it once for KotOR1 many years back and I don't have it installed anymore as there are better ways to make the changes.

A few days ago, I decided to start turning the Coruscant cutscene level into a functional landing pad for Coruscant. It has taken quite a lot of work but I have got the model itself to an acceptable state, at least, as it appears in Blender, however I haven't got it in-game yet because there are some issues with geometry and the walkmeshes moving when exported from Blender. The focus of this project has been to improve my skills with Blender, but I would also like to finish this and get it in-game to replace the Nar Shaddaa reskin from the Coruscant mod. But, it might end up being an overhaul for the Coruscant mod, only time will tell. For reference, here is a screenshot of the original level. And this is how it looks now. So far I have put around 15-20 hours into this and I think it looks good, I need to add some more buildings and do some work with the surrounding area, but it's coming along nicely. I have re-used the hallway from the council chambers to create this cross section corridor and the elevator from Peragus to be used to access different parts of Coruscant. It took quite a while to get these corners made and looking right, as well as the floor and ceiling textures. While it's not perfect, it was the best I could manage with the geometry and textures available to me. I also noticed that on the Nar Shaddaa landing pad and these landing pads, they are missing the safety barriers, which I think is fine for Nar Shaddaa, but not for Coruscant. As seen here, there were no barriers at three of the edges of the landing pad, but I added them in. The Ebon Hawk is now fixed, not sure what happened to the texture previously, I have also included the changes made by WildKarrde which gives the Ebon Hawk transparent windows. And that's everything so far, I am not entirely sure if I will finish this, but if I don't I will release the .blend file as a modders resource. Though I am hoping to fix the current issues and get it in-game! Thor110

You are such a buzzkill SH. It's applicable because I said I might make one, you need to stop being so passive aggressive and generally hostile.

View File Telos Missing Shuttles This was made as a request for @KiraYamato It adds two shuttles to the empty bays on Telos. It's far from perfect, I still need to tinker with the lightmaps a little but for now I have done as much as I can. This is still a bit of a WIP but I might not get around to fixing the lightmap issues. Thor110 Submitter Thor110 Submitted 11/19/2024 Category Modder's Resources  

Speaking of this landing pad... I spent today working on this little beauty, my plan is to delete the landing pads from 950COR, that way they don't feel too familiar and aren't seen in the background of the level. I've also deleted the council chambers from this version of the level, that way an elevator can be taken down and another elevator can be taken to the council chambers, just as in the existing mod. Quite proud of this, but I have yet to see how it actually fares in-game, the walkmeshes need some adjusting and I need to finish the cross join hallway in the middle of the building to add two elevators, or possibly a room, I am not sure yet. There's still a lot of work to do, but this took me the best part of a day to put together. This shows the landing pad without, for some reason it only had safety rails on 2 of the 5 gaps in perimeter, so I added them to all 5 on both sides of the level. Nar Shaddaa has these gaps too, but I think it's fine for a run-down old landing pad on Nar Shaddaa, not some fancy fresh landing pad on Coruscant. And a preview of the hallway from the inside. I might attempt to make a landing/take-off animation myself, though I have no idea how it will turn out or if I will even get that far yet, the surrounding area needs decorating somewhat still I think.

Always good, I am preparing this project for all 8 versions of the game as well. Amazon Android Disc GoG LegacyPC Steam Switch Xbox And I will probably need to make a Mac specific version too, but I have it set up where I only edit one set of files and automatically create the changes.ini file for each version of the game. Amazon, GoG & Steam are practically identical, apart from the .exe edit's for the port. Disc & LegacyPC are also practically identical, again except for the .exe edit's for the port. Switch and Xbox have their own GUI's and specific textures. Unfortunately Android cannot have custom movies which kind of kills the entire thing, but here's to hoping someone figures it out eventually, I tried quite a few times and TSLRCM just didn't include their movie files with the Mobile version. Not sure about iOS, I think it requires a jailbroken iPhone which means I might not support it due to low demand, however users should be able to just install the Android version for iOS and everything should be fine, I also don't have a Mac or an iPhone to test with, so it's something I will look into much later on. Oh, is that the case? Good to know, I suppose the Mac version of HoloPatcher will be handy for that then, should be easy to support it as well then! "m/k"? are you referring to the remake? Yeah, will have to wait an see on that, it's bound to be different and some people just want to experience the original, many might want to even after the remake, if it happens. While I know the button prompt stuff isn't super necessary, I have written down what I need to do in order to support this as a feature one day, it will just require a custom launcher that edits the dialog.tlk file using all the string references from tutorials.2da, so it won't really be a problem, it will just have to wait until I get around to programming a custom launcher. There are also a variety of limitations when it comes to iOS, Android and the LegacyPC version on Steam and that is that I cannot alter the dialog text colour, mouse cursors or some of the hard coded GUI elements due to being unable to edit the executable, for some reason the LegacyPC version on Steam pops error code : 41 with an edited .exe file which means it must check the bytes I need to change. As for iOS and Android, I would have to release a modified .apk or .dmg? ( not sure what it would be for iOS ) which wouldn't work without rooted or jailbroken devices, I already tried making edits to the .apk for Android and it just redownloads it. Not a big deal though, I am trying to leave no stone unturned, to try and cover everything, but there will just have to be some limitations. I did manage to edit those things on the original xbox though, by editing the .xbe file! So only iOS, Android and maybe Mac will miss out on those GUI edits. Oh yeah and the Switch.

Ah, now I see what you mean, it is actually there as I just tested with my controller, it's just almost the same shade of blue! thanks for pointing this out! I don't use controller so I would have probably never noticed this. It is barely noticeable! But it is there, I will see what I can do about that. Also, with regards to updating the tutorial prompts, it is not possible to display the icon images for each button, so each tutorial entry would have to be edited specifically for whatever controller type is being used, I am thinking whenever I get around to programming a custom launcher I could implement a tickbox for Xbox or PS controller, where you can only tick one at a time and it updates the strings in the dialog.tlk accordingly, otherwise it would require a whole separate install and differing dialog.tlk files all over the place. Doing it this way, there would of course be no way to change from controller to keyboard mid-playthrough, but I don't think that's really an issue, though saying that, the launcher might be able to run in the background and edit the dialog.tlk on the fly, but it's also possible that could cause a crash if done at the wrong time. Will cross that bridge when I come to it but I have left myself meticulous notes on the subject in the repository / future folder.

I am not sure what you mean, whatever item is highlighted flashes, in this image it is the combat suit at the top.

Even TSL says left click with controller support, but I think that it can be added in, it would just have to be a completely different dialog.tlk file. I am trying to keep things as vanilla as possible while also expanding and enhancing the game, so that's a no from me, but you can always mod it in yourself, people are free to release mods for my mod too. Yeah, there are still a number of issues for me to fix, as I mentioned don't expect perfection just yet! But I would say it's 99% complete. Changing all of the UI was difficult enough and required hexediting the executable to get a number of specific things to change colour. It's also possible to swap between playing K1 & K2 under the same installation, which I felt was necessary. The selection screen does have a flickering highlight and new items have a green/yellow border. I had to overcome a lot of obstacles to get it this far, there are quite a few cutscenes that need fixing up, the first level needs reworking to include the special messages for each class and fixing the cutscenes, on Taris, the cutscene with the Hidden Beks is broken, the Rancor is broken, Malak walks off after being defeated during the ending. Oh, the current release has a broken version of the Naga Sadows tomb level, but it is fixed in the repository. Feel free to post any issues you encounter in the WIP thread for the project or on my Discord server. Hopefully with a few more years I can make it perfect! But there's still a lot left to be desired. EDIT : Unfortunately the tokens for the buttons don't work like they do on console, but it could be manually written in. ( "<abutton>" etc ) When I get around to programming a proper launcher, I could potentially add a tickbox that swaps between dialog lines specific to using or not using a controller, but that's a long way off. There's a lot of things that are more important left for me to work on unfortunately, but I would like to get around to doing everything eventually.

True! But that is a totally different breed of mod! Looks so damn good too!!!!!!!

It's pretty much complete, I have finished LS & DS playthroughs, but there's still quite a few little bugs, some broken quests, some balancing issues and still quite a bit of general tinkering left to do. You are more than welcome to help out, the repository has access to everything, I have also written tutorials on modding the game. Currently it is just me and one other working on it who joined recently, I have been working on the Expanded Galaxy Project for around 6 years now on and off.

I have a better idea as I have been working on a port of K1 to K2 for quite some time now, I will release it here when it's actually ready. Play my port of KotOR1 to KotOR2 https://github.com/Thor110/Expanded-Galaxy-Port Though I will say, it isn't finished yet and is FAR from perfect, still quite buggy.

Yeah, I didn't do anything with the lightmaps. Someone was going to take a look at them for me but they haven't got around to it, it might be possible for me to paste parts of the lightmaps from the K1 levels, but figuring out which tiny blotch of pixels to copy across would take a while.