I'm having trouble with DAZ's Magik Poseable & Conforming FX Figures - ps_ac191 The fireballs when rendered in Vue are within an obvous semi-transparent cube. No matter what I do to the textures, ie transparency settings, etc the cube is still visible. Also are Eon ever gonna fix mover's missmatch between Vue and Poser reflection settings, or do I have to move to Bryce. I'm just getting sick of changing those same shiny textures all the time, I thought I purchased mover to do the damn work, not me.

I can't say anything to the fireballs. But what i don't understand it why you blame Vue for a Poser problem? It is Poser that strangely does the reflection black and with much too high values. The Render engine of Poser corrects that probably automatically so that it looks ok. But the fact still is that Poser writes black highlights. Full stop. And Vue interpretates that correctly. Anyway, i would really love to see how Bryce deals with that problem. And however the result looks like, it is a difference in the render engines that cause the problem (sort of). I am not happy with this situation and wanted always an option to copy specific attributes from one material (object) to the next one so that it will be a little easier to handle. Maybe it is a good idea to check wether it is possible to write a Python script to do that automatically. An expert of Python can answer that perhaps.

I guess I'm of the opinion that the software has to do the work for me and not the other way round, otherwise why use the software? So Poser does textures a weird way, if you make a plugin for a particular package then make it and make it work! Eon decided to make the plugin, so they have made it their problem now. Lets face it except for the ability to import animations mover is not that rare an application anymore, and more competition will come (I hope). Dont get me wrong, I like Vue and Mover, but its about time they dealt with this. The world doesnt stop for anyone or anything.

You are absolutely right. But what is the solution? I know that you are not a developer - as i am not - but how does it have to be changed? What is a reasonable value for highlight setting? That works for skin maps and others the same way. I only have problems with human skin textures, the animal skin maps i use look mostly ok. Do the have to be changed as well? I prefer solutions that leave the original data as untouched as possible. But i want an option that I can change settings quickly to my needs. I decide, the software follows that. Not another automatism that does things out of my control!

Well something is going to have to change either the texture that imports into Vue or how Vue treats textures. I'm guessing that changing the texture may be the easiest option, I'm just not skilled in 3d application programming to be able to give an informed opinion on this. Are there any informed opinions available?