I got that H2O, too was not water, but I didn't know what it was at the time. I've poured H2O2 in my ear to clean out wax though

Well, ndless doesn't have a math.h so it shouldn't be an issue. I have compiled programs previously that use math.c and math.h and they work fine.

Here's another problem I can't seem to figure out:

The compiler gives me the error "math.h:2:13: error: expected identifier or '(' before '{' token" and I have no idea why. Here's the entire contents of the math.h and math.c files:
extern float sqrt(float x);
extern long abs(long x);
extern float fabs(float x);
extern float sin(float X);
extern float cos(float x);#include "math.h"

float sqrt(float x) {
  float r = x / 2;
  int i;
  for (i = 0; i < 10; i++) {
    r = 0.5 * (r + x / r);
  }
  return r;
}

long abs(long x) {
  return (x > 0) ? x : -x;
}

float fabs(float x) {
  if (x > 0) return x;
  if (x < 0) return -x;
  return x;
}

float cos(float x) {
  x = x - TWOPI * ((int) (x / TWOPI));
  float x2 = x * x;
  return 1 + x2 * (-.5 + x2 * (.0417 - x2 * 0.00138));
}

float sin(float x) {
  x = x - TWOPI * ((int) (x / TWOPI));
  float x2 = x * x;
  return x * (1 + x2 * (-0.1667 + .00833 * (x2 - .0002 * x2 )));
}

I figured that out, and now I find it quite amusing how he compared his engine to internet search engines in the first video.

The model itself doesn't use polygons, it uses voxels. Let's assume that the elephant statue is contained in a 750mm (75cm) cube. The guy said there were 64 voxels per cubic millimeter, so that makes 75 * 75 * 75 * 64, or 27,000,000 voxels. If the voxel has a 32 bit color value associated with it, that is 102MB right there. On a disk, that number can be greatly reduced by not storing information about the voxels inside the model, which nobody sees, but in memory it pretty much has to be in a 3D array so the renderer can quickly access the voxel at the arbitrary point x,y,z. (Unless the breakthrough he is talking about is in searching for voxels in another way) Actually, now that I think about it, an octree could be used so empty/unseen space need not be stored. But there is still massive amounts of data to be stored for a whole level, so I have a feeling a lot of stuff will be repetitive.

Also, did anyone notice how that guy left out games that use tesselation? So far, it has been a great solution to the polygon budget issue.

Are those sold cheaper in China? I know China still has poorer areas that are being developed and some companies sells them cheaper stuff to still make money there, so maybe that's why they removed some features?

Nonetheless, this is interesting. I wonder if Ndless will be possible on those...

I'm guessing it's that too, although TI probably still makes a huge profit margin on calcs, they have to introduce a new product if they want to sell for a cheaper price in a certain area, or everyone will buy it for the cheaper price. I also wonder how well these will be adopted in China. I think America is starting to overuse technology in schools (things like smartboards are fine and useful, but using a wireless network of calcs to hand out math problems to a class or to take a vote on something is just overkill.), but I don't know about China.

Well, the rules do say it has to be a game, and the fact that it requires custom external hardware (not just using an adapter like on 8x calcs) means that unfortunately, it will most likely not get accepted. You could try making a simple game that has sound but is not required to play the game, though.