Do any other allegro 4 games or any one of the the allegro examples work at all on Windows 10 machines that also crash ZC?
Printable View
Do any other allegro 4 games or any one of the the allegro examples work at all on Windows 10 machines that also crash ZC?
@DarkDragon : Would you these binaries please, and inform me if it does the same thing:
1. Open the ZQuest binary, then make a blank custom quest, and save it.
2. Open the ZC binary skipping the intro screen.
3. Open the custom quest that you saved, and see if you can alt+tab safely, or if it still crashes.
The intro screen in that build, and some music stuff is still unstable, but I'd like to know if it resolves your issue otherwise. We're working on making this bastard branch stable, but it's a slow process.
The executable will not run with my version of alleg42.dll. Did you recompile Allegro with a different toolchain?
[Frack, I hit edit instead of quote. Fixed.]
Oops, I forgot to include the libs.
Recompiling allegro was of course, mandatory for this, and something went awry...The obvious suspect is alogg, which has been deprecated by logg.
Make a backup of alleg42.dll, and libzcsound.dll and temporarily replace them with the libs in this pakage.
alleg44.dll can live perpetually, but I forgot to fix things a bit, and it still pumped out alleg42.dll, despite this library actually being 4.4, as a special dep. We'll eventually remedy that. Suffice to say, that it needs both the included ag44.dll and the included ag42.dll to run, and that this ag.42.dll differs from the one in the 2.50.3 package, so you will need to rename the existing library, and drop this in, or just duplicate the directory and drop in everything. Likewise, libzcsound.dll is also different, as it uses the allegro 4.4.3 packfile password functions.
Those are the root of all evils, with regards to the migration.
Alright, after hours ofbanging my headraging against the dying of the lightdealing with Micro$oftraping myself with Windows 10contemplating suicidegetting ready to drink myself into a comamessing with ZC on my super-awesome engineering-marvel-of-the-world Windows 10 machine, I conclude that it basically works the same as on Windows 7 except that it even worse in the managing FPS department and it indeed does crash toggling fullscreen mode. I couldn't get very far in DirectX layer either; it seems to run through some compatibility layer and I have no idea how it works. It has an AMD card in it, and GPU debugging was not very successful. Aside from that, it runs surprisingly well.
Why does ZC still default to fullscreen though? I thought I changed that years ago.
(Emphasis, mine.)
Sounds like you're having a fun day. :/
Good point there. Not sure why that is the default, but should be easy enough to change out. The default for ZCL is windowed mode, but running the binary raw, fullscreen. You could always pack DXGL with it I suppose? Is the code for that open, or closed?
I still need some analysis on the test binary, as I think it should be better with some of this.