DarthParametric

Modders
  • Content Count

    4,601
  • Joined

  • Last visited

  • Days Won

    518

Everything posted by DarthParametric

  1. No? They were were always shit. The implementation is fundamentally broken and not recommended for use by anyone. Aside from that, basically other than TSLRCM/M4-78 and Effix's various mods, pretty much everything on there is stolen and uploaded without permission. HP is a relatively new tool. Aside from being multi-platform, it opens up some possibilities beyond what TSLPatcher can handle. You can hotlink to DS-hosted textures, although only as regular embeds in a post, not in the image carousel the mod pages have. I don't know whether mod page images have a maximum upload count. Probably a question that only @Tyvokka can answer fully. I would really question whether any mod actually needs 70-odd preview images though. Just attach a curated selection of a dozen or so to the mod page and link to an offsite gallery with the full showcase for those that want it.
  2. I wasn't saying that you specifically should do it, just that Salk's request would make more sense if it harvested the heads and plonked them on the standard bodies. Someone else could do surgery. Left as-is they would be compatible with your textures with no further effort, but if you allow 3rd party mod reuse then they could probably stand to be remapped. You shouldn't be encouraging the use of Workshop mods. And no, loose textures aren't any more compatible with Workshop mods than other mods. Mac and Linux users can use the multi-platform HoloPatcher as a drop-in replacement for TSLPatcher, if it is required.
  3. It's not a "glitch", you just broke your install with incompatible mods.
  4. If you're going to start chopping up body parts, you'd be better off just lopping off the lite heads and turning them into standalone heads and using them on the "full fat" bodies, since that seems to be the only thing you're actually after.
  5. No, there will never be Iriaz in K1CP. It's not a content restoration mod. Besides, doesn't the K1R installer already offer Iriaz as a standalone option? Although presumably it would need to edit OnEnters and thus be a hard incompatibility with K1CP.
  6. No, K1 models do not work for TSL, or vice-versa. They need to be recompiled for the target game. I have no interest in creating a TSL version.
  7. It's somewhat random depending on what the player does, but most noticeable on Kashyyyk. You can find the specifics in the issue thread for it - https://github.com/KOTORCommunityPatches/K1_Community_Patch/issues/756 I haven't looked at it for over a year, so my recollections on the implementation specifics are kind of hazy, but I gather locking it to a cutscene was the most expedient and least intrusive (from a game changes standpoint) approach. If you wanted to change it then I'd suggest you'd need to strip all the scripted animation cues out of the DLG and manage them externally so they can't be interrupted.
  8. This was done to prevent the animations breaking.
  9. Upload the TPCs in the enduser mod (one for K1, one for TSL). Create a separate modder's resource with the source assets. Optionally you could have a single modder's resource or split it per game, since the site has per-game modder's resource sections. Its use will likely be pretty minimal, since most downloads will just be the actual mods, so just go with what you think is best. Have a look at how JC split his cloaked robes mods for how it could work.
  10. I assume you're still using NWMax? You may want to consider switching to KOTORMax (with this fix) and MDLEdit / MDLOps v1.02. Although note that these are not compatible with Tainia's Replacer due to changes in the ASCII format.
  11. With the advent of seedhartha's fork of KBlender and his implementation of binary model I/O, breaking normals shouldn't be an issue. At least if you can stomach using Blender.
  12. Wow, long time no see. Welcome back. You definitely want to split them for each game. Definitely not half a gig's worth. You'll have to create an off-site gallery somewhere. Imgur maybe, or you could create a Github repo and use their Sites functionality (have a look at Kex's skyboxes mods for an example of how it is done). Not sure off the top of my head, but I have released stuff under CC BY-NC-SA 4.0 before - https://creativecommons.org/licenses/by-nc-sa/4.0/ You'd need to add it to every release page and readme I guess. You'll want to read the rules regarding it, since I have never looked into it personally - https://deadlystream.com/topic/7454-deadlystream-forum-rules/?do=findComment&comment=73940
  13. @Scirs: Please try again with a fresh install of the game using this version of HP - https://github.com/NickHugi/PyKotor/releases/tag/v1.60-patcher-beta4 Grab HoloPatcher_Windows_x64.zip if you're on Windows. Speaking of which, can you please provide some details of your system. What OS version are you running? Where's the game installed? What version of the game is it (Steam, etc.).
  14. There's definitely something weird going on. It's complaining about the ini lacking things that should be there. Can you confirm what version of K1CP you have?
  15. That was the plan eventually, although it wouldn't be of any use here since it is designed for taking screenshots/videos of weapons. This particular case would require a custom solution, but would follow the same basic idea.
  16. Because it's the vanilla blaster model. It was for testing/demonstration purposes, nothing more. That's why I mentioned the invisible character approach above, because it obviates the need for any model at all (besides the character itself), so it will work with any arbitrary custom model simply by specifying the appropriate UTI in the script (exactly as you'd equip any other NPC). Albeit possibly/probably requiring custom positioning adjustment, depending on the type and style of weapon.
  17. We'll need to wait for the authors of HP to chime in on the technical side of things, but it looks like you're trying to reinstall it over a previous installation. Don't ever do that. K1CP needs to be done over a clean, unmolested copy of the game.
  18. Does it generate any logs? If so, post them. Try downloading a newer version of HP and using that - https://deadlystream.com/files/file/2243-holopatcher/ Perhaps @th3w1zard1 can help troubleshoot and/or provide a newer beta version.
  19. Not necessarily. Off the top of my head, the only other obvious examples I can recall are for Matrik laying mines and Calo throwing a grenade. I don't think there are any problems with either of those. For the former, that presumably explains why the trapkit models protrude beneath the floor. But as far as weapons go, yeah if you are creating a custom scene then it's probably not great. A better, or at least more flexible, alternative to the current approach would be something like the stunt weapon holding rig I made for taking screenshots of my melee weapons mod. Basically an invisible character that's just a couple of hand hooks. Going that route would allow you to equip any weapon you wanted dynamically, without needing custom models for each one. It would probably require different positioning depending on the weapon though, for which you can use different animations.
  20. That's the "measuring stick" I mentioned. Each colour is 10cm high. It allows for a rough estimate of the required offset. Based on the pic, looks like -10cm is required (bottom of the light blue/top of the green is the model's Z axis 0 point).
  21. Yes. As I said before, there could be some hardcoded element to prevent clipping through the floor. Given that changing the height of the spawn location doesn't appear to change anything, I'm assuming it just ignores the Z value altogether and calculates it from the walkmesh height. While item is listed as a valid object type for that function, that could just be a holdover from NWN. They have the specific CreateItemOnFloor and CreateItemOnObject functions in Odyssey to handle their needs. Try this alternate model: Alt_Model.7z It contains a "measuring stick" that should be useful to gauge the offset from the floor. I also moved the blaster mesh below world zero.
  22. Is that with the adjusted waypoint height? Try this script that switches to a location instead. Alt_Script.7z
  23. If you want to test it, try this and see what happens. Duncan_Stunt_Blaster_Test.7z
  24. The only difference is that vanilla blasters don't have shadows enabled. Just makes it harder to notice that it's floating as well. If you edit the vanilla model and enable shadows you'll see the same thing. If it was laying flat on the floor then half of it would be clipping beneath the ground. This could be an issue with the way CreateItemOnFloor works. Perhaps it only takes X and Y co-ords from the input location and calculates the Z (height) value dynamically from the walkmesh to prevent clipping. After all, locations only support a Z rotation value (heading), so it is giving it a Y rotation by itself. There might be some hardcoded element for how to deal with certain object types. In that case you might need to create a custom model of a different type.