Blender BGL module deprecation message - add information about the addon that trigger's it

Couldn't find any info about it in info editor :\

This has been discussed, feedback was gathered and the gpu module was improved.

You can read your statement as: Users want to use new features provided by their GPU, but add-on developers don't want to because it requires them to use a different paradigm.

Imo add-on developers have been given all the support to migrate and give feedback to the developers and these have been addressed. If add-on developers haven't done so, it isn't about the gpu module lacking a specific feature, but mainly how to address these features or that they haven't checked how to do so.

Fair enough, I was following along with the BGL deprecation discussion for a while but have not checked recently. That said- when so many addons are still using BGL this close to the sunset date you have to wonder why they have not switched over yet. It could be symptomatic of a greater issue, some BGL feature that was not covered in feedback, or perhaps some lack of understanding on what they need to do to update their addons for GPU support.

Personally, all of my addons have been updated to use GPU, but I did run into one missing feature that I used extensively (bgl.GL_LINE_SMOOTH_HINT, et al). When I asked about it I was told to write a custom shader pixel shader.. okay cool. kind of a blow-off answer, but I did. I'm not sure if there are other similar features that are missing that could be turning addon devs away from upgrading, but there's one example.

My point being- if addon devs aren't updating, you guys should really be asking yourselves "why?" and not just assume people are being lazy.

Yes, it is also on my radar.

Issue is that we cannot track random add-ons/scripts from the internet. So we are only aware of add-ons who are commonly used by users that are willingly to report it. Looking at blendernation, blendermarket and other market places typically used, new add-ons appear on a daily basis. We cannot keep track which one of them uses a specific feature and requires an update.

We also improved the smooth line issues by introducing the POLY_LINE shaders. This should remove most custom shaders that just want smooth lines. I wasn't aware of them, and might have pointed people in the wrong direction once. Sorry about that.

I hope I didn't give the impression that we find add-on developers lazy. That is totally not the impression we have or the message we give. Communication should happen from both ways and communication is hard too do correct especially as we want to be an open community.

Fail: I tried to like your post, but wasn't able to :-(

Btw is there some example of code transitioning from bgl to gpu ? Wanted to replace some bgl statements I've been using like

bgl.glEnable(bgl.GL_LINE_SMOOTH)
bgl.glHint(bgl.GL_LINE_SMOOTH_HINT, bgl.GL_NICEST)
bgl.glBlendFunc(bgl.GL_SRC_ALPHA, bgl.GL_ONE_MINUS_SRC_ALPHA)
bgl.glBlendEquation(bgl.GL_FUNC_ADD)
bgl.glEnable(bgl.GL_DEPTH_TEST)
bgl.glEnable(bgl.GL_POLYGON_OFFSET_FILL)

etc and was looking for a easier way to do it without diving into opengl and writing custom shaders

I also am looking for this. Particularly the glBlendFunc one. For some, you got the answer for this stackoverflow question: Addon stopped working on Mac/Metal in v3.5+ due to shader compile error. Console spam errors about bgl.glEnable calls

Everyone checking that way for the same thing is kind of cumbersome.