Messages

Our other option is to have detailed build instructions for lots of different platforms, and WadjetEye can just provide the game data files. BYOE style.

Getting those old libraries should be easy (if we can find an old version of the GR beta). If compiled ags on Fedora 32/64 bit, the resulting binary would work? Or would it need to match the distro the libraries come from?

BigMc can you make us a current build of the engine/libraries that Janet can use to bundle Gemini Rue?

Janet from Wadjeteye contacted me about releasing their games commercially on Linux. One question she asked me was about an installer. I don't have any experience with creating an installer, so I wasn't much help.

1) Do you think they need an installer? Or would a .tar.gz be enough?
2) If they do decide to do an installer, what should they use?

Maybe I'm old school, but I'd prefer a simple .tar.gz with the binaries/assets in it.

Where do we stand on a Mac build? I know the Humble Bundle guy sent us a lot of Mac code. Are we anywhere close to merging that? If we did merge it, do we have a Mac guy who could compile/test it?

Great... glad it was "simple". If you notice any other issues please let us know.

Have you tried it with the Noveau drivers? I've definitely had the issue you describe in other programs (not specifically ags), that was related to a bad video driver.

There are no known pointer lag issues, especially on an updated distro like you have.

What does -hicolor do exactly? And while we're at it, what does -letterbox do? I've never used either of them. Are they still relevant?

I'm looking at changing the --help to be more helpful.

I'm just getting back in to github and AGS, what branch are we working on currently?

I build AGS from the master branch and tried to run Wadjeteye's new Shivah demo and I get this error:

AGS: Built library path: ./libagstouch.so
AGS: dlopen returned: ./libagstouch.so: cannot open shared object file: No such file or directory
AGS: Built library path: /tmp/The Shivah - Kosher Edition (DEMO)/libagstouch.so
AGS: dlopen returned: /tmp/The Shivah - Kosher Edition (DEMO)/libagstouch.so: cannot open shared object file: No such file or directory
AGS: Plugin loading failed, trying built-in plugins...
AGS: No built-in plugin found. Plugin loading failed!
AGS: No placeholder functions for the plugin found. The game might fail to load.
AGS: Built library path: ./libagswadjetutil.so
AGS: dlopen returned: ./libagswadjetutil.so: cannot open shared object file: No such file or directory
AGS: Built library path: /tmp/The Shivah - Kosher Edition (DEMO)/libagswadjetutil.so
AGS: dlopen returned: /tmp/The Shivah - Kosher Edition (DEMO)/libagswadjetutil.so: cannot open shared object file: No such file or directory
AGS: Plugin loading failed, trying built-in plugins...
AGS: No built-in plugin found. Plugin loading failed!
AGS: No placeholder functions for the plugin found. The game might fail to load.
AGS: Built library path: ./libags_shell.so
AGS: dlopen returned: ./libags_shell.so: cannot open shared object file: No such file or directory
AGS: Built library path: /tmp/The Shivah - Kosher Edition (DEMO)/libags_shell.so
AGS: dlopen returned: /tmp/The Shivah - Kosher Edition (DEMO)/libags_shell.so: cannot open shared object file: No such file or directory
AGS: Plugin loading failed, trying built-in plugins...
AGS: No built-in plugin found. Plugin loading failed!
AGS: Placeholder functions for the plugin found.
Script link failed: Runtime error: unresolved import 'IsOnPhone'

Is this an AGS error, or a Wadjeteye error?

For what it's worth I run AGS on Fedora 17 and Fedora 18 both 64 bit, three different machines, and haven't had any audio crackling. Some users HAVE reported it though, I suspect a driver issue incompatibility with AGS/Allegro, but I'm not 100% sure. I haven't seen it enough to test.

What type of audio do you have? Any other audio issues on your system?

Also see: http://www.adventuregamestudio.co.uk/forums/index.php?topic=47590.0 for more build instructions.

Everyone still alive? Been awfully quiet around here lately.

These things are more relevant for an AGS release. Or do you think about doing a beta AGS release?

Do we want to clean up the build process a bit before we look at an "official" release? There are still quite a few warnings on compile.

1) ALSA not set up properly in acsetup.cfg

Can you elaborate?

Produced on the console, even from a stripped release build.

Oh duh... I wasn't seeing the switch messages because I was running -windowed.

AGS: Widescreen side borders: game resolution: 320 x 240; desktop resolution: 1680 x 1050
AGS: Widescreen side borders: gfx card does not support suitable resolution. will attempt 384 x 240 anyway
AGS: Attempt to switch gfx mode to 384 x 240 (32-bit)

How/where are you getting this information? When I run ags on GeminiRue I don't see the output you're mentioning. Is there some debug mode I'm not using?

If someone with more patience than me wants to give the resolution issue a go: There is also another way to deal with it, namely to make the OpenGL backend JJS wrote for the mobile platforms ready for Linux. In that case AGS draws in whatever resolution it wants to a virtual screen which is stretched to the screen by OpenGL. I'm sure this will also increase speed.

That seems like the ideal solution. Probably something we should shoot at for the next version?

All I did was making sure an appropriate filter is selected. I didn't change the code that sets the video mode and that code still selects a resolution in questionable ways.

For the reasons you mentioned, we probably do NOT want it to switch resolutions when using auto scale? We should probably ONLY change the resolution when the user picks both fullscreen and a specific scale value?

Autoscale is fine, but changing to unsupported resoltions and crashing is still there. It depends on the combination of screen resolution and filter used.

Are we still switching resolutions, or does it leave the resolution alone, and just pick the appropriate scale factor? I'm confused.