You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
//if prev and curr pipeline layouts are compatible for set N, currState.set[N]==nextState.set[N] and the sets were bound with same dynamic offsets, then binding set N would be redundant
2033
+
/*
2034
+
// @Crisspl this is BUGGY.
2035
+
// Imagine I have desc sets A, B, C
2036
+
// I do some compute work while binding a pipeline layout with {A,B,C,nullptr}
2037
+
// then I do some graphics work while binding a pipeline layout with {nullptr,B,nullptr}, I only ever use one pipeline
2038
+
// when I do the graphics flush, the bindings will not be updated because prevLayout and currentLayout come from graphics (and are the same)
2039
+
// AND the effectivelyBoundDescriptor matches with the only descriptor of the graphics bind point (both are B) this leads to problems
2040
+
// you need to detect if switching effective pipelines (graphics to compute and back) will cause offsets to shift
2041
+
// my suggestion is to track `current.effectivelyBoundDescriptors` and `next.effectivelyBoundDescriptors` then work from that instead of compare the next state for a pipeline with "previous" effectivelyBoundDescriptors
0 commit comments