This one has been puzzling me for ages. Whenever I create a Vue 6 Infinite (or V5I for that matter) scene that includes Poser 6 figures, and I save it with the "Incorporate Texture Maps" box checked, it doesn't embed the textures used by the Poser figures.

I often share scenes with a colleague, who has to re-map each texture individually, assuming she even has them on her system (she also has V6I and Poser 6). And vice-versa. This had us pulling our hair out with V5I and Poser 5 as well.

Does anyone else out there have this problem and / or a workaround? I was hoping that there would be some option in Poser 6 to "incorporate texture maps" like Vue does but I can't find it... (or in the manual).

Any help gratefully received!

My guess is that you still have the connection to the Poser file "alive".  Means, you import a pz3 and leave this as it is then. The intention to keep the connection is that you are able to work on the Poser scene later ans the Vue content is updated then automatically (Vue detects the changed pz3 and asks then).

What you should do is to import a Poser file and then directly save the import as vob with the embedd texture option on. Then load this vob and work with that furtheron.

The only case when this is not working for me is when there are textures missing in the import and I do NOT do a search for them. The reference to this missing texture then is in the Vue scene and it will always ask for the texture, whenever I (or someone else) open this scene.

The other case where the link can not be broken is when you work with animations.
Then the pz3 file HAS to go with the Vue scene because Vue reads the animation information from there.

Oh, another trick might be to simply ungroup (and regroup) the imported item. Then the link to the pz3 and to Poser is broken as well.

Thanks Wabe,

Saving the pz3 as a vob is such a simple solution that I didn't think of it! I'll give it a test.

It's a shame that animations require a live link to the pz3 - but this wouldn't be such a bad thing if you could bundle all of the pz3's textures into one file - making portability much easier. Does Poser 7 offer this?

I've just seen the latest newsletter from e-on, which mentions the Ranch Computing render farm, and it looks like they will only accept a single .vue file. A shame if you have a complex animation with lots of animated Poser characters!

Cheers,

Tom

The problem with the animations is that Poser saves the animation part as well in an external file (I think with the extention .dyn) So to find this, Vue needs to know what the name of the original file is - and therefore asks for it.

Because of exactly the issues you face right now - missing textures etc etc etc the render Ranch is a little more strict than others. Think about when you forget one texture, they render the scene (automatic process) and you are then not really happy because something is wrong in the result. What discussions about who is paying for what. Would you want that as service provider? I don't and therefore totally understand that they protect their service against all this.

And no, no change in Poser behavior as far as I know. Information is spread out in several files. Maybe as well a sort of protection. To make it a little more difficult to pass items on to others. Which of course is illegal.

I can completely understand why the Ranch only want to accept a single .vue file!

I'm just musing on a way to get an animated Poser file to be incorporated into a single .vue file to I can collaborate more easily with colleagues.

As to why Poser cannot create a single file which contains all geometry, animation and textures is quite beyond me though. Sharing Poser files that you have created completely yourself (or based upon the characters that ship with Poser) is not illegal, certainly not here in the UK!

Well, in principle you are right. Of course and I am totally with you. But unfortunately e-Frontier is not, they prefer it obviously the way they do it, files with different content everywhere so that it is hard to find the elements. Even when there are programs that collect the parts for you as far as I know (not on Mac unfortunately).

With the copyright it is as well not so easy. I agree, Poser probably allows what you say, even when I have not read their EULA. But I have Onyx TreePro Studio and was VERY shocked when I installed it and used it first time. TreePro is a plant generation program, in my eyes the best and easiest available. But all models you can create are based on standards that come with the program. And Onyx proclaimes simply all copyrights to them because of that. They do not allow any exchange of their models with anybody. Result? They are almost unknown and XFrog gets all the honor. Wether local law overwrites this is not sure. I asked some lawyers once in Germany and they told me it is not legal what nyx does. But do I want to try it out? Not really.