| Pages: [1] :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
LXicon
Sanmatar Kelkoons
Minmatar Republic
54
   |
Posted - 2012.12.20 17:15:00 -
[1] - Quote
Dev Support request : outgoing mic / voice chat not being heard:
when i get into a squad with working mics i can hear them talk but they can't hear me. the mic icon is being displayed on my screen and they can see the voice icon beside my name in the squad list.
in the squad list, i see the voice icon beside a player's name turn green when others talk, but mine is always white. should mine turn green when i'm talking and it's transmitting?
1) i have a slim PS3, model #CECH-3001B
2) i have a PlayStation 3 Wireless Stereo Headset
3) i have chat enabled and push to talk off in the Dust514 options
4) in game, i've tried enabling both team voice and squad voice. neither have worked yet.
5) i don't have this problem with the playstation chat / video chat or in other games (MAG, Motorstorm, Warhawk, 1943, etc.)
6) my network is NAT Type2: i have a linux gateway with UDP ports 12000:13000 and 20000:21000 open in the firewall (shorewall)
7) my wireless router is behind the gateway. i used to have UPnP enabled, but i turned it off and moved the PS3 to the DMZ as a possible solution from this forum but that did not work (i never had to use the DMZ before either)
so, what is different about the Dust514 mic system from the playstation chat or other game's systems?
i've been in many squads where i see others with a voice icon but don't hear them talking and they don't respond to me. are they having the same problem i have?
thanks for any help you can provide. |
LXicon
Sanmatar Kelkoons
Minmatar Republic
54
|
Posted - 2012.12.20 20:24:00 -
[2] - Quote
i looked around some more and found this thread : https://forums.dust514.com/default.aspx?g=posts&t=21922
so i added these to the open ports on my firewall and tried again:
TCP Ports: 5223,10070:10080
UDP Ports: 3478,3479,3658,6000:7000,10070
i also checked my firewall's log while i played and looked at all the dropped packets
dropped 340 packets : UDP DPT=1029 (looks like various trojans/threats : SubSARI, W32.Kipis, W32.Kobot)
dropped 8 packets : UDP DPT=1028 (looks like various trojans/threats : SubSARI, KiLo.)
dropped 6 packets : UDP DPT=8067 (EMC2 (Legato) Networker or Sun Solcitice Backup or QuickTime Streaming Server)
dropped 1 packet : UDP DPT=31648 (Unassigned)
these look promising. the source is 87.237.38.9 whichi looks up as fcp-probe.ccpgames.com do you need UDP ports 33441,33442,33443,33445 or some range?
Dec 20 14:23:21 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=2314 PROTO=UDP SPT=12017 DPT=33445 LEN=12
Dec 20 14:23:30 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=1803 PROTO=UDP SPT=12017 DPT=33443 LEN=12
Dec 20 14:23:30 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=2314 PROTO=UDP SPT=12017 DPT=33445 LEN=12
Dec 20 14:23:39 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=1292 PROTO=UDP SPT=12017 DPT=33441 LEN=12
Dec 20 14:23:39 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=1803 PROTO=UDP SPT=12017 DPT=33443 LEN=12
Dec 20 14:23:39 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=2 ID=2315 PROTO=UDP SPT=12017 DPT=33445 LEN=12
Dec 20 14:23:48 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=1292 PROTO=UDP SPT=12017 DPT=33441 LEN=12
Dec 20 14:23:48 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=2 ID=1804 PROTO=UDP SPT=12017 DPT=33443 LEN=12
Dec 20 14:23:48 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=2 ID=2315 PROTO=UDP SPT=12017 DPT=33445 LEN=12
Dec 20 14:23:56 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=2 ID=1293 PROTO=UDP SPT=12017 DPT=33441 LEN=12
Dec 20 14:23:56 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=2 ID=1804 PROTO=UDP SPT=12017 DPT=33443 LEN=12
Dec 20 14:23:56 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=3 ID=2316 PROTO=UDP SPT=12017 DPT=33445 LEN=12
Dec 20 14:24:06 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=2 ID=1293 PROTO=UDP SPT=12017 DPT=33441 LEN=12
Dec 20 14:24:06 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=3 ID=1805 PROTO=UDP SPT=12017 DPT=33443 LEN=12
Dec 20 14:24:06 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=3 ID=2316 PROTO=UDP SPT=12017 DPT=33445 LEN=12
Dec 20 14:24:16 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=1552 PROTO=UDP SPT=12017 DPT=33442 LEN=12
Dec 20 14:24:16 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=3 ID=1294 PROTO=UDP SPT=12017 DPT=33441 LEN=12
Dec 20 14:24:16 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=3 ID=1805 PROTO=UDP SPT=12017 DPT=33443 LEN=12
Dec 20 14:24:26 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=1552 PROTO=UDP SPT=12017 DPT=33442 LEN=12
Dec 20 14:24:26 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=3 ID=1294 PROTO=UDP SPT=12017 DPT=33441 LEN=12
Dec 20 14:24:32 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=2 ID=1553 PROTO=UDP SPT=12017 DPT=33442 LEN=12
Dec 20 14:24:40 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=2 ID=1553 PROTO=UDP SPT=12017 DPT=33442 LEN=12
Dec 20 14:24:49 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=3 ID=1554 PROTO=UDP SPT=12017 DPT=33442 LEN=12
Dec 20 14:24:58 SRC=87.237.38.9 DST=[redacted] LEN=32 TOS=0x00 PREC=0x00 TTL=3 ID=1554 PROTO=UDP SPT=12017 DPT=33442 LEN=12
|
Garrett Blacknova
Codex Troopers
1849
|
Posted - 2012.12.20 22:08:00 -
[3] - Quote
While in-game, open the XMB and go to "settings" then "accessory settings" then "audio device settings".
Check the mic is actually syncing to the PS3 correctly. In my experience, it sometimes doesn't. |
LXicon
Sanmatar Kelkoons
Minmatar Republic
54
|
Posted - 2012.12.20 22:37:00 -
[4] - Quote
i did. the PS3 Wireless Headset shows up, and the mic level is good.
the headset shows up on screen when i toggle the mute feature as well. it works in other games and when i start a chat.
p.s. the log time listed in my previous post are EST (GMT -05:00) |
LXicon
Sanmatar Kelkoons
Minmatar Republic
54
|
Posted - 2012.12.22 06:24:00 -
[5] - Quote
mic problem SOLVED!!
in addition to my PlayStation 3 Wireless Stereo Headset i have the PlayStation Eye USB camera. when i have the headset turned off, the audio accessory menu defaults to the USB Camera as it's input device and it sets to "System Default" as the output. using the USB Camera as a mic kinda sucks as it rebroadcasts the explosions and game voice to all your sqaud, so I had it set to "Do Not Use" in the audio device menu.
this afternoon, i gave up on trying to get the headset to work and decided to try using the USB camera as my mic... LO AND BEHOLD IT WORKED!
so, i unplugged my USB camera and restarted Dust514 with only the PlayStation 3 Wireless Stereo Headset connected and i was finally able to get into a squad who had working mics and they could hear me!
this bug should be reproducible. i'm not sure if it's having the playstation eye plugged in and set not be in use, or, if just unplugging the playstation eye while using the PlayStation 3 Wireless Stereo Headset is the solution. the Devs can sort that out.
the bottom line is that unplugging the playstation eye while using the PlayStation 3 Wireless Stereo Headset in Dust514 makes it work for me.
* note when i have both the playstation eye and the PlayStation 3 Wireless Stereo Headset connected, the audio device settings switch to the PlayStation 3 Wireless Stereo Headset when i turn it on. maybe Dust514 is just looking at the first mic it finds instead of the ACTIVE mic? you can figure it out. |
|
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |