All Activity

This stream auto-updates     

  1. Today
  2. Yesterday
  3. Working on set this week with Kelly Hu.

    My life for hers... I am going through channels to get a picture with her, so fingers crossed. She looks great, and still sounds just like Visas.

    I'd know that voice anywhere!

    1. Sith Holocron

      Sith Holocron

      You lucky devil. Good luck on the signature!

    2. DeathScepter


      hey you are a lucky man. 

  4. Custom OnPerception event? Seems like that would work essentially how you want it to.
  5. Is it normal if the zip file takes so long to extract ? I also get files that are said to be way bigger than the archive itself. Is everything working properly ?
  6. PS isn't really of any relevance to this. You can use Gimp or whatever other image software you're familiar with. Actual generation of a normal map is done in other programs, as described in my post. Or via an online tool, as linked.
  7. Thanks for the reply even though I have no idea what this means as a non-PhotoShop user. If there are follow up questions for DarthParametric, please tag him in your response!
  8. should this be first over ajunta pall's blade?
  9. When talking about normal maps for 3D models like weapons, armour, placeables, etc., generally the "correct" way to do it would be to generate the map from a high poly version of the model. This is what is known as baking. In modern texture generation, this is often as much for creating the diffuse texture itself in the first place as it is for use with the final game model. Here's an example from some of my own experiments with recreating the Ebon Hawk textures from scratch. Take LEH_grwall01. This is the vanilla texture on the left, and my recreated texture on the right (lacking a grime pass): I started by creating a 3D model of the original texture, like so: This was the high poly model. The low poly model was a simple flat plane of two triangles. When baked out, this was the resultant normal map: Obviously this approach is not always practical. Sometimes you'll want to generate a normal map directly from a diffuse image, which I gather is what you are primarily interested in. The simplest route is to create a greyscale height map. At its most simplistic, this would entail desaturating the source image and then running through any number of programs or PS filters to generate the normal map. For example CrazyBump, AwesomeBump, xNormal, etc. There are also some online tools to do this, for example NormalMap Online. Results through this approach will vary wildly depending on the quality of your source image. As an example, let's take one of the texture sources from Sithspecter's "High Quality Blasters for Modders" modder's resource. We'll take w_blstrpstl_001 and simply desaturate it to create a pseudo-height map. Then we'll feed this into NormalMap Online: This is only about 30 seconds of effort, but the result isn't too bad considering. However if you have a look at the attached normal in closer detail, you'll see a lot of noise. This is typically very bad in a normal map, and in this case is somewhat exacerbated by NormalMap Online's lack of sufficient adjustment parameters to mitigate it. But really the root of the problem is that a diffuse is an extremely poor input source, especially in traditional textures that include baked/fake shadowing and highlights/specular. You can see in SS's source image that there are some highlights across the top of the main body, on the top of the sight back piece (bottom left corner), and along most curved edges. There is also a lot of noise in the flat areas from what I gather is the use of PS's Clouds filter, particularly noticeable in the trigger guard and surrounding area. Fortunately in this case we have some ability to quickly and easily tweak the height map, since SS's source is a layered PSD. Turning off a few of the noisy layers to create a new height map input, the revised generated normal looks like this: Looking at the attached revised normal, you'll see there is now far less noise, giving a mostly crisp map. There's still a little bit of wonkiness due to the highlights - notably at the top edges of the grip/handle, the lens of the sight (top left), and the screw heads and scallops - but that's part and parcel of using this sort of image as a source. Those particular issues could be reduced or resolved with some manual adjustment of the height map. Just imagine it as a gradient where white is the highest point and black is the lowest point. The thing to keep in mind with Odyssey is that its normal map implementation is pretty terrible. It's rarely worth the effort to create normal maps. I certainly wouldn't bother for anything small, like weapons or the like. Large floor and wall panels is probably where it will be the most notable, and these have the added benefit of typically being fairly simplistic in terms of the height details, meaning they are easy to create height maps for. Armour and bodies (like droids) can also make use of them, although this is best reserved for large details rather than lots of noisy fine detail. If you are thinking of trying it for stuff like monitor panels and the like I'd suggest you don't waste your time. Especially if it is going to be in a dark area (like the Hawk's cockpit). Stick with faked details in the diffuse for that sort of thing. Edit: Still far from perfect, but here's a further quick adjustment of the height map to address some of the highlighted (no pun intended) problems: You'd actually want to vary the height of the straight panel lines I think, make them a dark grey rather than black like the scallops. And the top edge of the handle needs to be a gradient to get a nice smooth curve. Same thing for the scope lenses (see the screw heads). w_blstrpstl_001_Generated_Normal.7z w_blstrpstl_001_Generated_Normal2.7z w_blstrpstl_001_Generated_Normal3.7z
  10. how is the cutscene triggered? is it by pressing the datapad?
  11. s123

    Sith Stalkers [K1]

    btw can i loot the sith stalker armor or nah? ( havent really gotten around to battling with the stalkers and assassins yet because of game issues) also where do i place the "nm27aastalker01" sound file?
  12. oh, I see. I feel dumb, now. Sorry about that. 😐
  13. want to try using this as well as your tsl robes and crystals, but which ones should be installed first?
  14. s123

    Feat Progression

    what exactly does the mod do? how's it different from k1 improved feat gain
  15. Last week
  16. The Quest name and description are blank in journal, is this normal?
  17. Don't think I did it fundamentally differently from you, but sure, here's what I did. - KotorTool, RIMS, Modules, tar_m02aa.rim, module.ifo -> Extract file. - K-GFF, open module.ifo, Mod_OnPlrLvlUp, change the Value to onLevelUp (I put unique values in all of the slots so I could check each one, just 'test' is fine too). - Save. K-GFF does not manually prompt you to save, so double-check that. - ERFEdit, open KOTOR /modules/tar_m02aa.rim - Drag module.ifo onto the window, say Yes to replacing it. - Save. This is not best practice, as JCarter said, but I have the module folder backed up so it doesn't hurt me. - KotorTool, Text Editor, write something I can easily check, save it as onLevelUp.nss and compile. I go with GiveGoldToCreature(getFirstPC(), 1) traditionally since you get the obvious popup. - Put the compiled onLevelUp.ncs in the Override. - Load the game, load my save in Taris South Apartments. - Level up the PC, receive 1 credit. - (Level up Carth, get no credits, get annoyed and scrap your nascent plans)
  18. Put it in modules folder, not working. Can you tell me how you test this step by step?
  19. You also want to package it in a .mod file rather than overwriting the original .rim files.
  20. Module rims have to go in the Modules folder I believe, not the Override. Oh yeah, and onPlayerLevelup will apparently only trigger on the PC's level-ups, not other party members. So, temper your expectations there, it's not as good as I thought.
  21. I ve try to put script in module for testing, but no success. What am i doing wrong? I ve edited module.ifo file, is it right? Then i packed module.ifo back in rim file with ERFEdit. And put rim file in override folder with script.
  22. Alright, well after a bit of testing, I found that JC doesn't use the high-poly tin cans mod. When I went to change the models, it turned into a blue beam, this was tested with a viridian shortsaber. Also, for some reason, the textures still didn't append on to the model after I replaced JC's model with the shortsaber model found in VP's Tin Cans.
  23. Assuming that JC didn't change the texture names, which seems unlikely, then yes. Just put the textures from this mod in the Override. A before and after check in the workbench should make it pretty apparent whether it worked or not.
  24. So, how exactly would one go about changing the textures for the hilts in JC's extra saber colors? Is it as simple as putting the files currently in your mod's folder in the override, or will there be renaming involved?
  25. Hello, Quanon! In the description it is mentioned normal maps being included and not just upscaled but rerendered. I checked the archive and, if I am not mistaken, there is not a single normal map in it. There are a few .txi files for the normal maps which are the very same the original game uses. Is this correct or am I missing something?
  26. Great work so far, let me know what you think of the dialog for the NPC Jedi that I sent, and if it would still work for when they're encountered in the sub-level.
  1. Load more activity