Is there a way to reload the Poser Shader Tree after making changes in the poser file? And this without having to delete the character and importing it again?

If you edit the materials of the character, you break the connection to Poser for this material, so no, there is no other way than reloading the figure. If you change the figure in Poser, same you need to reload it in Vue, if you don't have the advanced browser module, I think it's called "Deep access", or Vue Infinite.

No, i'm working with Vue E. They could have add a button "Reload Poser files". It would be very useful!

I have Vue 6 Esprit and I'm getting ready to buy the Deep Access module (to go along with my Ecosystems module and the Botanica module) so that I can synchronize textures without having to reload.  That's why I haven't reposted my last image yet ... just waiting for the $$

I would be curious to know if the Deep Access module helps with the total mess that seeems to come with loading textures on Poser scenes right now. I know e-on is working on patch, at least according to forum notes over at Cornucopia, but if this would help, I might spring for it myself.

The neat thing about Deep Access is that it synchronizes the textures so that, if they're modified outside of Vue, they reload inside Vue without having to re-import the Poser characters.  That's the main reason I'm getting the module, along with Light Tune.  I don't have any problems with textures coming in wrong but I don't like to have to re-import the pz3 if I modify the textures in Poser.

My problem is Vue can't seem to find my texures most of the time. I put most of my stuff in the Download runtime instead of the main one, and Vue can't seem to deal with that. It says it can't find the texture, even when the path is says it can't find is the path it needs. Worse, when I save a file with a Poser figure in it, when I reopen the scene, it wants me to reload every farking texture manually, even though again it says the path it can't find is the path the texture is at. Sorry - ranting. But this is frustrating for a program who's big strength is supposed to be a nice, tight integration with Poser. Ok. I'm done.

All my stuff is also in the Download runtime, but i never had to localize manually the maps.

Hey, vincebagna - are you using Vue 6 Infinite or Espirit? I have read that the Vue 6 Infinite version handles this better than Espirit right now. Just curious.

I use multiple external runtimes for my Poser stuff and save my pz3's to a specific file when I know it's going to go into Vue.  I don't have any problems with textures not loading or with Vue 6 Esprit asking me to locate the textures for any particular pz3.

My suggestion is to make a folder somewhere you'll remember and save your pz3's to that folder if you plan on importing them into Vue.  This is what works for me the best but it might not for you if Vue is always asking to locate the texture files.

For my part, i use Esprit. And i also save my pz3 to a folder dedicated to that, just to be a little organised :D

But i never had problem loading any pz3 files. Never be asking to localize  anything manually.

I have read somewhere that Vue doesn't support multiple Poser runtimes. I found that the hard way when I upgraded from Poser 6 to 7 and I wanted to keep both runtimes separated. I started having a mess with Vue imports, I searched for it and I found in some knowledge base (e-on?) a specific note saying that.

Regarding reimport of Poser characters, I have V6I and I just save the Poser file again and Vue automatically asks me if I want to reload the character. It's reloaded in exactly the same place as I had placed the old one in Vue. Of course, I can not break the connection to Poser by manually changing anything, like ungrouping or such. If I do that, I do a very simple trick: I center the object I want to replace, in all views, I delete it, and without changing anything, I reload the new character. Choosing the option "center object", it goes to the exact same place as the old one was.

Vue 6 Pro Studio is quite happy with multiple runtimes - I have about 7 of 'em.  I just need a lot more RAM so I can actually import some things without causing Vue to freak out

Here's an extract from e-on support knowledge base, statement from e-on team on January this year, regarding V6I (but probably applicable to other V6 because they all probably use the same SDK):
http://www.e-onsoftware.com/support/ShowMessage.php?id=1169748339&stage=-1&chooseCategoryPage=&categoryName=&category=&subCategory=&superCategory=
"It may be that the current Poser SDK we use is not compatible with multiple Poser 7 runtimes. This is mainly because the SDK is basically designed for Poser 6, so there are still problems with Poser 7. We are still working on this along with e-frontier to improve the compatibility with Poser 7."