DarthParametric

Members
  • Content Count

    3,293
  • Joined

  • Days Won

    315

Everything posted by DarthParametric

  1. The pillar facing changes were already implemented alongside adding the missing lamps.
  2. Well for starters, just allowing the vanilla Bioware ones to work. Almost all vanilla scripts have debug outputs that are disabled by a simple check to see whether it is running on the retail/shipping build. If you can find out how to get that check to fail, that should allow for said scripts to pipe various debug info to the screen and also an external log file. Poking through the exe, you can see reference to "ProductVersion" and "PrivateBuild", which may be relevant.
  3. I will say that despite the spaghettification and other wonkiness, it does seem more functional than Xoreos, which is a notable achievement. I doubt I'd ever actually consider it for a playthrough before it was fully feature-complete, but if you manage to incorporate some debug-style features then I can see its utility for mod testing even in a semi-complete state.
  4. I might check it out again when development is a tad further along.
  5. That's all well and good, just don't actually announce your project until you actually have something tangible. The internet is a graveyard of big idea projects that ended up going nowhere (I've been involved in some myself). Still, well done on progressing this far, although on my end I can't get past the initial player spawn-in in K1, or even past the initial class selection screen in TSL. Which is a shame, because I like that there appears to be the option to visualise triggers and so forth - that could be a very useful debug tool. I haven't given it more than a cursory examination yet, but the Forge component looks like it might be useful to ease people into modding. By the way, might I suggest an option in the settings to disable internet access? I'm not sure what you are trying to pull from Steam or DS, but I am not a fan of offlline applications that think they deserve unrestricted network access, especially without even asking first.
  6. Sounds you just need to stop screwing around and use a stunt animation.
  7. Pop in a script with a delayed ClearAllActions on the NPC.
  8. Looks like you might need to increase the falloff a bit. It seems to me that it fades out a bit too quickly at the top of the plume.
  9. Not sure what happened there. I thought I fixed it last time. Maybe the eyelids got accidentally reverted in the second version that adjusted the eyeball UVs. Try this version: K1_PFHB03_Fixed_(Again).7z I also smoothed out some of the bumps in her head (as much as was possible anyway, given the low poly count), since it looked like someone had taken a hammer to her. Presumably @Dark Hope will be interested in the update as well.
  10. View File Movie-Style Holograms For Twisted Rancor Trio Puzzle This mod replaces the 2D billboard holograms used in the Twisted Rancor Trio puzzle in the Taris Lower City Apartments with full 3D holograms, coloured blue like in the movies (and TSL). Also fixes some missing sound effects that were intended to play when activating each hologram. You may also be interested in my Movie-Style Rakatan Holograms and Movie-Style Holograms for Endgame Cutscenes mods. Changes: Replaces Bith 2D sprite with four separate animated 3D Bith models, each with a different instrument Replaces singer 2D sprite with animated 3D model (two different anims) with semi-custom texture to look like the original Adds emitter VFX Only switch emitter light on when activated instead of always on Repairs broken activation sound effects Known Issues: Because meshes do not self-occlude, there are some artefacts when viewing from certain angles. Requires a save before entering the Taris Lower City Apartments (East) for the first time due to GIT changes. Acknowledgements: Thanks to @bead-v for KOTORMax and MDLEdit Thanks to @ndix UR for TGA2TPC Thanks to @CarthOnasty for the original idea, which I shamelessly stole (I did wait 2 years though) Submitter DarthParametric Submitted 06/20/2020 Category Mods K1R Compatible Yes  
  11. Version 1.0.0

    105 downloads

    This mod replaces the 2D billboard holograms used in the Twisted Rancor Trio puzzle in the Taris Lower City Apartments with full 3D holograms, coloured blue like in the movies (and TSL). Also fixes some missing sound effects that were intended to play when activating each hologram. You may also be interested in my Movie-Style Rakatan Holograms and Movie-Style Holograms for Endgame Cutscenes mods. Changes: Replaces Bith 2D sprite with four separate animated 3D Bith models, each with a different instrument Replaces singer 2D sprite with animated 3D model (two different anims) with semi-custom texture to look like the original Adds emitter VFX Only switch emitter light on when activated instead of always on Repairs broken activation sound effects Known Issues: Because meshes do not self-occlude, there are some artefacts when viewing from certain angles. Requires a save before entering the Taris Lower City Apartments (East) for the first time due to GIT changes. Acknowledgements: Thanks to @bead-v for KOTORMax and MDLEdit Thanks to @ndix UR for TGA2TPC Thanks to @CarthOnasty for the original idea, which I shamelessly stole (I did wait 2 years though)
  12. You can specify functions in an external script (an "include") which the compiler will pull in during compilation. Bioware's compiler also pulled in every global constant specified in any includes, regardless of whether they were needed or not. And since the planetary includes (what you are seeing there is from k_inc_end) tend to have a bunch of globals, compiled scripts are typically full of useless garbage. You'll know when one of them is used, as you'll see something like CreateItemOnObject(stringGLOB_12, OBJECT_SELF, 1) Like anything else, working with scripts is just about practice. Look at enough scripts and you'll start to decode how they work, and recognise certain patterns. For example, any time you see a script that has a function from an include ("sub") with a few if statements that include "GiveXPToCreature", then you'll know that is UT_SetPlotBooleanFlag from k_inc_utility (and that UT_GetPlotBooleanFlag is almost certainly one of the other functions). Eventually you'll be able to clean up source to bring it back to what it would have looked like originally, sometimes taking a multi-hundred line script and paring it back to just a few simple include functions (OnSpawn scripts being a great example of this).
  13. There are a few. Some should already be fixed as part of K1CP.
  14. I think that's the neck plug. It's hidden underneath the head, it's just there to hide any gaps.
  15. It seems that UVMapper doesn't handle the separate meshes very well. It's a simple fix. You just need to unify everything into one mesh before exporting. Once you have deleted all the bones, etc., select one of the meshes. Doesn't matter which, let's just choose the torso as an example. With it, select the Modifier tab (little blue pipe-thing icon on the right). You'll see a stack of modifers - Skin, OdysseyTrimesh, Editable Mesh. Right click on one of them and choose "Collapse All". You may get a warning message, but if so just select OK (and if you do there should be a checkbox to disable future messages about it). Now you should just be left with an Editable Mesh. Further down you should see a sub-heading called "Edit Geometry". Under that is an "Attach List" button. Click that and a selection window will pop up. Select the other two meshes and hit the Attach button. Now the three meshes have been combined into one. Export the OBJ again and you should get a proper UV template. Here's a test output vs 3DS Max: Edit: Ah yes, my original instructions in that linked thread say as much - "A note concerning multi-object GMax files. The OBJ script only exports a single mesh object at a time. If you have a multi-part model (like a body for instance) you'll have to join them all together into a single mesh before exporting. You should also delete any bones and helper objects if there are any. "
  16. So the trophy heads in Davik's estate on Taris. They are pretty dire, and I always mused about replacing them at some point. This is the vanilla room: The heads themselves are just stuck directly on the wall, with no obvious mounting/backing board like you normally see with hunting trophies. In addition, I never understood why they put the weird arch things in there, blocking the view. It's the only room that does that. So I had a look through what TOR had to offer. I couldn't replicate it 100%, since the vanilla heads are Rancor, Dewback, Wraid, Tuk'ata, Ronto, Kataarn, and Iriaz, but TOR doesn't have the last three species. Here's what I came up with: I got rid of the arches and plugged the gaps in the sides with some new lights, while moving the overhead lights up to the ceiling. The substitute heads are a Reek, a Nexu, and a Tauntaun. And since I know a lot of people don't like the TOR stuff, I also made a version that replaces the original heads with the ones from the regular vanilla creature models. Still low poly and terrible textures, but slightly less garbage than the originals. But they do at least match the same species types: The heads now match their actual creature size in the game (at least the vanilla species). The original versions were scaled down, the Rancor especially being comically small compared to the description Calo gives of bringing it down (big enough that he was able to perch on its shoulders). Although it is now so big (the size of the one you see in the sewers) that it can't actually fit on the back wall, so I had to come up with some struts to mount it out in free air. The wall lightmaps might need to be cleaned up, and I'm also not really feeling the mounting/backing boards. It just a chamfered cylinder with a procedural wood texture, since I wanted to keep it simple. I'm not sure what I should do about it. A different material/texture? Maybe more of a shield-type shape?
  17. Further to AFP's point, here on DS would be what you would call the "stable build" and should be what 99% of people use. Github will host occasional designated beta builds and the like, and the truly adventurous can clone the repo to get the bleeding edge development build as we push new fixes.
  18. You're doing the opposite of what I said. You are deleting the body and keeping the bones.
  19. Yes. that's fine. @bead-v will have to pipe in with what the "CoCreateIntance() failed" error refers to. But you appear to have the body meshes imported, which should be sufficient to export UV map templates. The thing you have to remember is that GMax is crippleware. It can't really do anything - that's the entire point of it. But there are ways around the limitations. I cooked up a way to create UV templates from it over a decade ago, and amazingly all the links still appear to work. Go check out step #2 in this tutorial - https://web.archive.org/web/20151013150937/http://lucasforums.com/showthread.php?t=195825 The tools mentioned: UVMapper Classic and Renx OBJ Tools. The only thing you need to do for a character model is to delete all the bones and such first. Click on the "Select By Name" button in the toolbar (or press the H key) and enable the "Display Subtree" option down the bottom. Then scroll down until you see the skinned meshes. For a body they should be something like "torso", ArmL" and "ArmR". Anything named "xyz_g" is a bone. CTRL click to select all three and hit the Select button. Now go to "Edit -> Select Invert" and delete. Now you should have just the body model ready to grab the UVs from using the method described in the tutorial.
  20. You have to decompile the model first. The game uses a binary model. KMax needs an ASCII model. Get MDLEdit. Most recent beta version is available here.
  21. One day, many moons from now, we may get a wiki for that sort of thing.
  22. Well that's because "OdysseyBase" is an object type, not a name. There always has to be some level of assumption in advice, lest you write a telephone book-sized blow-by-blow account for even the simplest of tasks.
  23. Some of your problems definitely come from doing things you shouldn't have. In this instance, a simple mesh edit, you should not have needed to touch the KMax toolbar after the initial ASCII import.