This was done by two people in one month. Once everything was decided, programming took an additional 40 hours of work to finish the functionality and polish it for final release. After this was done, 35 hours were spent drafting GUI concepts and discussing core functionality approaches for the coding segment of the program.
How long did this take to make? 130 hours were spent developing a rendering system to handle thousands of rendering passes with consistent naming patterns to assist in exception-based situations for our source code. It simply couldn't be achieved in Photoshop on a dynamic basis. This is all only 1/7th of the shader components. This is blended over the base alpha channel of the diffuse map as a further mask, and within this is masked area is our actual raytraced reflection for our HDRI environment. The reflection channel for the base metal shaders is masked using a fresnel method, and within the masked reflection is a composite material that uses RGB instances of the selected colours for Primary or Secondary. The long answer: If you apply a colour and try any method of blending, it won't look accurate. Why not just apply the colour in the program after the render is done? Unfortunately, it isn't that simple. 
3,659 render passes were run across 241 folders in our current hierarchy system.
If you rendered every component in every colour, wouldn't that be thousands of images? Absolutely. With that in mind, we do plan on having future iterations of the program utilize DirectX for a more intuitive menu animation system. Because of this, we decided to even the playing field and composite stacked images. Though some people may have a machine that could comfortably render our shaders and meshes at 30fps without a problem, many people are on integrated graphics controllers still and couldn't even process some of the most fundamental of our shaders properties. Not render this in DirectX? Unfortunately not everyone's GPU is the same. Whether Bungie changed this system for security purposes, or simply because it made more sense due to the increased level of customization, we don't know. Bungie changed this in Halo Reach to be a hashed base64 using a custom key. 
This is wholly the foundation on which the previous 'armor generators' were based off of.
Make this? Unlike Halo 3, the images on are not encoded URLs that allow for simple variable changes to alter the image being rendered. After this is done, we "stack" the layers to give the representation of a composite render. We render every component that is customizable in every colour available in Halo: Reach. 
How does the program work? The functionality behind it is simple.What does this program do? Vanity allows you to quickly preview a final-armor set while giving you a clear path of how to get there.
0 kommentar(er)
