Just learned that there is no way for a GLSL shader to send data to the CPU side program.
-
@kertinker @landelare also if you happen to be on linux could you paste the output of glxinfo to a pastebin somewhere and link it here?
@aeva @landelare Oh, sure. I don't have a "glxinfo" command, but visualinfo produces this: https://nopaste.net/l92XzrU5kr which... oddly includes GL_EXT_shader_image_load_store.
I'm clearly doing something wrong. Not sure how I could get a working OpenGL program running, without it saying extensions that are supported, are supported. Maybe you have to set a specific... mode, before they get supported?
-
@aeva @landelare Oh, sure. I don't have a "glxinfo" command, but visualinfo produces this: https://nopaste.net/l92XzrU5kr which... oddly includes GL_EXT_shader_image_load_store.
I'm clearly doing something wrong. Not sure how I could get a working OpenGL program running, without it saying extensions that are supported, are supported. Maybe you have to set a specific... mode, before they get supported?
@kertinker @landelare if you can, post your GL initialization code
-
@kertinker @landelare if you can, post your GL initialization code
@aeva @landelare https://nopaste.net/aTFTXWDVRU
Other than that just the usual gtk init and creating a GtkGlArea.
-
@aeva @landelare https://nopaste.net/aTFTXWDVRU
Other than that just the usual gtk init and creating a GtkGlArea.
@kertinker @aeva Are you running on some kind of retro system? These features are ancient, we're talking 2009 hardware.
-
@aeva @landelare https://nopaste.net/aTFTXWDVRU
Other than that just the usual gtk init and creating a GtkGlArea.
@kertinker @landelare what is the GL major and minor version reported by your program?
-
@kertinker @landelare what is the GL major and minor version reported by your program?
@kertinker @landelare I'm not familiar with GtkGlArea, but I spotted this in the docs https://docs.gtk.org/gtk4/method.GLArea.set_required_version.html
You have to call gtk_gl_area_set_required_version before the widget's rendering context is created, but I imagine if you set it to 4.6 (based on your earlier visualinfo paste) then you should be able to see the extensions you are missing. Ideally you'll want to set it to the lowest required version you need, but 4.6 is fine for debugging.
-
@kertinker @landelare I'm not familiar with GtkGlArea, but I spotted this in the docs https://docs.gtk.org/gtk4/method.GLArea.set_required_version.html
You have to call gtk_gl_area_set_required_version before the widget's rendering context is created, but I imagine if you set it to 4.6 (based on your earlier visualinfo paste) then you should be able to see the extensions you are missing. Ideally you'll want to set it to the lowest required version you need, but 4.6 is fine for debugging.
@kertinker @landelare it occurred to me just now if there's an explicit GL context initialization step needed that is missing entirely, then GLEW might be reporting 0 for most or all extensions depending on the platform you're on
-
@kertinker @landelare it occurred to me just now if there's an explicit GL context initialization step needed that is missing entirely, then GLEW might be reporting 0 for most or all extensions depending on the platform you're on
This post is deleted! -
@kertinker @landelare it occurred to me just now if there's an explicit GL context initialization step needed that is missing entirely, then GLEW might be reporting 0 for most or all extensions depending on the platform you're on
@aeva @kertinker This crap is why I'm using DirectX.
-
@aeva @kertinker This crap is why I'm using DirectX.
@landelare @kertinker as it happens, Windows is the really weird one for GL