(I did have a problem here before but it was solved afterwards, however this problem that is underneath relates directly to this one now. It crashed after I did the same thing to test; you can see the update on my most recent post.)

Maybe it has something to do with all the Message Severity: 3s at the top of your error log?

Nope, that's not my mod - it's Xavious's Space Kamino which (I think) works. And I've had the Dark Times ones for a while now, they aren't causing the crash. Should've made that more clear, sorry.


EDIT: Unbelieveable! I'd just finished copying all the map files into a new world folder (which took a good half an hour to get working), I accidentally ran the crashing version. It didn't crash. I have no idea why, but it suddenly decided to work again. Good waste of half an hour, but nice to know it still works.

sampip wrote:Nope, that's not my mod - it's Xavious's Space Kamino which (I think) works. And I've had the Dark Times ones for a while now, they aren't causing the crash. Should've made that more clear, sorry.

Just an FYI, that SK1 isn't my Space Kamino map. It's Mav's KotOR space map for KotOR Galactic Conquest, which has the same three-letter name.

I don't own the KOTOR galactic conquest currently, would it still be there?

Looks like you still have the custom_gc_5 file. But it really doesn't matter. That error isn't affecting your map, so you can safely ignore it.

UPDATE:
Well, I managed to get the crash fixed, but whenever I even try to hex-edit anything onto any model whatsover, the game crashes - and then normally does for quite some time even I replace the hex-edited model with the original. A manual clean sometimes fixes this, but it often takes using a completely different played model to actually get it working again.

I have two questions:
Is there something I'm missing out when I'm hex-editing? I did post some questions earlier in the FAQ thread but unfortunately they were left unanswered. I'm sure I followed the tutorial completely correctly, and yet it still crashes.

2. It's happened again, this time it's saying it can't actually find a piece of geometry that is blatantly in my msh folder. It gives me this: When that piece of geometry is, of course, in my msh folder.
Does anyone have any idea whatsoever why my hex-editing is causing such annoying and unrelated crashes?