Allegro5 for AmigaOS4.1

@samo79

Thank you for providing this comparison but as written on OS4Coding:

https://os4coding.net/forum/optimizing ... es-library-threading-code

This is not the problem, it was only an initial assumption.

@samo79

Quote:

Paranoid will probably show the same cpu load. Anyway it would be interesting how much FPS you get with default settings. When you have the FPS value for the default settings you can press the 'M' key 4 times on your keyboard to render the game only in a small frame. This FPS value would be interesting as well.

@IamSONIC

Yeah, even on this little game CPU hit 100% usage

As for the FPS:

In default window i have 40 FPS
While on smaller screen i reach 150 FPS

Game for itself is quite playable can say

Interesting to note, CPU still always at 100% even if the game is paused

@samo79

Quote:

Yes, simply everthing using Allegro Library causes 100% CPU Load, this is the problem we need to get rid of!

@samo79

Quote:

In default window i have ­210 FPS
While on smaller screen i reach 830 FPS

Anyway animations doesn't look and interaction doesn't feels like 210 FPS. This affects all Allegro Games. It's a bit better in Fullscreen.

Do you still have an AmigaOS 4.1 Installation NOT Final Edition around to verify this problem exists or not on OS4.1 prior FE. I had a Sam440ep in the past and don't remember this "handbrake" behavior.

@IamSONIC

I guess you post here to get some feedback on Allegro4, thats not same code as Allegro5, but I suggest that signal is per process / task / thread, they are not shared between processes.

If your Wait is always awakened it has to be because, something is always feeding it a signal, causing it to not wait.

line 24, if a thread signal is triggered, then timer signal is not checked on line 29, this might be a bug.

If the delta time is spiky then it probably because of this.

Is interval delta on line 34 giving you too low values? if so then the timer signal is generated too often.

I hope this helps.

@IamSONIC

I also suggest trying to profile the game, somehow, try figure out what parts is most often called, it is technically possible to suspend a running task, and to do a stack trace on it, to see where you are stuck.

@IamSONIC

Quote:

Actually not, but i remember this library have exactly the same problem even at the time it was released (around 2010 or so) so most probably it doesn't depend on this

But we can investigate in another direction, as the same library was ported also on MorphOS we can verify if they have the same problem also on that platform, if same problem happen to them we can atleast excluding that problem is related to the OS used

Better port Raylib.