I loaded in the latest DSON importer.  I brought in a figure and dressed the figure, applied a pose.  Saved the PZ3, then tried to reopen it and the dson scripts loading window went for minutes before opening.  then poser crashed when I tried to turn off subd from the dson menu.

I reloaded the PZ3 but this time it crashed on moving a dial. maybe those little dson importer scripts weren't finished.

This is still not useable for me for making a comic.

Love esther

Quote - I loaded in the latest DSON importer.  I brought in a figure and dressed the figure, applied a pose.  Saved the PZ3, then tried to reopen it and the dson scripts loading window went for minutes before opening.  then poser crashed when I tried to turn off subd from the dson menu.

I reloaded the PZ3 but this time it crashed on moving a dial. maybe those little dson importer scripts weren't finished.

This is still not useable for me for making a comic.

Love esther

And I was just thinking about giving Genesis another try in Poser. Hmm. Perhaps Joe's method of hacking the CR2 is the way to go. Before I even start down that road, I wonder, is anyone else having the same trouble as Esther?

WandW reports loading times are longer with the latest version of DSON.

I haven't tried it yet as the current version works fine with me.

Did you also download and re-install the latest versions of the Genesis-1, G2M and G2F base files ?

They got changed, too, to stay compatible with the new DSON importer.

Have you updated Poser with the latest SR ?

(BTW, Poser is doing some funny stuff with saved scenes now and seems a bit more "crash-prone" than with SR2.)

And, yeah, saving Genesis as a cr2 once it loads via the DSON importer is what I always do.

I first switch off the permanent subdivision by using the DSON support scripts in the script menu, change to "Unimesh Skinning" under "Figure" and then set the subdivision in the body actor so that it is only used for the actual render but not the OpenGL preview.

Why use the Genesis figure?

Is it because "everybody else is" so I must too?

Loading via DSON was 15 seconds.

Saved him as a pzz and closed Poser.

No problem restarting Poser by clicking on that pzz. Loaded actually quite quick.

No problem rendering.

OMG ! THE UV-BUG IS GONE !!!!!!!

I applied the M4-UV set, added M4 texture maps and rendered him. then saved hom as a .pzz.

Closed Poser.

Clicked on the pzz to start Poser and M6 appeared WITH THE M4 UV SET STILL APPLIED !

WEEE, one major, annoying bug squashed.

Only drawback, you can't use Poser's own "unimesh skinning" with it. And so, you have to manually switch between SubD settings.

Or live with the "high res" ghost halo in OpenGL preview.

Which, OTOH, doesn't slow OpenGL down anymore.

So I think it's actually better now to stick with the traditional Poser skinning and switch SubD OFF via the DSON helper scripts until you are ready for the final render.

Made also some "save with clothing" as a pzz tests, but so far no problems or crashes.

Acer i5 Laptop, 4GB RAM, Windows 7 64, PP-2014 SR3.1.

Newest DSON and Genesis files.

"Why use the Genesis figure?

Is it because "everybody else is" so I must too?"

Well, I could say because Genesis is the personified versatility, is much more realistic and hardly needs any fixes anymore, so it is a much better tool for realizing your own artistic potential, whether you are a beginner or an advanced user.

BUT....

...as they say, "One man's terrorist is another man's freedom fighter", so given that the vast majority of Poser users still stubbornly stick with V4, Dawn or one of the Poser girls, it is us few Genesis users who are currently the elite avangardistic rebels who simply don't go with the flow but are willing to embrace cutting edge technology, whatever the personal cost.

"To boldly go where noone has gone before..." and all that stuff.

No, noone has to use anything.

Actually, you all stay away from Genesis ! 

After all, annoying the masses is part of the fun, and we couldn't do that if Genesis suddenly became mainstream, could we ?

;-P

I think my pz3 was corrupt. I had another pz3 that didnt' take so long but it had a poser skinned genesis in it, so I'm still not sure.

don't be certain yet that the UV bug has gone. I messed around with genesis a long time ago and sometimes the poser skinned M5 seemed to keep his texture then suddenly he would revert to the wrong UV mapping.  save and open and move the figure around a bit and you may be surprised.

I think there will still be a UV bug, because when I import a genesis male into vue the mapping is only V4.

also I had another poser crash (probably because I have conflicting python scripts running in the background all at once) and now I think my next PZ3 is also corrupted. I don't think I can really work like this.

there are some speed improvements but there are still too many problems.

"...save and open and move the figure around a bit and you may be surprised."

So far no problem with the UV mapping as long as you stick with "Traditional Poser Skinning" and SubD Level 1 or 0.

Only with "Poser Unimesh Skinning" or SubD Level OFF Genesis will revert back to its base UV set.

"I think there will still be a UV bug, because when I import a genesis male into vue the mapping is only V4." That's actually quite normal. The alternate UV sets only apply to the Subd mesh. But Poser only allows you to export the raw, unsubdivided cage mesh. You'd have to hack a Genesis cr2 and assign an object file with a permanent UV set like I did. Then the UV set would stay during export. For example I have three Michael 6 cr2's: One for M4 textures, one for M5 textures and one for M6 textures.

hmm I think I might have to try that next.

I know that previously there were times when I saved a genesis Cr2 and then loaded it into poser and all looked fine and then all of a sudden it would lose it's uv mapping in poser.  so i'm still not certain that bug has been fixed yet.

However I will try it.

The load times for genesis in DSON has improved in the latest versions of the DSON importer. Still a lot slower as native poser figures, but acceptable. (15 secs for G2F with just the base morphs vs 10 seconds for a fully loaded V4). If you add morphs (genesis with a few morph packs and genX) load time will increase to 55 seconds.

There is another (old) problem with multiple figures however. You can load 4 G2F's without the load time significantly increasing. If however you then load a 4 items clothing set to each of them, performance for the 1st 2 sets is a few seconds, 3rd one is getting slower and the 4th set takes 3-4 minutes. And worse the performance in Poser is now gone down to almost complete unresponsiveness. You can't do anything anymore such as twisting a head - the cursor keeps spinning and never comes back. In the end you have to kill poser. This is with SubD levels at 1,0 and -1.  This is what is preventing me from using genesis on a regular basis

I can easily have 10 fully clothed, haired and morphed V4's in a scene without any serious slow down so it is not the number of figures or size which is the problem

I am using the latest DSON importer, latest Poser version with SR3.2, fast video card and fast machine

The M6 I tested had several morphpacks installed.

Just tested again, loading one M6, then duplicated him twice.

Then I loaded clothes to all three copys. No differences in loading times between copy one and copy 3 whatsoever.

I dialed different morphs for each of them, then transfered the morphs to the clothing.

No slowdown.

OpenGL stayed superfast and responsive, despite subD level 0 instead of OFF. OpenGL even was as fast with with the 3 clothed M6's as it was with one ! Amazing.

I'm not doubting some people having problems.

I'm just saying my lowly 4 year old i5 laptop with nvidia GT640m card can handle Genesis beautifully right now.

But the DSON importer is constantly improved, so even if one had problems in the past, it might still be prudent to re-try from time to time.

I'm not trying to proselyte anyone. I have better things to do. I'm just sharing the facts as I gather them while using Genesis in Poser. (And, btw, I still spend 95% of my Poser time with my own 3rd Gen meshes)

Some may even remember that before the bulge mapping conversion was sorted out, I wouldn't recommend Genesis at all.

But I think Genesis-2 has matured to a point where the pros outweigh the cons, so it would be a shame to not make an informed decision by testing it for yourself.

The massive slowdown started at 4 g2f's - each loaded individually and each time a full set of clothing (4 pieces) on each of them. The third was a bit slower. The fourth was a disaster.

Whatever the reason, DSON has a very big problem in Poser when you use it with multiple figures. Just reporting the problems I experience and which other people have experienced as well

I tried this today with the latest importer

I too found that poser slowed down and the dials weren't as responsive when I had two genesis figures in a scene wearing a 4 piece outfit each.

Love esther

As I said, I'm not doubting your problems. You should report them to DAZ, though.

I just loaded two more copys of M6 for a total of five and clothed them, too. No difference whatsoever in clothing loading times. It was 5 seconds or less.

OpenGL still fully responsive.

I'd never ever be able to do that with standard 3rd or 4th gen DAZ meshes, especially Vicky 4 with all her "joint-smoothing-magnets" dead weight.

Only my own "super-optimized" polygon reduced weightmapped 3rd gen meshes can usually do that, but even these slow Poser down after loading 5 or 6 naked figures.

Up to 6 or 8 fully clothed figures I have zero slow down with the V4 generation. It slows down a little bit after that

The G2F figures slow down at 3 clothed figures and with 4 poser becomes totally unresponsive. This happened to me with the new figures and with the old genesis figures.

I have had this with different PC's, different videocards, different poser versions.

And i did report it repeatedly last year when I experienced it (in Mantis when it was still available). After that they removed the reporting system with a message that they had closed the report. I never got a response.

Since I have zero performance problems with native poser figures (and I use a lot of different ones) it must be something which DSON does

Maybe it is configuration issue - but I do the default install and everything works fine upto figure 4

And yes, I have enough memory (64GB), use the 64bit versions of Poser and the DSON importer. I use a quadro card for OpenGL (Nvidia GTX680 has the same problem)

It must be a bug because when I save the clothed figures to the library and load them 4 times, the complete unresponsiveness does not occur - it is just slow (3 second delay on the dials). It is just complete unresponsive when I load the clothing from the library