DarthParametric

OK so I just went back and checked again and it seems that your hex edited vanilla model with added alpha node set the value at 1.0. That doesn't crash. However, if the value is edited to, say, 0.5, then it does crash. That would apparently rule out MDLEdit and put it back to being a fundamental game/modern OS problem.

Almost certainly the vanilla doesn't crash. Or at the very least I have never had it crash. I believe both @JCarter426 and @jc2 tested it and reported no crashes with VBOs enabled either when I had them test my custom model (which does crash). I have run several tests of it in a row with no crashes. It may need 3rd party confirmation, but it at least appears that a straight recompile does not crash. My question is if you do a hex comparison of a straight recompile MDL with a recompile MDL with a single alpha controller added, why is it so significantly different?

Yes, you are correct. The MDXs are a match. I just tested a straight decompile/recompile of the vanilla and it didn't crash. I was certain it did crash the last time I tested it, but I have so many different versions now I can't keep track. I tried a fresh attempt at decompiling the vanilla, adding an alpha 0.5 to the head mesh, then recompiling. This did crash, but the MDX was identical to the straight recompile, so maybe we are back to where we started with it being a MDL problem. Here are the files if they are of use. The_Ongoing_HoloRakata_Saga.7z Oh god damn it..... OK, that's my bad. I must have accidentally hit it when selecting hex mode in the menu. I have done that a few times actually. Maybe you can add "move buttons above menu bar" to your future ideas wishlist.

View File Taris Upper City Cantina Entrance Wall Panel Fix This mod is a small fix for a couple of wall panels in the entranceway of the Taris Upper City cantina. For some reason the mesh for this particular pair of panels was split off into a different model from the rest of the room. More importantly, it was assigned a lightmap that doesn't exist, thus it appears black in-game. To solve this, a duplicate of the adjoining panels was added to the entranceway room model in the appropriate position and the original mesh removed. To install, simply drop the MDL/MDX files into your Override. Compatibility: Won't be compatible with any other mods that edit those two room models, but the likelihood of that is low. Acknowledgements: Thanks to @bead-v for KOTORMax and MDLEdit Thanks to @ebmar for bringing the issue to my attention Submitter DarthParametric Submitted 08/24/2018 Category Mods K1R Compatible Yes  

You don't appear to get a notification of a review being posted for a subscribed file, only a comment. Edit: Hrm, did eventually get an email, but no site notification. Possibly a glitch I guess?

So I am guessing the MDX issues, whatever they are, are probably also the cause of VP's Ajunta Pall's ghost model crashes. Have you narrowed it down to a specific subset yet @bead-v? The normal data? Edit: On a different note, I see that when loading a binary model and switching to hex view, you are adding data that doesn't actually exist in the loaded model. For example: I gather MDLEdit is showing what would exist in a model it compiled (since you can look at the hex view of a loaded ASCII as well) rather than what actually exists. In this case, some of the "imaginary" data seems to be TSL-related, stuff like the hide in hologram flag. But this is a K1 model.

You can only import ASCII files. Make sure you have decompiled the model with MDLEdit first.

The last one you uploaded. The zip was labelled as 1.0.10 but the program itself displays 1.0.99 (same as the previous version). Edit: No crash with that one either.

No crash with that MDX.

No crash with that MDX.

Thanks, but I think the alpha thing was just a bad (if seemingly logical at the time) assumption on my part. Is there anything I can do to further the MDX investigation?

To clarify - the edited model you uploaded doesn't add an alpha controller to the head, it just positions the head on the ground. It doesn't crash though. Decompiling the vanilla model and recompiling with no changes results in a crash at the end of the scene. Decompiling the vanilla model and recompiling with no changes and then swapping the MDX for the vanilla one does not result in a crash. So it seems you are on the right track.

That's my point though, there is no alpha added to the head node. It seems like the position and rotation controllers were edited rather than adding an alpha controller. Edit: I removed all alpha, self-illum, and scale controllers from my custom model and it still crashes, so it seems like it's none of those at fault at any rate.

No, I decompiled a clean copy of the vanilla model, added the same alpha, recompiled and it crashed. The hex edited version you sent doesn't crash, so in the absence of other evidence MDLEdit must be doing something that induces a crash in that scene. Edit: Wait, I don't think you actually added a <1 mesh alpha to that model. I just noticed it looks like the head is sitting at ground level rather than transparent. Decompiling your model node skin Head parent C_HoloRakata position 0.0 0.0 0.0 orientation 1.066e-005 0.0365348 0.999332 3.14159 Versus decompiling the untouched vanilla model: node skin Head parent C_HoloRakata position 7.58e-006 0.025986 0.710792 orientation -0.0 0.707107 0.707107 3.14159

Perfect, thanks. I was trying to do exactly that. While I could add controller nodes 9 and 10 via a hex editor, I didn't know what to do to adjust the changed offsets for the camerahook nodes. Anyway, a test with this model with VBOs enabled did not result in a crash. Seeing as a version to achieve the same thing compiled with MDLEdit did crash, I must therefore assume that something MDLEdit (and MDLOps) is doing is causing the crash.

What you do in the privacy of your own Override folder is your business. It would only require permission if you wanted to publicly release a mod based on someone else's work (or have someone else do that work for you and post it on a public forum).

Some placeables are only used in one place, and that's especially likely if they are custom ones added for a mod. If would be a lot easier to add certain things via placeables rather than screwing with room models. But it's not particularly practical in K1 anyway given the placeable limits. In TSL you can apply tints on a per-instance level to sort of fake lightmapping.

OK, so here's something bizarre. I was getting odd graphical glitches on Lehon, like all the polygons on the beach being outlined and the dirt texture inside the Elder's compound being weirdly offset and blurred. I was forcing AA in the nVidia control panel so I tried turning that off. Going back into the game, those problems were fixed. But that also coincided with the crashes. I just tried turning the forced AA on again. Testing again, I now longer get the weird graphical artefacts, and I also don't get any crashes.... Yeah you are just lacking the textures. Edit: Testing the NPC hologram on Kashyyyk, I am getting a crash right at the end of the dialogue as the Star Map animation plays. I don't get the crash with the vanilla hologram. Here's a save if anyone wants to test it (same model posted above): K1_Save_Kashyyyk_Star_Map.7z Edit 2: So it seems like enabling the Disable Vertex Buffer Objects option in the INI prevents it from crashing. Now I need to figure out if the crash with that option disabled is being caused by the model, or if it's just the usual game being screwy on modern systems. Edit 3: My guess is that enabling mesh alpha is causing the crash when VBOs are enabled. At the point of the crash, a script fires with destroys the NPC. The game tries to fade it out. For whatever reason fading works fine with VBOs disabled, but crashes with them enabled. I'm trying to find a way of taking MDLEdit/MDLOps out of the equation, but the vanilla model apparently lacks the controller data for alpha (I guess those only get added when alpha is <1?) which makes hex editing problematic, at least for me. Any thoughts @bead-v?

Probably the best solution would be to sticky a redirect. Easy enough for the DS tools download section, but I don't know if that works with off-site links. Worth a shot at least. Summoning @VarsityPuppet to add it to the list of mod/admin jobs.

This should cover most of your needs. https://deadlystream.com/files/category/17-modding-tools/ http://www.starwarsknights.com/tools.php

Looks like you could change the GetDistanceBetween value so it only triggers when you are closer (currently appears to be 15m): void main() { int int1 = GetUserDefinedEventNumber(); if ((int1 == 1001)) { if ((!sub1(OBJECT_SELF, intGLOB_118))) { sub2(OBJECT_SELF, intGLOB_118, 1); } else { if ((!sub1(OBJECT_SELF, intGLOB_119))) { sub2(OBJECT_SELF, intGLOB_119, 1); } else { sub2(OBJECT_SELF, intGLOB_118, 0); sub2(OBJECT_SELF, intGLOB_119, 0); if (((!GetIsConversationActive()) && (GetDistanceBetween(OBJECT_SELF, GetPartyMemberByIndex(0)) < 15.0))) { sub3("ONE LINER", 5, 5, 5.0); SetGlobalBoolean("TAR_GORTONONELINER", 1); ClearAllActions(); ActionStartConversation(OBJECT_SELF, "", 0, 0, 1, "", "", "", "", "", ""); sub4(); } } } It could also be that sub3 is providing a delay timer, which would be 5 seconds if so. void sub3(string stringParam1, int intParam2, int intParam3, float floatParam4);