We were in the snapshot and were using two different VOX chans for the TBM flight and hellcat flight. I was on a different VOX channel (so a different IP addy in the RW side of things) at first. I got shot down (I was really dumb and pulled up into the con when I had hardly any E. please, someone tell me NOT to do that anymore!!!) so i decided to switch over to the TBM flight to listen in there. Seamless switch in AH like it usually is, but there was a lot of non AH comm traffic going on. Somehow, whoever was hosting the RW session for that VOX channel had gotten on the main RW directory service, and people were just joining in from that.
I tried to see what would happen if I started a session in game, so I head over to the MA, get VOX set like I always do for squad comms. No one joins in. I install RW on another PC at home, and check the directory... I'm not there at all. Ghosth joins in on my session. We fiddle with things, and come to the conclusion that maybe I didn't start broadcasting to the RW directory because I'm behind a firewall. The new feature of RW is called Base Station Hosting, and it uses a different port than RW uses for voice data. That new port isn't mapped on my firewall, so that's a possibility as to why I wasn't showing on the list and the other guys were. Also, maybe the base hosting doesn't happen automatically, so you're not on the directory by default.
anyone else with the new RW version noticing party crashers or other interesting connection stuff?
