Jump to content

Home

Tweaking USM to work with TSLRCM


LancerChronics

Recommended Posts

So, I really wanna use USM and TSLRCM... apparently the guy who was working on it stopped. (no permissions or something). But I'm not planning on releasing anything, I just plan on potentially shifting around files.

 

Now, there's things I've read, where it says trying to use USM compatibility patch with TSLRCM causes hang-ups on Malachor V. But I wonder WHY it causes those hang-ups. Anyway, I installed TSLRCM and droid planet expansion....a few minor mods (textures only, really)...and then backed-up my Override.

 

I followed the instructions for the compatibility patch, adding the extra files, but careful not to overwrite the files in the patch. I got 45 warnings, 0 errors.

 

• Warning: A file named k_def_ambmobtrea.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_def_spawn01.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_def_spn_t_jedi.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_def_spn_t_less.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_def_spn_t_more.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_arm.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_arm_h.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_arm_l.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_arm_m.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_arm_r.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_d_shld.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_d_stim.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_eq.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_eq_belt.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_eq_glov.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_eq_helm.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_eq_imp.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_up.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_up_a.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_up_l.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_up_l_cr.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_up_m.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_up_r.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_weap.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_weap_bp.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_weap_br.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_weap_l.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_it_weap_m.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_treas_disp.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_treas_empt.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_treas_less.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_treas_more.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_treas_norm.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_tresciv.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_trescorhig.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_trescormid.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_tresmilhig.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_trescorlow.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_tresmilmid.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_tresrakat.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_tresshahig.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_tresshalow.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_tresshamid.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named k_plc_tressndppl.ncs already exists in the Override\ folder. Skipping file...

• Warning: A file named 650jedi.dlg already exists in the Override\ folder. Skipping file...

 

Now I have to wonder...will the game work with USM mostly, except for these 45 instances, where it will default into the TSLRCM response? Or should I overwrite these files with the ones in the compatibility patch, and maybe have a slightly less up to date version of TSLRCM in those areas (not sure, as i don't actually know whats in the files)...

 

But mostly, I wonder if my game will freeze on Malachor V...if not...I don't see what the issue is.

 

Edit: Something I was reading suggests that k_plc and k_def are for item spawning, i guess in containers and on corpses. So...I would guess that would mean none of the dropped sabers would be created..sucks...but doesnt seem like it would damage the overall game..and everyone would get their uniques upon turning jedi...i think....

 

That leaves 650jedi.dlg which is the jedi master convo/fight....that ones more important...hmmm

Link to comment
Share on other sites

Yeah, you will probably break your game and yeah, it might just happen right at the end of your game, making you lose a lot of time for nothing. So here it comes, unless you are prepared to do a compatibility patch mostly on your own and by yourself, the best you can hope for is to wait for this amazing project which is on the make:

http://lucasforums.com/showthread.php?t=212481

Link to comment
Share on other sites

Dang....you just had to show me that. And whats worse, it's in "decent progress" limbo, where in one section it mentions an August release, and the last post is in October...which means I might not see it for another year, or tomorrow might be "Surprise! 1.0 Release!"...

 

Not sure I feel like waiting. A friend of mine will be playing Kotor 2 soon, and I wanna play it alongside. As an alternate measure, I currently have gone through USM, and cataloged what all the lightsabers are (took a good 2.5 hours)... Was planning on taking my favorites and transferring them into HOTOR to get my favorites from each. (more difficult then I expected..I know I need at least 1 MDL, 1 MDX and 1 TGA per lightsaber, but the labels aren't always equivalent between models and textures..like bao-dur's lightsaber)

 

I wish the date on the mod was more concrete, but such is life and modding. It's done when it's done.

 

Actually, what I wish I had was a full catalog of screenshots of all the lightsabers...would make deciding between sabers much easier.

Link to comment
Share on other sites

If you want the USM lightsabers there is an install option to just install them and console cheat them in.

 

Personally I like the USM for the party training.

 

Either way, what you ask is a ton of work and the legitimate reason no one has or will do a full compatibility patch between USM and TSLRCM is because of the sheer volume of nonsense involved.

 

Sorry :(

Link to comment
Share on other sites

No worries. I can understand the work involved. Just trying to mix and match the lightsabers in HOTOR and USM is tiring me out. And even now, I may undo it all (I love USM hilts like Kreia's walking stick..but HOTOR had so many more color options, and the individual colors suit each unique saber more.)

 

I wasn't so much asking for a full compatibility patch...just whether it would be possible to finagle it, so parts works..and the parts that don't are ignored. (Which is basically what I am doing between HOTOR and USM...finagling it!)

 

Either way...will keep my eyes on that USM 2.0 link....that would be so nice if it finished.

Link to comment
Share on other sites

Mostly it is the scripts that are "conflicting". Those 46 scripts can be "merged", as I did once for RH's Ord Mantell and the original BoS with their conflicting Tatooine area_On_Enter scripts.

 

The issue is the complexity of some of them. I have thought about taking this on several times but always stop short due to my schedule and the time it would take. I will reevaluate this position, but no promises :p

Link to comment
Share on other sites

As the person who helped making the last patch (and resolutely decided not to keep it up to dat for future TSLRCM versions, I think it was for 1.6?)... it's just... a mess.

Dialog files merging is a pain, not helped by USM's versions being buggy, badly set up. So not only do you need to merge it, it also needed to be updated.

Then came the scripts, and the other stuff, and I really don't want to do that effort yet again *at all*.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...