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.

Sign up for GitHub

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

Jump to bottom

Mechanism to disable Hardware Features on a per-app level #102

Open
haraldsteinlechner opened this issue Dec 19, 2023 · 1 comment
Open

Mechanism to disable Hardware Features on a per-app level #102

haraldsteinlechner opened this issue Dec 19, 2023 · 1 comment

Comments

@haraldsteinlechner
Copy link
Member

haraldsteinlechner commented Dec 19, 2023 •
edited

I just learned that some drivers claim to support MultiDraw but crash hard when rendering. Similar things are persistently mapped buffers, and several other features where we have workarounds.
Currently those flags reside in RuntimeConfig - would this be a good location to also allow to switch of MultiDraw?

RELATED: #78
@hyazinthh
Copy link
Member

A RuntimeConfig flag is probably the way to go if we want to control this manually. The workaround for glMultiDrawElementsIndirect in GLVM checks if the function exists and then uses glDrawElementsIndirect if that is not available. So in your case the function exists but crashes?

https://github.com/aardvark-platform/aardvark.rendering/blob/master/src/GLVM/glvm.cpp#L1020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@haraldsteinlechner @hyazinthh