bkil vs. programming

Here is a link where you could theoretically monitor Google outages: https://www.google.com/appsstatus#hl=en&v=status I had a problem with Google services just recently. However, as I wanted to verify whether the problem is on my side, this monitoring site was down as well. At the same time, the third party reports on alternative sites started to grow: http://outage.report/google http://downdetector.com/status/google http://aussieoutages.com/status/google This highlights why we should not put all our eggs into the same basket.

Runs very nice, at about 30-40 FPS on laser sniping, but only when the settings are adjusted correctly ! Out of box experience is garbage, performing something between 5 to 10 FPS on a random map, but of course a lot depends on the specific map. After going through hoops of tweaking, I went as far as uninstalling the game and completely giving up. That was until recently, as on second thought, I simply couldn't believe that such simple polygon graphics advertised to support legacy PC's chokes on a 3D accelerator. I gave it another try, and as how it generally goes, your calm mind works much better on the same problem after having left it get organized by your brain subconsciously over time. All in all, after literally toggling every option available from the GUI, I had to conclude that it wasn't the 3D effects which were holding back the computer or even the antialiased radar map in the corner - it was the overlayed bitmapped text ! At first I couldn't believe my ey...

My project has reached high activity status this weekend. I must thank all committers. Keep up the good work! ;-) Note that a major portion of my sources is still not up. Fortunately, gradual progress is easy and effortless. A central repository is a comfortable sharing method. It keeps the work synchronized on all 4 computers I regularly use.