-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create cubemap from file #93
Conversation
including example application
… to right-handed world space and vice versa using modelView matrices instead of in shader code; add comments explaining coordinate system transformations
…ng branch on current master
implement image_resource_t classes for GLI and stb_image loaders; add factory method create_image_resource_from_file(); implement composite_cubemap_image_resource_t class for creating cubemap from individual files; update texture_cubemap example
including example application
… to right-handed world space and vice versa using modelView matrices instead of in shader code; add comments explaining coordinate system transformations
…ng branch on current master
implement image_resource_t classes for GLI and stb_image loaders; add factory method create_image_resource_from_file(); implement composite_cubemap_image_resource_t class for creating cubemap from individual files; update texture_cubemap example
add links to source
simplify image_resource interfaces fix screen resizing in texture_cubemap example after update add caching to texture_cubemap example add loading of dds texture to texture_cubemap example
…en/Gears-Vk into create_cubemap_from_file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry if some of the comments might appear a bit nit-picky, but the framework shall serve users well and features shall be implemented in similar ways, so that users get the chance to "feel at home" with the framework. That means that new features must follow established principles and patterns.
I know that this can be a bit cumbersome from time to time and refactoring will take some time, but it is for a good purpose. It is more important to implement new features in a well and consistent way so that the frameowork feels like as if made from one piece than to implement a lot of new features and each of them requires different usage patterns.
If you have further questions, please do not hesitate to discuss directly at the issues or in Slack!
Co-authored-by: Johannes Unterguggenberger <[email protected]>
make conversion constructors of image_resource_base_t explicit make variables and parameters const and auto if possible prevent variable use after std::move
…en/Gears-Vk into create_cubemap_from_file
make conversion constructors explicit for image_resource_t classes
Co-authored-by: Johannes Unterguggenberger <[email protected]>
follow naming conventions use gvk::owned instead of std::move Co-authored-by: Johannes Unterguggenberger <[email protected]>
…::unique_ptr, adapt code accordingly add create_image_resource() helper functions fix compilation errors in texture_cubemap example
…nique_ptr, adapt code accordingly add create_image_resource() helper functions fix compilation errors in texture_cubemap example
…en/Gears-Vk into create_cubemap_from_file
Co-authored-by: Johannes Unterguggenberger <[email protected]>
Co-authored-by: Johannes Unterguggenberger <[email protected]>
…loading in texture_cubemap example
Co-authored-by: Johannes Unterguggenberger <[email protected]>
follow naming guidelines for parameters
…reate_cubemap_from_file
Co-authored-by: Johannes Unterguggenberger <[email protected]>
…en/Gears-Vk into create_cubemap_from_file
fix parameter type
…uct options`. This should improve readability. - Removed useless `updater` calls and restructured the remaining code to be clearer. - Added comments to the functions in `math_utils.hpp` that are added with this PR - Removed default parameter value for `mirror_matrix`'s `principal_axis` parameter. There is not really a justification why any of the axes should be the default. The user must be precise anyways. Also removed the parameter's `const` declaration.
@stf976 Please have a look at the changed that I have pushed and see if you agree! |
Changes look good. Shouldn't function arguments always be const if possible? I have already prepared documentation for the math_util functions as part of the API documentation, will update it when it is finished. |
Actually, |
@stf976 There is one more issue: It fails (in DEBUG mode!) in
I think, the fix is trivial, because the code has actually no reason to go there. GLI fails to load a Before re-requesting a review, please ensure that the following examples run fine:
If you don't have a ray tracing capable GPU, I'll test them before merging the PR. |
Fixed, the model_loader works again now. I also tested the other examples where possible, but don't have a GPU that supports RTX to test the last two. |
pull request for implementation of #62 for review;
API documentation not yet included