Issues swapping between accounts on same PC

[xerxes]

ShowEQ seems to get confused running the beta build. I don't recall this happening with the normal build, but it's possible.

Essentially, it seems to get confused on locking onto the session. It will be working with one account. I camp out to server select, logout, and log into another account at the login window, and it shows this in the console window. At that point, the app is essentially dead and no amount of zoning works. I have to close ShowEQ and relaunch it, zone, and then it starts working again.

Debug: Tue 12/20/2022 13:20:29 - PCAP Filter Set: udp and (portrange 9000-9007 or port 9876 or port 61167) and host 192.168.1.100 and ether proto 0x0800 and not broadcast and not multicastInfo: Tue 12/20/2022 13:20:29 - EQPacket: SessionRequest detected, pcap filter: EQ Client 192.168.1.100, Client port 61167. Server port 25901
Warning: Tue 12/20/2022 13:20:29 - Uncompress failed for packet op 0900, flags 3d. Error was data error (-3)
Warning: Tue 12/20/2022 13:20:29 - Packet decode failed for stream client-zone (2), op 0900, flags 3d packet dropped.
Warning: Tue 12/20/2022 13:20:29 - Uncompress failed for packet op 0300, flags 39. Error was data error (-3)
Warning: Tue 12/20/2022 13:20:29 - Packet decode failed for stream zone-client (3), op 0300, flags 39 packet dropped.
Warning: Tue 12/20/2022 13:20:29 - Uncompress failed for packet op 0300, flags 39. Error was data error (-3)
Warning: Tue 12/20/2022 13:20:29 - Packet decode failed for stream client-zone (2), op 0300, flags 39 packet dropped.
Warning: Tue 12/20/2022 13:20:29 - Uncompress failed for packet op 0300, flags 39. Error was data error (-3)
Warning: Tue 12/20/2022 13:20:29 - Packet decode failed for stream zone-client (3), op 0300, flags 39 packet dropped.

[cn187]

OK, this is related to the extra packet filtering I put in. If you turn off "track session" then it should behave like it did before. But that said, logging out should have reset the filter to allow it to pick up the next session. So there's definitely a bug there somewhere. Thanks for reporting this - it's definitely the kind of thing I want to catch before full release.