Build Error MingW 18 GNU 11.2.0 With Code blocks. Generated with Cmake 3.27.8

[IndieDev99]

Error: vsg::Win32_Window::Win32_Window(...) failed to create Window, screenNum is out of range.", VK_ERROR_INVALID_EXTERNAL_HANDLE};

I'm new and beginner so, if you guys can help me. My device is Quadro K620 vulkan 1.3 supported GPU. 16GB RAM Hexa Core CPU. Using Windows 10 pro 21H2. 1080p 60z monitor. Vulkan SDK installed 1.2.189.0.

I found something in code
if (screenNum >= displayDevices.size()) throw Exception{"Error: vsg::Win32_Window::Win32_Window(...) failed to create Window, screenNum is out of range.", VK_ERROR_INVALID_EXTERNAL_HANDLE};

[robertosfield]

I don't use Windows myself byt my best guess is your have a driver issue an the Vulkan driver is reporting that there are no available devices to use.

Could you run vsgdeviceselection example found in vsgExamples:

vsgdeviceselection --list

This is what I see on my Kubuntu 22.04 system that currently has a Geforce 2060 installed:

$ vsgdeviceselection --list
vkEnumerateInstanceVersion() 4206860
VK_API_VERSION = 1.3.268.0

physicalDevices.size() = 2
    matched ref_ptr<vsg::PhysicalDevice>(vsg::PhysicalDevice 0x7f85830bbc40) NVIDIA GeForce RTX 2060, deviceType = 2, apiVersion = 1.3.242, driverVersion = 23.516.192
    QueueFamilyProperties 4
        VkQueueFamilyProperties[0] queueFlags = GRAPHICS | COMPUTE | TRANSFER | PARSE_BINDING, queueCount = 16, timestampValidBits = 64, minImageTransferGranularity = {1, 1, 1}
        VkQueueFamilyProperties[1] queueFlags = TRANSFER | PARSE_BINDING, queueCount = 2, timestampValidBits = 64, minImageTransferGranularity = {1, 1, 1}
        VkQueueFamilyProperties[2] queueFlags = COMPUTE | TRANSFER | PARSE_BINDING, queueCount = 8, timestampValidBits = 64, minImageTransferGranularity = {1, 1, 1}
        VkQueueFamilyProperties[3] queueFlags = TRANSFER | PARSE_BINDING | VIDEO_DECODE, queueCount = 1, timestampValidBits = 32, minImageTransferGranularity = {1, 1, 1}

    matched ref_ptr<vsg::PhysicalDevice>(vsg::PhysicalDevice 0x7f85830bc0b0) llvmpipe (LLVM 15.0.7, 256 bits), deviceType = 4, apiVersion = 1.3.238, driverVersion = 0.0.1
    QueueFamilyProperties 1
        VkQueueFamilyProperties[0] queueFlags = GRAPHICS | COMPUTE | TRANSFER, queueCount = 1, timestampValidBits = 64, minImageTransferGranularity = {1, 1, 1}

[robertosfield]

Could you post your CMakeCache.txt file? Perhaps this might gives us some clues.

What application I you running when you get the "Error: vsg::Win32_Window::Win32_Window(...) failed to create Window, screenNum is out of range."?

The code that throws this vsg::Exception is found in this part of the Win32_Window constructor:

https://github.com/vsg-dev/VulkanSceneGraph/blob/master/src/vsg/platform/win32/Win32_Window.cpp#L350

This exception is thrown when traits->screenNum >= displayDevices.size(), screenNum defaults to 0, so I'd expect it to be 0, so for this conditions to happen the displayDevices is most likely empty().

Which suggests EnumDisplayDevices(nullptr, deviceNum, &displayDevice, 0) is not returning any usable devices. This is a Win32 function call and not something the VSG has much input on.

My best guess at this point is that your install of MinGW doesn't pick up on Win32 correctly for some reason.

I presume that other applications you are trying are prebuilt in other environments so unaffected whatever is going on, on your machine.

[robertosfield]

While I'm not a Windows users myself, others have reported success with MinGW and Cigwin, but perhaps these are different versions/configurations. Any chance that there might be some 32bit vs 64bit issue going on?

[IndieDev99]

@robertosfield let me try visual studio again. I will post the error.

[IndieDev99]

code test for vulkan using the codeblocks 20.03 with mingw

[IndieDev99]

Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\Ms2019Build\CMakeFiles\c0c82d1a4ebb7110b6b25dc960e99185\uninstall-vsg.rule
Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\CMakeLists.txt' exited with code 1. uninstall-vsg C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets 241

[IndieDev99]

CMakeCache.txt
at there might be some 32bit vs 64bit issue going on

[IndieDev99]

||=== Build: all in vsg (compiler: GNU GCC Compiler) ===|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\include\vsg\platform\win32\Win32_Window.h|191|warning: type qualifiers ignored on function return type [-Wignored-qualifiers]|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp||In constructor 'vsgWin32::Win32Surface::Win32Surface(vsg::Instance*, HWND)':|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|47|warning: unused variable 'result' [-Wunused-variable]|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp||In constructor 'vsgWin32::Win32_Window::Win32_Window(vsg::ref_ptrvsg::WindowTraits)':|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|364|warning: comparison of integer expressions of different signedness: 'int32_t' {aka 'int'} and 'std::vector<_DISPLAY_DEVICEA>::size_type' {aka 'long long unsigned int'} [-Wsign-compare]|
.||Error: vsg::Win32_Window::Win32_Window(...) failed to create Window, screenNum is out of range.", VK_ERROR_INVALID_EXTERNAL_HANDLE};|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp||In member function 'LRESULT vsgWin32::Win32_Window::handleWin32Messages(UINT, WPARAM, LPARAM)':|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|640|warning: declaration of 'event_time' shadows a previous local [-Wshadow]|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|533|note: shadowed declaration is here|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|645|warning: declaration of 'event_time' shadows a previous local [-Wshadow]|
D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|533|note: shadowed declaration is here|
||=== Build finished: 1 error(s), 5 warning(s) (11 minute(s), 21 second(s)) ===|

[IndieDev99]

I'm building the VSG from source using GNU GCC and Codebocks. All other vulkan based egnines and apps are building even C++ 17 based engines.
I followed the same instructions given but I'm not getting rid of ### Error: vsg::Win32_Window::Win32_Window(...) failed to create Window, screenNum is out of range.", VK_ERROR_INVALID_EXTERNAL_HANDLE}

[timoore]

This is finally becoming clear: you are complaining about a line in the compilation that mentions the ".||Error: vsg::Win32_Window::Win32_Window(...) failed to create Window, screenNum is out of range.", VK_ERROR_INVALID_EXTERNAL_HANDLE};|" message. This is not a compilation error: it looks to me that it is only causing a warning on that line. You do seem to have a compilation error somewhere else.

Search for the string "error:" in the compilation output.

[IndieDev99]

This is finally becoming clear: you are complaining about a line in the compilation that mentions the ".||Error: vsg::Win32_Window::Win32_Window(...) failed to create Window, screenNum is out of range.", VK_ERROR_INVALID_EXTERNAL_HANDLE};|" message. This is not a compilation error: it looks to me that it is only causing a warning on that line. You do seem to have a compilation error somewhere else.

Search for the string "error:" in the compilation output.

This is an error. Due to some reasons VSG is telling that window creation is failed due to something I cannot find. But I will try it tomorrow

[timoore]

Window creation isn't failing; you haven't succeeded in compiling the program and are not close to running it. I think you are being fooled by seeing "Error:" in the warning messages from the compilation.

[robertosfield]

Thanks looks your compiler is throwing issues that other compilers aren't. I am to pub right now. Will look into it tomorrow.

…

On Sat, 2 Dec 2023, 16:19 IndieDev99, ***@***.***> wrote: ||=== Build: all in vsg (compiler: GNU GCC Compiler) ===| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\include\vsg\platform\win32\Win32_Window.h|191|warning: type qualifiers ignored on function return type [-Wignored-qualifiers]| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp||In constructor 'vsgWin32::Win32Surface::Win32Surface(vsg::Instance*, HWND)':| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|47|warning: unused variable 'result' [-Wunused-variable]| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp||In constructor 'vsgWin32::Win32_Window::Win32_Window(vsg::ref_ptrvsg::WindowTraits)':| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|364|warning: comparison of integer expressions of different signedness: 'int32_t' {aka 'int'} and 'std::vector<_DISPLAY_DEVICEA>::size_type' {aka 'long long unsigned int'} [-Wsign-compare]| .||Error: vsg::Win32_Window::Win32_Window(...) failed to create Window, screenNum is out of range.", VK_ERROR_INVALID_EXTERNAL_HANDLE};| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp||In member function 'LRESULT vsgWin32::Win32_Window::handleWin32Messages(UINT, WPARAM, LPARAM)':| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|640|warning: declaration of 'event_time' shadows a previous local [-Wshadow]| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|533|note: shadowed declaration is here| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|645|warning: declaration of 'event_time' shadows a previous local [-Wshadow]| D:\Devlopement\C++\Vulkan Scene Graph\VulkanSceneGraph-1.0.9\VulkanSceneGraph-1.0.9\src\vsg\platform\win32\Win32_Window.cpp|533|note: shadowed declaration is here| ||=== Build finished: 1 error(s), 5 warning(s) (11 minute(s), 21 second(s)) ===| — Reply to this email directly, view it on GitHub <#1043 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKEGUCOBNCXKIR4AYBQEM3YHNIKDAVCNFSM6AAAAAA77OFXU6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TOMZYHAYDM> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[IndieDev99]

Thanks !!

[robertosfield]

I had a look at your snippet of build warnings and believe Tim is correct, the snippet doesn't contain any actual compile errors, it's simply that one of the lines with a warning about comparing two different integer types just happens to have a runtime error message.

I can see that at the end of the snippet your have 1 build error and 5 warnings, but I can't spot anything other than the 5 warnings in the snippet, so my best guess is that you've run a build, one of the files has failed to compile but the compile has continued and the warnings have caused the compile error to scroll off the screen or something similar - something that can easily happen with a multi0threaded build.

We have automated build testing on the major platforms, which includes WIndows but this is for VisualStudio, we also have gcc build in the mix but these are not for Windows. We don't have any build errors or warnings these build combinations so I presume that the Windows specific files that are being built on your system are throwing up more warnings and an error.

The warnings should be straight forward to fix, but the we'll need a copy of the build error before we can attempt to tackle it.

Would it be possible to run the build and redirect the output to a file to capture all the output?

Something like:

make &> build_output.txt

[IndieDev99]

Thanks for looking into the problem. I am currently busy in a work. I will reinstall the Windows on my new PC. So, i think it will take months before I can come back and start working with vsg again because I have found a job and I will be busy there. I will try this in my new pc. May be I will not comeback to vsg again if I continue with Godot. If I get this problem solved I will let you know. Thanks again for your time !!

[robertosfield]

I have checked fixes for the reported warnings into MinGW_build_fixes branch:

https://github.com/vsg-dev/VulkanSceneGraph/compare/MinGW_build_fixes

If the automated builds run cleanly on Windows I'll merge this with VSG master. They are only warning fixes though so won't resolve the build error, which alas will remain a mystery till someone can recreate it and post what the error is :-)

Good luck with the new job.

[robertosfield]

The warning fixes passed the Windows automated build so I've gone ahead and merged with VSG master with PR #1048.