Most Raspberry Pi users run LAC at 720p (or lower) resolution, in full-screen mode. That gives nice, smooth performance in flight.
However, Mumble's desktop frame likes higher resolution, and if mumble isn't already running when you invoke it from LAC, it will blast LAC out of full-screen mode and open a copy of mumble on top of LAC. It's fairly easy to use "ALT-TAB" to get LAC's frame back on top, and within 5 seconds or so, LAC will restore full-screen operation, but all of this is cumbersome to do and disruptive to combat.
To avoid all of this, just start mumble BEFORE starting LAC. That way, LAC will only need to send commands to an already operating copy of mumble: it will never need to start mumble up fresh. Consequently, mumble's start-up logic will never try to drop LAC out of full-screen mode, and you won't need to hit "ALT-TAB" and cycle through all of your running apps to find LAC and return it to full-screen mode.
This is an obvious, convenient, and natural way to combine mumble with LAC: Start mumble first, wait a few seconds while it connects with our mumble server at LinuxAirCombat.com and switches you into our root channel. Chat with anybody else hanging out there and negotiate a meetup in the mission of your choice. THEN start LAC and enjoy!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One other advantage to starting mumble before starting LAC: This lets mumble run independent of LAC, which is nicer than making mumble DEPENDENT on LAC.
When LAC starts mumble for you, mumble is dependent on LAC. Consequently, when you exit from LAC, you also exit from mumble. Because it is commonplace to exit from LAC when you end a mission and then re-enter LAC when you return to that mission or start another, unless mumble is running independently, you'll be dragged through the same cumbersome mumble startup process all over again, and you'll be cut out of any ongoing mumble conversations in the interim.
On the other hand, if you started mumble before starting LAC, upon exiting LAC for any reason, mumble remains running and you remain connected to the same mumble channel and in conversation with your mission-mates. Accordingly, if you're headed back into that mission to continue with them, you'll find a much smoother transition and you'll be able to tell them you're on your way back.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Most Raspberry Pi users run LAC at 720p (or lower) resolution, in full-screen mode. That gives nice, smooth performance in flight.
However, Mumble's desktop frame likes higher resolution, and if mumble isn't already running when you invoke it from LAC, it will blast LAC out of full-screen mode and open a copy of mumble on top of LAC. It's fairly easy to use "ALT-TAB" to get LAC's frame back on top, and within 5 seconds or so, LAC will restore full-screen operation, but all of this is cumbersome to do and disruptive to combat.
To avoid all of this, just start mumble BEFORE starting LAC. That way, LAC will only need to send commands to an already operating copy of mumble: it will never need to start mumble up fresh. Consequently, mumble's start-up logic will never try to drop LAC out of full-screen mode, and you won't need to hit "ALT-TAB" and cycle through all of your running apps to find LAC and return it to full-screen mode.
This is an obvious, convenient, and natural way to combine mumble with LAC: Start mumble first, wait a few seconds while it connects with our mumble server at LinuxAirCombat.com and switches you into our root channel. Chat with anybody else hanging out there and negotiate a meetup in the mission of your choice. THEN start LAC and enjoy!
One other advantage to starting mumble before starting LAC: This lets mumble run independent of LAC, which is nicer than making mumble DEPENDENT on LAC.
When LAC starts mumble for you, mumble is dependent on LAC. Consequently, when you exit from LAC, you also exit from mumble. Because it is commonplace to exit from LAC when you end a mission and then re-enter LAC when you return to that mission or start another, unless mumble is running independently, you'll be dragged through the same cumbersome mumble startup process all over again, and you'll be cut out of any ongoing mumble conversations in the interim.
On the other hand, if you started mumble before starting LAC, upon exiting LAC for any reason, mumble remains running and you remain connected to the same mumble channel and in conversation with your mission-mates. Accordingly, if you're headed back into that mission to continue with them, you'll find a much smoother transition and you'll be able to tell them you're on your way back.