Sun, Feb 2, 2:11 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 01 9:10 pm)



Subject: Morph Poser 8 bug


Trollzinho ( ) posted Wed, 30 December 2009 at 2:59 PM · edited Sun, 02 February 2025 at 2:04 AM

This has been haunting me for a week already and I thought it was my mistake, but I found it was actually a Poser bug.

Heres how to cause it:

  1. Open Poser 8. The starting figure will be Andy. Thats fine. Keep it there. We'll cause the bug with one of SM's figures.

  2. Click the Morphing Tool, then click the tab Create. The settings I used to create the bug were: Check [X] Pull, [X] Surface, [X] Average Normals, [X] Accumulate, [X] Stroke, [X] Display Brush, [X] Work with current morphs. Uncheck all the rest. Radius: 0.0150. Magnitude: 0.2. Most likely it happens with thousands of different settings. But thats what I used, which are the default settings (at least on my Poser).

3) Now, brush up a morph onto Andy. Make sure you spam different body parts. Spam from right hand to left hand for example, all the way thru the arms and chest. Don't need to be big morphs. Just enough for you to see them.

  1. Click "Save a copy as..." on the Morphing Tool window. Pick a name. Mor01 for example. After you save it, hit Zero Morph on the Morphing Tool window. Now close the Morphing Tool window.

  2. Now, on top of the main dials where it shows the currently selected object, click the little downwards arrow and select Body. Now on the dials, under "Other", set Mor01 to 1 to test your morph. Verify that it works fine. Then reset it to 0.

6) Save your scene, and open its saved file again. No need to restart Poser.

  1. Now go back to step 2 on this list and brush up another morph onto your loaded Andy. Spam from hand to hand again. Then save it as Mor02 this time.

  2. When you close your Morphing Tool and select Body again on the dials, go once more under "Other" but now set Mor02 to 1. See if your morph bugs out. If it bugs out, try to close Poser. See if it will crash when you close it.


RobynsVeil ( ) posted Wed, 30 December 2009 at 4:14 PM

Hope you posted this exactly as you did here to the SM bug reporting thingie... you documented what you did really well!

Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2

Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand] 

Metaphor of Chooks


Trollzinho ( ) posted Wed, 30 December 2009 at 4:16 PM

Well, I haven't send this to SM yet, because I still wanna get confirmation that its indeed a bug and not something I'm doing wrong or thats happening only on my PC.

BTW: I have SP2.1 installed.


Trollzinho ( ) posted Wed, 30 December 2009 at 6:27 PM

Some more info on this:

a) The bug will only happen if you create a new morph to a figure that already had a morph when you loaded the scene. If its a new scene, a new figure, or a figure with no prior morphs in a loaded scene, the bug won't happen.

b) The bug will never happen if you morph different body parts. But if your new morph touches a body part that has been previously morphed, the bug will happen.

c) You also can tell if the bug happened when you try to either load a new scene, start a new scene (File/New), or close Poser. Poser will crash if the bug happened and you tried to do either one of those.

d) The bug happens differently if you use the PMD file (Edit/General Preferences/Misc/Use external binary morph targets). Poser won't crash, and you won't get polygons flying all over your scene, but you'll get incorrect morphs.


Zaycrow ( ) posted Thu, 31 December 2009 at 6:24 AM

Attached Link: Video

I can confirm A and B. Reported this some time ago. But nothing has been done about this. And I think it's because the lack of bug reports on this subject. So do yourself and the rest of us a favour and report this! I had the poly explosion bug. But it turned out to be corrupt preference files I had. Just 1 crash can do this, so I keep a backup of fresh installed preferences files if that happens again - which it does sometimes - to copy over the corrupt files. Also notice that corrupt preference files can also corrupt your saved files with morphs. I had to delete alot of them as they would explode if I used the morphing tool on the figures again. SM confirmed I had corrupt saved files I was providing them. But I still can provoke a crash. I have a link to 1 video of many I sent to SM while we where trying to figure out what was going on.



Trollzinho ( ) posted Thu, 31 December 2009 at 8:34 AM

Where are those Poser preference files at?


Zaycrow ( ) posted Thu, 31 December 2009 at 9:21 AM

From SM:

"If Poser crashes or starts behaving oddly for no apparent reason, it may be that its preference files have been damaged or corrupted. Removing the damaged files will restore Poser to its factory default settings and may fix problems that won't go away otherwise. This won't remove any additional figures, props or poses that you might have installed.

To remove preferences, QUIT OUT OF POSER FIRST! and delete the prefs files. The specific files to delete are the Poser Prefs, LibraryPrefs.xml and Poser UI Prefsxxxxx.xml files. Poser will rebuild these files the next time you start the program.

NOTE: If you use Multiple Runtimes
Copy your LibraryPref.xml to your Desktop before deleting. You can then place it back after testing to see if the issue is resolved. If the figure required to check is in an External Runtime, you will need to add that one Runtime back within the Poser application to see if the problem is resolved this way.

COMPUTER > local disk C > USERS > your user account name > APPDATA > ROAMING > POSER folder"



Trollzinho ( ) posted Thu, 31 December 2009 at 9:29 AM

I did that, but it didn't solve the bug...
However, one thing that solves the issue is when I use my morph delete script to delete a morph called Custom_Morph which Poser creates when you use the morphing tool. So looks like that morph is the cause of all issues.


Zaycrow ( ) posted Thu, 31 December 2009 at 10:01 AM

I agree that the morphing tool does something so P8 crashes - for some. But when I was having the problem I exported the morphs to OBJ and now I use it all the time for FBMs. That way I can morph on an already morphed figure from an OBJ file which seem to work for me.



Trollzinho ( ) posted Thu, 31 December 2009 at 10:05 AM

But in order to export your morph to OBJ so you can import it back as a FBM, your figure has to be in its zero position and all other morphs (besides the one you want to export) has to be zeroed, right? Or is there a way you can do this with a posed figure?


Zaycrow ( ) posted Fri, 01 January 2010 at 11:42 AM

I haven't tryed it with a posed figure.



Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.