Vulkan | Examples and demos for the new Vulkan API | Graphics library

I'm trying to start android emulator on apple silicon mac and I'm always getting the same results:

1. Running emulator directly through Android Studio (the latest stable version, Arctic Fox 2020.3.1 Patch 4) causes a problem, when the process qemu-system-arch64 stucks and uses 99% CPU (there is no emulator's screen or something like than). Such behavior produces some logs:

internal-error-msg.txt says:

Just got a new M1 Mac Mini and I have been having trouble running my Android projects.

I'm using Android Studio (Bumblebee), JDK 11 (tried 17 as well), and Gradle 7.3.

When I try to run the project from AS, it builds fine and then gets stuck on "Waiting for target device to come online" and eventually times out.

If I try to run the emulator again I get a message that the device is already running, including a path to a lock file.

However, I've found that if I run the emulator manually from the CLI, the emulator does open, at which point I can get AS to run the app on said emulator. So the problem is apparently just that AS can't open the AVD.

Command line output when running emulator via adelphia$ emulator -avd Pixel_3a_API_32_arm64-v8a:

I cannot start the android emulator V30.9.4

I got this error message:

Setup:

• Windows 11 Home 21H2 22000.132
• AMD Ryzen 5900X
• WSL2
• Android studio lastest build (also tried with latest beta)

Problem: As soon as I install WSL2, the emulator stops working. It's giving the following error message:

Let's first acknowledge that OpenGL is deprecated by Apple, that the last supported version is 4.1 and that that's a shame but hey, we've got to move forward somehow and Vulkan is the way :trollface: Now that that's out of our systems, let's have a look at this weird bug I found. And let me be clear that I am running this on an Apple Silicon M1, late 2020 MacBook Pro with macOS 11.6. Let's proceed.

I've been following LearnOpenGL and I have published my WiP right here to track my progress. All good until I got to textures. Using one texture was easy enough so I went straight into using more than one, and that's when I got into trouble. As I understand it, the workflow is more or less

• load pixel data in a byte array called textureData, plus extra info
• glGenTextures(1, &textureID)
• glBindTexture(GL_TEXTURE_2D, textureID)
• set parameters at will
• glTexImage2D(GL_TEXTURE_2D, ... , textureData)
• glGenerateMipmap(GL_TEXTURE_2D) (although this may be optional)

which is what I do around here, and then

• glUniform1i(glGetUniformLocation(ID, "textureSampler"), textureID)
• rinse and repeat for the other texture

and then, in the drawing loop, I should have the following:

• glUseProgram(shaderID)
• glActiveTexture(GL_TEXTURE0)
• glBindTexture(GL_TEXTURE_2D, textureID)
• glActiveTexture(GL_TEXTURE1)
• glBindTexture(GL_TEXTURE_2D, otherTextureID)

I then prepare my fancy fragment shader as follows:

I can't recall if I have ever tinkered with the settings of Android Emulator, but I've been testing my app on an Android Emulator using Android Studio, and every time I take a screenshot, it crashes.

I tried deleting, and wiping, and creating a new Emulator. None of it works. I tried also to take a screenshot without running my app, with a fresh emulator, and the same problem occurs. It just crashes whenever I try to take a picture.

Android Studio reports this error:

Blockquote WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator. WARNING | cannot add library /Users/sbenati/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libvulkan.dylib: failed INFO | configAndStartRenderer: setting vsync to 60 hz INFO | added library /Users/sbenati/Library/Android/sdk/emulator/lib64/vulkan/libvulkan.dylib WARNING | cannot add library /Users/sbenati/Library/Android/sdk/emulator/qemu/darwin-x86_64/lib64/vulkan/libMoltenVK.dylib: failed INFO | added library /Users/sbenati/Library/Android/sdk/emulator/lib64/vulkan/libMoltenVK.dylib INFO | Started GRPC server at 127.0.0.1:8554, security: Local INFO | Advertising in: /Users/sbenati/Library/Caches/TemporaryItems/avd/running/pid_935.ini

My machine is a Mac with 32GB of RAM and i7 CPU, so I can't imaging this an issue with system performance.

If no one has any suggestions, I will have to just reinstall everything. Thanks for the tips everyone.

Edit:

I ran this on a new Mac mini I recently acquired, and got this really helpful message. I traced it down to a suggested solution about switching off Vulcan, but it did not work for me.

I'm building a game with raylib and made my own custom button in different files to reuse it when I need it.

I watched tons of videos and read docs but I don't know why it throws undefined reference to CustomButton::CustomButton().

Here's the error:

I'm learning vulkan, and as a (very) simple project I want to simply clear a single swapchain image to a single color (red). My code works, but I get two validation errors. I would like to know:

1. How can I fix the validation errors in my code
2. Is there a better way to simply clear swapchain images

Regarding (2): I specifically don't want to use a graphics pipeline: in the future I would like to use a compute shader to draw directly to the screen.

My project uses vk-bootstrap to set up, and then I try to render a single frame as follows:

1. Acquire an image from the swapchain
2. Record a command buffer with the following commands:
   • vkCmdPipelineBarrier
   • vkCmdClearColorImage
   • vkEndCommandBuffer
3. Submit the command buffer to the graphics queue
4. present the previously acquired swapchain image using vkQueuePresentKHR

The relevant code can be found below, but it seems that the validation errors arise from the calls to vkCmdClearColorImage and vkQueuePresentKHR.

The first validation error is from the vkCmdClearColorImage call, and seems to be triggered by my choice of layout:

This table shows the percentage of GPUs that support any given image format for different uses, such as sampling, transferring, as a depth and stencil buffer etc. If you look at it you'll see that that many of the most common formats are supported for uses such as sampling and depth buffer usage with the percentage showing as 99% or 100%, while the support for TRANSFER_SRC and TRANSFER_DST is at 78%. I'm wondering why this is, given that pretty much any format should be able to be transferred for reading it and writing it. When uploading an image to be used as a texture don't you need the TRANSFER_DST bit to be set as a flag? Similarly does this mean that there are GPUs that support something like R8G8B8A8_UINT (100% of them apparently), but only 78% of them support transferring them? This doesn't make sense to me. Strangely where the support for TRANSFER_SRC and TRANSFER_DST shows 78% for many of them the BLIT_SRC and BLIT_DST show 100%. The tutorials I've followed show the uploading of textures using copy commands and TRANSFER_DST to copy images to the GPU, for example when copying an image from a staging buffer.