Lights Off Settings

Working on all sorts of things at the moment, but here's a quick preview of the Settings pane for Lights Off. This might give you hints towards the directions being taken for Lights Off 2.0. Enjoy =)

Blog Update

You may have noticed some recent changes to the appearance of the blog: • Firstly, all my current and upcoming applications are featured prominently at the top of the page. This allows you to click on an application to display any blog posts about said application. Will be a great navigation tool for people wanting the up-to-date information about certain applications without having to sift through the other blog posts. • Secondly, my latest Twitter tweet is always displayed above the latest blog post. This is a running commentary of all things related to me, and as such can often include valuable nuggets of information about any of my iPhone applications. I hope these two additions will combine to make this blog more friendly for new visitors, especially as the App Store will direct customers to this blog for more info about any of my applications. This isn't just a static webpage, it's a direct conversational approach to customer support and I hope it will stand by me in the long term, and of course allows me to post screenshots and/or videos to help out. All my open source projects will be hosted on Google Code as and when I can make them public. I will provide more information and proper links in the sidebar when that occurs. Until the next update! -out

Speed Testing

So, guess what, it works, and is pretty accurate too (I presume this is GPS-compatible only). It starts to register changes if you're going more than 4km/h from what I've seen, so that must show the accuracy of the GPS receiver inside iPhone 3G. Even better, you'll see this app on the App Store as soon as Apple OK it =) My first App Store release, and yes it's free.

MobileNuker

So… who's been a naughty boy then? I continued work I'd spent on iPhone OS 1.0 on porting a WinNuke app to the device, for proof-of-concept purposes only. What it does is uses the RPC out-of-bounds exploit existing on Windows 3.x, Windows 95, Windows NT 3.x, Windows NT 4, and Windows XP. On XP it causes a svchost crash, meaning the computer does a forced-shutdown with a timer to alert the user. On the earlier platforms, it causes an instant Blue Screen Of Death. No this app will never make its way to App Store, don't ask =) Will be hosted on Google Code as with my other open projects. I did a quick n' dirty video capture showing it in use, no smoke and mirrors; it's just a straightforward port of the Linux/Unix code. The target is XP SP0 running in Vmware and using shared networking. YouTube Video: http://www.youtube.com/watch?v=Rt4_zO0hmV8

SpringBoard Icons

Stack Update

So, currently, SpringBoard goes out of its way to kill any GUI app that dares not be launched by it. So still no update on the feasibility of getting Stack working as a daemon. Otherwise, the UI stuff is up and running on 2.0 with both fan and grid view. Interesting menuing system to add to an application perhaps?

[MobileDoom] UI Update

Just working ideas out, here's a look at the current build:

Options

As mentioned earlier, the use of either rendering mode in Doom is up to you at compile time:

Whither CoreSurface?

The iPhone Doom port is knowingly destined never to hit the App Store, so one important question is asked:

Should I use only official (read SDK/NDA) APIs, or should I branch out into other APIs to make the game run faster?

I can't honestly answer that. I enjoy having the preference in my code, and I intend to let other have said preference when the code hits the GoogleCode project site.

So, built into the code is an #if switch, allowing you to choose whether to use the UIKit (and completely App Store-allowed) API or the private CoreSurface screen buffer API (being private, the only documentation comes from the iPhone Open Toolchain and is not covered by non-disclosure).

CoreSurface is a direct and insanely fast screen buffer, allowing you to draw graphics as fast as the hardware permits and without having to go through the CoreGraphics layers directly. Similar to the iPhone OS 1.0 code, the game can render into a CoreSurface buffer which is then displayed inside a Core Animation layer. Why would I bother doing this? For a software-rendered game like Doom, it's an order of magnitude faster than what I must do for UIKit (rendering the buffer directly into a CGImageRef and blitting that to the screen). CoreSurface is what many of the unofficial emulators and game ports use, including Zodttd's brilliant Quake 1 port to iPhone.

With CoreSurface enabled in Doom, the framerate is super-smooth and the colours are as they should be. So I will leave the option in the code for budding developers to play around with. And here's hoping Apple are given some impetus to make CoreSurface available through the public SDK, as I think the benefits would be very welcome.

[MobileDoom] Accelerometer+Landscape

Just playing around with possibilities atm, using the accelerometer for controlling forward walking and standstill (backwards doesn't seem to work in Doom code… will investigage). Large touch targets for turning and shooting, have tried accelerometer based turning but wasn't impressed, but we'll see.

Bonus Side Effect! Doom 2 Running =)

Looks like the iDoom source has full doom2 support, so I loaded in the doom2.wad game file and it seems to be working great!

[MobileDoom] A few more gameplay shots

Well, it seems to be working alright, no crashing so far. Even managed to get to Level 2, so I think this code handily beats our original port ;-) Apologies again for the even weirder colours this time, I'm poking around trying to get the right set.

Doom's Working =)

I swapped out the engine code with that from iDoom 1.3 and ported over the iPhone glue code, and now I have a fully working game with sprites, enemies, door opening, and controls. I'll have to keep working on the palette stuff as the colours are rather off, but I'm rather pleased at getting it all running through the SDK =)

I hate the Doom engine (aka, John Carmack, fix my code please =)

Right, so, I finally managed to get drawing moved to UIKit from the private CoreSurface APIs in Doom, and get meaningful output. I spend an hour working out iPhone OS' button mechanisms (very nasty btw, no [self action] or [self target], oops, NDA), finally get really nasty looking but working controls so I could test the rest of the game and performance, and GUESS WHAT? Some nasty bugs (most definitely my fault due to hacks used for iPhone OS 1.0) in the WAD/sprite engine mean that no in-game sprites show up. No items, no keys, NO ENEMIES. So, while the levels are playable, you're pretty much flying blind until I go back and undo the damage. But hey, it's actually up and running. Once I have the whole lot finished off, I'll make sure to post the code back up to the googlecode repository where the 1.0 code lies. Until then, have a screenshot. A nasty, yucky screenshot. But a screenshot nonetheless =)