All Activity

Thanks!! I'm already working on it, since it's a mod that needs translating. Progress: the dialog.tlk, the override DLGs, and telos are already translated, as well as nar sha. I'm working on the .mod files for modules. I also have the M478 mod in Spanish from before; that's what I started with. Well, when I have it complete, I'll let you know and send it to you. PS: Regarding the souser maps folder, do I have to paste the contents into override? Or is it for something else? Sorry, I'm a bit of a novice with some things. Greetings from Argentina! Thanks again.

That sounds great! I would love for more people to be able to play it! You have my permission to do that. As for your second point, my personal philosophy with designing these quests is that they're "all side quests." Some of the side quests are connected and over the course of development there somewhat did emerge a "main quest" of sorts (though if you're already translating it, you probably also noticed my internal quest names do occasionally indicate main and side quests, but those were more for my reference more than anything else, lol). I can think about it, though. Denoting side quests with the "Bonus Mission" label in the log does make sense.

Would probably work better with an Aurebesh font.

As mentioned previously, it should look like however your underwear looks.

Thanks, I solved it. Since all the new models are TGA, I forgot to run the script to "delete duplicate tga/tpc," Once I did that and purged the .tpc from the Override folder, the new models rendered perfectly in the game. Link here: https://www.nexusmods.com/kotor/mods/1384?tab=files. I layered them on top of Vurts full Visual Resurgence package and so far I really like the combination. And like I said, your work is AMAZING!

Don't suppose it's possible to get a Darkside version?

Good afternoon. The models are intended for use on PC; they have not been tested on other platforms. Based on your description, it seems the system isn't detecting the files at all—if there were an actual error, the game would crash.

Hola, si te interesa, puedo traducirlo por ti y luego puedes subirlo. Ya lo estoy traduciendo para poder jugarlo yo mismo. Pero si te interesa, puedo compartirlo contigo para que otros hispanohablantes puedan jugarlo. PD: En el archivo Global.jrl, sugerimos que especifiques qué misiones son secundarias y cuáles son principales, como en el juego base y el mod M4.78. Pero es sólo una sugerencia. En fin, saludos y gracias de antemano.

Your entire series of "High Poly" heads is amazing. But I can't get them to work. I still get the default models in-game while your work is just being ignored. I dropped them in the Override folder and it's not working. What am I missing?

I can confirm that 1440 60 runs at 1440 60. I'll double-check the 30FPS one today

this is true. also these 2 file sizes are suspect k1rs_30fps_2560x1440.7z = 15.67 GB k1rs_60fps_2560x1440.7z = 15.64 GB

Yes, it should be compatible with Extended Enclave.

This sounds great just to give you some breathing room not rapidly jumping from section to section, and one last chance to enjoy the calm before the storm aboard the ebon hawk, you technically already do off screen. Is it compatible with Extended Enclave as well? I don't believe these intersect but wanted to be sure.

The 1080 60 FPS upload here and on Nexus is yielding 1080 30 FPS files instead.

I think the discussion is mixing several different issues and treating an installation order as a proven compatibility solution when it isn't. Regarding Doodmane444's June 23 report: the tested order was K1CP → Sleheron → BOSSR, and some placeables disappeared in BOSSR modules. However, the suggested alternative still placed BOSSR last. It mainly changed the order between Sleheyron and K1CP, so it doesn't establish that this arrangement actually solves the underlying BOSSR placeable issue. As JCarter426 pointed out, if BOSSR is exhausting the available placeable rows in placeables.2da, changing the installation order cannot magically increase that limit. There is also the reverse side of the problem. OnJuly 2–3, Doodmane reported that BOSSR could replace leftover, unused Czerka sign placeables in Sleheyron's sle_m30aa.mod with its own stasis NPC. He traced this to obsolete placeable entries left in that module after the signs had been built into the model instead. This is a concrete example of BOSSR affecting Sleheyron, rather than the other way around. It is also a specific module/resource conflict, not proof that one universal installation order fixes everything. So I think we should distinguish between: 1) conflicts caused by overlapping or reused placeable references; 2) the actual placeable row limit; 3) installer overwrites and changes to shared resources. These are not necessarily the same problem, and they cannot all be solved by simply moving one mod to the end of the installation order. For players who want to enjoy both expansions without potentially ruining an existing modded installation, I would suggest keeping separate game folders: 1) Keep the existing installation for BOSSR and its associated setup. 2)Make a copy for a Sleheyron-focused playthrough, installing Sleheyron and its relevant compatibility patches there. 3) Start from a save made before the Dantooine Jedi Council mission, or use the save provided with Sleheyron, which starts at the intended point in the story. This doesn't magically make the two mods compatible within one installation, but it provides a practical way to preserve both playthroughs without repeatedly rebuilding the same game or risking the original setup. The current Sleheyron 3.5 instructions do provide a specific combined installation order and compatibility patches. However, I would still like to see reports from people who have actually completed substantial portions of BOTH expansions in the same installation. Ideally, such reports should specify the exact mod versions, installation order, and which parts of both campaigns were actually played. Loading a save or reaching a particular planet is not the same as demonstrating that the entire setup is compatible. I think that would be much more useful than continuing to assume that one installation order automatically protects one mod from the other.