We are looking into it.
Recent community posts
Memory leaks found in source.
Source\HammUEr\Private\InstanceDataHandler.h(25) Source\HammUEr\Private\MapFileLoader.h(171) Source\HammUEr\Private\MapFileLoader.h(172) Source\HammUEr\Private\MapFileLoader.h(173) Source\HammUEr\Private\MapFileLoader.cpp(2143)
empty() call to std::vector is used, which checks if the vector is empty (returns bool), but your usages discard the value. You most likely meant to use clear(), which erases all elements of the vector.
Yes, our target is 60FPS or more. If you get anything below that, you are extremely penalized. We will be optimizing integrated graphics cards more so their FPS is higher. Did you try out the simple renderer?
The Performance Test automatically scales your resolution to reduce bottlenecks which may cause unrepresentative performance for your system. So this behavior is expect. Of course, you will be able to manually set your resolution in the game.
Sorry, we aren't able to support 32-bit, as this would cause unrealistic limits for our game as well as increase work for us to provide proper support for this platform. If your CPU has 64-bit support, you should be able to run 64-bit Windows.
DirectX 10 is essentially running at a lower quality than DirectX 11, since it doesn't support all the rendering features DirectX 11 supports. So it is to be expected that DX10 runs better, but DX11 should be a more efficient renderer for what it can render over DX10.
1. Launch dxdiag, and Save All Information. Share DxDiag.txt with us.
2. Use Windows Event Viewer (https://wiki.unrealengine.com/Windows_Event_Viewer) to find the crash log for the game.
3. Use DependenciesGui.exe (https://github.com/lucasg/Dependencies/releases/download/v1.8/Dependencies_x64_Release.zip) to open WindowsNoEditor\projectborealis_ue\Binaries\Win64\projectborealis_ue-Win64-Shipping.exe and see if there are any errors in the dependency stack.