steve-law opened this issue on Dec 11, 2001 ยท 12 posts
steve-law posted Tue, 11 December 2001 at 3:51 PM
Ghostofmacbeth posted Tue, 11 December 2001 at 3:56 PM
Normally that happens whn you have two mike figures in the scene at the same time but I have had it happen once before. I was out of memory. Don't know what kind of computer you have or if you had other things open but try closing other applications and then opening it.
steve-law posted Tue, 11 December 2001 at 4:08 PM
I did a reboot and its back (phew!) I think it may well have been a memory thing. Thank you anyway.
Ghostofmacbeth posted Tue, 11 December 2001 at 4:32 PM
Okay and glad it is back
PabloS posted Tue, 11 December 2001 at 8:12 PM
Whew! That was scary.
tritorella posted Wed, 12 December 2001 at 4:55 AM
I had exactly the same thing happen when I set up a scene with too little memory allocated to Poser - even allocating more memory didn't fix it, I had to delete and reimport the figure. Wasn't aware it was linked to how many 'mikes' you had, but I had three in the one pic. scary, isn't it? T
egaeus posted Wed, 12 December 2001 at 8:09 AM
I think it's linked to memory and not the Mike figure. I've had it happen several times, didn't matter what the figure was, and it was always after I had been using Poser for a long time without shutting it down, or had many characters, textures, bump maps in a scene. It used to freak me out, but i imagine if you just double-click on the head and set it to visible, it would solve it. Mike
ronknights posted Wed, 12 December 2001 at 8:10 AM
Sometimes that will happen when you doubleclick on an image, rather than single-clicking and telling Poser to add the figure to the scene. By double-clicking, you could in essence, delete the body that the armor was supposed to go on.
praxis22 posted Wed, 12 December 2001 at 11:22 AM
Hi, I fell like that all the time, must be the "pocket coffee" :) later jb
steve-law posted Thu, 13 December 2001 at 10:36 AM
Mike, the head was set to visible. There was no way to "fix" it during that session. Luckily a reboot fixed it. I did have a lot of other stuff running at the same time (other progs) so that was likely the cause.
Starlok posted Mon, 17 December 2001 at 10:02 PM
I had a similar problem when loading (certain) multiple figures which turned out to be caused by something called "crosstalk" between Cr2's. There was a thread on it sometime back. While rebooting DOES work as a temporary fix, it's very depressing to work hard on a scene, load in that final figure, and be missing a head (or in my case, the hip/abdomen) Do a search on "crosstalk" and you'll find a solution for "just in case" it happens again... Starlok
ronknights posted Mon, 17 December 2001 at 10:46 PM
My best advice is to save your work often, as a pz3 file. I've done some complicated work, and each time I made a signficant change, I saved a new version of the file: picture1, picture2, etc. That way if I couldn't proceed one way at least I hadn't lost the work I'd already done. More than once I was able to go back to the last good version, and take another approach.