kc10b747fe wrote:Hi Roo,
I was able to do some testing this weekend and also today on the latest SIMCOMX app. I tested using only manual tuning at this time. I will try auto switching on another day and report back. Here's what I found.
1. I was able to connect all 3 of my machines on your server. I was able to transmit and receive with no problems. I was also able to see all machine names in the freq box. I did have an occasional stuck TX and RX light with both a joystick button or key selected. The lights did not time out after 15 secs and the only way to get rid of it was to shut down and restart the app. Just turning off the power button did not correct it. However it seemed like this occurred mostly on initialization when first trying to connect. When flying with a friend today, once connected and TX and RX correctly, we flew the entire flight (about a hour and a half) with me using a joystick button and him using a key, and we did not have any problems.
2. In SCX mode I was able to connect all 3 machines to 122.800 and transmit and receive. However if I switched to any other frequency, the app would crash on the machine trying to swap freq, with the same error message in my previous post.
3. I noticed in reference to the ghosting or 0 placed at the end of the call-sign, the call-sign indicates correctly on the transmitting machine and shows call-sign+0 on the receiving machine. So whatever machine I transmitted from, the call-sign on that machine always showed correct, and the receiving machines always showed call-sign+0.
4. I also tested with a friend today, and all of the above findings were consistent with the exception of seeing names in the freq box. Once connected, with both on the initial freq of 000.000 we were able to see each other in the freq box, and in the text box indicating that that person was tuned to that freq. TX and RX worked correctly. However when switching to 123.450, then transmitting, the the receiving persons call-sign would disappear in the freq box, and the "no one else is here" statement would appear, even though in the text box it showed that person tuned
to the correct freq. TX and RX still operated correctly.
5.There were some connection issues that seem to happen. For example one person being able to TX and RX, but the other person only being able to RX. To correct this, the only recourse was to have both shut down the app completely and then restarting. If only one tried restarting, the other person restarting would not see anyone in the freq or text box and was unable to TX or RX. The person that did not shut down would still show the other persons call-sign in his freq box but would not be able TX or RX. (As if the connection was still open).
6. In SCX mode between the two of us, we were able to connect on 122.800, TX and RX, but not on any other freq. Again when switching freq, we both received the error message and the app would crash.
7. In Group Host mode we were unable to connect to either of our listed IP addresses.
8. In SCX mode does being on ATC 122.800, and being able to see each other in the freq box and being able to TX and RX, indicate that port 9988 is open?
9. When "Distance" is checked, What is the distance where the comms start to become degraded? Does "Distance" only apply if ATC is checked? and if not checked, am I correct in assuming that anyone on that freq anywhere in the world would hear the transmissions?
This app is a great addition for those of us on JoinFS who just want a simple interface to communicate on the radios without the need to install Team Speak or Discord. Thanks again for taking the time in creating it. I hope the info helps and let me know if I can be of further assistance.
As always I'll be releasing a newer version shortly with these bug fixes.
I think it might help if I created a diagram too, showing features of the app and what they should do.
The main thing that stands out from yours and Grumpys feedback is the stuck TX/RX.
I think your right with the initializing.
I think it's getting hung up on something or trying to doo too many things at once.
I'll look into that next.
1. As above TX/RX needs looking at.
2.I've just fixed this after Grumpy mentioned it.
3. This may be the Nautical Miles your are away from that user?
If it's Zero, you either both have your lat lon set to zero which happens if you have no SIM connected or you have ATC mode ticked and the first 4 characters of or callsign are not an ICAO code (Ie EGLL_TWR or KLAX_APP), or you are both really close to each other.
4. Maybe the same issue Grumpy had with the app lying to you.
Should now be fixed.
5. Possibly fixed when fixing the above.
6. As number 2, now fixed.
7. Sounds like a UDP port 9988 not open or firewall issue.
That will still happen even with the port closed or blocked by a firewall.
I'm looking into ways for a user to check if their port is available.
It's proving an issue at the moment as the port is UDP.
I'm working on it.....
9. With the distance box ticked, you will not hear anything 200nm away or further.
190 -200 miles will be quiet.
180-170 will be a bit louder.... and so on.
Within 40nm (off the top of my head) there is no restriction.
With the tick box UNTICKED you can hear everything worldwide.
Ticked or UNTICKED you still transmit worldwide.
It's only YOUR receive that gets limited.
Hope that helps.