SiegeLord
SiegeLord
Perhaps related to https://github.com/liballeg/allegro5/issues/1549 ? I don't have better suggestions than shutting down Allegro manually. > I see that the ALLEGRO_DISPLAY struct has a bitmaps member, so my ask is:...
Oh I see, I read what you said more closely... let me think.
Could you clarify what you mean here? Do you have a test case?
https://github.com/liballeg/allegro5/pull/1645 could also be a fix, but hard to day: the crash for that one was elsewhere
What version are you using?
Is it possible to get them to try a build from master? There have been some fixes on that part of the code recently.
Yeah, I can't seem to reproduce this. I had a different issue with those flags set, which I fixed in https://github.com/liballeg/allegro5/commit/fd9b8199177f96a9e8a00d0e46166f7822a334bb
Proposed changes to the display etc (type names TBD, they might stay as `ALLEGRO_` prefixed): Remove: - `flush_vertex_cache` - `prepare_vertex_cache` Add API from primitives addon: - `int draw_prim(const void* vtxs,...
Roughly speaking, we'd support the following settings. 1. OpenGL 3.3 core (use vertex + index buffers + vao for the batch) 2. OpenGL
Not clear what to do about `ALLEGRO_CFG_SHADER_HLSL`, in some ways it was always wrong since Primitives addon used HLSL 100% of the time. Could perhaps treat it as going into...