fenglinnet / slimmath Goto Github PK

This is the current code

return (value1.X == value2.X && value1.Y == value2.Y); 

I think it should be 

return (value1.X == value2.X && value1.Y == value2.Y && value1.Z == 
value2.Z); 

Hi, I was searching documentation on how implement geometry of planes in 3D and 
I've found your project. A problem I've found is in aritmethic of planes. I saw 
that you scales a plane by multiplying the four coefficients by a given value, 
but if a plane is given by:

ax + by + cz + d = 0, we can see that

Value*(ax + by + cz + d) = ax + by + cz + d = 0

May you tell me what is the sense of this operation?

Thanks by your atention.

What steps will reproduce the problem?
1. create a project using slimmath
2. create a Color3 instance: Color3 exampleColor;
3. call exampleColor.ToString()

What is the expected output? What do you see instead?

expected: "Red:0.0 Green:0.0 Blue:0.0"
got: FormatException 
Exception.Message (german original): Der Index, basierend auf 0 (null), muss 
größer als oder gleich Null sein, und kleiner als die Größe der 
Argumentenliste.

rough translation: The zero based index must be greater than or equal zero, and 
less than the number of items in the argument list.

What version of the product are you using? On what operating system?
FileVersion: 1.0.0.0

Please provide any additional information below.

Used intensively whenever you need to deal with half floating point texture.

Classes are in SlimDX but not in SlimMath.

The code is an extract from SlimDX while using the following paper to implement 
the conversion : http://www.fox-toolkit.org/ftp/fasthalffloatconversion.pdf

What steps will reproduce the problem?
1. Perp unary operator missing
2. Enhancement
3.

Please provide any additional information below.

The Perp operator is missing. It could be useful in some geometry algorithms.
Here is what I'm referring to:

        public static Vector2 Perp(Vector2 vector2)
        {
            return new Vector2(-vector2.Y, vector2.X);
        }

It returns a vector perpendicular to the input one.
If it was implemented, it could also be used to implement the "PerpDot" product 
or 2D cross product.

Also, are there any plans to implement a double precision Math library?

The FieldPropertyDescriptor constructor is broken. Anything that attempts to 
use it will fail with a cast exception, for attempting to cast an object[] to 
an Attribute[]. Attached is a fix.

We need someone who has knowledge on the GJK algorithm to make an 
implementation of it in SlimMath. This will be very useful in the 
BoundingFrustum class and for several other collision facilities. Even a naive 
implementation would be great to at least start with.

Should make a Visual Studio 2010 specific solution file and project file like 
you did for the SlimDX project.

Not too important.

What steps will reproduce the problem?
1. Looked for integer Vector
2. ???
3. No Profit

What is the expected output? What do you see instead?
Integer vector. Like a normal vector but more integery.

What version of the product are you using? On what operating system?
Trunk, VS 2010

Please provide any additional information below.
foo[v.x, v.y]

Hi josh!

I'm back here :)

Plane class is missing the following constructor that is sometimes useful and 
is part of SlimDX.Plane

/// <summary>
/// Initializes a new instance of the <see cref="T:SlimMath.Plane" /> class.
/// </summary>
/// <param name="point">Any point that lies along the plane.</param>
/// <param name="normal">The normal vector to the plane.</param>
public Plane(Vector3 point, Vector3 normal)
{
    this.Normal = normal;
    this.D = -Vector3.Dot(normal, point);
}

Hi,
During all operation of multiplication i've noticed that i'm getting some 
overlapping result if i
send the same matrix as ref and out, XNA does not overlapping, probably before 
assign of result you should
assing temp float values and after that store them to final result;

Ex:
Matrix left = Matrix.Identity;
Matrix right = Matrix.Scaling(1.0f,1.0f,1.0f);
Matrix.Multiple(ref left, ref right, out right);

In this case right is overlapped.
This happens with all ref passed parameters.

Thanks

It seemed the function 

bool RayIntersectsPlane(ref Ray ray, ref Plane plane, out float distance)

in Collision.cs is incorrect.


It should be

...
distance = (-plane.D - position) / direction; 
...

Please check it And thank for great work.  :)

This line reads:

ClosestPointOnTriangleToPoint(ref sphere.Center, ref vertex1, ref vertex2, ref 
vertex3, out point);

should instead read:

ClosestPointOnTriangleToPoint(ref vertex1, ref vertex2, ref vertex3, ref 
sphere.Center, out point);

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

The Quaternion.SquadSetup method fails the new VS2010 test. The test is 
performed against MDX 1.1 which in turn uses D3DX. Some of the values tend to 
be close to the expected values while others can be pretty far off.

Someone with more knowledge on this method should take a peek.

The current Half type is incomplete, many operations defined on other number 
types are not defined for the Half type. It's also incorrect in places for 
example == should return false if both arguments are NaN.

Included is a patch for a more complete Half type, operations on it return 
floats in a similar way to how operations on Int16 return Int32. It is an 
immutable type in the same way that all basic number types are immutable, this 
is a breaking change as it means removing the setter for RawValue. It also 
includes basic Math methods Abs, Max, Min and Sign.

See corresponding SlimDX issue: 
http://code.google.com/p/slimdx/issues/detail?id=688

Should we append the word 'Create' to the static methods of the Matrix, 
Quaternion, etc. that create specific types. For example:

Instead of Matrix.Scaling we could have Matrix.CreateScaling. This more closely 
matches Xna's style.

This would clearly mark the methods that create specifics types of matrices and 
it will also alphabetize all of those types of methods together.

Just need some input before I start making those kind of changes.

or cake.