Quote - To save just material settings, you need to have the Material library selected (Poser itself has never been able to save MAT poses).

To save the clothing plus materials, you need either to have the Figure or Prop library selected as appropriate for the kind of item you've created.

Sorry, but not sure I follow. I do not want to save the actual cloths, which are figures not props, only the material for them and the settings. In other words, make it just like the ones in the market here that are texture packs for cloths which are put in your "pose" folder that apply the textures to cloths already made as a PZ2 file.

That is what I am not sure how to save because when I try to save my cloths materials in the "pose" library it does not work for me or keep the settings I have made in the material room.

BionicRooster -

It would help if you could post some "Material Room" screen shots of how you have the nodes setup along with the image maps in the small menus displayed. That would give me some more to work with and help see how you did some of yours.

Thanks.

Thanks for the help on this and the images too. The effect I was sort of after is like what BionicRooster did with the skirt. If I understand, to get this type of look I would make a transmap for the clothing item black in the areas I want to be transparent and white for the areas of the outfit I do not. I can also control the intensity with the "Transparency Falloff" and link to the trans map I used for the regular transparency map?

I am trying to get an outfit that has textures of satin and velvet to be transparent to some degree (say 50%) for the satin parts of the outfit and have some of the velvet areas to be solid with fully tranparent areas in specific spots of the outfit.

pjz99 -

The clothing on one of the oufits is sort of like what you have posted here. I will study what you said there too, but I am not clear on what effect this had on the outfit. Are you talking about the texture of the green areas here or the bare skin areas? Not sure what you are trying to do here with that image is why I was confused.

Thanks for the tips on using the Transparency Maps. I am trying to get an outfit to look  semi-transparent in specific areas and others to be more transparent or solid. Also I have been reading about what each of the channels does in the material room but it is bit complicated unless I can see something like it done on another clothing item so I can see the basics of how it was done.

So far I have managed to get the clothing material I used on an outfit to look transparent, but I seem to lose some of the texture on it when I do. I tried to adjust the "Transparency Falloff" which I can see makes adjustments for more or less when linked to my Transparency Map, but still working to figure all this out.

This all depends on the end result and how it is done. But if it does not work well or takes more time in the process, I see myself doing the whole model in ZBrush and then just making the textures for it as needed. When in ZB4, I have done very high poly models just because I need close up and great looks. It also depends on what you want to do. I have a VERY high-end main production computer with two additional render nodes for network rendering. Everything is possible, even very high poly models with lots of detail and complex scenes if you have the equipment for it.

Like I said though, will have to wait to see how this will turn out.

I have hundreds of items in my Poser Pro 2010 library and custom organize them myself with no problems. It is no different from the way I custom organize all my folders for photos, music, etc. What I found works for me is to keep everything in one runtime folder that is stored on my server. Then I make the directory structure of the runtime what I want it to be such as libraries/pose/v4/clothing, libraries/pose/v4/poses, etc. and make a structures the way I want them to divide. Others may like their methods best, it all depends on your work flow. For me, I have been a programmer for years and have my system organized how it works for me.

Hope things work out for you too.

Yes, that fixed it. I put the files in my Poser Pro 2010 program folder, NOT the content folder. It works now.

Having a problem though. I followed your videos on the web site for doing a conversion using FBM. However, my character name morph is not there like it is in your video. I did all the same steps in video 2 on your site. When it asked to add the WW morphs, my morph analysis of the figure was not there, say the name of it was "Jennifer", that was missing the others were there.

The only thing I oculd figure out was to add another step to what you did in the video. After you do the character figure analysis you immediatly went to converting clothing. What I did was insert a step where before you convert the clothing, you run the "Analyze Full Body Morphs", then proceed to convert the cloths as shown in video 2. If I do this, I get the "Jennifer" morph dial, otherwise it is not there.

Is that a missing step in your video2 or am I missing something? Is that a proper method to convert the cloths? Just want to be sure I am doing it right.

When you say "Extract the zip to your Poser 8 folder" in the readme file for the move script, where exactly do you mean? In other words, I have two runtimes, one where Poser Pro 2010 installed that has no content and another where Poser Pro 2010 placed my runtime for Windows 7 use in the "Documents" folder. Do I place the zip files in the "Documents" folder with my runtime content there or in the "Program Files" directory?

Thanks.

Quote - I received the email to get the final version, however the link points to my 8.5 version and not ver 9.  Hmmmm.

 

i did send a ticket in, I was just wondering whether others got this also, or am I special?

No, the same thing happened to me and it appears to be everyone I talked with so far. It's the same trouble they had before and their links and servers are messed up again. I don't think they have ever gotten it right the first time around. We should see an email correction soon though. :)

When I inject the morphs you sent me, I get an error saying it can't locate a .jpg file "cools1" I believe the name was or something like that. If you need the exact name let me know and I will do it over again. Kind of strange because I don't know if the morphs are linked to any .jpg files.

Let me know what you think about the eyes and if they look OK to you. I moved them as well using your morph and also did so on the translate dials.

Thanks.

Quote - > Quote - No matter what I tried though, I still could not get the corner eye tissue to have a skin color, it only renders white. Not sure why that is because I have seen some character here with a lacimal skin tissue color to it. Although, it is just a little.

Whoops. I think I misunderstood your original post "Here, I am trying to get it to look like the lacimals are a bit wider** from a photo reference I have". I thought you were wanting to change the size of the lacimals, not the colour!

If you post a screen shot of the material set up for the lacimals, it might give us a clue as to what's wrong.

No, you were correct, they were two different problems. First, was the size and shape of the eye corner lacimals  Second was the fact no matter what I tried it seemed the eye lacimals did not render any skin color, only white. I think you may have fixed the first problem with the morphs. While I did not have much time today to do much due to Election Day work, I did test it and think this may help. As to the color problem always being white, I will check the material room and post a screen shot of the lacimals to look at later this week per request.

Thanks again to all for the help.

lesbentley,

Thanks for the work and help on this. I will give this a try tomorrow and let you know. I did scale the eyes and also moved them on the x and y translation but this was as close as I could get.

No matter what I tried though, I still could not get the corner eye tissue to have a skin color, it only renders white. Not sure why that is because I have seen some character here with a lacimal skin tissue color to it. Although, it is just a little.

I will play with this some and post a reply. Thanks.

Quote - E-on relies on 3rd-party developers for a lot of their code in Vue and in their servers.  E-on can't write it all themselves.

Their servers have nothing to do with Vue itself, you can hire an outside firm to maintain that.

It is VERY easy for any good company to write import code. We are not talking about doing it all from the ground up with a new Vue program. A decently skilled programmer should be able to do this with no problems at all. Hoever, e-on has proven to be not as skilled in comparison to others. What they really need is a new team to come in with fresh eyes and take 1-2 years to go over the entire program and fix everything that is wrong. I know there are many like myself that would not care if any new features were added but instead had a much better and reliable program.

Quote - why do they have a poser option and promote it when it dosn't even work then?

now i cant finnish my project i was working on 

First, it does work, but it works with issues and is speratic in doing so. Second, you have to know how to work around all these issues. For some things you can and others you can not. An example is the "Poser Shader Tree" issues I found. When Neil at e-on and myself went through all the problems, the only work around was to NOT use that option when importing. Instead, you will need to tweak all of your materials for your Poser PZ3 import by hand. You can't really group them together if you want to tweak individial materials so it takes a VERY long time to work through them all. If it worked, it would save you a lot of time for your scenes.

The issues with OOM are random, sometimes it is OK other times it will crash. Neil told me they knew about this one and the latest SDK from Smith Micro they used for Vue 8.x was to blame. He also said there was no "official" support for Poser Pro at all at that time. Instead, using Poser 7 to import Poser Pro 7 or Poser 8 to import Poser Pro 2010 may or may not work. I found it all depended on certain things and Poser Pro 2010 would not work at all for me with that version of Vue.

The one thing I do NOT understand is how you can charge that much for your software and still be depending upon another company for an SDK to use with your program. Other companies do it better or at least have more 3rd party options. One company that gets it right most all the time is C4D and I have not had issues with Poser imports with them at all. I tried to get an answer from e-on as to why they don't write their own Poser import code and have full control of it. I don't think e-on will ever give a good answer for that one.

There is a whole discussion thread that e-on left on their site if you look at the technical posts there. I was assigned a tech, Neil, by e-on nearly a year ago. The reason is I was the first person to EXTENSIVELY report and prove numerous bugs with Poser importing. After sending many source files to them, Neil told me the problems I uncovered went all the way back to Vue 7.5 and there was basically nothing e-on could do about it. Those problems included: Random issues with importing PZ3 files, Poser "Shader Tree" issues, re-size on import scaling problems, random OOM errors and more. At that time, he said it was due to the Smith Micro SDK e-on uses as the code base for integrating with Poser. They had many issues with it and they said it is unknown when or even if Smith Micro will release a new SDK for programmers.

I found the "Poser Shader Tree" had issues they did not know about even though it appeared to work fine. It was a skin texture and node settings that get totally messed up on import into Vue 7.5 - V8.5 that Neil confirmed. You get what appears to be spots or blotches, more noticible on darker skin textures at times. Again, this was nothing Neil said they could fix and said Smith Micro would have to do so.

He reported all bugs I found to Smith Micro so IF they are using a NEW Smith Micro SDK for Vue 9.x then hopefully it will help some and perhaps some of those bugs were fixed. So far I have not gotten any OFFICIAL word from e-on about this but I have contacted them to find out what the SDK is now.

To find more go to the user matainence forum at e-on where my threads are. A few may also be on their technical search too. Good luck, I will report my findings once the FINAL version ships.