freem {l Wrote}:Just gave it a try (just launching for now). Few things:
1. the mumble instance it launches tries to connect to localhost, and fails (I don't have murmur installed)
2. some my screen's resolutions are not displayed, like the "best" one: 1366x768
3. changing resolution requires restart
4. mumble does not exit when game ends, and when game starts, already existing instances are not reused
I'll try more later
Freem, thanks for testing. I'm glad to know the AppImage ran on your system. Which distro were you using?
As for your four observations:
1- Upon startup, LAC does indeed try to invoke mumble but no attempt is made to connect it with a server until you click on one of the screens with your mouse. During the interim Mumble is indeed left trying to connect to "localhost". Most of our users have found this to be harmless, since the normal behavior is to click on one of the screens right away. At that point Mumble is directed to connect with the "root" channel of our free Mumble server at LinuxAirCombat.com. That's where new players "hang out" between missions and it serves as the social "hub" of the LAC online community.
2- The prominent "SETUP OPTIONS" cycles through eleven different display resolution options intended to satisfy the needs of the majority of LINUX users. Most people are able to use one of those prominent options with good success even though they may know (as you do) of an even better option for their specific hardware. Our hope is that the initial experience, with one of the eleven prominent options, is good enough to inspire discovery of the "LacConfig.txt" file which allows easy configuration of any desired display resolution setting. That file, located within the new, hidden ".LAC" folder, can be used to configure many, many aspects of Linux Air Combat. The display resolution area is near the top of the file. By editing that file you can select 1366x678 or any other display resolution that is supported by your hardware.
3- You are correct that changing resolution requires restart.
4a- You are correct that Mumble is not disconnected when missions are completed or when LAC exits. Our user community prefers it this way, since the root channel of our Mumble Server serves as the social hub of the LAC community and it is commonplace for our users to continue discussing LAC between missions and sessions.
4b- Normally LAC does re-use any existing Mumble instance when it starts up. We know of a bug that interferes with this on rare occasions. Accordingly, from time to time, LAC users suffer with two simultaneous copies of Mumble both running and interfering with one another. We have not been able to fix this yet, but in our existing community of users this is unusual. If it is happening consistently on your system, perhaps you can help us find and fix the problem. Please let me know which Linux distro you are using and which version of Mumble is invoked by LAC on your system.
Thanks!