I dont have them set to re-open. My runtime is only 17gig.

 Poser 8 had the same problem with the ever longer library load. Any time I had to throw away the prefs/Ui files to fix a bug the library would become snappy again. This time was the app update (PPro2014) that threw away those files and created new ones. Snappy library loads. I just figured everybody had the same problem with that.

What does happen to those files? Most of them aren't files modified often (or at all), except maybe the AIR subfolder. Why would yours go stale over time?

You might want to make a copy of a clean set, so you can copy them back when your library starts limping again...

Im not sure what happens to the files. They are user prefs files for saving your personal preferences of the defaults...mine is set to load up a blank scene with an enviroshere and my own light set. When you throw out those files, Poser just makes new default files and places them in their proper folders. All your settings go away bt you can save new ones so it's no big deal. The end result inmy case is that the library becomes fast again. give it three months and it will be back to the same old slow library.

What if you edit LibraryPrefs.xml, setting searchIndexed=0 for all listings?  I think maybe that was another tweak.  :unsure:  But perhaps that nukes your library search settings.  Umm.

Okay, after a year of hanging and crashing, of updates, replacements and other tweaking,  Pro 2014 continues to crash. I have taken the comp and a spare HDD back to the shop and I told them I wanted the drive re-formatted and a frsh copy of Windows 7 installed. While it is there, I'm going to install Pro 2014 on that drive and have the shop certify that both programs are clean installs.

I sent this information to SM. They insist that it's a component issue and I should have the shop make sure the components are compatiable. COME ON! I've been fighting with this for a freakin' year now! The comp's been in and out of the shop a dozen times checking everything under the sun. Don't you think if it were a compatiblity issue, it would have been found by now??

its gotta be some kind of software conflict on your machine because 2014 hasnt crashed on me yet.

Quote - its gotta be some kind of software conflict on your machine because 2014 hasnt crashed on me yet.

We'll find out when I pick the comp up Friday. The second HDD will only have Windows 7, Pro 2014 and it's related files and my Runtime. Then we'll see.

The Mirroring problem with the Morph Brush appears to be down to the figure.  I noticed today that the figure isn't welded properly at the seams even inside Poser, and it's those points that aren't welded that are causing the Mirror to fail.  If I use the Advanced Body Control to lift-up Roxies arms, use the Smoothing Brush around the arm pit area, Mirror it, and then hover my mouse over the Mirrored side, I can see double-vertices where the mesh isn't welded (see attached image).

If you look closely at the highlighted vertices, you'll see two rows of them in some parts, this is where the Smoothing Brush has smoothed them apart before doing the Mirror, and they only parted because they aren't welded.

The Poser figures seem to suffer this random unweldedness on just about every seam, not just the arms, and not just on Roxie, it's all of them so I can only imagine the software being used to create the welds isn't working properly.

This splitting thing has been a pain in the backside for some years now.  And it's not just splitting, there's an edge issue around the seams as well.  Best way to test it is to export the figure from Poser without welding the seams, and then import the obj into ZBrush and run the smoothing brush over it.

Ugly splitting and hard edges will make an appearence on Poser figure seams, but not so with DAZ figures.  Whatever is wrong in the creation process needs rectifying because it's a pain in the backside from a content development point of view, I really hope Teyon will fix whatever it is that's causing it.

Quote - > Quote - its gotta be some kind of software conflict on your machine because 2014 hasnt crashed on me yet.

 

We'll find out when I pick the comp up Friday. The second HDD will only have Windows 7, Pro 2014 and it's related files and my Runtime. Then we'll see.

Got the comp back with the spare drive a installed. New install of Windows 7 and a new install of Pro 2014. NOw, the program can't find it's library- all I get is a big white square where the library is supposed to be.

Quote - > Quote - > Quote - its gotta be some kind of software conflict on your machine because 2014 hasnt crashed on me yet.

 

We'll find out when I pick the comp up Friday. The second HDD will only have Windows 7, Pro 2014 and it's related files and my Runtime. Then we'll see.

 

Got the comp back with the spare drive a installed. New install of Windows 7 and a new install of Pro 2014. NOw, the program can't find it's library- all I get is a big white square where the library is supposed to be.

Edit:

Never mind. This second HDD didn't have Adobe Flash on it. Got it working at the moment, now.

Quote - Ugly splitting and hard edges will make an appearence on Poser figure seams, but not so with DAZ figures.  Whatever is wrong in the creation process needs rectifying because it's a pain in the backside from a content development point of view, I really hope Teyon will fix whatever it is that's causing it.

They seem to have modified the sensitivity for the weld handling somehow.  I have figures that weld at actor without trouble in all the previous versions of Poser, but which fail to weld at all in Pro14.  I've assumed that this modification of weld handling has something to do with the subdivision system and the new skinning methods.   :unsure:  I hope they can resolve bugs like this before too long.

Whatever it is that's causing it needs fixing.  It's hardly surprising vendors aren't too enthusiastic about working content for these figures when we have to live with this stuff.  DAZ figures don't have splits or hard edges anywhere when you smooth them, and nor should the Poser figures.

Like I said, it's my guess the problem is down to the software that is used to create them, it can't be down to Poser because figures from DAZ don't have these issues even when exported from Poser.  If Teyon creates the figures, he's really the only guy who can nail the problem.

Somebody should tell him, for I doubt he's reading this thread.

This is more a client-side "is that me, or is this really broken?" kind of discussion thread.

Quote - > Quote - > Quote - > Quote - its gotta be some kind of software conflict on your machine because 2014 hasnt crashed on me yet.

 

We'll find out when I pick the comp up Friday. The second HDD will only have Windows 7, Pro 2014 and it's related files and my Runtime. Then we'll see.

 

Got the comp back with the spare drive a installed. New install of Windows 7 and a new install of Pro 2014. NOw, the program can't find it's library- all I get is a big white square where the library is supposed to be.

 

Edit:

 

Never mind. This second HDD didn't have Adobe Flash on it. Got it working at the moment, now.

This morning- Saturday, April 12,2014, went to use Pro on the second HDD. The Program came up, the scene file I wanted to use came up, worked on it for about 5 minutes-

• and Pro crashed. :-(

I recall someone on here said they do read the thread, I bloody hope so, anyway.
They can't have much interest in fixing things if they ignore a thread with this title!

I don't think they WANT to fix anything. They're too busy blaming your os or your system to take a good hard look at their own program.

I wish I had access to a programer that could take Pro apart line by line. I have no doubt he'd find the answer within a day- or less.

Well, whether they want to fix it or not makes no difference to me now.

Just wanted to add an update to what I posted above and point out that in fact even V4.2 has issues (very small ones) even though her mesh doesn't split.

In other words, the problem is down to both Poser and the Poser figures so I can't see it getting fixed any time soon.  I reported this plitting nonsense years ago yet it's still there even on brand new figures built since then.

They either need to fix it or continue to wave bye bye to potential content developers - lol

I went back and re-installed Poser 9- Thank God I kept the serial number and install files.

 I was always under the impression that once a new verison of Poer "tasted" a work file, it couldn't be used in an earlier version. But so far, every scene file I set up in 2014 is working in P9- and the program hasn't crashed yet.

That's one thing the Techs have never tried to explain. Why would P9 work without any problems while 2014 screws up on the exact same system?

As far as I can remember, I myself had loads of Poser crashes from Poser 5 forward. Now I am trying with Poser Pro 2014 and pray for more performance, especially on complex geometries. I was able to load, move, scale and rotate near 9 million polygon geometry in Daz Studio Pro 4.6 (!), but Poser have great difficulties even on loading the object to scene, where is all possible figures removed, only one infinite light present, without shadows, without different docked tools, no figure circles, camera names etc. visible and still Poser cannot run the geometry. Processor usage is below 10% at the same time, it would be the same as I had a single core without hyper threading. So what is proce performance...

Quote -
Well, whether they want to fix it or not makes no difference to me now.

Just wanted to add an update to what I posted above and point out that in fact even V4.2 has issues (very small ones) even though her mesh doesn't split.

In other words, the problem is down to both Poser and the Poser figures so I can't see it getting fixed any time soon.  I reported this plitting nonsense years ago yet it's still there even on brand new figures built since then.

They either need to fix it or continue to wave bye bye to potential content developers - lol

Wondering... did you export the mesh to get it into ZBrush? If you did, don't.  Either use GoZ or use the OBJ from the Runtime directly. Poser's OBJ export can sometimes act up.  As for the issue you're seeing in the arms when raised, I'm not seeing it on my end but If you can send me a zip of the PZ3, I'd like to see what you're seeing. 

Also,  and this is to everyone, if you have bugs be sure to file them with the company or at least contact Tech Support so that someone in-office is made aware of the problem.  I just happened to be here today and decided to give this thread a look. Not something I often do and not something I can garuntee I'll do again.

Sorry Teyon, just saw this after having to explain something in another thread!

Regards the splitting: it appears to be down to Poser exporting it, but it doesn't make sense because if you export a DAZ figue, there is no splitting.  I just don't get how Poser can deal with DAZ meshes on export, but not their own meshes.

Try it, export V4 and export Roxie, then smooth them over in ZBrush.  I honestly think it's down to the software you're exporting the final figures from, I can't think of any other reason because like I said, the DAZ meshes export from Poser without splitting.

Regards the issue with the Morph Brush Mirroring with the arms lifted (Vilters spotted it on legs as well), can you message me an email address to send it to?  I was just explaining to Keith in the other thread, I have no problem reporting bugs otherwise I wouldn't have bothered in this thread.  

Anyway, thanks for posting, and like I said, I can email the file, no problem.

As a content developer I feel your pain everyone...

Sr4, you are dreaming. They never go sr4, they go straight to the next version...

Mirroring issue: Exists for multiple figures, even 100% symetrical ones. I don't see that getting any love.

Many issues have existed over multiple release versions and never get fixed.

Customer Support: They are helpful as long as it has nothing to do with 1) a known bug (that they have "never heard of before"),  2) Software crashing, 3) Content you are making that encounters a known bug with the software, 4) and more!

I feel your pain(s), I do, I have many of the same issues.... I was hoping to come here to offer fixes, but after so much time and experience with SM software and support I would not hold my breath or increase my expectations. Not trying to put them down, but I am a realist. Expect a release of a poser 11 soon. Expect all of these issues to continue to exist. Do not expect any update of previously released figures, patches above sr3, etc...

Quote - Regards the splitting: it appears to be down to Poser exporting it, ......Try it, export V4 and export Roxie, then smooth them over in ZBrush......the DAZ meshes export from Poser without splitting.

V4 splits. Always has. They only way to get her not to split is if you are welding verts on export or import to zbrush.

I saw a post from Cooperman the other day that suggests we can expect an SR4.  He mentioned that Poser 10 and Pro 2014 will be around for some time yet, so it's great to hear there will be an SR4!

I hope they fix the biggies, and I have it on good authority that the splitting might be sorted on the next wave of figures, so that's more good news!

Quote -
I saw a post from Cooperman the other day that suggests we can expect an SR4...

I was told by support (after submitting many a bug getting to "the right people") that Poser 10 and 2014 was "no longer supported".... ie. Don't expect anything from us.

Quote - > Quote -

I saw a post from Cooperman the other day that suggests we can expect an SR4...

 

I was told by support (after submitting many a bug getting to "the right people") that Poser 10 and 2014 was "no longer supported".... ie. Don't expect anything from us.

If they're cutting off support, that sounds like Poser 11 isn't too far away- maybe the end of the year?

Well, like I said, I'm just going on what I read.

Here's the thread if you'd like to see it:
**[ http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2869147

](http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2869147)**

Quote - > Quote -

I was told by support (after submitting many a bug getting to "the right people") that Poser 10 and 2014 was "no longer supported".... ie. Don't expect anything from us.

If they're cutting off support, that sounds like Poser 11 isn't too far away- maybe the end of the year?

They are not cutting off support.  Steve Cooper indeed said the other day that 10 and PP2014 will be around for a while and SR4 is in beta, and there will be an improved Download Manager...

Edit; X-post with pumeco...  

Quote - > Quote - > Quote -

I was told by support (after submitting many a bug getting to "the right people") that Poser 10 and 2014 was "no longer supported".... ie. Don't expect anything from us.

If they're cutting off support, that sounds like Poser 11 isn't too far away- maybe the end of the year?

They are not cutting off support.  Steve Cooper indeed said the other day that 10 and PP2014 will be around for a while and SR4 is in beta, and there will be an improved Download Manager...

Edit; X-post with pumeco...  

Well, after fighting with 2014 for over a year and getting nowhere with it or the techs, I went back to Poser 9. I think I'll stick with it till Poser 11 does make an appearance.

Nice to see there will be a SR4 according to this. I have not yet installed sr3 because once i get a stable build I like it to work that way for awhile, maybe I'll install it...

Also, it is DISTURBING to heard that they have more time to test a patch than they do a FULL VERSION release. SM, why you no test release right? You take money......

Quote -
Also, it is DISTURBING to heard that they have more time to test a patch than they do a FULL VERSION release. SM, why you no test release right? You take money......

Because the real stress test on any software only comes after innitial release, where there's more feedback from the majority of the user base than a closed beta team can provide, and the devs can respond to the most pressing issues based on those that are most reported and fix them with service releases. 

~Shane

Ah, makes sense(kind of)....! I have other things to say about that, but nothing constructive, so I'll bow out!!

Regards to the splitting/assymetry issue with Roxie, V4 and other figures: Are you using the dev rig with the morph brush symmetry or the production rig? Roxie's production rig/mesh seems to be assymetrical when exported to zbrush, but the dev mesh is symmetrical. I can mirror a morph in zbrush across the dev mesh. I can't mirror a morph in zbrush across the production mesh. 

V4 doesn't split in zbrush when using GoZ or when importing directly from the geometries folder. At least I've never seen it happen. I did a tutorial a while back on how to use GoZ to create morphs in PP2012:

http://www.renderosity.com/mod/forumpro/showthread.php?message_id=3975663

Never have had to delete any verts on her. If you're exporting from inside Poser manually then the export settings can get confused and sometimes it just doesn't work correctly even with the right settings.

~Shane

Quote - I wish I had access to a programer that could take Pro apart line by line. I have no doubt he'd find the answer within a day- or less.

When you find a programmer that can wade thru hundreds of thousands of lines of code that he never saw before and find anything out of place, you let us know. Because there is no such person, or program,  on the planet.

A day or two? Get real... It would take them months just to get the jist of it, let alone fix anything.

carry on....

they can't take it apart line-by-line: is EULA violation.  even if you find some guys as smart as stefan et al., those guys would be too smart to try reverse-engineering it. 

Dynamic hair groups suddenly stop populating. 

This peristent problem keeps occurring at random, and there is no way to correct it other than going back to an earlier saved version. 

The populate check box does nothing.  And the broken hair groups remain sparse both in preview and in full render.

Does anyone know of a workaround, which will let me reactivate the corrupted hair groups? I am losing hours of work on a daily basis.

cage wrote an hair-to-path script, but I ain't tried it yet.  will check it out.

Usually I've had that happen if I accidently delete either a group or the cap and then undo the delete. Unfortunalty I don't know a fix and neither does SM it seems. Cage's script, while very useful, doesn't help with this.

I can create in Poser that refusal to modify the hair growth group settings if I add a dynamic hair prop directly to an actor which does not have a geometry group to associate with the growth group.  Everything shows up in the Hair Room, the hair renders properly, the Hair Style Tool works (if what it does can be called "working"...).  Yet the Styling Controls for the hair do nothing.  It looks like the hair may only be rendering as guide hairs, too.  :unsure:

It looks like Poser still requires a geometry group to be associated with a hairGrowthGroup listing.  This is strange behavior, since Poser no longer requires a "cap" prop for use with dynamic hair.  You can now add dynamic hair to an actor without that geometry group assigned for the hair group.  But full dynamic hair functionality still requires the geometry group.  It looks like dynamic hair functionality was expanded, but incompletely.

This sort of fits with what RedPhantom is saying.

@ teigan: Can you determine whether you have a geometry group for the hair growth group, on the parent actor for the hair prop?  In my test .pz3, I have this:

hairGrowthGroup puppet_hair:1
{
    hairProp    puppet_hair:1
    baseActor    head:1
    ...
}

But the geometry for head:1 has no group for the hair:

actor head:1
{
    storageOffset 0 0 0
    geomHandlerGeom 13 head
}

I skimmed the previous posts and did not see my problem - sorry if this was listed and I just missed it.

My morph dials quit working in PP2014, Win 7, SR unknown (whatever it was up to when I bought it last month).  I will use Posette's chest as the example:  The XYZ and Scale dials work, but the Small, Large, Cleavage, etc. do not.  The dials still appear, and the values change when spun, and I can type a value in, but nothing happens in either preview or when rendered.  I have the external binary morph box unchecked - I think it was checked when they locked, since I added a no nips morph someone else made, but several days and several figure loads later and still no changes in the affected dials.

I just checked Posette and she works fine in PP2014, 10.0.3.26510

Make sure you updated the content; I updated by using the SM Download Manager (I purchased the download version) to download a new copy with the SR integrated, unimatalled Poser and reinstalled the new version, telling it to keep my preferences... 

Thank you for that.  Posette was working fine before, then those types of dials quit while everything else was fine.  I have PP2014 marked to automatically check for and install updates, but I will look to see if there is anything new - I just bought it last month.

I was thinking I might need to do the uninstall/reinstall anyway just to clear the bug. >:(

Did you try to simply reinstall Posette? Something quite similar happened to me a long time ago, a specific V3 morph went inert, and reinstalling morphs++ did fix it. Apparently somehow the morph file got corrupted (don't ask me how, it's not supposed to be written to, and the disk it's on is still running fine, many years later. It never happened again either).

Quote - Did you try to simply reinstall Posette? Something quite similar happened to me a long time ago, a specific V3 morph went inert, and reinstalling morphs++ did fix it. Apparently somehow the morph file got corrupted (don't ask me how, it's not supposed to be written to, and the disk it's on is still running fine, many years later. It never happened again either).

I do not have a viable Posette, since P5 will not run, P7 will not install, and P9 will not access the libraries.  The only external runtime I have with her is the one I have linked to PP2014.

I uninstalled/redownloaded/reinstalled PP2014 and it did not clear the bug.

Even the things I have already saved with her will not adjust with the dials.  I will try to morph her manually tomorrow.

Huzzah and never mind - I do have a second copy of Posette - it is included in PP2014 in the Poser Originals folder.  Loaded her into the workroom and the dials did what they are supposed to do.  Saved her into my project runtime, deleted new from scene, loaded project copy, and everything works.

Still do not know why the dials locked up in the first place.  3 possibilities:

1)  Had her in the workshop and loaded a differend version into the same space and T pose to see what the difference in proportions would be.  Did not save anything to the library.

2)  Placed and parented a posable bow to accentuate her poly-painted bikini top and saved Posette's body with bow as a separate figure in a different folder.

3)  Don't know if I had "Use External Binary Morphs" checked when I loaded a nipple morph someone else made, then saved to library.  I seem to think dials worked after that.  When they quit working, I searched the forums and found I should try unchecking "Use External Binary Morphs" - I did but nothing changed when I restarted the program.

:-/

Can someone please tell me if the stray Morph Brush vertices problem I pointed out on Roxie has been fixed in SR4?

If anyone checks for me, please don't forget to use the Smoothing Brush on Roxie's arm joint area as pointed out.  I just read the release details and there's no mention of the fix, so don't worry, I'm not holding my breath on this one!

Forget that, I just realised I can download the update through the Install Manager and try it myself.

Nope, not fixed.

This is the simplest of all questions, but for some reason I cannot find the answer very easily. Is there a specific place to file reports for possible bugs? Or do you just contact SM support with an "incident"?

Quote - This is the simplest of all questions, but for some reason I cannot find the answer very easily. Is there a specific place to file reports for possible bugs? Or do you just contact SM support with an "incident"?

Yes, you have to contect SM support with an incident