Extreme Lag Linux ZC 2.5.2

Normally this wouldn't be considered a bug, but granted the lag is so horrible in 1st quest there has to be something wrong with the code.
The problem only occurs for me for resolutions above 240p even though I have a pretty decent computer.

Here are the specs:
http://i.imgur.com/sG8djPb.png

https://www.youtube.com/watch?v=ng2o...ature=youtu.be

Also another issue which is most definitely a bug.
(zlaunch-l:15290): GLib-CRITICAL **: Source ID 57 was not found when attempting to remove it
(zlaunch-l:15290): GLib-CRITICAL **: Source ID 56 was not found when attempting to remove it

The PIDs don't matter but the same GLib-CRITICAL appears every single time I exit zlaunch-l.

Likely an allegro issue. Try setting "color_depth = 32" and "triplebuffer = 1" under [zeldadx] section in the config file just to see what that does out of curiousity.

You might have to run gprof or some equivelent on the code to get a better idea of where in allegro it's failing so miserably.

Oh god it's slower and looks like shit (the shitty part is the same in the Windows version)
I guess I gotta compile from the source for gprof.

http://i.imgur.com/f2bIOc6.png

If I can figure out how to fix this myself, I'll make a new branch just for Linux.

So am I supposed to gprof each individual file in allegro?

XD. ..okay, okay.... I give up. Make sure you check allegro if you can. Whatever it's doing it doesn't like you very much.

[edit] Doesn't linux have some profiling tools? I thought it had some built in, but IDK.

I've been using Linux since I started my Operating Systems class. I think there is but I don't know.
gprof is included with Ubuntu but I wasn't sure what you meant. Everywhere I read it compiles source files slightly differently and shows stats on how long a process takes.

[edit] Been reading this
[edit] I'm sorry but allegro 4 is kind of a pain in the ass, allegro 5 has easier installation but I will get back

Allegro uses software rendering on Linux. Scaling to higher resolutions is also done in software. It's not a fast way of doing things, and it's not easy to change.

I FINALLY got allegro 4 to compile and install. That took me more time than I thought. I didn't test anything yet except the make install.
I specifically only got allegro-4.2.3.1 to compile (dev) with allegro-4.4 base. I had 4.4.2 but I wasn't sure if that library was too high for this.

@Saffith
I agree, changing anything in software isn't easy. Especially if impacted dependencies are deep potentially will break the chain.

I didn't mean to double post I thought it didn't send since my message was still in quick-reply.
I assumed I needed to get the libraries from allegro because I only found header files on github.

I had to do some MAJOR overhauls to configure.ac, install-sh, ltmain.sh, acinclude.m4, and aclocal.m4.
I had to create a makefile myself: Makefile.am.

If I didn't do that it wouldn't have worked.

[edit] Many allegro templates were not there and I had update macros to m4.