DarthParametric

Members
  • Content Count

    3,419
  • Joined

  • Days Won

    332

Blog Comments posted by DarthParametric


  1. You should definitely use the Unofficial Tweak Pack to remove the most questionable elements of TSLRCM. Some other suggestions from my usual suspects list:

    Backdrop Improvements
    HD Cockpit Skyboxes (despite violating my "HD" rule)
    Head Model Fixes
    High Quality Blasters
    Luxa Hair Fix (make sure to use the hotpants option!)
    Realistic Nar Shaddaa Skybox
    Realistic Visual Effects
    Telos Citadel Station Skybox

    Since I seem to recall you not always playing in widescreen, these are optional I guess:

    Improved Widescreen Experience (stretched UI fix)
    Main Menu Fix for Widescreen

    Now I will enjoy TSL as-TSLRCM-K2CP-is and mind about my nitpick later.

    Probably a good idea. Not least because, unlike K1, TSL is fundamentally broken in ways that are not easily fixed beyond the remedial work TSLRCM has already performed.

    • Thanks 1

  2. Well in truth, local strings - be they in DLGs or UTIs, etc. - are probably sufficient in 99% of cases. But if you want to follow best practice then adding strings would be the proper approach. Then if someone ever wanted to translate your strings, all they need to do is alter the append.tlk, not directly edit every file (which, I'm sure you'll agree, is a real pain in the ass in the case of DLGs).

    As to the how, it's not particularly difficult. Have a read of the PDF that comes with TSLPatcher and it should cover most of what you need to know.


  3. Cannot let my freeloading identity of jc2 go to waste

    You need to pick up your copycat game by changing your avatar to a picture of an Exile in a black t-shirt shrugging. It could still have the Mythosaur logo on it.

    The dlg editor eats all of your apostrophes if you copy and paste text into that

    Tsk, tsk. That's what you get for being a dirty local string user and not properly appending new strings to the TLK.

    • Haha 2

  4. There are Max import scripts that import the TOR skeleton, so that's not a drama - https://forum.xentax.com/viewtopic.php?f=16&t=11317  (don't forget to grab the update on page 2).

    The problem is you can't get the KOTOR rig and animations out of Max, at least not in a form that Motionbuilder would work with. I think the only practical option currently would be to create a new KOTOR rig from scratch using actual bones.  Unless someone created a Max script that automates the geometry to bones process.

    Edit: Well, well, here is something quite interesting:

    K1_Male_Rig_Dance_01_TH.gifSpacer_50.pngK1_Male_Rig_Dance_02_TH.gif

    This is the K1 male rig in Cinema 4D. I discovered that you can use the Max Bone Tools to mark any object as a bone ("Bone On"), so when you export the KOTOR rig as an FBX you get proper bones in other apps. And you can also export the animations, as our fine dancing friend here demonstrates. Somewhat ironically it doesn't look like this when importing back into Max, as for some reason the FBX  importer screws up the bone sizes so they end up as tiny cubes.

    The only real problem I can see now is that the TOR import script imports the meshes/rig rotated 90 degrees. I wonder if we might be able to get someone like @bead-v to have a look at it and add in a snippet that would correctly orient it? It would still need to be scaled, but that can probably be done manually.

    Edit 2:  So setting the FBX import dialogue bone option to "Convert as Dummy" solves the problem of the bones being the correct size/shape in Max, albeit as dummy objects rather than true bones (it also causes some weird visibility issues unless in wireframe mode). Looking at a TOR import, it seems the root bone of the rig ends up with a Y rotation of 180°. Meshes have their rotation values at 0°, despite being in the same position. Based on that, the scripts ideally need adjusting to do a -180° Y rotation and a 90° X rotation to import TOR assets in the same orientation as KOTOR assets. Scaling still needs to be examined in depth, but from a cursory glance it looks like a BMN rig is going to need to be around 87% of the original TOR scale to match a medium K1 male rig. I haven't looked at a female yet.

    Edit 3: After some Googling I came across some Maxscript that will allow for a quick and dirty rotation of the current object selection:

    (
    group selection name:"MyGroup" select:true
    $MyGroup.pivot = [0,0,0]
    rotate $MyGroup (angleaxis -180 [0,1,0])
    rotate $MyGroup (angleaxis 90 [1,0,0])
    ungroup $MyGroup
    )

    You can also insert the line

    select $*

    at the top to automatically select everything in the scene. But this will add those rotations to every object, which is probably undesirable when dealing with bones/animation. I'd prefer to "offset" the world axis during the import so that the original rotations are retained.

    Edit 4: So I am guessing that the TOR team must use Maya. That would explain the models - they are in a Y up, Z forward facing (right-handed?). KOTOR needs a Z up, Y forwards facing (left-handed?). My meagre understanding of these sorts of things is that this can be solved with a matrix transform.


  5. I was looking at Juhani and wondering whether it might be worth porting a TOR Cathar head to replace her (and maybe add additional NPC and/or player heads). I noticed they actually have something like her hairstyle as a player Cathar option, which I would guess was an intentional nod. There's also a set of facial markings that are kind of in the same ballpark.

     

    I was also thinking how this is really a situation where being able to do something like what Motionbuilder does and map the animations to a different rig would be awesome. If you could transplant the K1/TSL animations to a TOR rig, you could just create some new supermodels and import the TOR models as-is, without needing to go through a whole bunch of editing and reskinning.


  6. TOR's files are all stored in archives with hashed filenames. You need a program to extract them and a hashlist to generate the proper filenames. Unfortunately publicly available hashlists tend to be somewhat out of date, so more recent content is probably not accessible. Once extracted, the files are all arranged in various sub-folders. Some things can be found by a simple filename search, but other stuff might require searching through XML files to discover the actual filename of the thing you are looking for (body parts for clothes/armour being a good example).

    Format-wise:

    • Models are in a customised GR2 (Granny) format. For dynamic (i.e. skinned) meshes, skeletons are stored in a separate model. You'll need a Max or Blender script to import.
    • As mentioned above, terrain meshes and level layouts are stored in some sort of (presumably custom) DAT format
    • Textures are standard DDS
    • Animations have been figured out privately, but there is no publicly accessible import script available
    • Audio is stored in Wwise formats. Dialogue is in ACB and BNK archives, music as straight WEMs. These probably need to be manually listened to in order to find specific lines.
    • UIs use Scaleform (a game-centric derivative of Flash)

    A current extraction of correctly named files in something in the order of ~50GB, ~600K files, ~14K folders. I'm not sure how much is missing, probably multiple gigs at least.


  7. Regarding TOR areas, as far as I know only static meshes like buildings and so forth are extractable as usable meshes. The terrain meshes and layouts are stored in a file format that there is no publicly available importer for (that I know of). So you could partially recreate environments, particularly indoor ones, but it would all have to be assembled by hand from the component pieces. For outdoor areas that rely heavily on a base terrain mesh, say something like Tatooine or Hoth, you'd be out of luck for big chunks of it unless you modelled it from scratch. Or unless you could find someone to reverse-engineer the file format and code some sort of import/conversion script/program.


  8. One thing you forgot to mention in your MMO content porting summary - sound. Music, FX, and (perhaps most interestingly) VO could all be ported to K1/TSL. Of particular note is that Grey DeLisle (Handmaiden), Catherine Taber (Mission), and Jennifer Hale (Bastila) all have major roles in TOR, and using the same voice accent/intonation as in K1/TSL, so have plenty of dialogue to utilise. Other notable mentions that play named NPCs in TOR are Kristoffer Tabori (HK-47), Tom Kane (Master Vandar/Uthar Wynn/others), Charles Dennis (Davik/Lt Grenn), Daran Norris (Goto), Greg Ellis (Disciple), Phil LaMarr (Gadon Thek/Cpt Riken). There are also a few others doing "misc" voices in both, but they might be hard to pin down (and the content is probably minimal).

    • Like 2

  9. If you want to minimise issues, you'd import the TSL head, save out the skin weights, delete the rig, then load in the K1 rig, load the skin weights back in. The eyes/eyelids/teeth are all effectively visible bones, so you'd need to add those back to their proper place in the hierarchy.

    • Thanks 1

  10. 54 minutes ago, JCarter426 said:

    Could probably be done with a Photoshop macro if there isn't a plug-in for it already.

    I did a half-assed action for PS for DAO normal maps back in the day that can be used in conjunction with the nVidia plugin to recreate the Z. It will also work on TOR maps.

    https://www.nexusmods.com/dragonage/mods/4019

    54 minutes ago, JCarter426 said:

    What concerns me is stuff like the facial bones, eyes, mouth setup, and shape of the neck. Not concerned that anything will be fundamentally incompatible but concerned that things will be subtly different enough from KOTOR to make the re-jiggery a huge pain.

    I've never looked at it, so I couldn't say, but yeah it would be unlikely to be a very close match. That shouldn't prevent doing a port, but face skinning is always a pain in the ass.

    • Like 1
    • Thanks 1

  11. 49 minutes ago, ebmar said:

    Is it possible, with porting- to have KotOR the 24h passage of the day and night cycle, and features realistic weather patterns?

    No. Porting is related to assets. Dynamic day/night cycles are an engine feature, one that Odyssey doesn't support. There was thread some time back about trying to fake it via scripting a switch between different versions of the same module with different baked lighting, but it's an idea doomed to fail - too much effort involved (if it would even work at all).

    Quote

    I’m not at all familiar with how the MMO models are set up so I can’t comment further.

    The same as any other skinned mesh, pretty much. The only difference is they split the mesh and the skeleton out into separate files.

    Quote

    I stripped it of its bump maps because I didn’t know how to work with those at the time, but I imagine if we could figure out how to convert the formats those could be included as well.

    There's nothing special about the normal maps.They use the standard approach of storing X in the A and Y in the G channels (Z is calculated at runtime), then use the R and B channels to store various masks like emissive.

    • Thanks 1

  12. Yeah I'd think the Telos thing would be minor. I was thinking purely on the station. One or two Wookiee NPCs with dialogue, then a few non-interactive flavour NPCs dotted around the place, "talking" to Ithorians, etc. That would be a nice way to ease yourself into things, shouldn't prove too challenging.

     

    The Red Eclipse thing, I'd suggest you could put a new level transition in one of the empty rooms that TSLRCM opens up. Maybe make it hidden, with either a guard you have to fight (LS) or talk to (DS) to reveal/access it. You could go for the old standby of a door hidden behind a cupboard or something. Then that would go to some other module, yeah. It wouldn't need to be anything too elaborate, probably just one or two rooms to start off with (you could always expand it later). The easiest option would probably be to just reuse part of the existing landing pad module, like Tien's shop or the swoop area. Add some different props, maybe change the lighting or textures, whatever is fairly simple. I'm not sure if that would actually require two modules - you should be able to script whether they are hostile or not. But if that was necessary, you'd still only need the one set of level models.

     

    As far as actual hunts, I'm not entirely sure how that would work, as that sort of thing is way outside my ballpark. I guess dot some new NPCs around planets and then have the usual fight -> talk thing, where once they are down to 1hp or whatever you go into dialogue and through that put a shock collar on them. Kind of like what they have done in recent Fallouts. Tell them to report to a Trando named XYZ at the spaceport or their collar will incapacitate them/blow up. It wouldn't necessarily need to be all Wookiee targets, could be Twi'leks for dancers, etc.

     

    Edit: Oh, yeah I forgot the RE bases/outposts on other planets bit. I guess that would require an additional 2nd module at least, possibly even a unique one per-planet if you wanted to get fancy. Although how many other places could they realistically appear? Korriban is out, as is Dxun. Onderon seems unlikely given the blockade. Dantooine is mostly poor farmers.


  13. It would make sense that the Ithorians would scout Kkashyyyk for deadly wildlife as part of their restoration scheme, so you could work them into Telos based on that. Even if they didn't take anything, they would at least encounter the Wookiees and maybe encourage some to come help.

     

    If you wanted to go the slave route, something involving the Trandoshans is an obvious choice, given they are the Wookiee's next door neighbours and long time mortal enemies. You could maybe extend the Red Eclipse quest. Perhaps in the LS version you could raid a base to free their captives, including Wookiees. That might provide clues to other RE cells you could shut down on other planets. In the DS you could visit there and maybe access a shop, get some bounty quests to capture more slaves for them elsewhere.


  14. I'm not sure Wookiees on Nar Shaddaa would  be a good idea. The convo with Mira indicates that Wookiees are generally unknown and that Hanharr is something of a unique specimen (as a species, not just that he is a psycho). The player can even indicate they have never heard of the species. Maybe you could have a couple on Citadel Station, helping the Ithorians out. That would be doubly beneficial, as you could easily splice in references to them in the Ithorian dialogue without worrying about VO. Anywhere else though strikes me as similarly out of place as Nar Shaddaa.

    • Like 1