Skip to content
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

Fix backEnd.currentVAO #1513

Merged
merged 1 commit into from
Jan 24, 2025
Merged

Conversation

VReaperV
Copy link
Contributor

This was previously getting reset in R_Init(), so it was always 0 after a map was loaded. This also meant that the call to glDeleteVertexArrays() in RE_Shutdown() was silently erroring out if a map was loaded (or vid_restart used).

@slipher
Copy link
Member

slipher commented Jan 22, 2025

Is it even used for anything?

@VReaperV
Copy link
Contributor Author

Is it even used for anything?

Yeah, a VAO is required for any vertex specification commands (and by extension the typical rendering commands).

This was previously getting reset in `R_Init()`, so it was always 0 after a map was loaded. This also meant that the call to `glDeleteVertexArrays()`  in `RE_Shutdown()` was silently erroring out if a map was loaded (or `vid_restart` used).
@slipher
Copy link
Member

slipher commented Jan 24, 2025

LGTM

@VReaperV VReaperV merged commit 8cc5260 into DaemonEngine:master Jan 24, 2025
9 checks passed
@VReaperV VReaperV deleted the fix-current-vao branch January 24, 2025 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants