Stencil
This operation is similar to the Normal function where it uses A to cutout a spot in B (B*(1-a) = C) If the alpha is some other value than 1 or 0, it gets multiplied.

Add (plus)
This is most arguably the second most used operation. (A+B=C)
This gets used in places such as adding specular or reflection highlights. However, it should only be used when working in floating point values because the final pixel can exceed the normalized 1.0 threshold and create superwhites. If this operation is used in an 8 bit image, it can often get over-exposed and washed out, which is not desirable at all. To fix this there is another function called Screen.

Screen
Screen offers a solution to working in LDR images. The math is as follows ((A+B)-(A*B)=C It does not allow a pixel value to exceed 1

Multiply
Straight forward enough. (A*B) Multiply uses a conditional that tests for negative numbers and coverts them into zeroes which prevents C from becoming a negative value. It is most often used to composite dark elements against lighter backgrounds. Multiplying is often overused in compositing and can often lead to degradation of the final output. It best serves in the texturing phase. ]]> http://jdbeals.com/blog/archives/202/feed 0 http://jdbeals.com/blog/archives/197 http://jdbeals.com/blog/archives/197#comments Sun, 20 Jun 2010 04:01:04 +0000 admin http://jdbeals.com/blog/?p=197 Progress on the shoe has been painfully slow, but my internship at Adidas is up at the end of the month, which means that I will no longer have a job which equals more time to work on the shoe. Here is an update of where I am at. So far I like how it’s coming along. It’s incredibly difficult not to get any lumpiness and to stick with a good edge flow without getting crazy dense in areas that have holes. The places where the laces go through the eyelits were by far the hardest to keep smooth, and I tried a couple different approaches, as you can see in the image, and eventually went with the high dense, not as pretty way that is nearest the toe of the shoe. It kept things perfectly smooth without any pinching or wobbliness, but I did take a hit on the poly count. *ouch* My tri count is at 144K right now and I haven’t hit the high detailed areas yet, nor have I added in the stitching :/

This detail shot of the shoe is maybe an inch across and 1/4 inch width and maybe a couple mm deep and is locate on the sole of the shoe.

Adi_test_intro from Jonathan Beals on Vimeo.

This .ma was almost 400 megs and it was too big to open for notepad, but astonishingly wordpad was able to open it (doh!). This file was over 500,000 lines long, so long that wordpad had to open it in sections and ended up taking about 20 minutes to fully open. Generally an .ma is structured in this way:

Basic File Info (name, date etc…)

Camera nodes and tranformations

Other node information (creation, transformation)

Lights

Layers

Histories of objects

Animation Histories

ConnectAttrb of lights/shaders/materials

Now granted this information could be off and should taken with a grain of salt, but GENERALLY this is the order.

Since I knew what killed it (MergeVertex), and where it was located, I scrolled down near to the bottom and searched for “MergeVertex”. I found it and deleted it then saved but it still didn’t open. So I figured it had to be linked to its history so I deleted the entire history of the object and all of its connections (basically the entire last bit of the .ma). Be very careful when you do this and make sure the structure stays in tact and semi colons and such remain in the right places.

After this I was then able to open it up. Everything was in Chaos-all my display layers were deleted, things were misnamed-utter chaos and of course no materials existed on the objects. But this was fine, since I had prior working scenes and I just needed to export and import the object that I had been in the middle of working on when Maya died.

So in Conclusion, make sure you save an .ma at least once per work session and if you do need to root through one, especially if it was as big and scary as mine, do it smartly. Know what you are looking for and where it is located. If you are not sure what caused it, it usually is one of the last things you tried to do.

Also, a lot of times fatal errors can be caused by conflicting preferences so move your preferences and try and opening the file first and see if it does it, if not move your preferences back and start rooting away!

Oh and if you notice, you can see in the center of the area light is a bright point. You can see this strongly because the softbox that is in front of it, intensifies this flaw. This proves that area lights in Maya emit more from its center and not uniformly. Can’t wait for 2011 to test this out with the new physically accurate light.

here is the actual shoe more or less (found the pic on the web because I’m too lazy to upload one of my own):

Here is the image:

and here is the article

http://mentalraytips.blogspot.com/2008/11/joy-of-little-ambience.html

my notes continued.

So say you have a point on a surface and you want to find out how much illuminance it is getting. What we do, is look at the light source and see how big of an angle it covers. We take that angle, multiply it by the amount of luminance the light has and you get the illuminance value at that point. If the light source is bigger, it covers a larger angle. If the same light is farther away, it covers a smaller angle which means the illuminance of that point is lower. Distance is irrelevant actually. All that matters is the size of that angle. A large light from a far distance and a small light at a near distance that covers the same angle and same luminance value will give the same illuminance.

You have heard the term “light falls of quadratically” or at least seen the option for the light in Maya (distance^2). This is actually a fairly inaccurate representation of the above subject. It is only accurate for distant lights. Example. You have a plane of light that has a length of X meters at a distance of Y from object P covering an angle of Z.  If you were to half the distance between the light source and the object, the angle of course gets bigger, and at far distances it’s really close to doubling the size of that angle Z. However, since the light source can never reach point P, that means the angle can never grow past 180 degrees. This means that for each time you half the distance, the degree that the angle changes will grow farther away from doubling and closer to staying the same.

Example. Walk up to a large light source such as a window or tv. Look at your hand as well as how bright the tv/window is and notice how bright it is. It has a specific luminance. Take two steps back and look at your hand, your hand will appear darker, but tv/window look to have exactly the same luminance.  This is because when you were closer, the light source covered a larger angle compared to your hand and when you stood back, it covered a smaller angle which means it will illuminate your hand less.

There are many ways to imitate this in CG. For MR, you have your final gather, photometric lights, and of course the beautiful and amazing Portal Light.

There is a big problem with traditional cg lights because they are point lights. Points cannot cover an angle to a point on a surface because it has no area which means it cannot emit any illuminance. This means the objects in a scene does not know what luminance the light has so it is faked. It also has an unclear mythical 0-1 value of color which is of course unrealistic (value of light is from 0-whatever). Lights also have strange falloffs (none, linear, or tries to do a distance^2 blindly). They are also rarely ever visible in a scene like they are in real life. When they are visible, their intensity is computed incorrectly. Even old MR. lights are buggy and hacks.

The reflections of the light source is generated by a fuzzy blob. This is a big problem because our eye uses highlights to judge an object and figure out most of it’s features. If we make it visible so it can be seen in reflections we run into major sampling issues.