Vulkan is currently broken in Star Citizen and this is a much bigger problem than it looks. Right now the game crashes at startup when Vulkan is selected on NVIDIA GPUs because Vulkan device creation fails. The reason is already known and documented by the community: the engine is requesting invalid or incompatible Vulkan extensions during vkCreateDevice, including AMD-specific extensions on non-AMD hardware and duplicated extension requests. This causes Vulkan initialization to fail immediately on NVIDIA drivers. This is not a driver issue and not a hardware issue. It is an engine-side configuration and validation problem. Why this matters: Vulkan is supposed to be the future rendering backend of Star Citizen, but this bug prevents Vulkan from even starting. That means players cannot test it, cannot provide feedback, and cannot help stabilize it. Modern RTX GPUs are affected, so this is not an edge case. The worrying part is that the fix is trivial. The engine simply needs to validate requested Vulkan extensions per vendor and avoid requesting unsupported or duplicate extensions. The community has already proven that filtering those extensions makes Vulkan start and run immediately. This is not theoretical. It has been reproduced, logged, and confirmed. The issue is tracked as STARC-178555. The real problem is visibility. Because this bug is highly technical and only visible in Vulkan logs, most players never understand what is happening. They just switch back to DX11 and move on. As a result, Vulkan looks unstable when in reality it is misconfigured. If Vulkan is meant to become production-ready at any point, this issue needs confirmation and prioritization. Ignoring it now means wasting future development time and losing valuable testing feedback from the community. This is a small fix with a very large impact. If you care about Vulkan, performance, and the long-term health of the engine, please reproduce, upvote, and push STARC-178555.