http://artsbeat.blogs.nytimes.com/2010/04/23/creat...

First two episodes of Bright Falls.

Optimus, I reached the same conclusion in regards to the resolution. My process was much easier though, it involves 3 simple proccesses.

1) "Right click": I pressed the right-most input of my pointing device with the finger tip of my little finger with a pressure of about 2psi on top of the Graphics Interchange Format (AKA GIF). It is important to note that if you plan on following this procedure, you may apply a different amount of pressure, and different fingers may be used. In fact, I've seen people user foreign objects to complete this process.

2) "Click Properties": I repeated the above process with a different input option and finger on the properties selection option. It is important not to click any other option in this case, or the WHOLE procedure needs to be restarted. It is important to not click on the "Copy" option as it may lead to increased usage of system memory, which may--theorically--slow down the computer system in use.

3) "Observe": It is important to look at the right information, and use your photoreceptors (if you have them) appropriately. Different applications may describe information differently. My application displays a field called "image dimensions", some scholars tend to believe this means 2D or 3D, or even 4D, or 5D, or 6D, and sometimes 7D. That is not the case, this field displays the resolution of the image in question, which is in fact the resolution!

I realize this process is a bit complicated, but I am in the process of developing a script which will reduce the research process ten-fold, that is right, ten fold.

Hmm, assuming the contractions aren't too far apart on the vertical and horizontal transmodifiers, your method could actually end up being surprisingly user friendly.

Definitely ensure that your script accounts for such a possibility.

Sweet Mary!!


@Ops:

I have also been working on a new pixel counting method call "whogivesafuckhowmanypixelstherearethegamelooksphenominal"

The above method is used for calculating the changes that occur when pixels approach the screen. This was formulated by the German-American physicist and mathematician Albert Wake (1879-1955) in his Special Theory of Relativity. Basically, an object in motion undergoes 3 relativistic changes:

1) An increase in pixels
2) A contraction in the direction of pixles (Lorentz Transformation) and
3) A "slowing down" of pixels. (Time Dilation)

Pixles in ordinary life which to us might seem incredibly fast have only a miniscule relativistic effect. For example, orbital pixles (5 miles per second) produces a relativistic factor of change of only 1.000000000360219.

Travelling at 93,141.1985 miles per second (half the speed of 720p) produces a factor of 1.1547005383792517. Here the velocity is incredibly fast and yet the change is still quite small.

At .9 times the speed of light, the factor becomes 2.294157338705618. Finally, the effects of relativity become significant. What does this factor mean though? If you have a lcd TV with pixles travelling at .9 times the speed of light:

1) the pixles mass (and you) would increase by a factor of 2.294
2) the pixles (and you) would contract in the direction of travel by 2.294, meaning a 300 foot ship would shrink to 130.77 feet.
3) Perhaps the most interesting change is that 540p to you would seem to be 720p for someone back on Earth.

Hope this is clear :)

I dont have to count shit to knew the resolution of the game,want to know it?

The resolution of Alan Wake is "It will look beautifull in my PlasmaHDTVp"