Hello Igors,
5. Better texture/shader transfers. We’re all aware of the UV coordinates issues within EI. The procress of bringing in models with UV textures is getting better but without an internal editor to EIAS..we’re still not there. Custom shaders within Maya and EI can’t be exchanged and this is on of the reasons to justify texture baking. If someone is using a custom shader within EI and wants to bring the look of those shaders into Maya, a way to bake out the shader into a texture map that can be applied within Maya via UVs could be helpful. Maya already possesses texture baking capabiltiies and a method to ensure the transfer of those baked textures into EI could be useful.
More ideas anybody?
This is PARAMOUNT!! TEXTURE IMPORT for hard body surface modeling is ABSOLUTELY PARAMOUNT.
I have to take off the gloves here for a second. This should not be a problem with a App that would seek to position itself as a “hard body surface renderer”! How do you take a big file with lots of parts and not import the textures?
How does that make it an alternative? Texture is one thing, Materials is another.
EI should at least be able to get a scene in EI first so people can take advantage of it’s poly count management.
Then I can see EI making better money to support their Renderer. It’s the little things folx. It’s the small fox’s that destroy the vine. How we play with the big features with small features are trying to hold us back? This should have been taken care of first. You can’t take advantage of EI’s ease of use interface, massive poly count managements, render feature unless you can the SCENE in the app. Once the scene is in then get you can have assess to color features, or EI assest. Bind the strong man first then set the captives free.
I have been so busy wailing over character features that I havent’ seen how someone of the obvious stuff when it comes to rendering is lacking. It’s workflow not just features that shut us out.
