SilverTile needs your help!

9. mars 2010

A few days ago I discovered a very interesting project. Ryan Corradini has a project named Canvassa that is a HTML5/Canvas based Zelda clone. He does more or less the same thing I do with SilverTile but his approach is quite different. His blog is quite interesting and especially the posts about reverse engineering the game map based on a huge picture was very interesting.



Inspired by Ryans posts I wrote a simple C# program that would parse the entire map for The Legend of Zelda (I found the map here) and spit out tile images and Xaml code that SilverTile could utilize. (More on this in a later post - it was quite fun actually!)

The entire game world - click the image for the full 4096 pixel wide version


With this in place I think SilverTile is ready to be tested by a broader audience than me and a couple of friends. So that is where you dear reader come in.

I need you to test out two versions of SilverTile, one running under Silverlight 4 beta and one running under Silverlight 3. If you only have Silverlight 3 installed then just run that one. :-) What I am after is feedback on wheter I need to optimize the game engine or not. In its current state the engine is full of naive implementations that could probably be easily optimized, but I don't want to spend unnecessary time on it. I am also interested in getting feedback on the game engine itself. Does it work? Is it playable? What should I change?

Monsters! This is what awaits you if you move left from the start area


Once the game is running you can control your character using the arrow keys. Move to the open edges on the screen to visit other areas of the game world. If you move to the left you will face hordes of enemies and if you move up you will face a few enemies. All other areas are empty, and you cannot fight the monsters at the moment. If you die just reload the page to start again.

What I want you to do is the following:

  • First move around the screen and see if you can control the player sprite properly.
  • Then move up to the next area and see if the monsters run around more or less randomly. If you run into a monster your life (the hearts) should decrease.
  • Then move back down and to the left. Here you will meet a huge number of monsters. Watch the monster counter and let me know how many monsters there are when the game starts to feel sluggish. Aslo watch the frame rate counter in the bottom of your browser window. It should be around 38-40. How long can you survive before the monsters eat you?
  • Finally explore the map a little and see how this works. Does the game engine crash or behave strangely?


When you are done testing I want you to leave a comment to let me know what kind of computer you are running and what your results were. I am particularily interested in hearing how many monsters the game engine could handle and if you experience anything strange. Which operating system and browser you are using is also interesting.

Click here for the Silverlight 4 version and here for the Silerlight 3 version.

Thanks in advance for helping!

kick it on

.NET, Silverlight , ,


10.03.2010 11:47:50 #
I'll be the first to comment myself.
On main computer with a dual core 3ghz processor and 4gb ram I saw no slowdowns with 50 monsters on screen in the Silverlight 4 version. On the Silverlight 3 version I reached over 60 monsters before I died and still saw no slowdowns. I am running Windows 7 x64 Ultimate and tested the game in both IE8 and FireFox 3.6.
10.03.2010 12:58:21 #
Another comment from me using my EeePc with a single core atom processor. When I went past 20 monsters some animations started to skip frames, both on Silverlight 4 and 3.
I tested the game in Google Chrome 4 and everything appeared to work properly.
10.03.2010 13:30:02 #
This is cool mate!

Moving around is fine. I have to click on the SL app first though and then get scrollbars. Auto focus on app?

Monster creation, never seems to get sluggish.

Frame rate hovers around 35-40. When I get game over (35 monsters :p) it jumped to 68fps. I can only use Silverlight 3 right now - just installed VS2010 RC and it doesn't play ball with SL4 as you tweeted before...

Using the work PC you know and love only using Windows 7 Ultimate on separate HDD. FF 3.6

10.03.2010 13:40:01 #
SilverTile needs your help!

You've been kicked (a good thing) - Trackback from
Jan Magne
Jan Magne
14.03.2010 23:44:26 #
Interesting project.

I did some testing on two different computers with Silverlight 3 and moving around works well, but damage dealt seems to be framerate dependent. On machine 1 I would consistently lose only half my life after being run over by a monster (standing still at the right-edge of the monster spawning area). On machine 2 I would sometimes lose all my life or somewhere above half my life.

Machine 1: Windows 7 x64, Core i7 2.66 GHz (quad-core, hyperthreading), 6 GB RAM
- Chrome Died at 83 monsters, no slowdown noticed. Couldn't find the statusbar in Chrome so I have no idea about the fps.
- Opera 10.10: Died at 79 monsters, no slowdown noticed. It was running at 40 fps all the time.

Machine 2: Windows XP x86, Pentium M 2.13 GHz (single-core), 2 GB RAM
- Firefox 3.6: Died at 81 monsters, frameskipping first noticed at 11 monsters. It was running at max. 30 fps and between 25 and down to 15 fps in the monster spawning area.
- IE 6.0: Exactly the same as for Firefox 3.6.
16.03.2010 20:57:25 #
Thanks for the comments! I got a few comments via email as well and it seems that while the game engine works well on faster computers it needs some optimizations to work well on older hardware.

Hopefully it will be fast enough to run on the Windows Phone 7 Silverlight. Smile
19.06.2017 08:07:53 #
Diamond earrings and diamond necklaces - or any form of earrings or necklaces, for that matter - remains hidden for the majority of the day and is really more goodies for everyone else to enjoy them the actual recipient.
27.02.2018 06:30:09 #
Thanks friends, for providing such enlightening data.

Add comment

  Country flag

The number (5) not with letters. This is to stop spammers.

  • Comment
  • Preview