I have used -rc4 since it was released and have found it quite stable with
three notable exceptions:

*1. Sudden closing in FT8 after extended periods of operation*
After an extended period of use in FT8 mode (normally more than two hours),
WSJT-X may close down abruptly. The closing happens at the start of an FT8
sequence. I have never experienced closing on FT4, but then I have very
rarely worked FT4 for extended periods. To start again, an orphaned JT9
decoding application first has to be terminated in the Task Manager. This
issue started with WSJT-X 2.6.0-rc1 and still happens.

*2. "CQ: Max Dist" doesn't work*
After selecting "CQ: Max Dist", WSJT-X still selects the station first
decoded, notwithstanding the distance. It makes no difference whether "CQ:
Max Dist" is selected after "CQ: None" or "CQ: First" or if "CQ: Max Dist"
was selected on start-up before first CQ.

*3. "CQ: None" stops working after a while*
I often call CQ DX with the "CQ: None" setting, to be able to select which
DX station to work. This normally works well, but suddenly WSJT-X may start
answering the first station decoded automatically, without being selected
manually by me. Sometimes, reselecting "CQ: None" helps, and sometimes I
have to close and reopen WSJT-X and select "CQ: None" before calling CQ.

These are my experiences with WSJT-X 2.6.0-rc4.

73, Frode LA6VQ
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to