Skip to content
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

LoadData was being called twice from InitializeImage #2079

Conversation

panos-lunarg
Copy link
Contributor

AcquireInitializedStagingBuffer will call LoadData so InitializeImage does not need to explicitly call it again.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build queued with queue ID 397615.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6356 running.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6356 passed.

@@ -181,8 +181,6 @@ VkResult VulkanResourceInitializer::InitializeImage(VkDeviceSize dat

if (result == VK_SUCCESS)
{
result = LoadData(data_size, data, staging_buffer_data);

if (result == VK_SUCCESS)
Copy link
Contributor

Choose a reason for hiding this comment

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

I think you can remove the inner if.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

right

AcquireInitializedStagingBuffer will call LoadData so InitializeImage
does not need to explicitly call it again.
@panos-lunarg panos-lunarg force-pushed the do_not_LoadData_twice_in_InitializeImage branch from 0f86544 to e6ad108 Compare March 18, 2025 09:33
@ci-tester-lunarg
Copy link

CI gfxreconstruct build queued with queue ID 397665.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6358 running.

@ci-tester-lunarg
Copy link

CI gfxreconstruct build # 6358 passed.

@panos-lunarg
Copy link
Contributor Author

This is included in #2081

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.

3 participants