inoremap / battlestar-tux Goto Github PK

What steps will reproduce the problem?
1. Remove yaw rotation limit on hex cells.
2. Limit movement of cells on y-axis.
3. Collide multiple cells.

What is the expected behavior? What happens instead?
Cells will collide with some rotation, depending on the angle.  No cell
will rotate very quickly, and the straight angles on the cells will usually
"catch" one another.

Due to the cylindrical collision shape currently in use, the cells will
often rotate very quickly when they catch each other at the wrong angle. 
There are no straight angles for the cells to catch.

All settings should be available to users, even if not visible through
in-game GUI.  A human-readable XML file is clean and easy enough for users
to modify.

What steps will reproduce the problem?
Im trying to make 3D noise using raw_noise_3d, but I think the function is not 
working propertly for me. 

What is the expected behavior? What happens instead?
Im expecting "random" values in range <-1; 1>, but what i get is attached. 
Value is returned value and x, y and z are inputs. I think there is too much 
zeros and lot of values is repeating, dont know why. So is this normal, or what 
could be wrong?

What version of the product are you using? On what operating system?
Im using rev. r0843926209e2 on Windows 8.1 x64 and Im testing in Visual studio 
2013.

Why is this new feature necessary?
XML will not provide good performance for network messages.  Additionally, 
there are 
other libraries, such as Protocol Buffers and Thrift, which provide an 
interface for RPC.