- User Since
- Apr 27 2010, 10:07 PM (338 w, 5 d)
Sat, Oct 22
I don't know why that would glitch. You enable GL_MULTISAMPLE before drawing and disable right after. *shrugs*
Fri, Oct 21
Thu, Oct 20
Alert!! Work in temp-blender2.8 branch for now.
WTF, this is not what I intended to commit. Damn you GitKraken!!!
If my previous comment explains the problem, it's probably best to remove the confusing immRecti & have only immRectf. Minimal APIs are easier to understand / harder to screw up.
@Dalai Felinto (dfelinto) Did you set up pos like this in the calling function?
GL_INT, 2, CONVERT_INT_TO_FLOAT
If pos is GL_FLOAT then immRectf is more suitable.
This looks good.
Wed, Oct 19
Should we have another shader that combines texture and a uniform color or update GPU_SHADER_3D_IMAGE_MODULATE_ALPHA to do this job?
Tue, Oct 18
The overall organization (UI) makes a lot of sense.
Yes, as of Blender 2.77 we are very clear about what GL version is supported. Extension checks seem to be complete. Blender closes with a message if the host system can't run it.
Also, removing matrix calls = progress on T49450.
In a twist of fate, Windows & Linux now work for me, but Mac started having the triple buffer issue.
Mon, Oct 17
Sun, Oct 16
Sat, Oct 15
Passing in start + end points and getting a fancy curve drawn would be awesome!
@Krantz Geoffroy (kgeogeo) is patch author
landed in blender2.8
Fri, Oct 14
We decided to bump system requirements to Mac OS 10.9 "Mavericks". Mostly for its improved C++11 runtime. This also lets us bump OpenGL version to 3.3 on all platforms!
Looks good to me!
Thu, Oct 13
Always good to draw nothing when there is nothing to draw.
Wed, Oct 12
I also value simplicity. From a dev perspective it would be nice if the old model can be dropped and we have one "official" sky model. Do we know if the Preetham model is in wide use?
Good so far, comments below.
Tue, Oct 11
Forgot to mention, this is a big part of T49450
On Intel HD 4000, latest OS 10.12, Blender 2.78 -- it works for me.
I'll take a look
As we all know, the legacy viewport will exist only as long as it's needed, and won't ship with final 2.8. If the purpose of this proposed system is to allow old & new viewports to live together... well that will only be needed for a few months! I'd rather use duct tape for temporary problems instead of designing a new system to handle them. @Julian Eisel (Severin) how will this flexibility benefit us (developers and users)?