Chuck Walbourn
Chuck Walbourn
The split algorithm is basically a loop over faces. If the number of vertices required by adding a new face exceeds a threshold, a new mesh is created. The function...
There are a number of these warnings before the failure: ``` Try to clean the non-manifold mesh, generated by partition ``` The DirectXMesh ``Clean`` and ``Validate`` methods are very useful...
Right. ``meshconvert`` only calls ``Clean`` if you use ``-c``, but ``uvatlas`` always calls it. Do you get any warnings from ``Validate`` (which is called before ``Clean``) or just from UVAtlas?
Try hacking up your local copy of uvatlas to do the ``Validate`` again after the ``Clean``. It seems like it's not fixing all the issues...
OK, so the Clean worked but there's some degenerate case in your model that's tripping up UVAtlas...
What GPU are you using?
Sorry, the attachment is missing. It's likely a driver bug, but you could try ``D3D11_CREATE_DEVICE_DISABLE_GPU_TIMEOUT``.
I suggest reporting this as a driver bug to Intel.
These templates work well with [DirectX Tool Kit](https://github.com/Microsoft/DirectXTK/wiki/Getting-Started) which creates the WIC factory internally on-demand, so there's no need to explicitly create one in the template. Direct2D/DirectWrite is a bit...
The Win32 templates include embedded manifest elements which indicate that the EXE is "dpiAware". This means the app is only told true pixel sizes in all cases, which is typical...