MUNKIKI DOWNLOAD

Additionally in the game it was required that there be a 2D view and a 3D view. I also dallied around with the concept of writing an obfuscator for the game. Archived from the original on 18 January For some reason, I also remember getting really bad stomach pains for two of the days I was over there - that wasn't fun at all. This page was last edited on 23 September , at

Uploader:	Tabar
Date Added:	10 August 2010
File Size:	32.18 Mb
Operating Systems:	Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads:	37244
Price:	Free* [*Free Regsitration Required]

First things first - course storage.

Munkiki's Castles : Nokia : Free Download, Borrow, and Streaming : Internet Archive

It also can store up to 10 notes as reminders and has customizable and downloadable profiles. Back when I was doing Wentworth Golfthe java, course data and images stored on the server came to about KB when zipped up. Slick and I ended up going over to Copenhagen to the Nokia offices there for about a week to work alongside the people making the handset to try and polish off a lot of the development and I think almost every evening on our walk back to our hotel we had the same discussion on how to get the renderer working faster.

Most the others I could probably go back to now, years on, and find some way of adding a new handset specification to - with this, eurk, I wouldn't wish that on anyone.

Nokia 3410

The last game where I had to worry about black and white handsets. However, rendering on this device is only displayed on lower polygon count since it uses software renderer and it runs slower than other mobile phones that supports 3D graphics. Real world example - if you wanted to store the detail of 50'x20' rectangular swimming pool, you would get a piece of graph paper and write X's in a 50x20 grid - that's hugely wasteful - you'd store corner-position: Not a bad thing, you might think, but generally the colour phones had larger screens too, and we didn't really make any effort to enlarge the images, so on larger phones the game tended to have a very 'letterboxed' feel to it.

We're on our way to crunch stuff down.

From Wikipedia, the free encyclopedia. I feel sorry for Steve who had to come along later and put it on some other handsets - as a studio, we didn't exactly have a great deal of munkikj porting experience then, so I was kinda making up ideas as I went along.

There was the downside that on the higher spec handsets you could clearly see the vectorisation of the map data see those jagged edges to things in the screenshots above!

And on top of that, it would be in 3D!!!

Munkiki's Castles

Views Read Edit View history. Oh sure, when we were doing later projects things like the and Siemens SL45 were still around, but the people who owned them weren't the people spending money downloading new games, so as revenue earners they were becoming a smaller and smaller part of the games market. Munjiki still being in black and white, and still having a 96x65 screen, it came with something akin to OpenGL-ES!

I was pretty happy with that. As a result, I got all 18 holes kunkiki data stored in less than 10KB.

Nokia - Wikipedia

Archived from the original on 18 January Or at least, that was quite large by mobile standards. Okay, so we'd only be requiring one course the illustrious Pebble Beachnot two like in Wentworth, but that still left a huge amount of changes and optimisation I'd need to look at. This could mean that downloadable apps were about to enter the mainstream a little more.

This page was last edited on 23 Septemberat And due to the deadline and importance of the project, we had two programmers working on it - Slick and myself. Another Java based mobile development system, it sounded like more handset manufacturers were considering taking it up and adding munkiko to their phones.

In the Velma game, we had a variety of charcaters with different facial features that we could draw tall or short, with glasses and without. Another project that we did with Digital MunkiikDB came to us with the Scooby license and asked us to come up with a game for it.

I also dallied around with the concept of writing an obfuscator for the game. The Nokia is a mobile phone made by Nokia [2] being the successor of the popular Nokia I really needed to crunch that course data down. Well, unfortunately, it meant that the code ended up being a complete dog and a mess!

You can't scroll more than a couple of dozen lines in this codebase without finding some " ifdef something-or-other" hack to get around the fact that all the phones were acting differently. And a lot of them weren't that great. By using this site, you agree to the Terms of Use and Privacy Policy.

It was a real pain, and conceptually not terribly well thought out, although it did work somewhat for this one project. Retrieved 18 January