A bug report resulting in improved error handling might be nice but someone else will have to initiate it, I'm...err... "not on the DAZ LIST of shiny happy people. "

The original outfit I encountered the error in is an unreleased personal mesh that has already been corrected with no unaltered cr2 available...I "eliminate with extreme prejudice" any non-working files.

The Salome outfit should provide sufficient test grounds for error resolution as it's a trivial error.

The error can occur at any point in the morph deltas list; however, as the obj information has been loaded prior to the error, it's not a show stopper.

In my case it only affected texture loading, as seems to be occuring with the Salome (chest), any error in the affected morph function itself was unnoticeable. (Didn't look, as nothing was glaringly obvious.)

Testing the functioning of the corrupted morph as well as those that load after it for more complete information prior to initiating a bug tracking report would be reasonable.

Until the error handling routine is tweaked to handle corrupted morphs better, the method I outlined previously will correct the actual error in the cr2 that generates the error code.

It's a bit of an aggravation but only needs doing once as opposed to manually loading the texture every time the object is loaded.