Quote - > Quote - Also, it seems that poser import works nicely now, at least for a static mesh (didn't try animation). I imported Stephanie 4 + clothing + hair from Poser Pro 2010 (selecting the latest smith micro SDK in vue drop down) and the result in vue was perfect :) The ability to resize the textures on import is also a very nice one :)

And another good new, after 3 hours no crash :)

Yes, the texture handling is an amazing improvement. I can throw the resizing step in ACDsee out of my work-flow now. You can not only resize all maps during import you can also down-sample each map individually after import. There is also an option to copy all maps to a specified folder. This is really great. No problems here either so far. I noticed that the openGL demands have gone up again. My trusty old Nvidia Quadro FX 4000 which was running 8.5 nicely has become quite slow, but it is still very solid. Fortunately, I have a new system with a GTX 460 coming in a few days...

Ciao
TD

I will do some extensive testing on this too and find out if the Poser Shader Tree issues and others I was working with e-on with for fixing are now OK or improved. When I was assigned a tech to work with by e-on, Neil was the one I was working with and said it would require a big change to the Smith Micro SDK and he reported 5 major problems I found with it. These ranged from the Poser Shader Tree not working as it should (even though it appeared to but failed with specific nodes) to resizing on import issues, OOM errors at random times and lack of Poser Pro support. So, here's hoping some of this is now fixed by Smith Micro and e-on as it made Vue unusable for what I do with it mostly.

I will post results of my testing in a separate thread in this forum area once completed.

For the answer to this thread topic, the solution was to uninstall and reinstall. What was happening according to tech was a corrupted permissions issue in Windows 7 and it got messed up. It happens sometimes and the only way to really correct it is to install the program again.

Also, the answer about the uninstall is there is no separate uninstall for 32 bit, however to uninstall you have to go to your Program Files>Smith Micro>Poser Pro 2010>uninstall directory and launch from there. They know it does not show up in Control Panel for some reason so you have to find it manually.

Hope this helps others maybe.

Quote - You never answered whether or not you have UAC turned on. I don't have any issues saving content to my runtimes because I told Poser Pro 2010 to create it's content in an external runtime outside of Program Files area because of UAC.

And yeah, it still creates a 32 and a 64 bit runtime in both Program Files and X86 directories. This is awkward when keeping your Python Scripts updated because you have to change files in  both directories if you use both 32 and 64 bit and switch back and forth as I do.

The UAC question was not addressed because that was a non issue as I did not have UAC turned on to begin with or else I would have mentioned it. Still don't know why there is no un-installer for the 32 and 64 bit Poser versions either so that is another question to ask.

Quote - I doubt it's looking in the other directory.

Truthfully, I never looked at how the 32 and 64 bit versions are installed together until just now. It looks like each gets its own runtime. That seems like an odd choice.

I know what you mean, but I think that is because it is like other programs such as Adobe Photoshop where it has two totally different installs. One of them is in the Windows 7 64 bit Program Files directory and the other in the 32bit x86 directory. Each of them running independently.

Also, another thing that is odd is I don't see any uninstaller in my Control Panel program list for Poser Pro 2010 or Poser Pro 2010 32 bit version. Only a Poser Pro 2010 content uninstall. Is yours the same too?

Not sure what is causing this because it only is a problem when saving to the library. I can install new content just fine by either hand copying them to the right places or just unzipping in the Poser Pro 2010 directory. So, I may have to contact Smith Micro tech support on this and see why I can't save content there as I have no clue at this time.

Quote - I'm guessing.

You have UAC turned on.

The folder JSHStudio was created in the virtual store, not really in Program files.

Meanwhile, you're running Poser as administrator, so it is trying to put something in the REAL location, but it doesn't really exist.

I checked to verify and I did in fact create the directory in Program Files and it does exist there. It is located in the main Windows 7 Program Files directory, NOT the x86 directory. Could that be the problem, it is looking for it in the 32 bit directory? I am running the 64 bit version of Poser Pro 2010 though so I don't know why it would be looking in the x86 directory for it.

Thanks.

Quote - > Quote - well 8.0 and 8.5 are doing this now, rotating conforming parts at 90 degrees, again...oh FFS....!! :(

and 8.5 has messed imported scale up so Vicky 4 is the size of a titan!

I gotta feeling I do't have to mention this to you, but I would suggest that anyone having (similar) problems, report this to e-on. The more info they get, the bigger the change this may be solved..

Most all of this has already been done by me when I was working with their tech support earlier this year. If you want, you can look at my threads over on the e-on web site and search for Poser import problems to find more on this.

Basically, I was assigned a tech, Neil, that worked with me on many of the Poser importing issues. They were not aware of many of the issues until I reported them and sent them source files explaining each problem. I was able to fully confirm at least 5 known bugs and Neil said when he tested they went all the way back to Vue 7.5 builds. Bottom line is the problems lie in the Smith Micro SDK and both him and Lee at e-on said there was no fix they can do unless Smith Micro updates their SDK for them. Mainly, they blame Smith Micro for all these issues.

The scaling and re-sizing are known issues I reported as was the Poser Shader Tree, OOM errors at random times, conforming and more. For now, Neil and Lee said it is hit and miss for the re-sizing and scaling and to leave the re-size on import turned OFF. Also, Neil said it was best to leave "Poser Shader Tree" turned OFF as we found many errors where it did not work or translate as it should from Poser when it was ON.

I have asked MANY times when or if they are going to write their OWN code and not rely on Smith Micro SDK for all this to work. But the last I heard is they have no plans and it is unknown when or if Smith Micro will update the SDK. This is what makes no sense to me because other programs don't have this much trouble getting Poser to work OK, such as C4D. Also, I was told their is NO OFFICIAL support for any Poser Pro products such as Poser Pro 2010. To try it with the Poser 7 or Poser 8 import settings and see if it works.

So, for now things are broken and seem like they will remain that way until Smith Micro and e-on work more together on this with the SDK. I am starting to lose hope in any of this gets fixed since it goes back to Vue 7.5 and there is no word at all on any fixes for these issues. One of the main reasons I got Vue was to work with Poser imports in my scenes and this has certainly put a damper on that big time for me. I really don't know if I will continue to use Vue or not if they don't fix this soon and not just talk about it and blame Smith Micro.

Quote - Well, I can explain how to use UVMapper for this but I don't know that it's going to work in your case - nor do I think any morphs will either if you're altering the geometry (subdividing alters the vertex count). It has been awhile though.

For the UVMapper trick, you usually want to save a copy of the original obj you're working from, that way you have access to the previous grouping.  A simple copy and paste to a new location would suffice but you could also load the obj into Uvmapper and save to a different name. Then you do what you need to do in ZBrush and if it destroys the group names, you simply import the untouched obj's UV's. It will automatically reassign the grouping/materials as long as no changes were made to the vertex count. The idea is, since the geometry is the same order/number of verts, copying between a morph and the original won't cause problems.

Subdividing introduces new polys into the model though and that changes the vertex count, so if you save a subdivided copy of the model, you're gonna have a hard time. You'll likely have to manually rename the groups and probably kiss the pre-existing morphs good bye.

This is very true and why you can't really fully sculpt a basic Daz mesh from the ground up. Changing the poly count is going to cause all sorts of issues like mentioned above. It would be very nice to do a truly high-end V4 sculpt but you can only work on the mesh in basic ways such as how vendors here do it for their custom figures they sell.

Getting everything to work would not be possible, at least without a LOT of work. The time would be better spent simply sculpting your own mesh in ZBrush and importing into Poser, Max, Maya, etc.

Quote - The iris area looks too big IMO.  Not by much but enough to make them look off to me.

Most custom character vendors use a modelling app to create the morphs and reposition the eyes.  A dial spin character would use the available morphs so there wouldn't be a problem with the eye position.

I really would lose that baked on reflection if I was you, though.  :) 

OK, can you tell me how to get rid of the "baked on reflection"? I am not sure how except to maybe use another eye package. Is it a setting I can adjust in the "material room" to change this?

Also, you said most use a modeling program and I was wondering though how they load the eyes in with the head. I understand how to export and import the head as an OBJ but not sure how to do both the head and the eyes at the same time. Would that be a custom pose file where you click on it to load the character morph it loads the custom head OBJ and custom eyes at the same time? In other words you would hand edit the pose file to load your head OBJ and eyes both left and right as an OBJ too all at the same time?

Why does that NOT mess up other poses from vendors since the eyes are moved? Say I  have a bought character and it has a custom head morph, eyes moved, etc. as mentioned above. The poses from other like DM for example all work OK on that bought character and the eyes line up properly. Yet if I load in a custom head and eyes OBJ that have been properly adjusted the pose files don't work for the eyes because of their adjustments?

Just trying to figure all of this out. Thanks

The issues I now have is the eyes just don't look like they should, too big and there is just something about them that is not real looking any more. I did not try to "link" my pose for the eyes since I don't have a good result yet. However, the eyes move way out of place when any of my poses or store bought poses are used.

I am posting another picture showing how far I got. At this point I am not sure what to do because I have tried what I can using the translate and magnets. Any advice to get this down is appreciated. I just have not had this much trouble before with the eyes and don't know how custom character vendors here get them corrected.

Thanks for the help

I am posting an image of it fixed better, but still seems to be a gap in the eye corner area. The eye poke through is fixed though on top of the lash area. Not sure how to fix the gap because I tried the adjustment morphs above and could not get them closer with the X, Y and Z translate. Playing with the other dials distorted the eyes too much and changed how they looked.

Does anyone have any advice on this new image for correction or is that as close as you can get at times? I can try something else if you think it would help.

Thanks again for the replies, this is one of the first times I have had so much trouble adjusting the eye placements.

Here is an image showing the area I am talking about so you can see. I will also try to post a Material Room screen shot later on today.

Quote - Not too sure about the materials used in V4's eyes but it may be the Tear or Eye Surface.  You could be seeing the edges of either.

I know things have moved on a lot since the days of V3 but most vendors still have no clue how to set up eye materials, what with them having fake reflections/specularity  baked into the corneas and so on and - my pet hate - leaving Reflect_Lite_Mult checked on all materials.

Thanks for the reply. I tried to upload an image to show exactly the problem but every time I do Firefox locks up on me. I can post OK and other sites work fine for uploading images so must be something strange going on. Anyway, I should have been more clear, but the area seems to be the top eye lid near the outer corners of both eyes and about half way over on top of the lid. The mat for the eye textures and face look just fine and I checked them in Photoshop too and never saw this before. I am not sure what has changed or why this is showing up at this time.

Do you have any thoughts on the eye lids or what I can check? I don't know what else to do because everything seems fine with no obvious reason for this problem.

Quote - **3DNeo...My information isn't FALSE as you have called it.
**Fact is, and it is a fact no matter how you don't like it, I haven't seen any of those problems and I use "Shader tree" each and every time I import my Poser stuff.
You can look at all my gallery and many of my forum posts where I state many times that the "Shader tree" has been used.
Maybe you have problems, I don't...

**Vue 7.x was buggy and did have import problems, IMO versions 8.x have largely seen those problems vanish with various updates.
**One of the reasons I asked the OP what version he was using..
And for the record, Yea I know there are issues with the SDK, I was told that "stock answer" from the e-on techs too..

I must say that you are giving out FALSE information here. Yes, it may work for you, but that does not negate the fact I have documented several known bugs as stated and they have been OFFICIALLY confirmed by e-on as KNOWN problems now. This is not just something I am saying because I think it is so, this is something that was PROVEN. Now, if you want to believe you know better than e-on and the tech guy working on the code that confirmed my reported bugs and was PROVEN to be problems, then I think you may want to retract your comments.

Again, all of this was well documented over on their web site long ago and I was the first to do extensive testing with their tech on this. Here is one of the OFFICIAL reports straight from the source:

"*I tested your model and noticed that these blotchy patches are also present in Vue 7.5. In Poser, the material editor shows that the diffuse color is the result of a blend of two nodes (image map + spots). In Vue, those spots are too dark. As the materials are rendered using the Poser Shader Tree, I reported this bug on the Smith Micro bug base.

One thing you must know about Poser imports in Vue is that it mostly depends on an SDK (Software Development Kit) provided by Smith Micro. It's a black box that allows Vue to have some functionalities of Poser. The latest one was added in Vue (build 51713) to fix the annoying "Hulk Effect" that several users reported (and complained about!). It was also supposed to bring support for Poser 2010. Instead, many users are now very upset because other bugs appeared (crashes, OOM errors, Poser features not properly functionning...etc).

It is best to leave "Poser Shader Tree" turned off.

Best regards.
Nick Deafman*

I tried using the Universal Pose python script and it batch converted my old V3 custom poses. However, it really did not do anything that just loading the pose on a V3 and then re-saving the pose did. They looked nearly identical using these two methods and turning on/off "use limits" did not help either. Basically, they simply are way too messed up still using these two methods and it would take just as much time doing them over as it would to try to make them correct.

Is there any way to improve my results? Does the PhilC "Puppet Master" work much better? I did a search and found several posts on this saying about the same thing, but I was not sure if anyone has had very good results using a certain method or a certain program if one is available that would work well.

Thanks.

Quote - I can recommend puppetmaster, made by PhilC and available at content paradise. Works very easy and it has batch processing AFAIK.

best regards,

Bopper.

PhilC is not listed as a seller at Content Paradise web site. Can you give more details or a link?