Hey,

I'm wondering how should I get around with those types. I've read that I should use XMFLOATs in classes for storage purposes but for calculations convert it to local XMVECTOR objects.

1. Doesn't converting from one type to another, whenever I need to calculate sth, slow down the performance? Isn't it better to properly align class and then always use XMVECTOR in it?

2. If I should use XMFLOAT for storage purposes, does it mean that I should use XMFLOAT for filling the data as well? Or is it faster and preferred to use XMVECTOR to fill data in there and then store it in XMFLOAT?

I would be very grateful for answering 2 of my questions!

1. Doesn't converting from one type to another, whenever I need to calculate sth, slow down the performance?

Yes! But It's not that bad. You just need to be careful.

Isn't it better to properly align class and then always use XMVECTOR in it?

A lot of libs (I'm using Bullet Math) follow that pattern. You should be very careful again, with passing aligned values, type casting ect. (http://msdn.microsoft.com/en-us/library/83ythb65.aspx)

2. If I should use XMFLOAT for storage purposes, does it mean that I should use XMFLOAT for filling the data as well? Or is it faster and preferred to use XMVECTOR to fill data in there and then store it in XMFLOAT?

I can't understand the question.

thanks for answer!

Isn't it better to properly align class and then always use XMVECTOR in it?

A lot of libs (I'm using Bullet Math) follow that pattern. You should be very careful again, with passing aligned values, type casting ect. (http://msdn.microsoft.com/en-us/library/83ythb65.aspx)

So it's a better solution if I want my program / game run as smoothly and quickly as possible?

According to my 2. question I mean:

I have a XMFLOAT3A Position in my class and

Should I use something like this:

DirectX::XMStoreFloat3A(&Position, DirectX::XMVectorSet(-1.0f, -1.0f, 0.0f, 0.0f));

or:

Position.x = -1.0f;
Position.y = -1.0f
Position.z = 0.0f;

to fill the Position vector? What's faster and better to use? or it doesn't matter at all?

Should I use something like this:

DirectX::XMStoreFloat3A(&Position, DirectX::XMVectorSet(-1.0f, -1.0f, 0.0f, 0.0f));

or:

Position.x = -1.0f;
Position.y = -1.0f
Position.z = 0.0f;

inline XMVECTOR XMVectorSet
(
    float x, 
    float y, 
    float z, 
    float w
)
{
#if defined(_XM_NO_INTRINSICS_)
    XMVECTORF32 vResult = {x,y,z,w};
    return vResult.v;
#elif defined(_XM_ARM_NEON_INTRINSICS_)
    __n64 V0 = vcreate_f32(((uint64_t)*(const uint32_t *)&x) | ((uint64_t)(*(const uint32_t *)&y) << 32));
    __n64 V1 = vcreate_f32(((uint64_t)*(const uint32_t *)&z) | ((uint64_t)(*(const uint32_t *)&w) << 32));
    return vcombine_f32(V0, V1);
#elif defined(_XM_SSE_INTRINSICS_)
    return _mm_set_ps( w, z, y, x );
#else // _XM_VMX128_INTRINSICS_
#endif // _XM_VMX128_INTRINSICS_
}

Well probably yes.

The point is that loading/storing unaligned values into the aligned vars is slow, but it isn't a big deal. That part of the program won't give you the desired 30 to 60 fps jump.

If you're asking me for an advice I would tell you to use the aligned data. Because:

- for x64 achitecture there will be no overhead when 'converting' from XMFLOAT* to XMVECTOR

- the code is more readable