It was happening in my own code, but it also 100% reproduces for me in the examples. Simply build the examples, run and hit the window close button.

Seems to be something relating to it still being inside renderFrame() during bgfx::shutdown().

<img width="1582" alt="Screenshot 2019-12-25 at 14 38 40" src="https://user-images.githubusercontent.com/621629/71447311-a7752680-2724-11ea-8a29-c2eae

We use PIX labels to organize the events in a single frame (e.g. Z PrePass, GBuffer, Alpha, etc). These can get quite deep/nested.

It would be useful if we could see a 'path' for the event currently selected, e.g.

Camera 1\3D Stage\GBuffer\TreeBark Material

It would be extra nice if clicking on any of these would take you to the beginning of that section.
(think folders in Windows Explor

When I run the Borderless gaming app, it loads the game into full screen, but the resolution is far too large and it only shows about 25% of the screen.

![screenshot 2018-09-03 17 12 24](https://user-images.githubusercontent.com/42929957/44975126-256e5680-af51-1

The Forge sounds pretty great but there does not seem to be much in the way of documentation.

I don't even see simple "How to compile" or build instructions. Which seems like a good place to start.

The description talks about it being like "Legos" where you can use the different parts of the system as needed. So does that mean it can be built in sections and integrated into other projects pi

Combine Tutorials 4 & 5 from
http://wiki.ogre3d.org/Basic+Tutorials

into one "Input and Listeners" tutorial as with SDL we only support buffered input.

However, include the new InputListenerChain based on the ImGUI sample.

EDITED SUMMARY
Make CMake complain if user is only using precompiled dependencies, but is compiling in 32-bit mode.

ORIGINAL ISSUE
I don't think BSF is intended to be used as a 32 bit library, so probably the easiest way to resolve this user confusion is to make cmake complain loudly if it's being configured to build a 32 bit binary.

directxtk is available as a port in vcpkg, a C++ library manager that simplifies installation for directxtk and 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 v

I wish doxygen documents is hosted online somewhere, it's kinda annoying just to clone and make my own copy to read documentations.
Anyway, this framework really helps me to make my own game engine.

Thanks.

For now the wiki page of OpenXRay is a mess!
I mean all necessary pages on all possible languages are trying to fit into main wiki page.
I haven't even found coding conventions from the first time!

That should be structured by the next design:

• Main page contains only links to language main wiki page.
• Language main page contains thematic sections like: Development, Modding, Using, Conti

The texassemble tool creates 2D array textures from a set of input 2D images or an animated gif. It might be a nice alternative to support outputting as a 'sprite sheet' using a packing algorithm similar to the DirectX Tool Kit tool MakeSpriteFont.

It's a RubikDemo in the default window size for example.

and it's the same RubikDemo when the window is maximized:

How to avoid this oversize effect if I n

1. UI is displayed incorrectly.
   D9VK
   
   D3D9 Native
   

2. Bifurcation of objects
   D9VK
   ![mm3](https://user-images.githubusercontent.com/45942960/67120136-58c18280-f1f1-11e9-9be5-82

I tried using the ScreenToClient and ClientToScreen methods in WinApi/WinApi/Windows/NativeWindow.cs because I thought they did the same thing as the Windows functions of the same name. But, after getting unexpected results, I noticed that the methods had AdjustWindowRectEx/InverseAdjustWindowRectEx calls in them as well, which results in something other than a simple client/screen coord

本体はCmdでショートカット使える。

The current configuration wiki provided is not complete and/or outdated. It causes confusion to me and probably many other people. Could you update it at least 1 by 1 when you have free time?

I would like a function that verifies that all naively using the document (only checking indices against -1) will not cause a buffer overrun; i tried writing this but i just started learning the gltf format this week and got confused.

I'm also pretty sure that Animation::Channel::Target::Path has only 4 valid values in the spec, and should be an enum, not a string, but maybe you know somethin