I have observed a similar issue but only when switching from FT8 to FT4 in which FT4 will not decode. If I shut down WSJT-X and restart it in FT4 mode it works perfectly. I have no idea what is causin

#ContestMode

Hi all, The reason of popping up th e"Log this QSO" dialog, is the incorrect reaction of WSJT-X when receiving unsolicided R-Reports, or receiving R-Report confirming "old" reports. It happens if a st

#BugReport #ContestMode

Fake it does not mean you run the rig manually. NONE would be the one to check for manual frequency control. Fake it shifts the VFO back and forth to make the “required” frequency change for split. RI

#ContestMode

1. Messages Tx1 through Tx5 can't be filled in until you know who you're working. Enter some call as DX Call and click "Generate Std Msgs". 2. Yes

#ContestMode

Hi, I checked the Field Day contest mode and found that the letters for the class of operation only go from A to F. There are 8 letters allowed for that entry, and having G and H will help allow codin

#ContestMode

Just a reminder that all log submissions that use WSJT-X for today's RTTY RU need to categorized as using spotting assistance. WSJT-X decodes multiple signals at once and the ARRL says this is classif

#ContestMode

Just FY, I the following link http://www.arrl.org/files/file/ContestResults/2019/January%202019%20QST%20-%20Taylor%20-%20FT8.pdf is posted by ARRL and contains recommendations from Joe Taylor , K1JT,

#ContestMode #WSJTX_config

Hi Mike, Excellent program. Thanks much! I vaguely remember you discussing the fudge program on the Dev list. Glad you pointed me in the right direction. it works well and will now be on each computer

#FT8 #ContestMode