SiegeLord

I wouldn't even begin to know how to compile A4 on windows, could someone try this?

Note that we have fixed the flickering in https://github.com/liballeg/allegro5/commit/b1f96f7bf0a6221b0e6110358971f99bba96f237 (and 3 more commits after that). As part of that, we found an issue that the D3D sample selection was fundamentally...

No. Slated for 5.2.8 which is coming soon:tm:

I don't have an Intel GPU to test with, but given how broken this system was before, perhaps it's fixed there now as well?

If you'd like, you could test the development binaries I made a few months ago. They have the commits above in them: http://siegelord.net/files/5.2.8%20dev/

That's interesting. If you catch the `ALLEGRO_EVENT_KEY_CHAR` event, does that contain a quote in its unichar field?

Which file did you download? I tried `allegro-x86_64-w64-mingw32-gcc-10.2.0-posix-seh-static-5.2.7.0.zip` (note the `static` suffix, which is what indicates that the runtime libraries you mention are linked in), and it worked for me.

This is an interesting idea, we certainly could get the MSYS2 builds working automatically.

While we think of what to do, here's a build for you: http://slabode.exofire.net/files/allegro-i686-w64-mingw32-gcc-10.3.0-posix-dwarf-static-5.2.8.0.zip Note that there's no such thing as OpenGL multisampling fixes, we only changed the D3D code.

Would things be better if we generated frameworks instead of dylibs?