I just found a tutorial, and made my first MAT pose. However, I'm looking through it, and I see that the area where you tell it where to find the texture file, in my case 'C:Program FilesPoser 4RuntimeTexturesKagatoGategateclean.jpg' is very precise. There must be a way to make it work for everyone....What if someone has it installed in a different directory?

Use :Runtime:Textures:Kagato:Gate:gateclean.jpg

Thanks a ton :)

Search freestuff for scourge and get his MAT Pose Edit. You can create MAT pose and more easily if you don't want to do it by hand.

You can also edit the texture paths to use simply textureMap ":texturename.jpg" That's all a Mat or cr2/pp2 file needs to find a texture as long as the texture is in Rutimetextures someplace - Poser 4 starts looking in Runtime, and only beeps you with an error if if can't find it, or if you tell it a specific folder and the texture's not there. To make them useable in pro-pack, make the various image map references read like this: textureMap ":texturename.jpg" 0 0 with the "0 0" entries in the appropriate format in the Mat. That includes after bumpMap, transparencyMap and reflectionMap references... we had a heck of a time diagnosing why a PPP user at RDNA wasn't able to get my skin reflect and subdividing reflect map Mats to work, and it turned out that I'd left off the "0 0" entries on the reflectMap lines, and PPP wasn't reading them. shrug No offense to scourge or anyone else, but I find it just as fast to design Mat/Mor poses and delta injection poses in wordpad as in any other app.

To make them more Mac compatible, remove the Runtime and Textures and just use :Kagato:Gate:gateclean.jpg This gives you less characters (REAL good for Mac users) in the path and Poser automatcally searches the texture directory anyway.

Chuckle - some folks design websites using notepad as well but I've always been an IDE kinda guy - maybe because I can't type ('cept with two fingers :-)

"Search and replace" - don't have to typo any. ;] And ifn yas ever read many of my posts, you'll note I can't typo either. ;]

The problem with MAT poses that just do :Texturename.jpg is that it seems take Poser forever to search through my gigabytes of textures to find it.

That's why I use the folder name as well as the texture name :)

Yeah, Xena, your method is the best I think.

I usually go in and edit everyone's MAT files to read ":texturename.jpg" since I organize my textures according to what model they go on instead of who made them. (ie: Vicky textures go in "runtime/textures/Vicky" and so forth) Makes it much easier for me to actually find them that way. Kate

I theek what we're demonstrating here best to the poor guy is... ya just kaint make everone happy. ;]

Now if you could just get it so that MAT Pose Creator starts the path at ":texturename.jpg" so I don't have to edit out all the ":runtime:textures:creatornamefolder:modelsubfolder:" garbage by hand. sigh Other than that, it's a great program, John, and I use it a LOT.

John; ) LOL! You should preface that with "Shameless Self Promotion" :-) a crime I am most certainly guilty of. Unfortunately you forgot mention it's PC only. For the Mac guys there's a neat little program called "MATconverter" by Jim White. Not as sophisticated as John's but does the job. It's in Freestuff/Poser/Utilities. Good luck, and a good text editor never hurt Jon

Just an aside note: Changing the texture path to remove ":runtime:textures:etc:etc" will make the MAT file take longer to load. By referencing only the texture name, you are forcing Poser to look in the Textures root directory first, then every subdirectory until it finds the file it's looking for. If you have more than one file with the same name, this can sometimes have disastrous results. It will also be considered a 'bad reference' by other third-party utilities, such as PBooost!, which will be unable to perform its main function if a MAT file with a bed reference is loaded. As much as I understand and agree with wanting to save space in Poser files, this isn't the best place to do it. If you have a large texture directory, it can add minutes to the time it takes for a MAT file to work...and the whole idea of MAT files is to save time, right? I go through and check any item I install with PBooost's Deep File Editor now, and correct any bad references to include the full ":runtime:textures:" pathing. The speed increase in MAT loading (and even other .xx2 files) has been dramatic... Just my .02... CT

"MAT file with a BAD reference"...sheesh, can we get an EDIT feature yet, please?