Eruanna wrote:Your card supports OpenGL 3.0. It should perfectly support the render buffer features just fine. I don't know - I'll leave this to one of the main programmers, or another techie, to figure that one out, because from what I can see there's no reason this shouldn't work.

Yes, it's really strange. The effects was working fine some versions ago (g2.2pre-2067-g2f893af for example, from Aug 24).

Does it report the presence of GL_ARB_uniform_buffer_object? This extension is a requirement to get the 'modern' render path, without which the postprocessing is disabled.
This wasn't the case in the earlier revisions. I had the choice between making a clear distinction between 'legacy' and 'modern' or allowing mixed configurations to run. I chose the former because it means a significant reduction in workload and was really the only solution to get the 'modern' render path working on macOS. Your card may just have been caught square in the middle of it.

If you can get a decent graphics card installed in that system, sure. It not only will have more features but also be a lot faster. Even the lowest of low end cards, like a Geforce 610 would do a lot here.
The intel Q43/45 is among the weakest chipsets still supported and the feature set is dismal.

fr1dd wrote:Has the following been removed completely and can no longer be controlled as a global setting?

gl_lights_size=
gl_lights_intensity=

Yes, it has.

Ok. And there is no alternative/workaround for this?
Reason for asking is because I think that dynamic lights with lights.pk3 generate too much light and doens't look realistic or create the right atmosphere in dark maps.

Graf Zahl wrote:Does it report the presence of GL_ARB_uniform_buffer_object? This extension is a requirement to get the 'modern' render path, without which the postprocessing is disabled.
This wasn't the case in the earlier revisions. I had the choice between making a clear distinction between 'legacy' and 'modern' or allowing mixed configurations to run. I chose the former because it means a significant reduction in workload and was really the only solution to get the 'modern' render path working on macOS. Your card may just have been caught square in the middle of it.

Oh... there is any way to know if I have this extension?

If this is the problem, what could I do? I need to buy a new card or it's something that I can solve with a download/update?

GZDoom prints the list of extensions to the console when starting. You can log that to a file with the '+logfile' command line parameter and then search the created text file. If this is the reason, a hardware upgrade would be the only way to get the modern features - I hope this isn't a laptop where such things are often impossible.

Is the openAL sfx library shipped with the x64 build the 32-bit version of that library or does the numeric suffix of the file name signify a version number? Regardless of which is the case, would it not be easier for the library to be dropped from the official build and distributed separately, á la fluidsynth?