The performance of this build is indeed very poor. I'm seeing about a 2x slowdown from 2.50.2 here. Time to break out the profiling tools!
 Yeah.... ZoriaRPG: Compile 2.53 (with the same settings) and link with the old allegro4.2 lib [and not 4.4] instead. You should see it (if for some reason you don't can you upload that here to make sure).
Gleeok, is there any chance you would be willing either to stream the process that you go through in figuring this out; or record and upload it? I do not need live commentary, or to chat during a stream. I merely want to watch you work it out, so that I can learn how you handle it, for the future.
Edit. Flidd, I replied without refreshing. Allegro 4.2 is just plain out, as it is the pure source of half a dozen critical bugs that this fixes; and future stuff completely relies on it. If the performance drop is purely caused by 4.4, and there is no way to rectify that (still using 4.4) , its just a bitter pill to swallow, and move on for now.
Future builds are destined to have even greater system requirements too. Hell, jman was recetly talking about using HW rendering in the future, which would make it nearly impossible for me
to run ZC at full speed on any system that I own.
The only thing that I can suggest, might be to try the 4.4.3 version of allegro that is only on GitHub, and hope that it addresses performance issues. I believe that we are using 4.4.2, but I have no clue what was actually changed between the two, as there is no basic changelog entry for 4.4.3, and I would need to review all the GH commits for it.
I'm open to suggestions, but if people can't run this because it uses ag4.4, and runs too slow, then why are they running stuff like Windows 10 on their HW?
Edited by ZoriaRPG, 13 July 2017 - 06:44 AM.