LiliArch

Funny thing is, I'm quite sure I once managed to trigger an Unhandler Error with TSLPatcher, but for the life of me, I can't recall what I did. I'm pretty sure it was something crazy simple, and it might or might not be relevant, but alas... if my memory fails to serve me, there's not much I can do about it. Of course there is always the chance that Win 10 screws some library. What it was written with, anyway? c++?

I apparently got my terms screwed. I meant "info.rtf" and "changes.ini" in the "tslpatchdata" folder.

Do you have the readme.rtf and the changes.ini present in the folders? Does this happen in every conversation on that level, or only some of them? I remember having these ones, the cause was junk data in the dlg file that overrode the correct data in game, but not in DLG Editor (since they apparently use different settings). I believe it is caused by an error in the dlg structure, where game doesn't know which branch of the coversation it should follow. (It has a "(continue)" and "[End dialogue]" nodes, from which it should choose from, but it can't, because no condition isn't guarding them, or something like that.) I may be wrong, though.

Dear sirs, you are awesome.

Whether that works or not, depends on the mod itself and the other mods you have installed, but if you didn't need to overwrite anything, you probably are good to go. When you choose the install directory, it should always be the one with the game executable. That usually does read in the mod's readme (at least in the mods I've used), but not always. It's good to remember, nonetheless.

Absolutely NO WARRANTY against damage caused by bad puns. So, I recently managed to find my modding project files and tools (they were kind of lost when I moved to a new computer a couple of years ago) and decided to get back to it, since thanks to these new exciting tools, it seems more likely than before that what I have in mind could actually be done. Anyway... I have this story project that started as a thought about bringing a character in KotOR who would not be dependant on PC to solve their problems. It has evolved since the first formation of an idea, and the story continues in TSL. Or, at least that is the plan. And now it occurs to me that I probably should have thought a bit more what I'm going to write before starting to write a post, so I guess I just need to rely in people asking what they actually want to hear. I am currently working on some new NPC models to bring into the game, but in the meantime, here's some storyboard-stage screenshots. Some of them are quite hilarious. Thanks to Fair Strides for ripping the hat as a separate item, but it appears that I either need to relocate all GoggleHooks or make two separate models if I want to take that approach. I was going to use that as my primary NPC for the KotOR part of the story, but I've since started creating completely new models (need to iron out some issues, but nonetheless). This is actually why my project was brought to halt before I switched computers. The head model I was going to use for one of the main NPCs for the TSL part of the story simply didn't take kindly to remapping. Sadly, I don't have those screenshots anymore. I experienced all kinds of things, from head rolling on the floor to it exploding, so to speak. And no, I'm not going to replace appearances of the default party members. This was simply the most efficient way to test whether the apparance works or not. Studying the texture structure of Peragus, a strong candidate for a recycled area for TSL. Sometimes you just want to see the structure behind it all. I haven't tested on my newer computer, but on my old one, removing the texture simply coloured the model white. Taris Lower City, more than meets the eye. When models go horribly awry. It is still animated, believe it or not. Moves a bit like spider. Sadly, I have no video of it.

I can confirm Intel graphics can indeed cause some very confusing issues. Or at least they used to, I haven't tested latest hardware.

Sounds like fun to isolate, indeed. So it's in decompiling, then. Thanks for clarifying that. I was unable to verify which one it was - granted, I didn't run my full scale of tests either, the results of those tests when I run them last time (with mdlops 0.6 I guess?) were so horrifying that I almost started to believe the whole model was haunted. Anyway, a minor documentation issue if I may, now that I remember. The "Head Link" button could use some explanation in "Help" section. It isn't exactly self-explanatory.

I was running some tests, and it appears that there is still ("still", since it's been haunting me in MDLOps as well) this bizarre issue regarding certain head models (at least in TSL, haven't tested in KotOR - call me lazy if you will) that I wish someone would be able to fix. Now I don't claim to understand what is happening under the hood, but the way the symptoms appear to me is that in certain cases, something in bonemapping goes horribly wrong when decompiling and/or recompiling (can't tell which one, since I still don't understand weighting in 3D programs, ahem) - based on my tests, that happens if the "head" node (I assume it's the same for "tongue" as well, but it's hard to see the tongue when head goes haywire) is not a direct child of the root node (the [modelname]). Take n_dockof (the Peragus dock officer) for example: decompiling and recompiling the head model makes him move his eyebrows instead of lips while speaking, in addition to other weird ticks in facial animations. I can keep experimenting on this if you wish. If you're not interested in the issue the slightest, please let me know, so that I won't bother you with it. As a related note, I was attempting to modify "qbones" values of the recompiled model's "head" node via the "Edit values" feature to see whether that has any effect in the issue or not; trying to save the modified values gave me Visual C++ Runtime Library error "This application has requested the Runtime to terminate it in an unusual way", leading to MDLEdit crashing. Attached in the file, the compiled model and screenshots for what I did and the error message itself. mdledit-testing.7z I hope my text makes any sense. It's been a while since I've written on any forum.