V4.1 - wtf???
I went ahead and downloaded the updates and installed them. spent some time this weekend working up a couple of new pieces using V4.1. they looked great and all that, had to go, saved them and walked away. came back later.... nothing.
posert acts like it's opening the file, but there is no image box. if i try to open something else it asks if i want to save my changes??? wtf??? changes? i can't even see the durn thing!
apparantly i'm not the only one having issues with this update - did some poking round at a few of the forums. unfortuneatly, the only solution that seems to be offered is to uninstall and go back to V4.
i have tried to open a bunch of other stuff and as long as V4.1 is not in it, it opens just like it's supposed too....
anyone have any ideas or fixes???
P.S. - thank sartori for pointing me in this direction!!! you were right on the money!!



i hope however that they resolve the issue, it's really frustrating when an update comes out, which should better the product, not the contrary

v4.1 is optional and is only needed if you are loading a ton of morphs ( like the muscle and the creature morphs )

instead, i get massive headaches and irritations.
it was the ext binary thingamajigger - like i have a clue what that is, what it does, or why i might use it. though i did pick up the creature pack, so i may end up needing it after all...
whatever happened to keeping things relatively simple???

external binary morph targets = the .pmd files, aka "poser morph data". its somehow supposed to shrink filesize, or some nonsense, but i think i'd rather keep the data in 1 file than in 2. so yeah.
go read the v4.1 thread in crayon box, it'll help clear up some issues. i'll amend it about the external binary morphs too.

i did go looking for this thread, cuz i remembered seeing something about this, was pretty sure it was from you, but since it didn't talk about the darn thing wigging out and i had done exactly what you had outlined... well, i figured the problem was at my end and went poking around the other forums... and the more i read, the more irked i got. thank goodness Sartori had had the same problem, which did fix the idiocy i was engaging in!!
i just think daz could have handled this better from their end. end of my bitching!!
thanks for the help!

I've been using V 4.1 without any problems.

