-
Notifications
You must be signed in to change notification settings - Fork 66
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
GPU/driver lacks sufficient vertex uniform vectors for QuadShader. #14
Comments
It should fall back to the triangles-based shader in this case. It's just an informative message. |
And it means what it says, the QuadShader needs the GPU to support a minimum number of "vertex uniform vectors" which your GPU (or driver) does not. It's not a big deal. The QuadShader is not that much better than the IndexedTrisShader. |
But it's not doing the fall back, when this message appears the game just hangs saying that
|
That's unrelated. |
foobraco same issue with me after upgrading to 1.5.1, wondering how u solved it finally |
@neerajnagi if it is about the Quadshader, Michael was right, it does a fallback so it is just a warning, the OutofMemoryError, it seems like it was part of our implementation on a tilemap of interactive background we had. |
@foobraco but the application hangs ultimately with black screen. My use case is very simple where I am getting this error. I am just drawing an imagelayer, and thats it. And no one else is getting this error on playN group, I am really surprised. |
@neerajnagi but your problem is with the Quadshader or with the OutofMemoryError? If it is the first one, there is no much I can do to help you, is a GPU issue, and the second one, was resolved by another member of my team, but with your use case, you shouldn't be having memory issues. |
application is not responding and just hangs so its a memory issue. |
I just receive this error on the java backend after upgrading my game to a 1.5-SNAPSHOT, it was working fine with 1.4.
Is this error a result of my hardware, wich is kind of dated, or there was some change that could be triggering this?
The text was updated successfully, but these errors were encountered: