Skip to content

Conversation

@asuessenbach
Copy link
Contributor

Description

Introduces a new Vulkan-Hpp-based sample, which is a transcoded version of the api sample hello_triangle_1_3.

Build tested on Win10 with VS2022. Run tested on Win10 with NVidia GPU.

Fixes #1312

General Checklist:

Please ensure the following points are checked:

  • My code follows the coding style
  • I have reviewed file licenses
  • I have commented any added functions (in line with Doxygen)
  • I have commented any code that could be hard to understand
  • My changes do not add any new compiler warnings
  • My changes do not add any new validation layer errors or warnings
  • I have used existing framework/helper functions where possible
  • My changes do not add any regressions
  • I have tested every sample to ensure everything runs correctly
  • This PR describes the scope and expected impact of the changes I am making

Note: The Samples CI runs a number of checks including:

  • I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
  • My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions

If this PR contains framework changes:

  • I did a full batch run using the batch command line argument to make sure all samples still work properly

Sample Checklist

If your PR contains a new or modified sample, these further checks must be carried out in addition to the General Checklist:

  • I have tested the sample on at least one compliant Vulkan implementation
  • If the sample is vendor-specific, I have tagged it appropriately
  • I have stated on what implementation the sample has been tested so that others can test on different implementations and platforms
  • Any dependent assets have been merged and published in downstream modules
  • For new samples, I have added a paragraph with a summary to the appropriate chapter in the readme of the folder that the sample belongs to e.g. api samples readme
  • For new samples, I have added a tutorial README.md file to guide users through what they need to know to implement code using this feature. For example, see conditional_rendering
  • For new samples, I have added a link to the Antora navigation so that the sample will be listed at the Vulkan documentation site

@asuessenbach asuessenbach force-pushed the hpp_hello_triangle_1_3 branch from 0114390 to 969bde3 Compare May 8, 2025 08:52
@asuessenbach asuessenbach requested review from a team and SaschaWillems May 8, 2025 13:37
SaschaWillems
SaschaWillems previously approved these changes May 17, 2025
Copy link
Collaborator

@SaschaWillems SaschaWillems left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Sample works fine for me on Win11 + RTX 4070.

Thank you very much 👍🏻

Copy link
Contributor

@gary-sweet gary-sweet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some reason this sample doesn't work for me. I get:

[error] Error Message: Failed to create window surface.
[error] Failed when running application Vulkan 1.3 HPP Hello Triangle

hello_triangle_1_3 works fine, as does hpp_hello_triangle. Any ideas?

@asuessenbach
Copy link
Contributor Author

Any ideas?

Nope.

That error is probably thrown in hpp_hello_triangle_1_3.cpp, line 131 (after rebasing).
That is, the function options.window->create_surface failed to create the surface.
What platform are you running? Is it GlfwWindow::create_surface that's called or HeadlessWindow::create_surface?
What's the result of that function call?

@gary-sweet
Copy link
Contributor

gary-sweet commented Jun 16, 2025

That error is probably thrown in hpp_hello_triangle_1_3.cpp, line 131 (after rebasing). That is, the function options.window->create_surface failed to create the surface. What platform are you running? Is it GlfwWindow::create_surface that's called or HeadlessWindow::create_surface? What's the result of that function call?

So it looks as though a NULL context.gpu is being passed into create_surface(). Given that init_device() hasn't been called yet, I guess that isn't a surprise, but doesn't seem right?

My platform will end up in the DirectWindow class.

@asuessenbach
Copy link
Contributor Author

My platform will end up in the DirectWindow class.

Yeah, and I think, that's the only platform where this issue pops up.
Hopefully fixed it with my latest change.

@asuessenbach asuessenbach force-pushed the hpp_hello_triangle_1_3 branch from b43dd63 to 9b16c4a Compare June 16, 2025 15:08
@SaschaWillems SaschaWillems self-requested a review June 16, 2025 16:17
SaschaWillems
SaschaWillems previously approved these changes Jun 16, 2025
gpx1000
gpx1000 previously approved these changes Jun 16, 2025
Copy link
Contributor

@gary-sweet gary-sweet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sadly this is still crashing for me, but in a different place now.
I'll need to do some debugging later to figure out what's going on.

@gary-sweet
Copy link
Contributor

Sadly this is still crashing for me, but in a different place now. I'll need to do some debugging later to figure out what's going on.

It's looking like the extension functions haven't been setup yet when find_display_candidates() is called.

@asuessenbach asuessenbach dismissed stale reviews from gpx1000 and SaschaWillems via 564b284 June 17, 2025 10:27
@asuessenbach asuessenbach force-pushed the hpp_hello_triangle_1_3 branch from 564b284 to f526939 Compare June 17, 2025 10:31
Copy link
Contributor

@gary-sweet gary-sweet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good now, thanks

@SaschaWillems SaschaWillems self-requested a review June 17, 2025 17:04
@marty-johnson59
Copy link
Contributor

3 approvals - merging

@marty-johnson59 marty-johnson59 merged commit 3944ae5 into KhronosGroup:main Jun 18, 2025
19 checks passed
@asuessenbach asuessenbach deleted the hpp_hello_triangle_1_3 branch July 1, 2025 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Vulkan.hpp variant for Hello Triangle 1.3 sample

5 participants