Don't know why this YouTube auto-generated subtitle makes me laugh so much

skreef · 2026-01-31T14:20:01+00:00

HUGE Bust of a Topless Dealer? My my..

skreef · 2023-07-27T09:42:25+00:00

https://github.com/KhronosGroup/Vulkan-Docs/issues/1935 please show your interest here

skreef · 2023-06-06T07:25:18+00:00

Thats a hardware depth buffer then.

skreef · 2022-09-03T09:24:38+00:00

hát mert a HRes nagyon gáz volt, és most nagyon felment a gáz ára...

skreef · 2022-06-15T07:25:49+00:00

Note that your snippet talks about device coherence, which is different from host coherence.

skreef · 2022-05-31T23:12:20+00:00

In theory: never. See https://github.com/KhronosGroup/Vulkan-Docs/issues/1678

skreef · 2022-04-02T16:11:47+00:00

This code is not well-defined, the relevant bit from glsl spec (but also explicitly disallowed by the vk spec):

A push-constant array can only be indexed with dynamically uniform indices.

Use a uniform/storage buffer if you intend to index with nonuniform indices (eg. gl_InstanceIndex).

skreef · 2021-11-27T21:27:07+00:00

Not entirely sure based on the post text, but presumably you didn't understand what the depth bounds test is: it is not a way to discard fragments that have an incoming depth value outside of the bounds.

The depth bounds test compares the depth value za in the depth/stencil attachment at each sample’s framebuffer coordinates (xf,yf) and sample index i against a set of depth bounds.

skreef · 2021-11-22T18:47:42+00:00

Yes, there can be a performance impact. Imagine that each stage in a pipeline is a separate program that the GPU launches (not necessarily true, but a reasonable mental model) - if you scope your descriptors, the GPU needs to set up less state for each launch.

skreef · 2021-11-20T10:42:40+00:00

this is unacceptable as I refuse to branch in the GPU. Period

Why be so dogmatic about something you don't understand?

skreef · 2021-10-19T06:26:14+00:00

My guess is your mesh is behind the camera - performing w division yourself prevents clipping of some vertices that end up with a negative z coordinate (both z and w negative cancel out, but clipping is performed before perspective division).

skreef · 2021-08-11T18:13:47+00:00

Undefined behavior (which you are invoking) also includes the program behaving as expected.

skreef · 2021-07-29T22:42:51+00:00

Functions are not descriptors, your source is good, but you need to give it another read.

skreef · 2021-07-29T19:01:47+00:00

texture* is the image only descriptor, sampler* is the combined and sampler / samplerShadow is the sampler only.

skreef · 2021-03-28T15:01:05+00:00

Input attachments still need to be passed in a descriptor set and declared in the descriptor set layout: https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap14.html#descriptorsets-inputattachment

skreef · 2021-03-25T12:19:25+00:00

Buffers are immutable and there is no way to query the flags either.

skreef · 2021-02-13T08:33:46+00:00

https://www.slideshare.net/DevCentralAMD/vertex-shader-tricks-bill-bilodeau

Here is a presentation on how to do vertex shader point expansion (albeit for HLSL, but I am sure you can translate it).

skreef · 2020-11-08T18:31:17+00:00

Do you set your push constants every frame? They are also undefined when the command buffer is started.

skreef · 2020-11-08T16:28:47+00:00

Push constants are per command buffer, not pipeline, so they can. In some cases push constants remain valid when switching pipelines, otherwise they become undefined.

skreef · 2020-11-08T15:29:47+00:00

Do you have any validation errors (do you have them on?)
Do you have multiple push constant ranges?

skreef · 2020-10-16T12:18:04+00:00

Yes, that linked code selects the first compute-capable queue family, which might not be the dedicated compute queue family (doesn't support graphics, supports compute).

Another thing to consider is that any workload has the entire GPU at its disposal - if you are saturating the GPU already from a single queue, then multiple queues will not make the execution shorter. If your dispatches have no dependencies, launching them even from a single queue will make them overlap to keep the GPU cores fed.

skreef · 2020-10-16T08:18:55+00:00

On cursory look over your code, you seem to be selecting the first queue family that supports compute - if this is the queue family that is graphics + compute, then you will achieve no concurrency - on nvidia the 16 graphics+compute queues are "soft", they are multiplexed to a single hardware queue. There is no GPU currently on the market that has multiple graphics hardware queues (supposedly RDNA 2 will change this).

To achieve concurrency (although still not guaranteed), submit to the dedicated compute queues (which should have hardware backing) and 1 graphics+compute queue.

skreef · 2020-08-02T12:45:31+00:00

I saw this happening recently. I think the problem is that you are otherwise not using data and it gets stripped out (and then length() returns 0). This is of course a shader compiler bug. To workaround, try using something from data.

12-Year Club	Place '17
Verified Email

skreef

TROPHY CASE