Can anyone explain howcome a game can have system requirements lower than the GP2X, but then when ported the game plays slow on the GP2X?
The example I have in mind is Quake 2. The requrements to play this game in software mode are:
* Windows® 95 or NT 4.0 with 100% compatible computer system
* Pentium® 90 MHz Processor (133 MHz recommended)
* Memory:
Win 95 - 16 MB RAM Required (24 MB recommended)
Win NT 4.0 - 24 MB RAM Required
But as far as I know the current Quake 2 for the GP2X is quite slow.
Is making a fullspeed Q2 (that uses software mode) for the GP2X a matter of optimising code, or is there more to it?
Is the Pentium (or AMD or insert other PC processor here) itself just better at doing certain things than the GP2X ARM's - regardless of speed?
The main reason I ask it because a small minority of the GP2X population here DO have a love for 3D (yes, even if it's on a handheld) and considering what a good engine Q2 was, maybe software Q2 could be used as a base engine for many GP2X specific 3D games (as in, designed for the 3.5" screen and Gp2X controls in mind)?
The example I have in mind is Quake 2. The requrements to play this game in software mode are:
* Windows® 95 or NT 4.0 with 100% compatible computer system
* Pentium® 90 MHz Processor (133 MHz recommended)
* Memory:
Win 95 - 16 MB RAM Required (24 MB recommended)
Win NT 4.0 - 24 MB RAM Required
But as far as I know the current Quake 2 for the GP2X is quite slow.
Is making a fullspeed Q2 (that uses software mode) for the GP2X a matter of optimising code, or is there more to it?
Is the Pentium (or AMD or insert other PC processor here) itself just better at doing certain things than the GP2X ARM's - regardless of speed?
The main reason I ask it because a small minority of the GP2X population here DO have a love for 3D (yes, even if it's on a handheld) and considering what a good engine Q2 was, maybe software Q2 could be used as a base engine for many GP2X specific 3D games (as in, designed for the 3.5" screen and Gp2X controls in mind)?