Unicode is a really great thing. It allows for a wide range of special characters and letters in different languages.
The problem is that is is messy to work with while programming especially when you want to create standardized code.
Anyway, I am working on a Linux terminal picture viewer probably because I’m enjoying using the terminal and sometimes need to see a picture file before copying it or moving it.
This presents a problem for text only terminals I need to view the image, especially if it has come from a digital camera with an odd name.
Here is the result of my tinkering you can see a standard ASCII version and a Unicode version using the braille letters as dithering patterns. Currently it is SFML powered C++. The image is the standard test image, “lena”.
So there you have it, a use for a very odd set of Unicode characters, the braille set.
An ongoing project is currently driving my crazy all because I’m missing one piece to make it work.
The idea is to provide a cheap and acceptable way to do 3D photograph construction and viewing with a single picture.
The idea is as follows:
1. Obtain a large mirror finish ball or hemisphere.
2. Place it on the ground.
3. Take a picture from directly above zooming in to fill the the view of the camera but not cropping the sphere.
4. Crop the image to a square keeping the sphere in the center.
5. Use custom image software that reconstructs the sphere from a polar image to a rectangular one – giving a full 360 degrees of view along the horizon with some acceptable distortion at the top of the image. This will not be as good as the effect constructed from 6 pictures but should give a complete 360 degree panorama from a single shot.
My problem is that I cannot find a cheap solution for a mirrored sphere or hemisphere between 8-18 inches. Currently I’m not working so a 20 dollar or less solution would be best.
Before I start, let me say I have NO RIGHT to tell you how to make games. These are just personal thoughts. Please take them with a grain of salt.
I have mixed feelings about the term “retro” as it has evolved into a gaming buzzword. Allow me to explain.
I feel that grouping older games into a single genre called “retro” is both ignorant and unnecessary. This is a common buzzword tossed around without a solid definition in order to sell games to the 25+ crowd. I see a lot of games that are called retro that have very little look and feel of the classic games I played as a kid in the late 80’s and early 90’s.
A game created in the 80’s and 90’s style should conform to a large majority of limitations of the time. I see a lot of games pushed out under the guise of being retro that don’t remind me of anything I played back in the early days. In those days we never saw 1000 sprites on the screen all being dynamically rotated and transformed with 32 bits per pixel. Clone games that run in absurd resolutions and have stiff unanimated smudgy 256×256 sprites being rotated in hardware are by no means retro. OK now that 2D is almost dead in the mainstream I guess it could be considered retro for what … the year 2005?
Please if you are going to call a game retro make it look and feel like it came from the early 90’s.
Even though I cringe at the term retro (it is not specific enough and groups entire genres into a mess by release date) the blow is lessened by the following.
My original sprite (yep some of my OLD art here!)
Adhere to low resolutions. (NEVER INTERPOLATE pixels use integer scaling and find the best fit for the window.)
Good clean integer scale.
If you are going to transform a sprite, transform it in the lower resolution before upscaling the entire screen to run in a modern resolution. Don’t have differently sized pixels … please. Rotating a sprite after scaling it into the display resolution will cause diamond shaped pixels and ruin the effect … yuck! Transform in low resolution then upscale the entire scene with integer scaling.
Now the retro feeling is lost, this should have been rotated in the low 1:1 sprite resolution not the display resolution!
Stick to color limitations, don’t go making 256×256 pixel smudgy Photoshop messes. Also don’t go making 256×256 pixel smudgy photoshop sprite messes then posterizing and shrinking the sprite to fit it into the game. Blurring the heck out of poor Mario won’t make him seem any more detailed in a higher resolution.
Uh oh… (Look just because it is bigger and more colors doesn’t add any detail!)