Update: So after trying many things, i seemed to have found a temp fix. At least where two genesis 1's are concerned. Before, if i imported both into a scene, the second one breaks when i tried to pose it. However, now, im importing both into a scene, then saving it out as a pz3. Then re-open the pz3 and both work fine. Does anyone have any clue why that would happen? Or maybe this info will point to a better solution, which im hoping for.

What could suddenly cause my genesis1/2 to behave that way? The first genesis i imported poses fine, no problems. It's the second one i import that does that. The only things i recall recently that i did was reinstall my genesis runtime, upgrade my ds-on and genesis essentials to the latest one, and install a few new scenes. I was thinking maybe it's because i have SR3.1 instead of 3.2, but this didnt happen before, so i dont think its that.

If im upgrading my ds-on and genesis essentials from an earlier version, am i able to still use my old PZ3's and saved figures in the Figures library?

Well i downgraded back to the older ds-on, and my second genesis figure still breaks on pose. I also installed the older starter essentials/poser cf. This might of started happening after i reinstalled poser, where i saved out the genesis runtime. Does anyone have any other idea whats going on? I didnt have this problem before

Yeah i updated the base figures with starter essentials and poser cf's that come with them. Every time i import a second genesis or genesis 2 into the scene, the body breaks apart when posing. Is there any other suggestions?

Also, how do i uninstall the current version of ds-on if i didnt have an uninstaller?

hborre: The poses are for Freak 5. In the past, i've used a few M4 poses, and those usually worked on my other Genesis characters, though sometimes the feet break apart. But those i fixed by restoring the elements on them. But on the rhino, even after restoring elements, it breaks apart when i pose it. Also happens if i load a saved Genesis pose.  

RHaseltine: It seems kinda random. It doesn't happen a lot luckily, but when it does, it gets pretty annoying.

JimTS: Yeah, i tried a blur radius of 1 (it doesn't let me go below that for some reason), and a 2048 map, and the render time was about 5 mins. With raytracing, the render time is 1 hour! It looks like a higher shadow map does give better and crispier shadow outlines.

Latexluv: I tried this before on the horde werewolf figure, but for some reason turning off the light emitter on all the hair wasn't working. I'm not sure why it didn't, since it seems to work on other figures hair. It comes with Horde "Body hair A" and Horde "Mane hair A", and the body hair has like 30 material zones. Do i need to turn off light emitter for all 30 material zones for it to work?

winvdb: Thanks! I'll try that out.

MistyLauraPrincess: Yeah, i checked the task manager though, and poser was only using 900 mb of memory, which is well below the limits. And if it was a memory issue, wouldn't it fail on the first try?

luckybears: Nope, nothing was done to the file.

Quote -      What version of Poser do you have?  If it is P8/Pro2010 or newer, it will by default put the library in shared documents.  If it is P7/PoserPro or earlier, then you may need to sacrifice a level of security and install P7 outside of program files.

I'm using Poser Pro 2012 SR3.1. I'm still 50/50 on this. A lot of artists told me they put their download runtime in program files and have no problems with UAC turned off. That would be most convenient for me as well. So not sure which i will do when i get around to reinstalling poser and windows 7.

Another thing is, i'm going to backup my download/runtime (not the default runtime that comes with poser and has alyson), the runtime where i put all my purchased things in, like M4, V4, etc. Then move it to another hd. And when i format, and reinstall poser, move back that runtime. Do i need to reinitialize all the files that were exp, like M4?

ockham: Some scripts though seem to require you place them into program files, like the ds-on and m4 vein displacement maps converter.

I was talking to another artist, and he recommended to just turn off UAC, which i would probably do anyways since it's annoying.

If i have my download runtime in program files now on xp, and i move it to my_documents after my install of windows 7, will everything still work? Like if i saved a model to the figures library, or if i open a pz3 file i saved on xp, will those still work?

Quote - You can install the scripts to program files, but Vista and Win7's User Account Control will challenge you for permission to do so.  Click to continue.

However, when a program -such as Poser's library- attempts to write to program files, UAC blocks that and sends the files to "compatibility files", aka "virtual store".

So what exactly should i do with my downloads/runtime and scripts to get it working in windows 7 like it works on xp?

How would the scripts work though if win 7 doesn't let you install into program files, since the scripts have to be in there?

Doesn't windows 7 prevent you from installing in the program files though? That's what i heard.

Quote - lose the morph, dial  or lose the dial settings ?   Have you checked the pz3 file to see if its losing it on save or load ?

It loses the head morph. The dials are still there, but you can't move them until you reinject the morph.

I encountered this problem on the daz millenium subdragon's wings before. It happens in areas that are very thin. The 2 fixes for it that worked were:

1. In your render settings, check "remove backfacing polys"

2. Go to the advanced material room, and select the material zone of the area you're having the artifacts. Add a simple color node to the displacement for those particular material zones, and set it to around .01. You might have to mess with that number a bit to get the results you want.

Not sure if your problem is the same, but it might be worth a shot to try these things. If it's for personal use, the first trick would be best, but if you're planning on selling this, you definitely want to find the cause of the issue or use #2. Hope it fixes your problems!

Great ideas! Thanks for the tips guys! This forum never fails me =)

Will be using that technique on my next render.