You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As new features are introduced, it would make sense to branch of to a OpenGL 3 backend implementation because right now, most of the code is GL 3 compatible and might get lost in the process of OpenGL 4 advancement!
Along with that, motor needs gen3 objects.
Also make sure to share as much OpenGL code as possible among OpenGL 4, OpenGL 3 and OpenGL Es3! Otherwise the amount of code could get out of hand and would lead to an absolute divergence when new engine features are implemented and need testing!
The text was updated successfully, but these errors were encountered:
aconstlink
changed the title
Branch of an OpenGL 3 backend from the current OpenGL 4 backend
Branch off an OpenGL 3 backend from the current OpenGL 4 backend
Mar 6, 2024
As new features are introduced, it would make sense to branch of to a OpenGL 3 backend implementation because right now, most of the code is GL 3 compatible and might get lost in the process of OpenGL 4 advancement!
Along with that, motor needs gen3 objects.
Also make sure to share as much OpenGL code as possible among OpenGL 4, OpenGL 3 and OpenGL Es3! Otherwise the amount of code could get out of hand and would lead to an absolute divergence when new engine features are implemented and need testing!
The text was updated successfully, but these errors were encountered: