> On Nov 23, 2022, at 21:58, Black Michael via wsjt-devel
> wrote:
>
> Would that switch to FT4 be occurring while decodes are still appearing on
> the screen?
Probably while or before decodes are happening, since they come so fast with
heavy activity.
Gary - AG0N
Would that switch to FT4 be occurring while decodes are still appearing on the
screen?
Mike W9MDB
On Wednesday, November 23, 2022 at 10:16:20 PM CST, Gary McDuffie via
wsjt-devel wrote:
> On Nov 23, 2022, at 13:54, Michael Black via wsjt-devel
> wrote:
>
> Known bug if you are
> On Nov 23, 2022, at 13:54, Michael Black via wsjt-devel
> wrote:
>
> Known bug if you are using max dust or call first. It’s fixed for RC5.
> Mike W9MDB
One more confirmation from my station, Mike. As previously stated, it is very
repeatable.
Go up on 17, 12, or 10 meters (probably
Known bug if you are using max dust or call first. It’s fixed for RC5.
Mike W9MDB
Sent from my iPhone
> On Nov 23, 2022, at 1:52 PM, Reino Talarmo via wsjt-devel
> wrote:
>
>
> >Maybe just co-incidence but I have had two crashes now where the last entry
> >in the ...ALL.TXT file was a
>Maybe just co-incidence but I have had two crashes now where the last entry in
>the ...ALL.TXT file was a station with compound call that was answering my CQ.
221123_18124521.074 Rx FT8-12 0.2 1386 KB1EFS/2
Hi AL,
Could this be the same issue Mike stated: ‘Referring to "Max Dist"
(WSJT-X v2.6.0-rc4 )
Maybe just co-incidence but I have had two crashes now where the last
entry in the ...ALL.TXT file was a station with compound call that was
answering my CQ.
221123_181245 21.074 Rx FT8 -12 0.2 1386 KB1EFS/2
Looking back through the ALL.TXT, KB1EFS/2 had not
