-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Various issues around types that are valid in gpu-structs and the ssbo interface #233
Comments
In the above example - most importantly - you can make an SSBO on a byte array, but then you are thoroughly fucked:
|
Actually, it's even worse... The only way I can get an SSBO across:
So, let me get this straight. In order to pass an array, you have to put it into a struct, and then you have to put that struct into an array of 1, stick an SSBO label on it and pass it to a shader? |
Mo*****er! The above method works, except it's impossible to get to the data! There are 3 indirections:
And that comes in as a C array; I have no idea if it has anything to do with the GPU array. Shite. |
It just gets better! Assuming that the above code is correct, the final dereference requires the actual defstruct-g to get the C array. It seems that there is no |
The fuckery is not over for me. Just as I got comfortable using the C arrays as standins for the GPU arrays, and wrote a fair gob of code, I realized that I am screwed yet another way:
My ass hurts from this treatment. |
char isnt a types supported in glsl It definitely supports scalar types:
in fact when compiling you examples it even suggested scalar types when it couldnt find a glsl type that matched
It'll take a bit to pick the issues out of this thread. I see some stuff relating to how ssbos are defined which has validity and even tickets already raised on these repos to address them. |
Unless I am missing something... int and float works fine, but I want to make structs, man!
This one made me laugh (cry?) as right next to it I have - with a different syntax for type...
The text was updated successfully, but these errors were encountered: