KateTheShrew opened this issue on Apr 02, 2002 ยท 27 posts
KattMan posted Thu, 04 April 2002 at 6:45 AM
This is getting way out of hand. It seems like soe of yolu aren't even sure what is the problem here. Kate, if the CR2 file is saved under a vendorA in the Characters library it is just a matter of copying that character to a new folder. No editing is necessary normally. Extremly easy to get rid of the extra directories with no CR2 editing. The only time you will have to edit the CR2 is if the OBJ is in the same directory and the reference actually lists the full directory path. If both the CR2 and OBJ are in the same location then the CR2 can have just the file name listed. This allows moving the CR2 and OBJ file together with no editing at all. MadYuri, Pay attention to what I just said about the OBJ being found in the Character library. Now if the OBJ is found in the Geometries folder, then there is a differernt story. I would agree with you that the German version does not retain the american spelling of geometries to my understanding. This should not affect any installed item as the reference should point to geometries and the install should have placed the OBJ under a folder called geometries. The spelling would match so you shouold not have an issue even there. Ankh, If you have a problem with editing CR2 files then you could always ask the developer what the issue is. IF the product works if you follow the developers install then you should not have a complaint. This should be the case with all products bought from the MP as the testers should have seen a problem before releasing it to the store. If your problem occurs only when you try to customize the install, do not hold the developer at fault. Now how do we resolve something like this? I think renderosity has given us (the developers) a method to work around this problem. All products now uploaded to the store also requires the read-me to be uploaded. This will allow all potential buyers to view this file before purchase. Now it is up to the merchants to be sure they provide what the customers want. I think this could lead to more detailed readme files, and more work for the merchant. This work is all upfront and might end up making or breaking a sale. The customer might be using the completness of the readme file as a gauge to how complete the actual product is. Think about it for a minute. Are you going to trust an item now that only says "Unzip the files into your poser directory with folders on" as opposed to an item that not only says that but also lists the files and the locations expected? A full and complete readme can also give the user an idea of just how easy or difficult it might be to use this product.