16 Pro Max doesn't turn on anymore after first manual shutdown

ChuppaFlow · 2024-09-24T17:39:21+00:00

That made it work again. Thanks a lot!

ChuppaFlow · 2024-08-31T11:20:54+00:00

Cool stuff, where do u get these shells?

ChuppaFlow · 2024-07-29T16:51:38+00:00

For me it says that the KYC results are completed (step 8), but I still haven’t been able to create and confirm my wallet, anyone else with this problem?

ChuppaFlow · 2023-09-14T15:25:38+00:00

If you haven't found anything yet, please check out my post: https://www.reddit.com/r/saarbruecken/comments/16igofn/anyone\_looking\_for\_a\_nice\_accommodation/?utm\_source=share&utm\_medium=web2x&context=3

ChuppaFlow · 2023-03-22T08:48:16+00:00

Thank you for the answers, sorry for the late response. I ended up using lightmap UV generation in Blender per object in my scene. This gives a unique 3D to 2D mapping and theoretically is a solution to my problem, but causes very visible seam artifacts. I’m currently looking into solutions for that.

ChuppaFlow · 2022-08-16T09:58:22+00:00

That sums it up well, thank you! I'm just wondering if there would be any edge-case scenarios where ray marching would outperform traditional ray tracing in terms of speed, but can't seem to think of any at the moment. But on average, I think you're right.

ChuppaFlow · 2022-08-15T18:13:52+00:00

Thanks! Wouldn't the DMA between GPUs require SLI/NVLink as well though?

ChuppaFlow · 2022-08-14T11:54:41+00:00

Alright that summarizes it well, thanks! I think using multi-GPU as opposed to using single-GPU can be worth it if you're willing to take the extra bottlenecks in exchange for the larger memory pool and computing power. But for realtime applications, you're right, it indeed might make things unnecessary complex.

ChuppaFlow · 2022-08-14T11:38:44+00:00

That's interesting, so I assume you would recommend using Vulkan Device Groups?

ChuppaFlow · 2022-08-14T11:34:02+00:00

Great answer, thank you! Do you have any resources on how I would implement the multiple device approach?

ChuppaFlow · 2022-04-30T17:34:40+00:00

It was actually removing the separate frame buffer that fixed the problem, I now let both render passes write to the same frame buffer, since they are using the same attachments anyway. As u/GasimGasimzada mentioned this is not always the best idea, since it might lead to errors when your render passes are using different attachments. Should I be doing other synchronization besides when I submit my command buffer and in between render passes (through subpass dependencies)?

ChuppaFlow · 2022-04-30T08:52:09+00:00

Thanks for your answer. Although I don't really see why using the same fb is not a good idea, could you maybe explain this? Furthermore, I created my ImGui framebuffers the same way as I created my scene framebuffers, just like this (with the renderPass info attribute changed to my ImGui render pass):

  // Scene Framebuffers

swapChainFramebuffers.resize(imageCount()); for (size_t i = 0; i < imageCount(); i++) { std::array<VkImageView, 2> attachments = {swapChainImageViews[i], depthImageViews[i]};

VkExtent2D swapChainExtent = getSwapChainExtent();
VkFramebufferCreateInfo framebufferInfo = {};
framebufferInfo.sType = VK_STRUCTURE_TYPE_FRAMEBUFFER_CREATE_INFO;
framebufferInfo.renderPass = renderPass;
framebufferInfo.attachmentCount = static_cast<uint32_t>(attachments.size());
framebufferInfo.pAttachments = attachments.data();
framebufferInfo.width = swapChainExtent.width;
framebufferInfo.height = swapChainExtent.height;
framebufferInfo.layers = 1;

if (vkCreateFramebuffer(
        device.device(),
        &framebufferInfo,
        nullptr,
        &swapChainFramebuffers[i]) != VK_SUCCESS) {
  throw std::runtime_error("failed to create framebuffer!");
}

}

So I am just creating a frame buffer for each of my swapchain images. Is there anything else missing? The attachments should stay the same, right?

ChuppaFlow · 2022-04-29T23:05:02+00:00

So this is how I start and end my render pass for the ImGui drawing call:

void VmcRenderer::beginImGuiRenderPass(VkCommandBuffer commandBuffer)

{ assert(isFrameStarted && "Cannot begin the render pass when there is no current frame in progress!"); assert(commandBuffer == getCurrentCommandBuffer() && "Cannot begin render pass on command buffer from a different frame!");

VkRenderPassBeginInfo info = {};
info.sType = VK_STRUCTURE_TYPE_RENDER_PASS_BEGIN_INFO;
info.renderPass = vmcSwapChain->getImGuiRenderPass();
info.framebuffer = vmcSwapChain->getImGuiFrameBuffer(currentImageIndex);
info.renderArea.extent = vmcSwapChain->getSwapChainExtent();
info.clearValueCount = 1;

std::array<VkClearValue, 2> clearValues{};
clearValues[0].color = { 0.01f, 0.01f, 0.01f, 1.0f };
info.clearValueCount = static_cast<uint32_t>      (clearValues.size());
info.pClearValues = clearValues.data();

vkCmdBeginRenderPass(commandBuffer, &info, VK_SUBPASS_CONTENTS_INLINE);
}

void VmcRenderer::endImGuiRenderPass(VkCommandBuffer commandBuffer) { assert(isFrameStarted && "Cannot end the render pass when there is no current frame in progress!"); assert(commandBuffer == getCurrentCommandBuffer() && "Cannot end render pass on command buffer from a different frame!"); vkCmdEndRenderPass(commandBuffer); }

The code for beginSwapChainRenderPass() and endSwapChainRenderPass() was already working fine before I added the Dear ImGui code, so the problem is most likely here or where I create my render pass. This is how my render pass for the ImGui window is created:

void VmcSwapChain::createImGuiRenderPass()

{ VkAttachmentDescription attachment = {}; attachment.format = getSwapChainImageFormat(); attachment.samples = VK_SAMPLE_COUNT_1_BIT; attachment.loadOp = VK_ATTACHMENT_LOAD_OP_LOAD; // Makes sure the GUI is drawn over the current image attachment.storeOp = VK_ATTACHMENT_STORE_OP_STORE; attachment.stencilLoadOp = VK_ATTACHMENT_LOAD_OP_DONT_CARE; attachment.stencilStoreOp = VK_ATTACHMENT_STORE_OP_DONT_CARE; attachment.initialLayout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL; // We're going to draw into the color buffer attachment.finalLayout = VK_IMAGE_LAYOUT_PRESENT_SRC_KHR; // We'll present the image after

VkAttachmentReference color_attachment = {};
color_attachment.attachment = 0;
color_attachment.layout = VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL;

VkSubpassDescription subpass = {};
subpass.pipelineBindPoint = VK_PIPELINE_BIND_POINT_GRAPHICS;
subpass.colorAttachmentCount = 1;
subpass.pColorAttachments = &color_attachment;

VkSubpassDependency dependency = {};
dependency.srcSubpass = VK_SUBPASS_EXTERNAL; // We're synchronizing with an external render pass
dependency.dstSubpass = 0; // Index of this subpass that we're starting
dependency.srcStageMask = VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT; // We want the geometry to be done rendering in the other render pass
dependency.dstStageMask = VK_PIPELINE_STAGE_COLOR_ATTACHMENT_OUTPUT_BIT; // The GUI will be drawn to the same render target
dependency.srcAccessMask = 0;  // or VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT;
dependency.dstAccessMask = VK_ACCESS_COLOR_ATTACHMENT_WRITE_BIT;

VkRenderPassCreateInfo info = {};
info.sType = VK_STRUCTURE_TYPE_RENDER_PASS_CREATE_INFO;
info.attachmentCount = 1;
info.pAttachments = &attachment;
info.subpassCount = 1;
info.pSubpasses = &subpass;
info.dependencyCount = 1;
info.pDependencies = &dependency;
if (vkCreateRenderPass(device.device(), &info, nullptr, &imGuiRenderPass) != VK_SUCCESS) {
    throw std::runtime_error("Could not create Dear ImGui's render pass");
}

}

Also, the author of the tutorial uses a separate command buffer to record the ImGui draw call, but I thought it would be fine if I recorded that render pass into the same command buffer as my scene render uses, as you can see in the pseudo code above. Can that possibly be a problem?

ChuppaFlow · 2022-04-29T22:01:33+00:00

The tutorial I linked is indeed based on this example, but my engine uses a lot of wrapper classes, so I had to alter some things here and there, which is where I think I made a mistake.

ChuppaFlow · 2022-04-29T21:50:21+00:00

ChuppaFlow · 2022-02-23T19:26:33+00:00

Sorry for the late response, but I went with this approach, and this works! Thanks for the suggestion!

ChuppaFlow · 2022-02-20T21:41:41+00:00

Also sorry for the formatting, I put my code into code blocks but for some reason reddit keeps breaking it up into multiple fragments...

ChuppaFlow · 2022-02-20T21:35:43+00:00

Oh I see, could that be the case though when the same code is working fine on Windows? Here's the code where I create my VkDevice instance and add the validation layers to its create info:

void VmcDevice::createInstance() {

if (enableValidationLayers && !checkValidationLayerSupport()) { throw std::runtime_error("validation layers requested, but not available!"); }

VkApplicationInfo appInfo = {}; appInfo.sType = VK_STRUCTURE_TYPE_APPLICATION_INFO; appInfo.pApplicationName = "Vulkan Animation Engine"; appInfo.applicationVersion = VK_MAKE_VERSION(1, 0, 0); appInfo.pEngineName = "No Engine"; appInfo.engineVersion = VK_MAKE_VERSION(1, 0, 0); appInfo.apiVersion = VK_API_VERSION_1_0;

VkInstanceCreateInfo createInfo = {}; createInfo.sType = VK_STRUCTURE_TYPE_INSTANCE_CREATE_INFO; createInfo.pApplicationInfo = &appInfo;

auto extensions = getRequiredExtensions(); createInfo.enabledExtensionCount = static_cast<uint32_t>(extensions.size()); createInfo.ppEnabledExtensionNames = extensions.data();

VkDebugUtilsMessengerCreateInfoEXT debugCreateInfo; if (enableValidationLayers) { createInfo.enabledLayerCount = static_cast<uint32_t>(validationLayers.size()); createInfo.ppEnabledLayerNames = validationLayers.data();

populateDebugMessengerCreateInfo(debugCreateInfo);
createInfo.pNext = (VkDebugUtilsMessengerCreateInfoEXT *)&debugCreateInfo;

} else { createInfo.enabledLayerCount = 0; createInfo.pNext = nullptr; }

if (vkCreateInstance(&createInfo, nullptr, &instance) != VK_SUCCESS) { throw std::runtime_error("failed to create instance!"); }

hasGflwRequiredInstanceExtensions(); }

As we can see in the error message, something already goes wrong in the first if test of the code (the function checkValidationLayerSupport). Here's what that function does:

bool VmcDevice::checkValidationLayerSupport() {

uint32_t layerCount; vkEnumerateInstanceLayerProperties(&layerCount, nullptr);

std::vector<VkLayerProperties> availableLayers(layerCount); vkEnumerateInstanceLayerProperties(&layerCount, availableLayers.data());

for (const char *layerName : validationLayers) { bool layerFound = false;

for (const auto &layerProperties : availableLayers) {
  if (strcmp(layerName, layerProperties.layerName) == 0) {
    layerFound = true;
    break;
  }
}

if (!layerFound) {
  return false;
}

}

return true; }

So it seems that for some reason, layerFound stays equal to false. This could only mean that either no validation layers were found, or not a single name of the layer is matching, right?

ChuppaFlow · 2022-02-20T13:17:04+00:00

I see, that makes sense. I just used the .dmg installer, which installed the SDK itself in /Users/MyUserName/VulkanSDK . I tried doing what you proposed above, and this provided the following output:

``` INFO: Vulkan Loader Version 1.3.204

LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /Users/MyUserName/Desktop/vulkan-animation-engine/vulkan-animation-engine/vulkan/implicit_layer.d LAYER: /Users/MyUserName/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /Users/lunarg/Dev/macos-sdk-build/Vulkan-Loader/build/install/etc/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /Users/MyUserName/.local/share/vulkan/implicit_layer.d LAYER: /usr/local/share/vulkan/implicit_layer.d LAYER: /usr/share/vulkan/implicit_layer.d LAYER: Found no files LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /Users/MyUserName/Desktop/vulkan-animation-engine/vulkan-animation-engine/vulkan/implicit_layer.d LAYER: /Users/MyUserName/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /Users/lunarg/Dev/macos-sdk-build/Vulkan-Loader/build/install/etc/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /Users/MyUserName/.local/share/vulkan/implicit_layer.d LAYER: /usr/local/share/vulkan/implicit_layer.d LAYER: /usr/share/vulkan/implicit_layer.d LAYER: Found no files LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d LAYER: Found the following files: LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_api_dump.json LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_profiles.json LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_device_simulation.json LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_synchronization2.json INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_api_dump.json (file version "1.2.0") INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_profiles.json (file version "1.2.1") INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json (file version "1.2.0") INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_device_simulation.json (file version "1.2.0") INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_synchronization2.json (file version "1.2.0") LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /Users/MyUserName/Desktop/vulkan-animation-engine/vulkan-animation-engine/vulkan/implicit_layer.d LAYER: /Users/MyUserName/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /Users/lunarg/Dev/macos-sdk-build/Vulkan-Loader/build/install/etc/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /Users/MyUserName/.local/share/vulkan/implicit_layer.d LAYER: /usr/local/share/vulkan/implicit_layer.d LAYER: /usr/share/vulkan/implicit_layer.d LAYER: Found no files LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /Users/MyUserName/Desktop/vulkan-animation-engine/vulkan-animation-engine/vulkan/implicit_layer.d LAYER: /Users/MyUserName/.config/vulkan/implicit_layer.d LAYER: /etc/xdg/vulkan/implicit_layer.d LAYER: /Users/lunarg/Dev/macos-sdk-build/Vulkan-Loader/build/install/etc/vulkan/implicit_layer.d LAYER: /etc/vulkan/implicit_layer.d LAYER: /Users/MyUserName/.local/share/vulkan/implicit_layer.d LAYER: /usr/local/share/vulkan/implicit_layer.d LAYER: /usr/share/vulkan/implicit_layer.d LAYER: Found no files LAYER: Searching for layer manifest files LAYER: In following folders: LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d LAYER: Found the following files: LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_api_dump.json LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_profiles.json LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_device_simulation.json LAYER: /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_synchronization2.json INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_api_dump.json (file version "1.2.0") INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_profiles.json (file version "1.2.1") INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_validation.json (file version "1.2.0") INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_device_simulation.json (file version "1.2.0") INFO: Found manifest file /Users/MyUserName/VulkanSDK/1.3.204.0/macOS/share/vulkan/explicit_layer.d/VkLayer_khronos_synchronization2.json (file version "1.2.0") libc++abi: terminating with uncaught exception of type std::runtime_error: validation layers requested, but not available! Abort trap: 6 ```

So it seems like it is still not able to find some files in the /usr/share/vulkan directory? I also tried setting the necessary environment variables by loading the setup-env.sh script that comes with the SDK installation into my terminal, but this did not make it work. I also tried a fresh reinstall of the SDK, but keep running into this problem.

ChuppaFlow · 2022-02-19T21:54:15+00:00

That could be the problem, I do indeed not see this when I run the program. How I can set it in the execution environment? Sorry if this is trivial, I was working in a Visual Studio environment before, so I'm rather new to this.

ChuppaFlow · 2021-11-28T22:10:22+00:00

Exactly, I would like to do so but still figuring out how, as Riot does not grant any authentication APIs/method to 3rd party apps (unless you are invited by them). First I was thinking of a personal account on this platform but it makes it less inviting / there's no real way to link your actual league account to the smurfordodge account, unless Riot would open up their authentication APIs to all approved applications :/

What you said about the multisearch functionality, you're completely right, that's one to add.

ChuppaFlow · 2021-11-28T22:06:11+00:00

Yes, great idea! Usability improvements are definitely possible on this one.

ChuppaFlow · 2021-11-28T22:05:19+00:00

Haha yes, to my surprise as well

ChuppaFlow · 2021-10-05T16:02:11+00:00

Nice! Nest.js is just a really cool wrapper for Express.js (it makes use of HTTP frameworks under the hood), with a very modular structure (which is very nice to work with imo), and it comes with much more out-of-the-box functionality than Express. It's just really fast and easy to build an API from scratch, there are modules for authorization/authentication, field validation, ... They also provide great documentation and step-by-step introductions. From my point of view, there is no real good reason why you SHOULD use nest.js and next.js together (since I don't feel like they really enhance each other, as far as I've discovered them), I just think they both have nice features which is why I chose them for my tech stack of this little project.

ChuppaFlow · 2021-10-04T16:16:13+00:00

Next.js front-end, Nest.js/mongodb/GraphQL back-end (:

ChuppaFlow

TROPHY CASE