« September 2005 | Main | November 2005 »

October 28, 2005

Architectural walkthrough using Timesplitters

The game engines created for first-person shooters are also ideal for 3D architectural walkthroughs. Although I couldn't find any that had been specifically adapted for that use, I did find that the mapmaker provided with the Playstation 2 game Timesplitters: Future Perfect was sufficient for creating a customisable three-dimensional house to explore.

Even if you have the Timesplitters game, you probably haven't played with the mapmaker because of the exceedingly light documentation provided in the manual. To remedy this, I used the mapmaker FAQ from the ever reliable gamefaqs.com. Since you're building a house and not a scenario for battle, you'll find you can ignore large swathes of the document, but don't miss the juicy bits.

The key to building indoor and outdoor areas is to realise that your "blank canvas" is actually solid rock rather than empty space (- you're more like a sculptor than a painter). So, if you place a tile denoting open area, then you'll need to add open area tiles in all the levels above to be able to see the sky. In addition, these tiles must all be of the same type, eg. large open above large open, and small open tiles above small open.

Although there seem to be a lot of tile types to choose from, most are too specific to be used in creating a copy of a real house. Instead, use mostly small corner and small t-junction tiles to create whole rooms. Whilst you can't customise the textures used, you can specify the lighting type and colour, for example flickering lights might denote a room with fluorescents.

It's important to start building on the correct level, as you can't move whole floors after you've started. You only get 5 floors to play with, and the top floor will not have a roof. So, perhaps start by building the top (roofed) floor of your building on the second from top level, and work down from there.

Stairs can be tricky, because you can't place stairs directly above another set of stairs. If you creatively offset them slightly, then this shouldn't be too much trouble.

Finally, leave the doors and windows till last. Whenever you move a tile, the attached doors and windows are lost, so it'll save work if you leave them till the rest of the floor plan is set in stone.

I'm sure that there are some PC-based first-person shooters which would provide a more customisable end result, but I doubt that they'd provide such an easy tool for its creation.

October 19, 2005

Timer bug checker

This is a simple TAP for users of the Topfield 5000PVRt, with firmware from March 2005 or later. Under some quite specific circumstances a recording will fail, and this TAP will tell you when that may occur, allowing you to do do further manual investigation.

An ongoing discussion of this bug is occurring on the Topfield Australia forums (reg. req'd).

- set 30 minute timer for channel A starting at x
- set 5 minute timer for channel B starting at x + 2minutes
- set 10 minute timer for channel C starting at x + 9
- leave Toppy on live channel A
- start watching a previously recorded program
- see 'check your reservation' message at time x + 2
- start watching a previously recorded program
- at time x+10 or later stop watching

You can now switch between all live channels, even though you're
apparently still recording A and C. The end of the recording of A turns
into channel C.

(Problems are most prevalent when A = Nine, B= SBS and C=ABC, for reasons that are not apparent)

Requirements
A Topfield 5000PVRt with the March 2005 or later firmware.


Installation
Upload TimerBugChecker.tap to your toppy, to either your "\ProgramFiles" folder for manual
running or your "\ProgramFiles\Auto Start" folder to run automatically.


Usage
When run, the TAP will announce any possible times when this bug may occur. You
may then wish to remember not to be playing back a program at the time noted.

The TAP exits immediately after running.


Revision history
v0.1: 18-Oct-2005. Initial release.

Download
Timer Bug Checker v0.1

October 14, 2005

Firefox canvas demos

Mozilla Firefox 1.5 introduces the <canvas> drawing tag to play with. Apple's Safari browser already supports it, but until the strangely popular Internet Explorer does too it will have only limited usefulness. Nevertheless, that's no reason not to experiment.

After a brief play, I came up with some fractal examples.

Perhaps with universal browser support this will replace Flash. It's certainly much easier for a competent HTMLer to work with, with a minimal learning curve compared to any of the Flash creation languages.

Update 16 June 2006: Flame demo added.

Update 21 June 2006: Fractal zoom demo added.

October 9, 2005

DVI sparkles

As noted in a previous entry, I recently bought my first LCD monitor, a Philips 190B6CB 19". It is connected to my stoic old Gigabyte Radeon 9200 via a 2m DVI cable.

I found that I got lots of sparkles on the desktop, which worsened to huge flickering lines when I watched digital tv via my PCI tv card. A sparkle is a single pixel that flashes somewhat randomly between two colours. The sparkle is colour, rather than location, dependent. If it occurs within a picture on a web page, then scrolling down that page will cause the sparkle to move down too.

Sparkles are relatively common in home-theatre installations where the DVI cable lengths are extremely long. They indicate that the signal is not strong enough to propagate the length of the cable. This can be cured by installing an active DVI repeater. In my case, the 2m cable was far too short for this to be of relevance.

As I mentioned in the previous entry, after some investigation I worked out that I had to untick 'alternate DVI operational mode' in the Catalyst digital panel settings. However, I also found that fullscreen 3D programs only worked when this option was ticked. Otherwise, the screen would go blank after flickering wildly on startup.

My thoughts were that if this was caused by hardware, ie. cable, video card or monitor, then it wouldn't be fixable by a Catalyst driver setting. An answer to this would be found if I could determine what that driver setting actually does, but I was unable to discover this.

As a test, I replaced my 1.5 year old $100 Gigabyte Radeon 9200 with my brother's 1 year old $300 Asus Radeon 9600XT, and found that this completely eliminated the visual errors. My current theories are that the latter card provided a stronger signal, or that its signal was more compliant with standards.

Update (14 Oct 2005): Setting the display size closer to the LCD's native screen resolution also improved matters somewhat. It's hardly a great solution, but might be a useful temporary fix.

Update (18 Oct 2005): After having major flickering DVI display problems when I upgraded my Linux partition from Mandrake LE 2005 to Mandriva 2006 I found a plausible explanation from a disgruntled user. Related bug entries in the X.org database are 1129 and 1829.