• Content Count

  • Joined

  • Last visited

  • Days Won


ebmar last won the day on September 29 2020

ebmar had the most liked content!

Community Reputation

766 Jedi Grand Master

About ebmar

  • Rank
    Caffeinated Jedi

Profile Information

  • Gender

Recent Profile Visitors

19,001 profile views
  1. It's fine, hahah. Thanks for considering the request anyway. From how I see things, there are some unusual practice which potentially freak-out the game -- As Kexikus said the resolution of the portrait/po_mekelh1 have to be in perfect-square and more importantly as form of power of 2; such as 64x64, 128x128, 256x256 and etc. Yours is 360x450, and the game should gone crazy on that. So I'd suggest to crop it and make it 128x128 -- that's the common-working setup to use for portraits, as either known mods or vanilla itself implements for this game For the head texture, as been said the texture looks fine - stands in 256x256 dimension. Though I suspect it could be the TGA compression you did which the game didn't like. Your filesize stands in 128 KB for a x256, while mine at 192 KB without compression. Maybe you can try this one and see if it loads [or try not to compress one upon exporting] -- N_MekelH02.tga If any of those examples didn't work then the problem is in some other places. Could be 2DA, even so model. Or something as simple as invalid filename. What you're using should be more than sufficient, I guess. Though in your case you might need to install some plugins as Effix said earlier.
  2. Face, body or any objects turning all white means the texture can't be loaded by the game for some reasons -- and one of them is an invalid TGA format. What program did you use to export and edit it? Edit: Disregard. Late to noticed that you're using PS -- sorry, hahah. Anyway, if you don't mind perhaps you can attach the relevant files for us to inspect. I mean, it could be anything. Like invalid fields for DS transition in heads.2DA, and with the portrait could be something with portraits.2DA. So for a good start I'd say is to see if the exported TGA's valid or not. And what SH asked earlier about the size of portrait is relevant also. Another thing could be with how you convert the JPG to TGA.
  3. Style 3 all the way! Simply because it provides a clear view of the surroundings, hence make it easier [for me] to compare the before-to-after results. Also impressive-looking stuffs there.ūüĎć
  4. Thank you for the information. I'm so lucky to stumbled upon this thread prior to my attempt that somehow related with. You just saved one's soul, hahah. While here I also want to attach a visualization of this idea, for one to easily understand what actually happened --
  5. Yeah, I can't really do anything with that. If you want you can try adjust lowering the high as your liking. And as for the volume, yeah - it gets normalized hence the cranked-up volume. Again, you can lower it down as you'd prefer. And again, when speaking about [professional] audio quality it all comes down to the resources. We can only do so much with the acting/voicing, but it's really those wares that does all the magic, hahah.
  6. Try this one, Salk -- nm35aavict23000_[Salk]_LowCut.mp3 See if there's any improvement with that. What I did was to cut the lower frequencies because I heard a bit too much around that area. Well -- that's just me with my ears, lol. As for the actor's; the quality of audio sounds professionally done -- well, as expected I guess. Can't really tell with the acting part, but I think it's pretty fittingly-good. But that cut at the end was a let down. Adding few silenced bytes could do, though not sure.
    Fantastic! Just gave the tool a run-test and turn out quite nicely. As a module extractor, this tool did an amazing work. Every assets extracted and re-organized very neatly. At the other hand, as a module cloner -- label-wise, every area infos, models, and lightmaps are cloned properly. Though improvements could been made with cloned lightmaps TXIs to be exported too, as well as the [area] textures'. An option to export them as TGA/TPC could have been nice also. If it's not too much to ask then [batch] hex-ing the Model Name to match the filename would be perfect, hahah. Nevertheless, many thanks to the author for this tool -- it certainly helps anyone that attempt to create a clone/reskinned module. Cheers!
  7. [Updated to v2.0.0: September 24, 2020]ÔĽŅ What's new? 2 version of the panel -- transparent screen and solid-non-transparent version New panel frame trimesh made by DarthParametric New 3D buttons trimesh made by DarthParametric Panel screen bitmap made by Sith Holocron Panel board bitmap made by ¬©FrankDiorio, as shown on his website [then niubniubsuniverse-dot-com]. Available to use but not for resale TOR-ported animated bits redistributed by DarthParametric
  8. Good question, and can't blame one for that. Long story short, before I know how the patcher works, I thought more/less the same as you -- the installation might not working as intended, and without knowledge for once I copied the MOD file inside a mod archive and then paste-overwrite the existing one inside my modules folder. Fun times, lol. So in general it's best for one to understand it like this -- as DP stated above It still should inject the appropriate changes into that MOD. What happened under the hood is the installer make changes to the already existing relevant MOD/unk_m44aa.mod file on your end, and does not copying what's inside the mod's archive. The opposite happened when -let's say- you have a clean install of the game and this mod being installed first. You will then have empty modules folder filled only with RIMs, without any MODs. What this mod does then it will copy the [vanilla] MOD inside its archive to yours, and then inject the appropriate changes onto it. It's a necessary procedure for the mod to work properly. And to answer the question -- I can only say to install this mod at the latter stage of your build, which means after K1CP and any other mods if necessary. Hoped that helps. Cheers!
  9. [Update: 09/15/2020] Indeed it is. So, after long hours of development; trial-and-errors, stress-and-joy, and not to forget the heart-warming assistance yet deadly-constructive-critics both from @DarthParametric and @Sith Holocron -- I got a Release Candidate for the now v2.0.0 [too much stuff changed for a v1.2.0, lol]. What's new in the upcoming version? Front -- Behind -- Some technicals: # node trimesh DP_commPanel by DarthParametric // New frame of the panel made by DP # bitmap sheb_compnl_scrn by Sith Holocron // Screen base/layout made by SH Diffuses that animated on screen were ported from TOR by DP, and kindly redistributed towards me to use with The buttons and its layout were downloaded from niubniubsuniverse[dot]com -- then/now https://dioramaworkshop.com/decals/ // ©FrankDiorio. Available to use but not for resale. Few edits here and there to blend with the game-world more suitably The panel texture/PLC_comPanel currently still in vanilla scheme, albeit upscaled to x1024 from x256 using PS'. To be honest I'm comfy with how it looks, because I can't think [or made one just to be fair, lol] of anything that suited for To-be expected issues: With current transparency setup, traffics seen from one of the room inside the Medical Unit will not be rendered, though they are from the Bumani office -- Lightsaber planes as well with the hilt also -- There's a workaround for the traffics, but that's beyond the scope of this mod so they're something to live with at the moment. As an option will be included the solid-non-transparent version of the screen so, those issues would not be known. Something to be argue, perhaps -- but I have always wanted the screen to be a little bit transparent, despite of the issues. So for preferences' sake the option is there. Cheers. That's all for an update -- if it's released I'll do an update with this post, but if anything changes then there will be another one, lol. Catch you later!
  10. With this attempt you'll need a fresh module load, and you must not enter the area previously -- that assuming Jolee were spawned soon as entering the module [can't remember if I ever check that]. Try to load somewhere before going down the lift first time. Granted, NpcOverhaulK1 can probably be the culprit, but I never use that far enough so can't give any insight on. Things will probably breaks more than it currently is if you're going that way. Let's see if you can make it work with current solution first, and look for an alternatives later [not that anything practical I can think of, lol]. Though probably someone can chime in and grant you of this wish. Good luck!
  11. If anything this could be the one -- #12 KOTOR 1 NPC fixes Is it this mod? -- If indeed that is, you may want to check any instance of p_jolee001.UTC in your Override. And if there, try to remove it temporarily and see if you can proceed. For further details you can try following this post and on.
  12. This can be useful, but for now and the foreseeable future I'd advise you to go with Notepad++ instead; as quoted from DP in above -- -- [although I didn't notice the former plug-ins this time around. Dang, that looks handy -- will try one now!]
  13. I can partially agree with you by installing a unique DLG to the Override [that not shared in different modules such as lev40_carth], and hard-overwrites any of the same instances -- as I've been there trying to setup a patch for a massive DLG and ends-up breaking things, lol. If anything the way I see it -- the patching comes when someone decides to change the script/how the script works in a specific nodes, without adding new trees and/or branches to the DLG. Can also work for new cameras placement or anything that basically not changing the structure. I can't see things working if let's say -- I decided to have a mod that does the same as you but having more/less dialogue options/variations and decides to patch yours. Because one thing I know that TSLPatcher could not delete nodes -- it can only adds/edit ones. Edit: well, figured out one could add a conditional script that is unavailable so the node/s will not shown, but you get the point. Alternatively -and last resort, as it will turns you a villain here, hahah-, you can make your mod a semi-closed system by editing the script that fires the DLG - point to your customized one that have unique labelling e.g. scr_unk41_mision. That will make yours very specific, and if anything breaks you know the one script that does that. Anyway, congrats with the release -- looking forwards for more from you. Cheers!
  14. That often happens when -as the warning said so- the file's index value for a menu goes out of bounds. Typically if you're loading a UTC that Appearance_Type exceeds the row limits of the loaded appearance.2da. In most cases, to fix that you will need to have this settings [with the KotOR Tool] -- Tools \ Options... \ Other \ 'Check' the *Look in Game's Override folder for 2DA files* -- so that it will load the edited 2DA in the Override, rather than the one from the base game. That can also be caused by other fields, such as Subrace/SubraceIndex -- though can't recall which one is it, depends on which have the exceeded values. TL;DR -- do not edit the crashed file with KotOR Tool. Use it to extract the file, and then use K-GFF for the editing. It might be difficult at first, but you can try looking at other same-format files to see how they were set up.