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

vkconfig3: Adding new layer locations to existing configs bugged #2193

Closed
mikes-lunarg opened this issue Nov 25, 2024 · 2 comments
Closed

vkconfig3: Adding new layer locations to existing configs bugged #2193

mikes-lunarg opened this issue Nov 25, 2024 · 2 comments
Assignees
Labels
bug OS - platform independent The issue doesn't depend on the OS P0 - Must Fix Must Fix / Critical feature Project - vkconfig3

Comments

@mikes-lunarg
Copy link
Contributor

Adding a new layer in a custom location:
image

The new layer gets added to the top of existing configuration and cannot be configured:
image

Restarting vkconfig-gui fixes it

@christophe-lunarg christophe-lunarg self-assigned this Nov 26, 2024
@christophe-lunarg christophe-lunarg added bug P2 Has a workaround / Minor feature OS - platform independent The issue doesn't depend on the OS labels Nov 26, 2024
@christophe-lunarg
Copy link
Contributor

I reproduced this issue a bit differently.

But yes, adding a new layer, caused issues, I'll fix it.

@christophe-lunarg christophe-lunarg added P0 - Must Fix Must Fix / Critical feature and removed P2 Has a workaround / Minor feature labels Dec 5, 2024
@christophe-lunarg
Copy link
Contributor

This issue is fixed with #2213

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug OS - platform independent The issue doesn't depend on the OS P0 - Must Fix Must Fix / Critical feature Project - vkconfig3
Projects
None yet
Development

No branches or pull requests

2 participants