Bad Company 2 has finally been released. Since I passed on Modern Warfare, I hoped that Bad Company 2 would be everything I wanted.  As reviews for the game came out, I realized that at least one aspect of the game did not meet my expectations.  But overall, it appears that the game got good reviews and most importantly it does not have any deal breakers for me.

The Bad

Before the game was released, I had see online reports that Bad Company 2 was going to support up to 40 players on the PC. But unfortunately, it seems like the game only supports 32 players now. Even though this is still better than the measly 18 players for Modern Warfare 2, I am still disappointed that it’s not 40 players.

The Good

Destruction, destruction, destruction.  Can’t really say this enough because almost everything can be destroyed in the game.  No words can do this justice so just go out and find a video where you can see this happen!

Although 32 players are not as good as my expected 40 or 64 from other Battlefield games, I will give this game credit for increasing the number of players for the PC.  The xbox and playstation versions of the game are limited to 24 players which is too bad.  But understanding that the PC can handle more and actually using that power is just a smart move on the developer and should keep the PC gamers, including me, happy.

Conclusion

I will be giving this game a go as soon as soon as I get my new graphics card.  I’ll see you on the battlefield solder!

gnome-screensaver-command --lock

or

xlock

But if you ssh into your linux machine to activate the screen lock or screen saver, you might run into this error:

** Message: Failed to connect to the D-BUS daemon: dbus-launch failed to
autolaunch D-Bus session: Autolaunch error: X11 initialization failed.

or

No protocol specified
xscreensaver: Can't open display: :0.0

You have to set the DBUS_SESSION_BUS_ADDRESS environment variable in order the command to work.  You can find the current running DBUS address by first getting the process id of the running screen saver.  Then grepping for the address in the environ file.  The following script will lock your linux terminal:

#!/bin/sh

PID=`pgrep -u $USER -f "gnome-screensaver"`
DBUS_SESSION_BUS_ADDRESS=`grep -z DBUS_SESSION_BUS_ADDRESS /proc/$PID/environ`
DBUS_SESSION_BUS_ADDRESS=`echo $DBUS_SESSION_BUS_ADDRESS | sed -e 's/DBUS_SESSION_BUS_ADDRESS=//'`
export DBUS_SESSION_BUS_ADDRESS

gnome-screensaver-command --lock

Holy remote locking Batman!

Well today Modern Warfare 2 has been released! So I decided to poke around the internet to see what the word is. And my verdict is… not recommended.  I have decided that I will not buy Modern Warfare 2 based on two main deal breakers.

Deal breaker #1: 18 player limit

Say what!  That’s right, it appears that Modern Warfare 2 is limited to 18 players.  Not 18 players on each side, but 18 players total, that’s 9v9 tops.  Personally, I love playing with a huge number of players because it just feels more like the scenes from the movie Saving Private Ryan.  And I think that’s awesome.  I love the concept of organized chaos which is what you get from 32 or 64 players duking it out while sub-dividing into miniature rambo teams.  With a maximum of 9 players on your side, half of them may be dead at any one time so that really leaves you 4 guys running around at a time.

If you’re a console guy, then you’re probably saying what’s the big deal?  And I would say it’s not a big deal to you.  For console games, this is pretty much the norm and this is what you expect.  More power to you.  But I am personally a PC guy and I am accustom to games that support up to 64 players.

Deal breaker #2: no dedicated servers

Initially I didn’t even know what this meant.  This basically means Infinity Ward, the creators of the game, will not have any game servers setup for people to play on.  The game is designed to be hosted directly on one of the client’s or player’s machines.  So yes, one lucky player in a given game will be hosting the game.  Based on my experience with FPS games and ping, this may give an unfair advantage to the player hosting the game as his ping will be virtually zero.  I have on many occassions, when my ping was super low, been able to defy death, almost in an omni-potent way, seen hoards of enemy shooting at me but always missing, as if they were targeting thin air.

Conclusion

A good summary is the title I have been seeing around the internet… Modern Warfare 2, DOA.  For those who are unfamiliar with that acronym, it stands for dead on arrival and is a common phrase seen when purchasing computer hardware.

Check out the funny ratings from GameSpot and IGN.

Ratings from GameSpot and IGN

For now, I will be waiting for Bad Company 2.  While I have read that it can support a maximum of 40 players, the game is still to a bit too far from release to know for sure.  So hopefully it won’t let me down.  If it does, well there is always Modern Warfare 1.

Finally, here are some direct quotes that made me laugh (disclaimer: quotes do not necessarily represent the author’s opinions):

• Take $60 out and burn it…least you get warm -zippythezip (GameSpot)
• it’s like mw but then crippled -ATFNeOpHyTe (GameSpot)
• Screw you consoles!!!!!!! -ZeppelinE6 (GameSpot)
• outside of consoles this game is already DOA -doorules (IGN)
• If I wanted to play 9 vrs 9 on small maps I would just reinstall my old Doom disks. -jdwksu (IGN)
• Complete and utter failure, a 10 year step back in PC gaming -Liksecken (GameSpot)

Holy bad PR, Batman!

Allow comments option

Seeing this option, it’s easy to assume this enables comments on your wordpress Pages, especially for the default theme. But unfortunately, this particular option in the admin page has no affect on the default Kubrick theme. To enable comments on your Page(s), you have to select a theme which includes them or modify your default Kubrick theme.

Default theme with page comments

To change your default theme, add the following line to /wp-content/themes/default/page.php

<?php
/**
 * @package WordPress
 * @subpackage Default_Theme
 */

get_header(); ?>

    <div id="content" class="narrowcolumn">

        <?php if (have_posts()) : while (have_posts()) : the_post(); ?>
        <div class="post" id="post-<?php the_ID(); ?>">
        <h2><?php the_title(); ?></h2>
            <div class="entry">
                <?php the_content('<p class="serif">Read the rest of this page &raquo;</p>'); ?>

                <?php wp_link_pages(array('before' => '<p><strong>Pages:</strong> ', 'after' => '</p>', 'next_or_number' => 'number')); ?>

            </div>
        </div>
        <?php endwhile; endif; ?>
    <?php edit_post_link('Edit this entry.', '<p>', '</p>'); ?>

    <?php comments_template(); ?>
    </div>

<?php get_footer(); ?>

Additional References

http://wordpress.org/support/topic/246879

http://wordpress.org/support/topic/196788

I noticed last night that my wordpress is not generating thumbnails from uploaded images like it’s suppose to. You’ll noticed that the size options (thumbnail, medium, large) are all disabled except for the full size.

After doing a lot of searching, I finally found out that in order for wordpress to generate thumbnails “by default”, you need to have GD library support for your php. It would have been nice if wordpress had documented that better.

The only reference I found was this:

http://wordpress.org/support/topic/235625

To be clear, wordpress does not generate thumbnails by default unless your php instance has GD support.

Install php gd library

For me, installing GD library was easy:

# yum install php-gd

Check for gd

To check if you have GD loaded in php:

# php -m
[PHP Modules]
bz2
calendar
ctype
curl
date
dbase
exif
ftp
gd
gettext
gmp
hash
iconv

PHP Warning:  preg_match_all() [<a href='function.preg-match-all'>function.preg-match-all</a>]:
Compilation failed: this version of PCRE is not compiled with PCRE_UTF8 support at offset 0 in ...

I am running apache 2.2.8 and it uses the built-in version 5 of pcre.

http://httpd.apache.org/docs/2.2/new_features_2_2.html

The problem is that version 5 of pcre does not contain UTF-8 support.  So I had to recompile apache with a newer version of pcre. Luckily I have pcre 6.6 already installed on my linux box.

>> rpm -qa |grep -i pcre
pcre-devel-6.6-2.el5_0.1
pcre-6.6-2.el5_0.1
pcre-6.6-2.el5_0.1

So all I had to do is re-compile apache with the “–with-pcre” flag.

./configure --with-pcre

If you don’t know what version of pcre your php is using, create a phpinfo script and hit it with your broswer.  You should see…

Happy compiling…

Another important factor for me was the ability to customize the software.  Not only the legal ability but also the ease to understand and change the underlying software.  Not being a php guy, I’ve been pleasantly surprised how easy and straight forward to understand and modify the code base.  The bad part is that it looks very much like procedural spagehiti code resembling much of what you would see if a java web app was written completely in jsp.

Just a few weeks ago, wordpress 2.8 came out.  So I installed the new version and it seems like a lot of the buggy admin functions are now fixed.  Using wordpress 2.7, I felt a lot of the backend pages had bugs.  Luckily for me, 2.8 came out at the perfect time.

You can find my old website here: old.chiaocheng.com. It going to take me some time to move everything over.

And guess what, you just read my first ever blog post!

Happy blogging.