Not sure if this be the right forum to post a product error but i get the attached error when loading the Chest for VaL Salome
It then loads with textures...

Any ideas?

Thanks and apologies if this is the incorrect forum...

Have you posted this at DAZ?  It may be something wrong with the installer.  To double check, try a fresh download of the product and then reinstall.  

Make sure that when you install, no errors are presented. 

Will post there too.

I bought it through Renderosity and downloaded a set of 3 zips (have downloaded again) which unzipped to a Runtime folder (no installer) . I then popped that into my content folder as per normal...

Ciao till i find a solution or if anyone else does...

Oh, I figured it was a DAZ installer, my mistake.  Can you link me to the product?

Its this one - http://www.renderosity.com/mod/bcs/index.php?ViewProduct=69935&AID=408

Everthing else loads great except the chest.

When i tell it to fit to Vic 4.2 it does this [see pic]

I have no idea.  The product page states on it that it wasn't tested in D|S, so I don't know what to say, as I don't have the product myself.  I hope someone who has it sees this thread, that's the best I can do...sorry :(

Ah - i never actually read that - i liked it so much in didn't read the fineprint. Thanks for the efforts. I can 'force-fit' it if necesary in the meantime

I bought it also and had the same problem, even though the product says it wasn't tested in Daz Studio.

When I loaded it, I got an error message and the object loaded but no textures.  I just went to the texture folder and loaded them myself.

No textures sounds as if the load is aborting part way through, assuming it's meant to load textured of course.

If you open the cr2 in a text editor, what is on the line listed (and the lines before and after)?

Same message as myself.
I've opened the CR2 in WordPad but can't find a way to get to that specific line to check it, Is there a better tool for this?

I use Crimson Editor...it's free if I remember correctly.

http://www.crimsoneditor.com/

It will re-format the text so that you can read the CR2.

Thanks MirageBay and RHaseltine

These are the entries for lines 669114/5 and 6. The offending line being the middle one.

d 27461 -0.001251170635 -0.000782012939 0.000722157955
d 27462 -0.001255028248 -0.000798492432 0.000747545958
d 27463 -0.001246337891 -0.000790138245 0.000733237267

This is interesting but i don't know what it means or what values to edit. My own learning curve is now well activated...

That's very odd - that's in the run of deltas (changes in position) for a morph, and there's no obvious reason for it to fail there. I do wonder if perhaps the number of deltas line is wrong, earlier in the file, and that's the point at which the index (the first number on the line) exceeds the declared number. If you search backwards from there for

deltas

you should find a block like this

            indexes #
            numbDeltas #
            deltas
                {

where # will be some number - what actual values do you have?

Hi again RHaseltine

The values are as follows:

            indexes 65012
            numbDeltas 72325
            deltas

Not obviously wrong - at least, it isn't clear that the line with the error could be out-of-bounds. One obvious question is how many vertices does the actual mesh have for that group, but figuring that out would take a bit of fiddling.

Had this problem with a different outfit awhile back and it's fairly easy to resolve. It's caused by corrupted morph target data during transfer to the clothing.

1. Make a COPY of the cr2 file.

2. Open the cr2 COPY in an editor and goto the line number throwing the error.

3. Determine which morph this line number is part of, you can either scroll up or do the math and goto the first line of the deltas then scroll a short way up, depends on morph size which way is easiest.

4. Note the morph target name, simply remove all references to it in the cr2 COPY using something like Morph Manager, CR2Editor, etc.

5. If it is a morph you want to keep you will need to re-insert the morph data into the cr2 COPY using the method of your choice.

6. Texture maps should also load correctly now since the break point caused by the error has been eliminated. Test by loading from cr2 COPY, since everything is good rename the corrected cr2 COPY to the original cr2 name.

"Another Friday, another problem solved"....... 

To find the beginning of the morph, with the name, just put your cursor on the offending line and search backwards for { or for deltas, then scroll up a few lines to get to the name. I was assuming it was something about the morph, thanks for confirming it - it's probably worth making a bug report, citing examples, in the hope that the code can be tweaked to recover as Poser apparently does or at least to fail more gracefully.

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.