Looks like you & poser have a love/hate relationship. :0)

:0)

I like the scene but I also get that 'something not right' niggle. I don't think the set is too small, you can see the woman's shadow on a pillar and that gives an idea of the scale. After looking at this for a while I noticed that the background sky gets brighter as you go down- implying the sun is setting/rising, but the shadows imply the sun is behind us. Maybe, subconciously, that's what was bugging me.

Well I'm convinced mine was not a heating problem because it could occur shortly after switching a machine on. I hear what you are all saying, all I'm saying is there is more than one cause for this symptom.

Ajax is correct, but you may have a problem deciphering it, so I'm just going to try and explain it a bit more clearly. I could be insulting Ajax here and patronising pookah69, but here goes... A morph works by applying the differences between itself and the original. If your morph is in a different location to the original, then as you apply the morph, the original will move from the position it's in to the position you placed the morph. So moving the morph to the same location as the original will stop the movement. I suspect, however, that that is easier said than done- then again, maybe not! :0) Good luck!

He's great! His left side looks best. From his right, he looks a bit weird. I think my subconcious tries to create an eye from the bit just above the beak- maybe if you took that out he'd look better. Also, I think his beak should look a bit sharper and slightly more curved. I'd love to see this guy perched on the shoulder of a Long John Silver type pirate.

Best way to start is to follow, or at least read, the tutorial in the manual/handbook.

Nice try ernyoka1, but that doesn't explain why defragging the machine fixed it as well or why the problem would switch to a different application later. Sarakat, before you spend money on a new fan and start pulling apart your laptop, try scandisk and see if it fixes any errors and defrag your machine. Then see if the problem goes away. If it does, it's almost definately hard disk related- if not, then it may be overheating.

That doesn't explain why my PC stopped doing it when I got a new hard disk.

I have a suspicion that Poser (4 & 5) does not reset everything when you load a new file. So I normally shut down poser and restart it before loading a new scene. In fact, now I mention it, I wonder if that's why I don't seem to get as many problems as some other users in this forum.

I used to get this problem a lot with Windows 98 but not with Poser. It would be consistent with a certain application till I scan disked & defragged my machine. Then it would be fine for ages till it started happening with another application. At one point it was occuring whenever I shut down another PC on my small network. Quite weird to shut down one machine and have another one turn itself off as well. Later, the hard disk on that machine became totally corrupted and I had to buy a new one. So it could be the problem is caused by hard disk failures. So scan disk & defrag, then wait to see which application gets it next. Oh- and backup your machine, soon!

Did you uninstall Poser 5 beore you re-installed it? If not, un-install Poser 5, reboot, re-install, apply the SR3 patches and kick her up. I'm assuming you've checked it works for a new scene and you are not loaded a corrupt pz3 file.

All the web sites I visit have changed recently. Change, change, change- it's becoming a rut! :0)

P.S. If you do want to try editing the pz3 file, there is a very brief description of the layout in the Poser 5 handbook in the appendix which applies to all versions, I believe, and can be downloaded from the Curious Labs website.

MSWORD is only trying to read the file and present it contents to you in a text format. Poser is trying to read the contents and process the content so that it is a three dimensional image. While I agree that Poser shouldn't stop responding, it's more difficult for the Poser application to handle a corrupt file than the MSWORD application. The only way I know out of this is to try and edit the pz3 file back to a valid format. How easy this is will depend on... How easy you find it to understand the pz3 format. How corrupt the file is. It's probably easier to recreate the scene, you'll find that if you spent days creating a scene, you can normally recreate it in a few hours as you know where you are going. A way to avoid this situation is to use the save as function. I use this method... V < 2 digit version number> For example... Knight V01 Started.pz3 Knight V02 Added castle background.pz3 Knight V03 Adjusted pose.pz3 etc, etc. Make sure you always save the file in the same directory, not as easy as it sounds as Poser will point you to the last directory you accessed. If you get a corrupted file, just go back to the previous version. Better still, if you mess something up you can go back a version and either continue from that version or copy the pose/material/whatever into the current version.