DarthParametric

Modders
  • Content Count

    4,639
  • Joined

  • Last visited

  • Days Won

    525

Everything posted by DarthParametric

  1. One thing I should also mention is that your normal map needs to be in OpenGL or +Y format (also known as "right handed"). Most apps will typically export normal maps in DirectX format (-Y, left handed). It is easy to switch between the two simply by inverting the G channel of your normal map. You can tell which one you have by looking for raised details. In an OpenGL normal map, these will appear to rise out of the image. In a DirectX normal map, these will appear to sink into the image. Like so: Images taken from - https://www.turbosquid.com/3d-modeling/stemcell/materials-texturing-stemcell/stemcell-texturing-guide/
  2. No, they must be different names. The diffuse will be pfbselven01.tga and also have a TXI file named pfbselven01.txi. That will contain something like: bumpmaptexture pfbselvenb Then the normal map will be named pfbselvenb.tpc (or whatever else you decide to call it - just make sure it matches what is in the diffuse's TXI). It will not have a loose TXI, but it will contain the TXI data that you specified during conversion. This will be something like: isbumpmap 1 isdiffusebumpmap 1 bumpmapscaling 3 You can change the bumpmapscaling parameter to 1, 2, or 3 depending on how you find the look of the intensity. Typically the engine is pretty piss-weak with normal maps, so they need an intensity boost to see any significant effect.
  3. Yes, DXT1/5 is DDS compression and will result in artefacts. I would not convert the diffuse to TPC - leave it as a TGA. The normal map must be converted to TPC or the game will freeze/crash when loading.
  4. Use TGA2TPC to convert your normal map: Make sure it has a white alpha channel and save it as DXT5. Create a TXI or select the text option to just manually enter the info. You don't need it afterwards - the info is stored in the TPC.
  5. They are under Stealth Items -> Belts in the inventory editor.
  6. DarthParametric

    #3: Porting

    So, Mission romance mod using Vette VO when?
  7. DarthParametric

    #3: Porting

    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).
  8. I'm waiting for this policy change to turn out to be some elaborate scheme to round up all the porters and ban them.

    1. ebmar

      ebmar

      Thankful for being basic 😂

    2. LDR
    3. Malkior

      Malkior

      The Mods wouldn't do this! They simply wouldn't!

       

      (As an aside, it's nice to finally be able to edit Status Update replies)

    4. Show next comments  345 more
  9. DarthParametric

    #3: Porting

    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.
  10. I wonder what it would look like with some sheet lightning off in the distance. What ever came of the discussion of animated skybox textures?
  11. Yes, and the solution is what I posted above. It's a problem with the engine.
  12. This can likely be solved by creating separate 47/50/51 models and adjusting appearance.2da to suit rather than using racetex. Summoning @ndix UR to dispense wisdom on the root cause of the issue.
  13. You ladies sure do like your drama. Perhaps @Tyvokka can hand out some lithium tablets.
  14. DarthParametric

    #3: Porting

    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 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.
  15. DarthParametric

    #3: Porting

    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). The same as any other skinned mesh, pretty much. The only difference is they split the mesh and the skeleton out into separate files. 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.
  16. Since it's open season on porting, why not go the whole hog? The "same series" argument is complete BS and has no basis in any sort of legal context. If you are fine about porting from TOR (which, by the way, I find hilarious was prompted by a merger with /r/kotor given how much they hate it), then why not Battlefront (original or new), JKO/JKA, Force Unleashed, etc.? Hell, why not Mass Effect, or Fallout, or any other game? And what about the other way? Can we make our own "proper" version of stuff like Aperion, porting KOTOR content into Unreal Engine?
  17. The official rule post on it pretty much indicates as much:
  18. If I may be so bold as to double post: I am not getting any notification for comments ("reviews", technically?) left on a mod's download page. I get an email because I am following it but otherwise I would have no clue. While we are on the subject of these reviews, all the old ones appear to have been eaten in the site update. I assume these are now lost forever?
  19. None of which are legal, and could attract the attention of an EA lawyer hit squad at any point. The move is such a complete 180 on previous policy that frankly I find it bizarre.
  20. Ah, no, this is indeed a hugely significant shift. The K1/TSL rule is fine, and to be honest it's about time. It was only ever a fairly senseless (and hypocritical) holdover from LucasForum's original policy. But suddenly you're going to allow porting content from SWTOR? That strikes me as a pretty big departure, and probably something that would attract undesirable legal attention. I'm curious as to what prompted it. Is there some secret cabal of TOR content porters that mods/admins have been furiously banning in the background? You're really working hard to make this a thing, huh @Snigaroo?
  21. @Tyvokka: The "Browse" drop-down menu in the header now appears to have two "Leaderboard" entries, one at the top and one at the bottom of the list. Edit: Ah, stealth fixed I see.
  22. I think that's just poor writing on his part, especially when he was surprised by the reaction people had to it - http://drewkarpyshyn.com/c/?page_id=162
  23. Another fix you may want to include:
  24. Only when you are trying to combine it with an envmap, which you won't want to do in your case. You can just keep the alpha solid white. I wouldn't worry about testing a normal map in-game before the texture is finalised though, as you have to recompile the model to enable the bumpmappable/tangentspace flag, and save the texture as a TPC. A lot of screwing around that is best saved for last.