Share On:

Probably the same.IMO most likely it's a workflow problem, but a different one: the current data is one big salad.Thus some model/texture combinations constructed for spawning from type/faction/whateverspec are bound to fail simply due to random naming of model and textures still actually present in data - it's not all combed and unified yet.Ideally, there should be a way to quickly check whether all combinations are correctly processed (debug mission in Modelview, with spawning via Python, etc), including fallbacks - but that's not what really happens.

loki1950 wrote:We really should cook up a Pearl script or such to check all the data as a first pass to find those miss formed units

Python script. Optionally, embedded into mission file (it works now) - this would allow to run several stages of testing simply by starting VS with a mission as parameter - so that if something quietly goes belly up, but doesn't report, it would be immediately visible anyway.