Second option - allegro5.cfg
You can also create an allegro.log by modifying the allegro5.cfg and putting it in the same folder as the Lix executable. (This works even with release DLLs, i.e., with the DLLs that Simon offers in the main download. You don't need debug DLLs.)
allegro5.cfg can be found in the allegro5 github repo. Below [trace], which is in line 193 as of January 2025, set the trace level (level=) to one of the following lines:
Save this allegro5.cfg in the folder where lix.exe is. Then run Lix as normal. After playing, you'll find allegro.log in the same folder. Read it with any text editor.
(Simon restructured/edited this post for better readability/information.)
You can also create an allegro.log by modifying the allegro5.cfg and putting it in the same folder as the Lix executable. (This works even with release DLLs, i.e., with the DLLs that Simon offers in the main download. You don't need debug DLLs.)
allegro5.cfg can be found in the allegro5 github repo. Below [trace], which is in line 193 as of January 2025, set the trace level (level=) to one of the following lines:
level=debug | ... to get all the information, but this will produce a huge logfile, |
level=info | ... to get lots of info, but not everything; this is a good level, |
level=warn | ... to get errors and some extra information, |
level=error | ... to get errors only. |
Save this allegro5.cfg in the folder where lix.exe is. Then run Lix as normal. After playing, you'll find allegro.log in the same folder. Read it with any text editor.
(Simon restructured/edited this post for better readability/information.)