Enough discussion has gone on in the merchant forum about what some of us think is common knowledge is not known by the newer merchants. Therefore I am trying to put together a list of rules that one should follow in packaging their product for sale here at Renderosity. It will be as this thread is titled. While we have already gathered quite a few things for the list, I would like to hear from the customers what they would like included. Some examples are: 1. All packages include RSR's, png are optional, but not required. 2. All thumbnails to be 91x91. 3. All thumbnails for transparent items are to be rendered. 4. All version numbers to be 4 or 4.01, 5. no hardcoded source files, i.e. should begin with runtime NOT C:Pro......... 6. delimiters in texture locations should be : not 7. Read me files go in :runtime:readme:vendorname folder 8. OBJ files should go in Geometries folder 9. Texture files should go in the texture folder 10. Pose files should place the figure on the "ground" 11. Pose files should not have hip translated in the x or z direction, UNLESS they are part of a "Couple Pose" 12. Pose files should not include props, hair, or light. In other words, do not include smart props, hair or light in posing, UNLESS the pose is designed for that prop. That is a sample, now any other items that have cause you pain in purchasing a product that you thought shouldn't be done?

Readmes should be named 'productnamereadme.txt', NOT 'readme.txt' mac

Good idea, in fact I have been doing that, for example BB_LaceBustier_Readme.txt I will add that to the list!! Thanks

No advertising blurbs from the assorted mat pose file editors in the mat poses. If the mat pose editor puts this kind of thing in a mat pose file, why can't the programmers do something useful like put a "description of file" editor in the thing instead. I have not bought one of these editors because of these type of enforced ads.

I hadn't seen these. I have been using the free MAT Pose Edit and it doesn't do that, at least that I know of. Feel free to IM me with an example of one of these. Thank you.

Can I ask you, where do you want the Readme file to go...I now put it in my texture folder, so it can be found and deleted easily, I don't really care if it is deleted after received. It is only there for instruction anyway. I find too many readme's floating around, I wish they could all go in one place. So...where do you suggest. Sharen

Item 4 is important, but has 1 significant exception: If the product or individual item within product is known by design to be Poser 5 only, e.g. uses Dynamic Cloth, then and only then it should have version 5. That way the user's attention is drawn if they've picked the wrong one. Similarly if Poser AND ProPack MAT/MORs are present in the product, the ProPack-only items could have version 4.3 for similar reasons. Any discussion on where ReadScript Injection files should be stored? Some vendors are using !Daz folders, others are placing just about everywhere...

<7. Read me files go in :runtime:readme:vendorname folder>

I put my readme files in a CDI Readme subfolder of the PoserReadme's folder. The PoserReadme's folder has been there forever, perhaps started by DAZ/Zygote. I just prefer to utilize it rather than starting a new Readme folder in the Runtime folder.

<9. Texture files should go in the texture folder>

They should go in the textures folder. I've seen them put in a Texture folder which creates a new folder rather than the textures folder created by Poser.

<10. Pose files should place the figure on the "ground">

I personally prefer the hip be zeroed rather than the figure be on the ground, but that is just me.

I prefer merchants not include png files at all unless they are developing only for Pro Pack and P5 as these versions of Poser will generate pngs from the rsrs.

I prefer merchants not force their library folders to the top with !, ~, etc. I don't mind the use of these characters within the merchants folder to help push the most used files to the top.

Just my opinions. Of course, everyone has one, so it is unlikely everyone would adopt a standard. However, it would certainly be good for reference. :)

Beth

For my own personal injection files, I made a folder named "Morphs" under the library directory. My suggestion: unique texture names. Much like readme. Put BB_Bustier_Lace.jpg instead of just Lace.jpg. I like to move stuff around, and it's so frustrating when Poser or Correct Reference grab the wrong file because it has a non-descriptive name.

Reference 8 and 9. What about further specifics such as GeometriesClothingBB_LaceBustier or (similar for textures and other poser files where a path is specified)? Just a suggestion but categorization is helpful to help keep things organized. Some more examples: - CharactersClothingV3nameofclothingitem - CharactersV3nameofVickiCharacter - CharactersM3nameofMikeCharacter - PropsArchitecturenameofBuilding - PropsOrganicnameofPlant You get the idea.

What has been discussed on the Readme file is to put it in runtimereadmevendornamefolder This seems one of the more reasonable locations to keep the readmes from cluttering up the poser folder. layingback Good point on item 4 I will modify that with the exceptions. No we haven't but I wouldn't see why the !DAZ folder wouldn't be a good place, because the injection is injecting a morph into a DAZ figure, isn't it? DAZ has one for V3 and one for M3 inside of the !DAZ folder, the vendor could just add their own folder inside of the !DAZ folder. That would keep things clean. Now you know why I am asking the question here. I am just a facilitator of this process.

The suggestions are coming faster than I can answer! ;) GOOD POINTS everyone. I hoped for great feedback and I'm getting it. Rather than answer everyone, I will keep tabs and post a revised list in the near future. Keep them coming!!!! ;)

This was an excellent idea, BB!! I much prefer hearing from the buyers what they would like as standards for merchants. I especially like the capsces made about not putting characters in front of folders so the folders go to the top. As a buyer, this is quite irritating to me. Come on people, lets hear what you have to say!! Keep the suggestions coming!! :)

Well one thing I would like to see is the name of the character in front of the mat file for example - Kassandra tatto body or something to that effect.

This is a Poser question?

yep!

I build all of my Poser stuff in Poser 4 PP SR3. How do I make a 4 or 4.01 compatible file using MAT Poses, morphs, alternate geometries, or whatever and be certain that it works in 4/4.01? Also, how do you create .RSRs? PP automatically creates .PNGS, no .RSRs to be seen in my PP libraries. Although I agree with all of this, instead of just making suggestions, how about also pointing to how to make these suggestions useful. ;) Also, for geometries, I always put them in vendorname/productname/. I don't see the point of putting them in Geometries:Weapons:Japanese:Swords:Stands... For anything other than P5 library hierarchy, it would be ridiculous and confusing.

kuroyume0161, You can use P3DO to convert png to rsr (and vice versa) vendorname can be even more confusing unless vendors just do one type of merchandise and their name becomes synonomous with it (e.g., Fyrene = poses). I just offered suggestions but something more descript would be helpful. Adapting your suggestion, how 'bout at least product/vendor? :-)

That part will be included! First search freestuff area for laetia's MerchUtil. This program does many of the checks and will reset the version number to 4! 2nd do a search for Seno Software, they have a freebie in the free section called P3dO Explorer or Poser Explorer, add the plugins and you can batch change the png to RSRs and it has a very useful pattern renamer! These would be listed along with links as to where to get them!

"No we haven't but I wouldn't see why the !DAZ folder wouldn't be a good place, because the injection is injecting a morph into a DAZ figure, isn't it? DAZ has one for V3 and one for M3 inside of the !DAZ folder, the vendor could just add their own folder inside of the !DAZ folder. That would keep things clean." I think this is a good idea,it will help eliminate the need for multiple Inj pose files. I am going to start doing this with my future packs.

DON'T stick all the readmes off somewhere in nowheresville where they'll just copy over each other. :pffft: Even if they don't overcopy, I'm not going to go hunting anywhere else for a readme... only to find that it barely lists the copyright information rather than anything actually useful to know. Leave the readme for the product in the files for that product. Not all of us use installers. Some of us prefer to do our own installations, thank you, mostly because of stupid things such as over-copying or throwing files all over the landscape where they are nver seen again. Leave them together and tidy. DON'T use .doc files as readmes. I'm not going to copy a .doc file to a zipdisk and walk it over to this balky Windows box... praying that it will cooperate and open Word... only to find nothing but copyright information. Use .txt files which can be read on any machine. DON'T make restrictions as to orientation of hips in poses. Sheesh. Isn't that what pose information is supposed to include? Positions in space? Orientations? This MAT stuff is a later sludgeheap occupying my Pose file... and too many people just include color variants in order to pad the numbers of their MATs... thinking that customers are too stupid to know the difference. Unless it is a REAL change in pattern, don't make it a space-clogging MAT file, and don't try to sell me 20 textures when it is only one and a few minutes with the hue slider in PhotoShop. DON'T clog up my Camera and Face folders assuming that my Pose folder is full. It isn't. :determined grin of enemy commander: Leave the MATs as Poses so that your consumer can rename them and place them elsewhere if needed... and go in and delete them if they are useless. Remember file name limitations in length and path syntax. I spend far too many of my precious minutes renaming stuff so it will work. Unless your work is very good or I need it desperately, I often just don't bother (a great way to lose a customer is to irritate them!). Please don't assume that DAZ is the only company which makes models with injectable morphs, and that everything has to accomodate these models and these morphs. They are biggest and best known, but there are other makers struggling with the process. There are also a number of consumers who aren't thrilled with it, either. It is quite possible that a couple of years from now, another scheme will be favored. NO EXECUTABLES!!!!! Carolly the Opinionated

Sorry I didn't realise that the MP only sold Poser stuff. I assumed it was toys for everyone and therefore standards would apply to all items.

I hear ya on all points and agree with a lot. Just to clarify, I wasn't meaning to limit the hip orientation, just that there is no reason to move the x and z positions, UNLESS you are posing it with something else. Besides the standard pose file will not include body positions or orientations, so that could be whatever you have. Note: if you move the hip in the x or Z direction, then spin the body around the y-axis, instead of spining, it now moves in a circle, and this could be a very large cirle. Most customers don't like a pose that moves the figure some distance. At least that is what I have been told. They just want to pose the figure as is. I think what you said was valid, I didn't know if you understood what was written. No need to worry, I will clarify it in the final draft.

Sorry, pierrecolat. It does sell more than Poser. This is just some discussion that has been going on and off and back on for some time. We just thought it time to compile some of what customers want into a document so that all merchants have the same standards. We thought asking customers in the Poser forum would be one way of finding out what they like and what they don't like in Poser packages. I think that it would be a big help to have something like this for newer merchants or prospective merchants. Hell, even some of the older merchants might learn something! Right now there are standards only to that it works, not necessarily what format or where things are put, etc. So, some of the merchants are trying to nail that down a bit, so that we all can benefit from it.

Thank you both, PabloS and BlueBeard for the information! :) As for the where to put stuff in both Geometries and textures, that's going to be somewhat subjective. That was my point. Some items defy categorization or it can get too finitesimal after awhile to keep things organized. Sometimes, I find that going by vendor is easier, other times, yes, it is hard to remember what is what. If it comes down to it, it'll have to be a standard folder hierarchy adhered to or it will still be a mess. Time for the Poser File Structure Committee! ;P

kuroyume0161, They got themselves a committee for that!?! Too bad. Nothing will get done then. :-) But got to agree that some standard would be helpful in the long run. Pablo Chairman, Anti-Committee League :-)

Do you see any problem with putting mat files for created for other merchant items, such as clothes, hair, etc. into the original creator pose folder. For example: If I made some textures for one of BatLab items. What about just putting the mat poses into his folder for that item. I just looked and his is called Bat-RMP. I try to organize my mats like this and I think it just makes sense for merchants to package them that way. BTW - I take the damned MAT off mine as soon as I download them. I can't find anything with 500 files starting with MAT.

A small suggestion; in readme file, just information about the product and contact info. I just brought a couple of products, and over half the text of the readme file was a mess of x, o, etc. I thought it was corrupted, but the merchant said it was a logo. Please don't confuse the purchaers!

Ok, here we go. MAT files: I'm with Carolly on this one. Do NOT put them in any folder except the Pose folder. I don't want to have to go hunting them down in the Camera, Hands, Face, lights, etc. folders. I want them where I can FIND them. So I can delete them, rename them, move them or whatever. It is beyond annoying not to be able to find them because they're in the camera folder or the hands folder or someplace stupid like that. Readme files: I don't have MS word or any other program that will read .doc files. Make them .txt files. Put the product name on them. Readme.doc will just get deleted. Readme.txt will get overwritten. MyProductReadme.txt will get filed in the appropriate location. Also, include your name, your contact info and what the heck the product is for - if it's a V3 product SAY SO. I can't tell you how many items I have that I can't use because I don't remember what they go to. This especially applies to clothing textures and hair textures. Geometry files: Put them in the Geometries folder. I don't care WHERE in the Geometries folder you put them, but I darn sure do NOT want them in the characters, hair or props folders. The Geometries folder is there for a reason people. Use of special characters (!~+ etc) in the folder names: Don't do it. One of the BEST ways to insure that I will NEVER buy from you again. I organize my libraries the way I want them organized, not the way YOU want them organized. (I'm still extremely pissed off at DAZ about this). Texture names: Please don't name your textures things like "black" "blue" etc. If nothing else add your intials or something so that when I run Poser or Correct Reference it doesn't wind up applying a brown horse texture to a brown eye. Do you know how many texture maps I have that are named "black.jpg"? 15. A horse texture, 4 dress textures, 3 hair textures, and two boot textures. Gimme a break here, would ya? Let's not even discuss how many blues, reds and greens there are. Sheesh, we're talking a LOT of editing here just to make sure things get applied where they're supposed to. Texture placement: Stick 'em in the textures folder. If they're clothing textures put them in textures:clothes:nameofproduct or something like that. Then the black dress textures won't get mixed up with the black horse textures PLUS I'll be able to apply them to the correct item when I export my poser scenes for rendering (pfft, yeah right, like I'm gonna render in Poser... Puhleeze) Kate the Konsumer

DAZ puts their readme files in the ReadMe's folder. It would be easier if everyone did that. Perhaps merchants should organize stuff by categories rather than merchant names? (Mike, Vicki, MilGirls, etc.) There's nothing more annoying than looking through 7GB of texture files, trying to find something. I'll know the name of a character, not who made it.

I prefer to put the readme file in the zip file all by itself so it stands out. When you open one of my zip files you'll see a Runtime folder and a readme file. If you can't figure that one out. You have no business using a computer in the first place. ;-) I also MUCH prefer to place the texture files in my Geometries folder. Anyone who uses Poser a lot will tell you that having to deal with the extra Textures folders is a total pain in the butt. -ScottA

takes notes

Here is me, the person who buys this stuff... I don't like having textures in any folder OTHER than my textures folder. I don't like having readme's in my textures folder. I don't like having readme's anywhere but a readme folder where I can FIND them. I don't like readmes that contain no info! I don't like readmes that are named readme.txt. I don't like products I have to unzip then copy into places where they should be. (i.e. xyzproductruntime....) I don't like Mat or Pose files in my Cameras folder. I don't like hardcoded bits in my files. I don't like products where I can't identify which figure they are for. I don't like additional object files that vanish into places unknown and which I then can never find again. (/objects/prodname !! How difficult is that?) I don't like morphs that vanish the same way (/morphs/prodname) I don't like blank thumbnails. I don't like P4 & P4PP/P5 files mixed in one folder I don't like V3/V2 (M2/M3) mixed in one folder. I absolutely positively DETEST ! & ++ etc naming of folders So there you have it. Make it easy for me to work with stuff. Granted, even if it's not done this way, if I like what I see, I will likely buy it no matter how it's organized. To be honest, I would even prefer textures to go into a PRODUCT folder, rather than a merchantname folder or just into the textures folder. That way I would know exactly where to look if I have to find something. But I won't like having to shift stuff around and think twice about it.

Quote - If you can't figure that one out. You have no business using a computer in the first place.

I hate to say it, ScottA, but that comment makes me want to slap you, and slap you HARD. If you sell something, you make it as EASY as possible for people to use and find stuff. Especially if you have to assume that people who buy it may not be as computer literate / proficient as you would like them to be. It has nothing whatsoever to do whether I can or can't "figure that out". I can find anything I bloody well want to find, and then some. I just CHOOSE not to want to go searching all over the place for textures that may be in a geometries folder where no one in their right mind would look when there is the OBVIOUS place called gasp TEXTURES!!

ScottA, you lost me on the last part... What would be the benefits of having textures in the geometries folder?!

I read all the stuff about organising the MAT files (and other poser files) and was wondering about a little thing.... Could it be possible to assign, at the beginning of a MAT file (not in the filename, but in the code), the product on which it should work. It could be then possible to create a little program (python or something else) to create a "dynamic" library, showing only the MAT files (or pose, or figures, ...) working for a selected figure. This would be a great time saving and you could find free stuff you installed and forgot somewere in you gigabyte library...

Some really great input, and I learned several things. Well the first thing to be changed from the list is the name Suggested Standards for Merchants by Customers! After I thought about it, it started by merchant complaints on stuff that they had bought. So, it was really the customer side of the merchant that started this, and we are continuing it on here. Sometime today I will work on a draft and repost it here formalizing your suggestions. But, keep them coming anyway. I will be checking back often.

I have another one... If MAT files start with MAT and POSE files start with POSE then we won't have to hunt so much. Oh yeah, I don't like poses and mat's mixed either. If I look for a MAT, I will scroll to MAT's, if I look for a POSE I will scroll to POSE Very very often I rip out the pose files and shove them into another folder and (if it lets me) rename a "XYZ MAT" folder to MAT for XYZ Oh yeah, if something has ISSUES with different versions of Poser, please say so in the readme. I know some stuff will not work in Poser 5, some will but it will come out differently. If it was never tested on P5 (or P4 for that matter) then please please say so. I remember a girl having real issues with Transpond's flowers. The tulips rendered with black smudges and what have you. For example: I've recently bought Versa Bench and - God help me - used the Firefly renderer. The result was.... lets just say I won't be doing THAT again. However, there was nothing (unless I didn't spot it) to say that it would result in bits bulging in all directions. (I am not kidding). In fact, I don't recall there being a mention of whether or not it would work with P5. Such info is vital. Really really vital. For the simple reason... if I were a beginner, I might not know that P4 renderer may do it because it's totally different to Firefly. But if the readme said "Not tested in P5" then at least I know it may not work. BTW this is in NO way meant to discourage anyone from getting Transpond's Versa Bench. It's an awesome piece and very versatile, and I'm not regretting the purchase at all. I just render it in the P4 renderer now that I'm aware of the Firefly thing.

The "bulging" is something P5 does to certain objects. Simply turn off "Smooth Polygons" for the offending object OR do it in Render Settings in general. It should have been mentioned in the Readme, yes, but it doesn't REALLY mean it won't work in FireFly (or P5). As long as you turn off the Smoothing it'll work fine.

i think this thread is a great idea,lots of great suggestions here and i agree with all of them,also a lot of the suggestions are not only useful for mercheants for their packages but also for help in reorganizing the dreaded runtime folder :) i have learned a few tricks to help me tidy mine up a lot..lol...thanks peeps,i can't think of anything that hasn't already been suggested,but wanted to say what a great idea this thread is :)

I know I see a lot of freebies that don't follow any of the above. We don't require any of these for freebies, but it would be nice if people who are comfortable with Poser try to follow these as well. When I help with approving the freebies, I'll sometimes point out to people ways to make their freebies easier to use. I make sure to stress that it's not required, I've found that the people who are generous enough to donate free stuff usually appreciate learning the subtle nuances to make their files more usable as well. Also, if anyone needs help with how to zip up files for extraction to the proper folders: http://www.fallencity.net/tut-posi/p-packaging.php Great thread, BB!

Ernyoka1 - thank you for the tip! I'll try that. :) Silke (Who wants a camera right NOW because the light outside is incredible and there is a tree in the full BLAZE of red lit just right and........ I HAVE NO CAMERA AT WORK cries and stares at the tree some more....)

I thought of a couple of things after reading everyone's responses. 1. Bumpmaps - there should be a standard on this. I have several packages that I love dearly, but they include bumpmaps, and the bumpmaps either need to be converted, or have the wrong file in them. It takes my system forever even though I tell it to not look for files it can't find. I wonder if the default file should be without bumpmaps and if the merchant wants it, a second to apply bumpmaps. Most often I don't use them, because the camera is not close enough for the viewer to tell the difference. Just a thought, I thought I would post it hear and see what kind of reaction I get! 2. is that there are 2 thoughts that are opposite in this thread. This involves the MAT Pose files. A lot of sites require that these start with MAT. But here they don't and quite frankly they can get confusing. Now one person has said they want this, but several other have said that they wish is would start with the product name. In either case, it still needs to have MAT in it, so that one knows what it is. Any further thoughts on this?

Another thought is postwork in promo images in the store. I don't think these should be postwork, other than composition. They can point to their gallery for examples of postwork images. UNLESS you are selling a postwork product, i.e. hair painting kit, or something like that. In general, I would think that most customers do not want to see postwork in promo images, they would much rather see what they are getting straight out of the box, so to speak. PS, I think freebie are where future merchants come from, so it would be good to encourage them to try some of these things in their freebie stuff. So, when this is finished, we might post a link to it on the freestuff submittal page or something like that! What do you think Crescent?

Oh yes, postwork! I too think there should be no postwork on promo pictures, except for compositing, and even in those cases it should be noted on the picture. Bumpmaps are tricky, since there's no way a pro pack /P5 user can generate .bum files. Well yes I think _dodger once described a way, but it was something that included a LOT of hassle. On the other hand, I guess a jpg bumpmap gives a p4 user a lot of hassle converting them, MAT poses won't work if there's a jpg bump in them, will they? I have no solution to that one. Another aspect is that .bum's are HUGE compared to a jpg. Speaking of the PPP/P4 difference.. . In MAT poses there is something with 2 0's that makes the file work/not work in Poser 4... Or?

Add two more items: Please say what platforms it's been tested on. Mac/Win and P4/P5. There are some oddities in some things when running under P5 or Mac that don't show on the P4/Win platform. I love some products that just don't render in Firefly (locks it up), I'll still get them, but the first time I render and I have to kill P5 and restart really gets me. Also, please do include a .png file. Not optional. I delete .rsr files now, since P5 uses .png files. Try to make your product as broad based for the various platforms as possible.

Re: .png vs .rsr There's a reason that the .rsr is included and the .png is not. ALL versions of Poser (4/PPP/5) will read the .rsr file. Pro Pack and P5 will convert them to .png. Poser 4 will not read .png and a LOT of folks are still using P4 only. The ones that make me nuts are those that don't include .rsr OR .png, just the object (.cr2,pp2, etc). I hate looking at that shruggy guy cuz it means I have to load the product and resave it to get an image. I shouldn't have to do that. Kate

Thanks Kate! That was the reason that I originally wrote it that way. If you have PP or P5, it will generate the png from the RSR, but not vice versa! It seems that the majority of the customers have P4, and that was the reason for this. I was going to add, later in the document about PP and P5 products, state png, but no RSR, and version number of 4.2 and/or 5 respectively.

Now that's my problem - testing on P4 as compared to PP and P5. I have PP and P5. Is there any way to install P4 again, in a separate location without PP and not have it interfere with the PP version? As for Mac testing, wish that I still had my G4. ;0) Still, the investment wouldn't be worth it unless I'm selling like a hundred of each of my products. The most inexpensive Mac that'll run both P4 and P5 well is probably $2000 or more.

Okay, here's something that's more of a general suggestion. My Pose list is huge, and I use P4. It takes me about 30 seconds just to scroll to the bottom of it (yes, I know, get PBooost. I've tried it, and I can't use it cuz win98 always locks the stupid folders). Now, I'm aware that there are limitations to the number of folders Poser can address (something like 250), so I believe that merchants should definitely keep this in mind when deciding whether to create a new folder or not. If it can be avoided, do it. For example, if you created a mat for another product, put the mat file with the product, don't create a new one. And here's one more customer preference: I really do love the zips that auto install the product, if I unzip it to the poser directory. However, I rarely do this because of the inevitable readme.txt that will overwrite whatever is sitting in my Poser directory. Instead, I just unzip the product to it's own directory, then cut and paste the runtime directory to the Poser 4 directory. That way I have a product-named directory with it's attendant readme. I wouldn't mind changing this habit if merchants adopted a readme location standard, but I'm not holding my breath.

The eMac is $799, throw in an additional $99 for memory and you should be fine. I run Poser 5 on a Mac slower than that.

ernyoka asked, 'Speaking of the PPP/P4 difference.. . In MAT poses there is something with 2 0's that makes the file work/not work in Poser 4... ' Yes, there is, and it's important. It's not a P4/PP4 issue, but a P4/P5 issue. Listen up and I'll explain. If you make MAT files by hacking the text file or copying the materials from a cr2 (or from other people's MATs), you . This also has thew advantarun the risk of not getting the 'double zero' line in your MAT. When you add a texture to an object WITHIN Poser and save it to the library, Poser automatically adds this double zero line after the texture path. textureMap ":runtime:textures:room creator:macpaper01.jpg" 0 0 If you just copy the material blocks from the cr2 into a text editor, then add the texture path manually, you won't have the double zero line (unless you add it yourself). It's not in the cr2 if there isn't a texture already applied. This means that the MAT file will NOT work in Poser 5. A full material block should look like this. material back_wall { KdColor 1 1 1 1 KaColor 0 0 0 1 KsColor 0 0 0 1 TextureColor 1 1 1 1 NsExponent 100 tMin 0 tMax 0 tExpo 0 bumpStrength 1 ksIgnoreTexture 0 reflectThruLights 1 reflectThruKd 0 textureMap ":runtime:textures:room creator:macpaper01.jpg" 0 0 bumpMap NO_MAP reflectionMap NO_MAP transparencyMap NO_MAP ReflectionColor 1 1 1 1 reflectionStrength 1 } So, the answer is - DON'T copy materials from cr2s to make MATs, unless you know what you're doing. Kate said, 'Texture names: Please don't name your textures things like "black" "blue" etc. If nothing else add your intials or something' Exactly. Look at the material block above. It's from one of my products. There are 3 things to consider. 1. The file path - NOT "C:/CuriousLabs/Poser/Runtime/etc, but ":runtime:textures:etc". A lot of people don't have poser on their C drive or in the Curious Labs folder. 2. File path length - Here's a quote from the DAZ brokering advice. 'If the texture paths are more than 60 characters long, including the extension, Macintosh will cut them off. Texture maps have the biggest problem with this. You can use a Global Find/Replace to eliminate part of the path to shorten it if necessary. Find "Runtime:Textures:" and replace with nothing' 3. Texture name - I add the prefix 'mac' (for maclean) to all my texture names. So, instead of 'wood01.jpg' it's 'macwood.jpg'. scottA, Textures in Geometries??? Oh, right! So THAT'S why Textures is called Textures and Geometries is called Geometries. Silly me! mac