Difference between revisions of "Wishlist"

From X-Moto
Jump to: navigation, search
Line 14: Line 14:
  
 
  Comment : Has xmoto ever been profile to find possible bottleneck ??
 
  Comment : Has xmoto ever been profile to find possible bottleneck ??
 +
 +
Comment : as someone stated in the first comment, if it's slow, it's probably because
 +
of an old non-opengl video card, although there's a large number of unoptimized parts.
 +
The development philosophy has generally been to focus on making a game, rather than
 +
making efficient code that runs on ancient computers.
  
 
* Practice mode where the game can be saved in the middle of a level.
 
* Practice mode where the game can be saved in the middle of a level.

Revision as of 17:14, 14 August 2006

  • Water - slows your bike down ;)
  • Jumppads
  • display speed
  • display max jump length
  • Ice (less friction)
  • Customizable driver-to-bike ratio (game is easier with a driver that is short relative to the bike). To keep hiscores comparable, make the ratio depend on the level.
  • Customizable natural constants (gravity, air resistance, acceleration etc). Make them depend on the level.
    • You can change the gravity using lua script with the 0.2.0 version of xmoto
  • Possibility for the level designer to prohibit the use of 'rotate bike' buttons (left and right arrows) on the level. The author of across has stated that the rotate buttons were originally a kludge to make the game easier.
  • System requirements down! The game is rather simple, and the requirement of a 500Mhz proc. is simply ridiculous.
Comment : who has a computer slower ?
In fact, if it is slow on a computer, it is mainly because of the graphical card which must allow 3D acceleration.
Comment : Has xmoto ever been profile to find possible bottleneck ??
Comment : as someone stated in the first comment, if it's slow, it's probably because 
of an old non-opengl video card, although there's a large number of unoptimized parts. 
The development philosophy has generally been to focus on making a game, rather than 
making efficient code that runs on ancient computers. 
  • Practice mode where the game can be saved in the middle of a level.
  • Display during replays which controls were used.
  • Unicycle mode for experts.

Done

  • Moving obstacles (a la drawbridges), maybe the ones that repeat a sequence would be best for the game.