Hi Developers,

I have notice that the MeasureString returns a wrong size. The string "W" is used to measure the string size. The spritefont file is generated using MakeSpriteFont tool. The font setting is

• FontName: Arial
• FontStyle: Bold
• FontSize: 185

The returned result for the width and the height are 233 and 283.642578 respectively. "W" is placed at (0,0) I have edited Image 1 to include a black dotted line and marked a red circle to indicate the position where my mouse positioned which reflects the values shown in the Window Title. Clearly, there is a big difference between the Vector2 returned and the size which I had measured.

Image 1:

In addition, when I used SpriteBatch to draw "W" on the screen (0,0) using origin (0,0), it does not draw at the correct place. Instead, there is some sort of spacing as shown in Image 2.

Image 2:

To test it further, I have used SpriteBatch to draw "W" on the screen at the bottom left (i.e. making it right justified) of the screen using the origin calculated via MeasureString, but it does not draw at the correct place as shown in Image 3. Instead, it is lifted and cut off.

Image 3:

directxtkis available as a port in vcpkg, a C++ library manager that simplifies installation for directxtkand other project dependencies. Documenting the install process here will help users get started by providing a single set of commands to build directxtk, ready to be included in their projects.

We also test whether our library ports build in various configurations (dynamic, static) on various platforms (Windows: x86, x64, arm, uwp) to keep a wide coverage for users. Note: Currently it only supports dynamic build on Windows.

I'm a maintainer for vcpkg, and here is what the port script looks like. We try to keep the library maintained as close as possible to the original library.

I'm trying to add vcpkg installation instructions but I couldn't find the related docs in code item except for on Wikipage.

Could you please help add the following contents to this port?

Installing and building directxtk via vcpkg

You can download and install directxtk using the vcpkg dependency manager:

  git clone https://github.com/Microsoft/vcpkg.git
  cd vcpkg
  ./bootstrap-vcpkg.sh
  ./vcpkg integrate install
  vcpkg install directxtk 

The directxtk port in vcpkg is kept up to date by Microsoft team members and community contributors. If the version is out of date, please create an issue or pull request on the vcpkg repository.

Thanks, Nancy

Hi, sorry for my bad English) I use those functions to make a cut-scene (or smooth moving a camera by points) and it works good but if i pass less this value like then i have this result Of course it doesn't equal and my code looks wrong. What do I need to do with this situation?

Hi,

I'm trying to get a bounding sphere of a modal mesh and transform it to world coordinates. but the bounding sphere without any transformation is not center at 0,0,0.

here is how I do the transformation```

 m_bounding = m_Tree->meshes.at(0)->boundingSphere;
 XMMATRIX sphereTranslate = XMMatrixTranslation(m_bounding.Center.x, m_bounding.Center.y,
     m_bounding.Center.z);
sphereTranslate = sphereTranslate*treeTranslate;

XMMATRIX boundingSphereScale = XMMatrixScaling(120.0f, 120.0f, 120.0f);
worldSphere = boundingSphereScale*sphereTranslate;
m_bounding.Transform(m_bounding, sphereTranslate* boundingSphereScale);

m_BoundingSphere->Draw(worldSphere, m_Camera.ViewMatrix(), m_Camera.ProjectionMatrix());

I keep getting undefined symbol errors when compiling with clang-cl for ARM64. Is it unsupported?

1>lld-link : error : undefined symbol: neon_dupqrf32 1>>>> referenced by C:\Program Files (x86)\Windows Kits\10\Include\10.0.19041.0\um\DirectXMathMatrix.inl:1235 1>>>> ARM64\ARM64Release\Game.obj:(struct DirectX::XMMATRIX __cdecl DirectX::XMMatrixScaling(float, float, float)) 1>>>> referenced by ARM64\ARM64Release\Main.obj 1>>>> referenced by C:\dxtkjuly4\DirectXTK-master\Src\SpriteBatch.cpp:733 1>>>> DirectXTKARM64.lib(SpriteBatch.obj):(private: void __cdecl DirectX::SpriteBatch::Impl::RenderBatch(struct ID3D11ShaderResourceView *, struct DirectX::SpriteBatch::Impl::SpriteInfo const *const *, unsigned __int64)) 1>>>> referenced by C:\dxtkjuly4\DirectXTK-master\Src\SpriteBatch.cpp:830 1>>>> DirectXTKARM64.lib(SpriteBatch.obj):(private: static void __cdecl DirectX::SpriteBatch::Impl::RenderSprite(struct DirectX::SpriteBatch::Impl::SpriteInfo const *, struct DirectX::VertexPositionColorTexture *, union __n128, union __n128)) 1>>>> referenced by C:\dxtkjuly4\DirectXTK-master\Src\SpriteBatch.cpp:862 1>>>> DirectXTKARM64.lib(SpriteBatch.obj):(private: static void __cdecl DirectX::SpriteBatch::Impl::RenderSprite(struct DirectX::SpriteBatch::Impl::SpriteInfo const *, struct DirectX::VertexPositionColorTexture *, union __n128, union __n128)) 1>>>> referenced by C:\dxtkjuly4\DirectXTK-master\Src\SpriteBatch.cpp:863 1>>>> DirectXTKARM64.lib(SpriteBatch.obj):(private: static void __cdecl DirectX::SpriteBatch::Impl::RenderSprite(struct DirectX::SpriteBatch::Impl::SpriteInfo const *, struct DirectX::VertexPositionColorTexture *, union __n128, union __n128)) 1>>>> referenced by C:\dxtkjuly4\DirectXTK-master\Src\SpriteBatch.cpp:1079 1>>>> DirectXTKARM64.lib(SpriteBatch.obj):(public: void __cdecl DirectX::SpriteBatch::Draw(struct ID3D11ShaderResourceView *, struct DirectX::XMFLOAT2 const &, struct tagRECT const *, union __n128, float, struct DirectX::XMFLOAT2 const &, float, enum DirectX::SpriteEffects, float)) 1>>>> referenced by C:\dxtkjuly4\DirectXTK-master\Src\SpriteBatch.cpp:1126 1>>>> DirectXTKARM64.lib(SpriteBatch.obj):(public: void __cdecl DirectX::SpriteBatch::Draw(struct ID3D11ShaderResourceView *, union __n128, struct tagRECT const *, union __n128, float, union __n128, float, enum DirectX::SpriteEffects, float)) 1>>>> referenced by C:\dxtkjuly4\DirectXTK-master\Src\SpriteBatch.cpp:1128 1>>>> DirectXTKARM64.lib(SpriteBatch.obj):(public: void __cdecl DirectX::SpriteBatch::Draw(struct ID3D11ShaderResourceView *, union __n128, struct tagRECT const *, union __n128, float, union __n128, float, enum DirectX::SpriteEffects, float)) 1>>>> referenced by C:\dxtkjuly4\DirectXTK-master\Src\SpriteBatch.cpp:1128 1>>>> DirectXTKARM64.lib(SpriteBatch.obj):(public: void __cdecl DirectX::SpriteBatch::Draw(struct ID3D11ShaderResourceView *, union __n128, struct tagRECT const *, union __n128, float, union __n128, float, enum DirectX::SpriteEffects, float)) 1>>>> referenced 11 more times

I'm making a menu

'enum Menu { FightNow, Career, BeatdownLive, Help, Options };'

'void MainMenu::LoadMenu() { auto context = m_deviceResources->GetD3DDeviceContext(); auto device = m_deviceResources->GetD3DDevice(); m_spriteBatch = std::make_unique(context);

ComPtr<ID3D11Resource> resource;
DX::ThrowIfFailed(
	CreateWICTextureFromFile(device, L"cat.png",
		resource.GetAddressOf(),
		m_texture.ReleaseAndGetAddressOf()));

ComPtr<ID3D11Texture2D> logo;
DX::ThrowIfFailed(resource.As(&logo));

CD3D11_TEXTURE2D_DESC logoDesc;
logo->GetDesc(&logoDesc);

m_origin.x = float(logoDesc.Width / 2);
m_origin.y = float(logoDesc.Height / 2);



while (gameOn != false) {
	
	
	cout << DX::ThrowIfFailed(
		CreateWICTextureFromFile(device, L"cat.png",
			resource.GetAddressOf(),
			m_texture.ReleaseAndGetAddressOf())); ;
	cout << DX::ThrowIfFailed(
		CreateWICTextureFromFile(device, L"cat.png",
			resource.GetAddressOf(),
			m_texture.ReleaseAndGetAddressOf()));
	cout << DX::ThrowIfFailed(
		CreateWICTextureFromFile(device, L"cat.png",
			resource.GetAddressOf(),
			m_texture.ReleaseAndGetAddressOf()));
	cout << DX::ThrowIfFailed(
		CreateWICTextureFromFile(device, L"cat.png",
			resource.GetAddressOf(),
			m_texture.ReleaseAndGetAddressOf()));
	

	cin >> mode;

	while (true)
	{
		switch (mode)
		{
		case FightNow:

			break;
		}
	}
}

}'

I keep getting these errors

E0349 no operator "<<" matches these operands E0349 no operator ">>" matches these operands

At some point we should remove support for these older versions in favor of UWP apps

DirectXTK_Windows81.vcxproj DirectXTK_WindowsPhone81.vcxproj DirectXTK_XAMLSilverlight_WindowsPhone81.vcxproj

This would also be a good time to drop VS 2013 entirely:

DirectXTK_Desktop_2013.vcxproj DirectXTK_Desktop_2013_DXSDK

Please put any requests for continued support for one or more of these here.

I would like to suggest that the methods listed in the subject line be made static, thereby eliminating the need to instantiate an instance of Mouse/Keyboard for most uses. For now, I'm wrapping instances of these classes in a class that has equivalent static methods, so I can achieve the effect I'm going for, but it would be nice if the DirectXTK more closely matched the XNA API right out of the box. If there is a technical reason why they shouldn't be made static I'd like to know why, if just for educational purposes. I'm humbled by the quality of the code and I'm still a ways away from mastering C++.

Another suggestion, and this is just a stylistic thing, I think it would be better to have the first letter of the Mouse::State struct members capitalized. This matches the style of the Keyboard::State struct and Microsoft conventions in general...at least in the clean and consistent world of .NET. :)

Thanks guys!

I think I found a bug when loading and rendering the island.sdkmesh using a Model class object. The island.sdkmesh model has two mesh parts but only one is rendered.

Hi there. After Mouse::SetMode(Mouse::MODE_RELATIVE) method call when I call Mouse::Get().GetState().x or Mouse::Get().GetState().y the values of x and y do not get updated. If I call Mouse::SetMode(Mouse::MODE_ABSOLUTE) the values of x and y update immediately.

I am using 2021.11.8.1 version of DirectXTK (directxtk_desktop_win10) downloaded from NuGet.

You can find a working demo in this repo.

Hi, I was reading the tutorial about how to load an render a model with this TK using the provided files and I run into this problem. No matter what file I've tried or how many times I tried, it always fails at loading the .obj file with an unhelpful error (80004005)

According to the source code, it fails at the LoadFromOBJ function, where the WaveFrontReader doesn't read the vertices/indices: (
if (wfReader.indices.empty() || wfReader.vertices.empty()) return E_FAIL; )

But how and why? What am I doing wrong? I've tried with other .obj files as well with no luck...

Thanks for you time and sorry to bother you!

So I've been using the toolkit for a while now for my personal education in graphics programming and one thing that's always annoyed me is how jittery the mouse movement is when you increase the sensitivity. I discovered this because I followed the tutorial for mouse input on the wiki but the mouse rotation was far too slow. Due to the low sensitivity, the issue is present but not nearly as noticeable. For example, here is how the mouse behaves currently when you multiply the inputs to increase mouse sensitivity. See how jittery it is? It's hard to describe but I am moving my mouse diagonally and it feels like it is either moving horizontally or vertically but never both at the same time.

https://user-images.githubusercontent.com/6319937/210378140-9d349906-6e7c-4b54-8773-f7617fffd5ec.mp4

Good news though! It took a while but I tracked down the cause to Mouse.cpp at 1304

                if (!(raw.data.mouse.usFlags & MOUSE_MOVE_ABSOLUTE))
                {
                    pImpl->mState.x = raw.data.mouse.lLastX;
                    pImpl->mState.y = raw.data.mouse.lLastY;

                    ResetEvent(pImpl->mRelativeRead.get());
                }

The problem is that the WM_INPUT message from windows can fire off multiple times in between frames of the application. That means that by the time your Tick() function runs, there have been multiple WM_INPUT messages received by the mouse singleton. It is extremely common for any individual WM_INPUT message to have either x or y be 0. That's why during diagonal mouse movement, it felt like only horizontal or vertical movement was being registered but never both.

The Cause

The issue is caused by the fact that we are assigning the delta to mState.x and mState.y instead of accumulating it. That means we are basically throwing away all inputs that windows throws at us except for the one it happens to receive before the application is ticked.

The solution

                    pImpl->mState.x = raw.data.mouse.lLastX;
                    pImpl->mState.y = raw.data.mouse.lLastY;

becomes

                    pImpl->mState.x += raw.data.mouse.lLastX;
                    pImpl->mState.y += raw.data.mouse.lLastY;

I would've done this as a pull request but this creates some issues due to how the class is designed and I didn't feel comfortable making deep changes to the API. The issue this creates is that the mState.x and mState.y must be cleared at the end of the application frame. It probably isn't the best idea to force any user to call some OnEndFrame() function because that will place an undue burden on any existing applications. However, the existing implementation requires that during relative mouse movement, GetState() should only be called once. I propose that when GetState() is called, we pass the state by value rather than by reference and then clear the internal state.

Here is what it looks like when the WM_INPUT message are accumulated and then cleared at the end of the application frame.

https://user-images.githubusercontent.com/6319937/210389857-287dfb0c-a084-4e00-97c5-d04371a6d9bb.mp4

The full implementation of the old 'load surface from surface' requires DirectXTex, but a subset of pixel format conversions can be implemented using WIC.

HRESULT WINAPI
    D3DXLoadSurfaceFromSurface(
        LPDIRECT3DSURFACE9        pDestSurface,
        CONST PALETTEENTRY*       pDestPalette,
        CONST RECT*               pDestRect,
        LPDIRECT3DSURFACE9        pSrcSurface,
        CONST PALETTEENTRY*       pSrcPalette,
        CONST RECT*               pSrcRect,
        DWORD                     Filter,
        D3DCOLOR                  ColorKey);

HRESULT WINAPI
    D3DXLoadVolumeFromVolume(
        LPDIRECT3DVOLUME9         pDestVolume,
        CONST PALETTEENTRY*       pDestPalette,
        CONST D3DBOX*             pDestBox,
        LPDIRECT3DVOLUME9         pSrcVolume,
        CONST PALETTEENTRY*       pSrcPalette,
        CONST D3DBOX*             pSrcBox,
        DWORD                     Filter,
        D3DCOLOR                  ColorKey);

HRESULT WINAPI
    D3DX11LoadTextureFromTexture(
	ID3D11DeviceContext       *pContext,
        ID3D11Resource            *pSrcTexture,
        D3DX11_TEXTURE_LOAD_INFO  *pLoadInfo,
        ID3D11Resource            *pDstTexture);

There are two facts:

• In Microsoft's Virtual-Key Codes documentation, this key does not exist
• In Microsoft's DirectInput Keyboard Device Enumeration, there is a DIK_NUMPADENTER

I used to think window messages couldn't differentiate between Enter and Numpad Enter, but:

• Press Enter key
• Press Enter key on numpad

This issue is also mentioned in the source code of Dear-ImGui (imgui_impl_win32).

Since my application was migrated from DirectInput to DirectXTK Keyboard, will the Numpad Enter key be officially supported in the future?

The original XNA Game Studio Mouse abstraction only exposed the vertical scroll wheel as most mice don't have the horizonal scroll wheel. The information, however, is exposed for Win32, UWP, and GameInput.

This work would likely modify Mouse::State to have 2 scroll wheel values:

struct State
{
...
    int     scrollWheelValueX;
    int     scrollWheelValueY;
...
};

This would be a minor breaking change.

And the reset method would be updated to:

// Resets the accumulated scroll wheel value
void __cdecl ResetScrollWheelValue(bool x=true, bool y=true) noexcept;

The Win32 integration would also require getting WM_MOUSEHWHEEL messages.

This old article provides a way to keep the Windows key from popping a game out of fullscreen. Maybe I should add it to the Win32 version of Keyboard?

https://docs.microsoft.com/en-us/windows/win32/dxtecharts/disabling-shortcut-keys-in-games

This original code does not cause problems for Xbox Game Bar shortcuts which work correctly even when this low-level hook is used.