-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modernize Renderer #527
Modernize Renderer #527
Conversation
ada33f1
to
81b450d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some quick non-related to functionality request changes.
On Linux I got runtime error:
|
interesting. run it under a debugger and it should give you a stack trace of the failing call. some GL call is failing with |
|
81b450d
to
52305a9
Compare
Force-push to address @winterheart feedback |
Aha, interesting, the edit: ah, i'm not building with |
52305a9
to
16cc66d
Compare
Fixed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR is ready to merge, let's merge it after 1.5 release.
…ngState is redundant with rend_SetLighting
eliminate gl(Enable|Disable)ClientState and glClientActiveTextureARB
Please resolve conflicts on files and we ready to set. |
e455ed5
to
8bd1b67
Compare
Rebased onto latest main |
Retested on Linux, no visible issues found. |
Pull Request Type
Description
Modernize the Descent 3 renderer to use OpenGL 3 (GLES 3, eventually) and shaders. A major caveat here is that this is a minimal modernization of just the OpenGL calls. Performance should be at least as good, but I am not by any means promising that the renderer is now "well-designed". It just now works using non-immediate-mode and non-fixed-function concepts.
Rendering behavior should be identical! Any difference should be considered a bug, unless discussed, determined to be acceptable, and specifically called out here.
Known Issues
None
Related Issues