12-30-2022, 10:38 AM
I think I remember hearing about a bug similar to this a while back. It was related to the Remote channel of the MRCC. I think the MRCC originally listened on a set port by default, but we turned that off so that you have to select a port and channel in the menu to use that feature, however I seem to remember that instead of not listening for PC messages on one channel, it blocked all channels on that port until you select an alternate. If you get a chance to test this for me, you can go into the menu and set it to listen on say channel 16 on any port that you're not testing with, then see if those messages get through. I will add this to my list of things to test next time I'm doing that sort of thing too, and make sure it's in the bug tracker.