Within the confines of Pixel Fish Studios rages a small yet heated battle. It’s not political, religious or even about sports. No it’s about something much more important- 3D software. In our studio the heavyweights are Maya and Lightwave and the smack talk never seems to die. Now to be honest, we’ve been moving away from Lightwave because of certain issues with UVs and game design, but it’s still considered a competent tool and it was the only thing we used for many years. You might say Lightwave has that old flannel shirt feel to it.
But when we were hired to do the Alpine Village previsualization project, it was naturally assumed we’d easily go from the architect’s program to Maya for texturing and rendering because after all, Maya is the “best” (so we’d been told). Except that it wasn’t. Time and time again the file import resulted in mangled meshes, missing UVs and head scratching.
So what does one do when faced with repeated Maya failure? Yep, Lightwave to the rescue. The pipeline plan changed to include both Maya and Lightwave and proved to be incredibly successful. So why do I even bring this up? Because it goes to show that all options should be placed on the table. Pride could have easily gotten in the way on this project. And while I’m sure an all-Maya solution could have been found, the better way was to fall back to an old friend.