Quote - shvrdavid: Thank god you found this thread, tell me.... Do you mean you leave the setup room and go back in to it again, without doing anything else in between?

When I rig a character from inside Poser, I leave the setup room after each bone I name and set the grouping up to see if it works, and to see if there is a parent/child problem.

If it does not work, I just delete the bone, leave the setup room and come back, then make a new bone. You will get a warning about ungrouped polygons until it is all set up. I have tried to find what gets lost in the cr2, and have discovered that it is not always the same error in the cr2 (depends on the bones parent, etc), so deleting the bone and redoing it is faster than trying to find the error.

I don't use the standard joint zones anymore, so I am not sure what to tell you there. All I have been doing is weight mapping since 2012 came out. Editing joint centers from the parameters tab with the offsets should be avoided if at all possible as well, more on conforming endpoints in a bit...

I just start by setting up the deformer for the main map, then add a weight map. Rough the map in then set the deformer for the bulge maps and rough them in.

There really is not much need to set up a traditional zone just to delete it later.

One thing that I would strongly recommend, is doing numbered file saves and not overwriting your previous saves. If you notice that something has gone wrong, reboot the computer and load a previous version. If you run into a file that just does not save right at all, check to see of the cr2 has conforming endpoints in it. There  should not be any in a character (non conforming character). Animated joint centers seem to make them appear more than if you do not use them, same goes for ERC'd bulge maps. Using the joint offsets in the parameter tab can be hit and miss as well. If there are conforming endpoints in a character, you can plan on things going downhill from there. They mess with the joint centers/maps/etc, and eventually you will get a corrupt save that puts Poser into a endless loop of "Not a valid Poser file"

Intermittantly Poser SR2 just crashes on me when entering the setup room as well. I am not 100% sure why, but it dumps the same error every time it does it. Windows recovers from it, but it takes it a bit to get the memory back when it does it. If you are getting this, you may have to reboot depepnding on how memory recovery is set up on your machine. It is not setup to fully recover by default in Windows.

If you are curious, this is the event log on it.

Quote - Faulting application name: PoserPro.exe, version: 9.0.2.21214, time stamp: 0x4f82b53a
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x948
Faulting application start time: 0x01cd1acea520ce9b
Faulting application path: D:Program Files PoserSmith MicroPoser Pro 2012PoserPro.exe
Faulting module path: C:WindowsSYSTEM32ntdll.dll
Report Id: c47639eb-8703-11e1-b41d-20cf305744ca

I also found an interesting intermittant bug with obj file generation as well. I had one save today with the winding order corrupted. Not a big deal when using numbered file saves thou.

---

Some things are easy to explain, other things are not........ <- Store ->   <-Freebies->