Hi all, I found a fabulous character, very unique, she needs Arduno's v1wgmt, (okay I know I spelt that wrong lol) but at any rate, found that...now that says I need v1 low res, can't find that. Does anyone know where that would be??

V1 Low res was available from Daz for a while, but I don't know if it still is available. Originally it was a weekly freebie, then for a while they sold it in their store.

I got my V1 lo-res free with the magazine Computer Arts Interactive CDROM (CD56) couple of years ago. Maybe you can ask over at the DAZ store ?

Message edited on: 01/17/2006 00:18

Had the same problem, couldn't find her anywhere but EveV2 or his Herma character are also very nice.

Attached Link: http://www.daz3d.com/shop.php?op=itemdetails&item=659&cat=8

@ EnglishBob I had the same idea but it is a pcf file, you need Mover and with the blMilWomLo.obj of V2 you get an "Range check Error"

I do like eve also, but really wanted the other...hmm thanks for all the help and tips all. I think I am going to ask over at Daz maybe just maybe they'll resurrect her for a little bit lol

Give us a feedback 'cause I love Arduinos figures and I am missing this one.

"with the blMilWomLo.obj of V2 you get an "Range check Error" I remember with one pcf, one of Arduino's actually, the name of the .obj had changed (may have just been the case of the letters). Changing it to match (on a copy of course) fixed the problem. I'm not sure if that would generate the range check error or something else though. In another case, the geometry hadn't changed but a comment line at the beginning of the .obj had changed. Putting in the proper comment fixed it. Of course the 3rd case is if the geometry actually did change in which case, you're SOL without the correct version.

But who knows the comment line needed for this, may be someone can publish that line here, I don't think that this is a violation of copyrights, am I right. BTW, if you start in Mover with the difference file you get the original filename neded for decoding show, so you can avoid the mistake with the uppercases.

True about the name if you look in the box. I'm not gonna get into the copyright thing--I'd ask Daz first. The fact they they sometimes make changes in the already issued geometry files does cause problems though for people using pcf ot rte to encode items based on them. In the case I mentioned, I think it was a timestamp at the top of the file. I only see those in the MilGirl's .obj files offhand. Others just have a Daz copyright Date so it varies.

This file has only a g in the first line, for group I think.

Out of interest, I looked at the files I got with my V1 and V2 low res by installing them in separate temporary folders. The OBJ files were identical down to the last byte. Your mileage may vary of course; a newly purchased figure isn't guaranteed to be the same. Mine were dated 16 May 2002.

As for publishing one line of an OBJ file, this quote is from the Copyright Forum FAQ:

"Under the fair use doctrine of the U.S. copyright statute, it is permissible to use limited portions of a work including quotes, for purposes such as commentary, criticism, news reporting, and scholarly reports. There are no legal rules permitting the use of a specific amount of use and whether a particular use qualifies as fair use depends on all the circumstances."

In my opinion publishing the comment line from a mesh (not even a single vertex coordinate) should not be a problem. However, do bear in mind that I am not a lawyer, nor do I play one on TV. Copyright law makes fools of us all. :)

There's been a similar problem with the various versions of V3; the newer SAE OBJ has a different header to the SR1 version. Although the actual mesh - vertices, facets, UVs - is identical, in order to decode an Objaction or RTE encoded item you still need the same version as it was encoded against. It's possible to convert one to another with a text editor and a little care.

Yeah, I ran into the latter problem with Netherwork's V3 hybrids. It's one of those things that someone should have thought of. I don't know how often Daz changes .obj files but it wreaks havoc with the encoding solutions. I had suggested the ability to decode from multiple versions but on reflection, I think the apps just need to ignore comments. I doubt even Daz keeps a list of changed comment lines. They'd have to go in and look.