-
Notifications
You must be signed in to change notification settings - Fork 423
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
iOS simulator initialization failure due to Invalid Pixel Format #2353
Comments
I am experiencing the same error on the iOS Simulator using the current MoltenVK head (MVK 1.2.11):
|
According to OP's backtrace, it's trying to work out the maximum minimum alignment for a texel buffer (i.e. a I recall reading somewhere that The solution, then, is to disable this format unconditionally on the simulator, even when the caps say it should be supported. We may have to disable the others before this is all through. |
The following CTS test started failing: I have yet to look at the reason for why it fails since I just run into this failure yesterday, so unsure if it may be related or not. I will eventually get to it this week. I recall there was some kind of limitation on having texel buffers for this format, so that may be the cause. I need to double check once I dig into the CTS failure. |
Empirically this is what I had to do in MVKPixelFormats.mm:
With this change I can load MVK 1.2.11 on the iOS Simulator. Not sure if the #ifdef condition is strictly correct, or if it should be nested inside |
Yes it does. |
I have added a PR that addresses this issue for my test cases. Perhaps @warmenhoven could test as well. |
As a result of 5afeaa4, the iOS simulator crashes during
vkCreateInstance
:The text was updated successfully, but these errors were encountered: