fixed it thanks

The jumppad should work allright. I tested it at home with a NVIDIA 6800 with recent NVIDIA driver for Linux and at the ofice with a GF2 with recent NVIDIA driver for Linux too, and the jumpad worked allright. While testing I discovered that jumping sideways or backwards I could even jump on the big column. Jumping backwards of sideways, results in a higher, further jump (!).

However, I have a laptop with a onboard Intel graphics chip. And on that machine all my jumps are lower. For instance I can't jump in the well in Smalltown, which is 5 cubes high, and I can't jump at higher level in Arena01 either.

I assumed that the Intel graphics chip, or the Linux driver for the chip did the opengl support wrong.

But you tod me you have a NVIDIA card too. So this is a interesting issue. Jumping seems to be different on different computers !

I assume you have recent drivers.

O ... deleted te readme.txt ...

It´s not a driver issue,
you probably get high fps? 200 or so?
That makes ppl generally jump higher, also when using jumppads.
When making a map, make sure the jumppads will get you up at 30-40 fps, but also won´t make high fps ppl bump against ceilings..
It´s got to be tried out..
It´s easier now with the minmillis command.

High fps ?

Before the jumppad, almost 400. Because of the standard minmillis value of 5 in the new Cube. When I set mimillis to 0 I get more then 700 at that place :)

Well, by raising minmillis I can get my fps down and test. I raised the jumppad from 40 to 44, that should work with fps 33 and up. I also updated Smalltown. Lowered the well, which is a a shortcut to the quad. So that should be reachable by all to.

Another thing to think about, when mapping. Who said mapping was easy in Cube ;)

Another thing to think about, when mapping. Who said mapping was easy in Cube ;)

It is easy, except for those (really) annoying Cube bugs. This behavior of FPS affecting jump height is really annoying.

crazytb,
Those aren´t "annoying bugs" as you call it.
In every engine the mapper has not only to map, but also has to take responsibility for the engine´s very own properties.
And cube is a darn easy engine to map for. Go map for doom3 and you´ll see what I mean. As a mapper, you have to know your engine´s technical side and its limitations aswell.
It´s a technical thing, so you will naturally get technical issues to solve at some point.
The fps thing is by far not as annoying as you put it.
Physics are influenced by fps, in any engine I´ve seen so far, that´s why most (and cube too after the release) have ways for the user to cap it. And furthermore, it´s not ard at all to adjust some jumppad values to make them work properly for low and high fps...

I also updated Smalltown.

Suggestion: next time post a comment on your other map too, saying you've updated it.

Site administrators: put some "last updated" field somewhere on each page, so we can know whenever the author updates a script or map or guide.