LS2

No, I'm not speaking about the smartphone at all:

You still insulted someone, and in so doing broke the rules. I don't see why they're at fault for enforcing their policy. You've already been provided an alternative. I can only assume your unwillingness to make use of it is either wholly misguided principle or, frankly, a victim complex.

If you've already made your decision, why even make this thread? Why even post in it? As much as several users have attempted to encourage you to think about this from a community standpoint, to realize that this action is not simply personal but will have serious repercussions on the entirety of the KOTOR community, you seem just as intent on going on as before. If that's so, why not simply make your decision and let's have done? You can believe that this stance will have meaning, but I assure you it won't. Valve wouldn't bat an eyelash if a mod which had hundreds of thousands of downloads were removed; if ten of the largest Skyrim mods were removed right now, I assure you that the most they would do is shrug, if they even noticed. And I tend to think they wouldn't. They are a massive corporation, and they don't care about you, or me, or anyone else as an individual. That might bother you, that might piss you off, but it's also simply a fact, and it's not something which is going to change. Removing TSLRCM won't give you a voice, it will merely make you appear petty. I am not a frequent user here, but I also have experience, a lot of experience, working in mass environments and with large institutions. I know that this will get you nowhere, and I hope for the sake of the KOTOR community--and frankly, for the larger responsibility to that community I believe is demanded of you as a power-user--you trust the words of a relative stranger and let this lie.

And rightly so; loose .2da files are the devil. That said, as I'm not the original author, no, you shouldn't be expecting a TSLPatcher version, unless you choose to contact Silveredge and either ask him to give you permission to modify the file like that or to upload a new TSLPatcher version himself. I only received permission for the reupload, and even if that weren't the case I have no modding skill to speak of. I mostly uploaded this here so the community would have access to it, as I needed permission to rehost away from gamefront anyway.

I found Heroes of the Old Republic, which not only looks a great deal like USM, but is supposedly custom-built to work with TSLRCM, so I'm hoping that one won't give me issues. The thing is, ever since last September I've been trying to get a group of mods together that're all compatible to present to a different group I'm in, so the less technically-savvy people there can play a really beautiful, restored KOTOR II. I know a ton of 'em want to. I loved the USM when I used it, and I wanted that to be in the build, but I can't include it because I can't finalize testing with the crash included, so now I have to settle for the next-best, no offense to the developer of HotOR. It simply irks me that it's what seems to be a small bug causing the issue, it's been known of in detail for nigh-on a half-year, and it hasn't been fixed yet. Hell, I'd be more worried about those who decided (and still decide) to boot up TSLRCM and the USM at the same time for the first time and got all the way to Malachor and had it bug for 'em. That's hours of playtime lost, and a great deal of whining here, but it's not fixed yet. I understand priority schedules. As I said, I'm an indie dev. But, also as an indie dev (albeit I don't have much experience with KOTOR II, so I don't know the difficulty of modifying its files for compatibility), I don't look at this as being a difficult fix. If it is, my mistake. If it isn't, as I said in the OP, I know a ton of us would love a fix for this bug.

I don't want to sound pushy, but there's either some severe lack of proper communication between groups here, or we're (the fans, at least those having trouble) not getting listened to. I first brought this bug to the attention of this site last September. Given, it wasn't known what caused it at that point, but I made it very clear that the bug existed then. By December everybody knew what the bug was and what caused it (TSLRCM being combined with the USM originally, then again even when using the USM Compatibility Patch), and yet here we are, in June, and, insofar as I can see, nobody has made any progress trying to fix this despite it being a major hindrance to many of us and the mod groupings we want to play. I'm an indie game dev myself, I know schedules are hectic, particularly over the internet. But when an issue has been brought to your attention over half a year ago and the response is still, "we'll get to it eventually," that's not good enough. If I'm missing something and the problem has been fixed, my mistake, but, assuming I haven't missed anything and it hasn't, I ask the team to please take some time out to just alter a few files and make the USM compatibility patch work for everyone.

That's not sufficient. I can't get the armband to work, and even if I could I'm working on a mod build to post in a different forum. All of the mods that I use have to be fully compatible to qualify, and if the USM and TSLRCM are conflicting, I'm going to have to choose one or the other. I'll choose TSLRCM when I do make my choice--because it's restored content rather than modded content--but for Christ's sake I hope somebody gets their ass in gear and fixes the compatibility issues, because I want both.

So let me clarify; I have this same issue, and have since 1.6. It was supposed to be fixed with this newest compatibility patch, but apparently wasn't. You're saying that, if I remove the USM completely, this issue will cease to happen for me? Is there no other way to fix this without USM being lost and without using this armband-thing?

Hate to just jump in here at the end like I've not been paying attention but, well, I haven't. Not since I joined up and couldn't find out what was wrong with my mod build; came to figure out it likely had to do with me running a compatibility patch for USM to TSLRCM that was outdated, but there was no magical fix for my problem and my game broke every time I hit Malachor, so I pretty much gave up. I'm hoping that something has changed in the meantime. Now that TSLRCM has been updated to 1.7, I'm wondering what the status is with the USM compatibility patch? I'm going to assume (probably correctly?) that applying the same patch for 1.5 (it was for 1.5, was it not?) to my new build would be beyond stupid. If that's the case, what are the details with the new patch? I remember hearing months ago that there was supposed to be a USM patch that would make it fully compatible with 1.6, but with TSLRCM 1.7 out I'm confused as to what the progress on the USM compatibility patch is. I don't want to leave the USM out of my build, but if I have to I have to. EDIT: Sorry, after taking a look around I finally found the news for the updated USM patch; great work, guys! Maybe I can finally get this to work now.

Hate to bump this, but I can't even land on Malachor right now with this kind of issue. I need to know if we--marsp and me--can download k_907_enter.ncs and possibly have our error fixed, or if there's some other kind of option.

I don't have that file. Well, there's your problem.

I'll test it now, I have a save right before the issue happens. If it doesn't work, it could also just be because the module loaded before my save, right? Anyway, if there are issues beyond this or this issue persists my best bet is to download the USM and then download the RCM on top of it, right? So then I'll get parts of the USM but most of it'll be gone, right? EDIT: The issue persists for me. I suppose I should just wait for the USM compatibility for 1.6 to come out and then start a new game?

I don't have a save before the Ravager, unfortunately, and as I cannot warp because of my bloody console not working I can't just start a new game and test it out or anything of the sort. Could it be the compatibility patch for USM be causing it? I have that, and version 1.6 of the RCM.

When you go to that black screen save the game and re-load. Are you in the Trayus core? If you talk to Kreia, she should talk as though you haven't gone to Dantooine yet. Sion should be stuck in a never-ending Force Choke animation. If you have that, then we have the same issue.

I have the same issue as the second one that this guy here describes (my problem was never responded to, unfortunately, and I still don't know what to do to fix it). I get stuck in the Trayus core early, black-screen, and if I save and load the screen displays again, but I'm still stuck in the core. I can't get out by warping, because my console doesn't work. The only mods that I use that this guy uses are as follows: If I could get some help this time, perhaps with this guy's help track down the root of the problem (if it does come from a mod we're using), I'd be very appreciative.