Ok, so I'm working on Rhen Var, and I want to make a ghost ulic. So I make him in my kth side, then read him in the cw lua. Crash. Through exhaustive processes, I determine it really isn't the unit that is crashing, rather it is any unit from my kth side crashes the cw era. The gcw era, to my knowledge, works perfectly fine.

In desperation, I copied my entire gcw lua to my cw lua. Now it doesn't crash right away, only jed_inf_sith_01 (and ulic, who uses a modified version of that unit) make the game crash. It crashes when I select them when spawning. There is no log to report. No munge errors.

I'm thinking it may have something to do with the cloth, since those two units share the same cloth, it may make a memory problem or something. At first I thought it was just a general memory problem, so I allocated more in the LUA, with no success.

This is the most baffling error I've ever seen, hence my posting a topic. Usually I'm able to fix most of my problems, but this one has me stumped

Post your Bfront2.log, we can diagnose the problem a lot easier that way.

Ah, ok, there were no message severity 3 errors, and I looked through the sev 2 errors, and I didn't see anything.
I believe I edited out most of the redmemory, "InVehicle" and duplicate class name things: I will re-check the sith guy to make sure all of his parts are there correctly again.

EDIT: I found a subtle mistake in the cloth odf, I'll remunge and see if that's it.
EDIT: Well I got ulic and the sith guy working, but It still crashes, I figure it is just another odf mistake, or some cloth-related thing.
EDIT: It was actually my old republic side that was making cw crash. It was missing the all_inf_default base class. Now the kth side works in cw.

Allocate more memory to the combos, the SoldierAnimation errors can crash a map, which is common when custom combos are done.


Message Severity: 2
.\Source\Combo.cpp(2475)
Combo[ba944832]::State[JUMPATTACK_FALL2]::InputLock unknown input '!Strafe'

This should also be the other problem remaining. I don't know how to fix this one.