Apperently "cube mapping" "cube sampler" and "texCUBE" is probably related
to something special called "cube mapping"...
It might still be usefull though for access the individual elements of the
surfaces, if and only if the direction vector from inside the cube can be
calculated in such a way that it always lands on the desired cube texel ;)
Though that could get pretty tricky to pull off...
So maybe CUBE is not that usuable... and I might have to fall back to
texture3D which could create a whole range of new problems if it indeed is
0..1 and limited to power of two textures ! yikes ! ;) :)
Maybe larger textures then the ammount of gpu memory are possible ? like
512x512x512xwhatever... maybe the gpu card will swap from main memory to gpu
memory as needed ?
I doubt it though... since I already saw it fail once... when there were two
very larger textures ?!? or maybe it was because vertex buffers can't handle
4096x4096 verteces ?