Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  Games  |  Strategy / RPG  |  The Restaurant Game  |  A Failure on a 12" G3 iBook

The Restaurant Game

The Restaurant Game

collaborative game development research project

Version:  1.9.1

   [ Views: 610 ]

A Failure on a 12" G3 iBook

Feedback Type:  Commentary

Contributed by: Tony Walton Tuesday, March 13 2007 @ 11:02 AM PDT

Product Platform: MacOSX

Used Product For: Have Not Tried

Recommend Product: NO

Appears to start up on my G3 iBook running 10.3.9, though the screen layout places wgat appear to be control buttons so far over to the left hand side of the screen as to be unreadable. Then it crashes in the image rendering code:
Thread 0 Crashed:
0   com.garagegames.torquedemo 	0x002ae324 Blender::blend(int, int, int, unsigned short const*, unsigned short**) + 0x4
1   com.garagegames.torquedemo 	0x002d27ec TerrainRender::buildBlendMap(AllocatedTexture*) + 0x14c
2   com.garagegames.torquedemo 	0x002d98d8 TerrainRender::renderBlock(TerrainBlock*, SceneState*) + 0x1708
3   com.garagegames.torquedemo 	0x002c7f10 TerrainBlock::renderObject(SceneState*, SceneRenderImage*) + 0x110
I won't be buying this one when it's released   

0 of 2 users found this helpful.

Rate this Commentary

Was this Commentary helpful? Yes | No

Comments

3 comments |

A Failure on a 12" G3 iBook - Tony Walton

Ah. I just realised it says it requires G4/G5. A bit of "check what processor you're running and fail gracefully rather than blowing up with all smoke coming out of the back" code wouldn't come amiss, though!

Reply to This

Tuesday, March 13 2007 @ 11:20 AM PDT


A Failure on a 12" G3 iBook - jorkin

The product requirements specify that you need a G4 or G5.

Reply to This

Tuesday, March 13 2007 @ 11:30 AM PDT


A Failure on a 12" G3 iBook - Tony Walton

Indeed, and my subsequent comment makes it clear that on re-reading the requirements I now realise this. I repeat: A bit of "check what processor you're running and fail gracefully rather than blowing up with all smoke coming out of the back" code wouldn't come amiss. Simply allowing an app to crash is inelegant in the extreme.

Reply to This

Wednesday, March 14 2007 @ 04:07 AM PDT