This has been happening to me for a while now, but I finally caught poser at it red-handed. I was doing test renders when suddenly poser corrupted one of the textures, like right in front of my nose! It does it from time to time, but it always seemed to be when my back was turned. You can see the result. I checked the tex in photoshop and sure enough, it was corrupted. Anyway, I have everything triple backed-up on my D drive, so I closed poser, dragged a copy of the tex into poser, started it up again and carried on. I've been using poser for years now and this is a new prank in it's repertoire. What I want to know is, does it happen to anyone else? Maybe I should re-install.... for the 476th time... mac

That is so weird. I'll be interested to read what in Poser would do that to a file. Is this a Poser 4 issue or is it happening in Poser 5??? It sure is something to watch for if someone is wondering what happened to their textures. Good grief, what next? Love your fire, though.

hey dialyn, Yep, I thought it was pretty bad. If poser can destroy my textures without hardly flexing it's muscles, what would it do if I got on the wrong side of it. 'Hell hath no fury like a scorned software' and all that stuff. LOL. Anyway, I'm pretty sure this is some weird manifestation that's peculiar to me. I have a list of 'features' that don't seem to affect other people. Poser 4.03 straight off the CL cd with no patches at all. mac PS The fire's still in a transitional stage. PPS Now you know why I have triple back-up!

Probably no one has realized that Poser might be the cause of the problem. One thing I've learned about computers...rarely is a problem isolated to one user, but often only one user admits they have the problem. Try getting that into a fortune cookie. :)

I have had that happen to me but somewhere I read that if you get too much in your poser libraries that it will start doing strange things. So Try not to have too much loaded in poser at one time lol.

I've only experienced the fairly common garbaged rsr geometry files, not textures. The solution to the former is to make all your rsr files read-only. Perhaps the same might be a good idea for texture files as well for anyone experiencing this bit of mischief.

I've never had a texture corrupted on me, but I have had Poser suddenly decide that it was going to change the UV map on something I had remapped. One minute it's working fine, the next, the mapping gets all messed up. Very weird. Maybe Poser suffers from SAD? Holiday Blues perhaps?

"I've never had a texture corrupted on me, but I have had Poser suddenly decide that it was going to change the UV map on something I had remapped. One minute it's working fine, the next, the mapping gets all messed up. Very weird." Yup, had that happen to me, too. I remapped Mike 2's bodysuit, using Doug Sturk's remap. Worked fine for one render, then reverted to the original mapping. So I redid the thing and write protected it. Never had a texture get corrupted, though.

'I read that if you get too much in your poser libraries that it will start doing strange things' I don't have a huge poser library. What I do is customize the entire poser setup for each project I'm working on. My projects usually last about 3 months, so it makes sense. I ditch everything from the libraries except what I need to work. My current Runtime size is about 400Mb. Not large by most standards. I think it's just me. mac

That is strange. Usually, the rsr corruption, in my experience, results from Poser crashing. That make sense - Poser has the file open and doesn't get to close it properly. Corruption (of the file itself) in the middle of a session without a crash seems to suggest that Poser is writing the file back to disk - which makes no (non-Poser at least) sense. At any rate, making them read-only should solve the problem. If you open a command prompt and type: attrib +R C:Program....RuntimeTextures*.jpg /S substituting your Poser location and the filetype you want to change, that should get all the specified files in all subdirectories of textures. Of course, you'll have to do it as you add new images and also remember to clear the read-only attribute if you want to edit and resave using the same filename. A hassle but better than losing an important texture or having to hunt for a backup perhaps.

Well, the problem is that when I'm working on a project, I'm constantly tweaking the textures and testing them in poser. In fact, that's exactly what I was doing when this happened. So read-only isn't really an option for me. Hence the triple back-up. I'm fairly used to the rsr corruption when poser crashes. I just delete the culprit and carry on. But the really weird thing about this is that it happened when poser was open and there was no crash. This was just another render, after having done several, and it just went mad. I'll be finished this project in a week or so and I think I'll just re-install. No biggie. I'm so used to it now. All I do is re-install, delete the entire runtime, then drag my current project files from the other drive, complete with prefs, custom .ini file, etc. mac

"In fact, that's exactly what I was doing when this happened." If you're saying that you were tweaking in your bitmap editor while Poser still had the texture "loaded," perhaps there lies the cause of the problem. I do the same thing on occasion and haven't experienced the problem but I can certainly see how there might be a potential conflict. In fact, it would seem more logical that PhotoShop or whatever, in the process of saving your tweaks to a file that Poser has an open handle to, may be doing the corruption as opposed to Poser which should have no reason to be doing a file save or write operation. In summary, ladies and gentlemen of the jury, I submit that there is reasonable doubt as to whether the defendant, Ms. Poser, comitted this crime. If the bitmap doesn't fit, you cannot convict.

Sorry. I should explain how I tweak and test. What I normally do is open poser and photoshop together and apply my 1st texture in poser. I do a few renders, then go to photoshop and tweak the tex. I then save it under a NEW name and apply it in poser, do more tests, and so on, until I get it right. So the tex that's loaded at the time of rendering is just another tex as far as poser is concerned. mac