[warzone2100-dev] [Warzone 2100 Trac] #1851: no way to pick which sound card/device to use
#1851: no way to pick which sound card/device to use
+---
Reporter: jaakan |Type: to-do
Status: new |Priority: trivial
Milestone: unspecified | Component: Engine: Sound
Version: svn/trunk|Keywords:
Operating_system: GNU/Linux| Blockedby:
Blocking: |
+---
It would be nice if there was a way to pick which ever audio device you
wanted to output the games audio with.
adding a CLI switch like the following would be nice to have
{{{
--audiodevice=default / what ever OS has for default audio device
--audiodevice=0-3 / card 0 device 3
--audiodevice=hdmi / first device with hdmi
--audiodevice=spdif / first device with IEC958 (S/PDIF)
}}}
my Mythtv box
{{{
r...@myth64:~# aplay -l
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC888 Digital [ALC888 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 3: INTEL HDMI [INTEL HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
}}}
my laptop
{{{
jaa...@jms1000:~/warzone$ aplay -l
List of PLAYBACK Hardware Devices
card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
}}}
--
Ticket URL: http://developer.wz2100.net/ticket/1851
Warzone 2100 Trac http://developer.wz2100.net/
The Warzone 2100 Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] team colors for old models
On Fri, May 14, 2010 at 3:12 AM, Stephen Swaney sswa...@centurytel.net wrote: On Thu, May 13, 2010 at 08:43:45PM -0400, buginator wrote: Anyone have any objections to this patch: http://developer.wz2100.net/ticket/1757 ? I say apply it. Team colors is the direction we are heading in. I'm fine with the idea. Are the new PNGs much larger now? - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] Commit mails for new repositories
Is there the possibility to follow commits in a similarly comfortable fashion as is currently done with SVN with the new repositories (be it Hg, git, Bzr or whatever)? If so, please give me some hints at how to set this up. Regards, - Kreuvf signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Commit mails for new repositories
On Friday, 14 May 2010 at 19:24, Kreuvf wrote: Is there the possibility to follow commits in a similarly comfortable fashion as is currently done with SVN with the new repositories (be it Hg, git, Bzr or whatever)? I guess once we actually use another repo for actual development we'll set up a commit list for it. But for now, it seems there's not much interest in trying out the various systems. I have to admit, I also don't do much with any of them, committing random crap gets boring fast... If so, please give me some hints at how to set this up. You can use the RSS feeds SF offers, http://warzone2100.hg.sourceforge.net/hgweb/warzone2100/qt_test/rss-log and http://warzone2100.git.sourceforge.net/git/gitweb.cgi?p=warzone2100/test;a=rss. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1852: Cyborg Transport
#1852: Cyborg Transport --+- Reporter: fsantello |Type: bug Status: new|Priority: trivial Milestone: unspecified| Component: other Version: 2.3.0 |Keywords: Cyborg Transport Operating_system: Microsoft Windows | Blockedby: Blocking: | --+- Hy, I just noticed a bug with the cyborg transport in skirmish mode. When it lands in a hardcrete it just acts as if the hardcrete was non- existant and land on it. -- Ticket URL: http://developer.wz2100.net/ticket/1852 Warzone 2100 Trac http://developer.wz2100.net/ The Warzone 2100 Project ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
