Bill,

Sorry to say, it's not fixed in v2.3.0-rc2; that's what I was using for noth the FT RU & RTTY RU.

It worked mostly ok in Dec. with only 2 crashes, but some issues with not logging properly (sending good & existing info to the log box).

This past weekend's rtty ru  was a disaster!  Same setup, no updates, but multiple crashes & would't log a lot!  Only had aboutv2 dozen qso's in 2 hours - pathetic & frustrating, so I walked away!

It didn't matter if AP was on or off, decoding level, etc.

I still think the systemic problem we will continue to have with contesting is that we can only test it in a contest!!!

I  think  you guys (BECAUSE YOU HAVE THE BIG MIC TO GET THE WORD OUT...!)  should have psuedo-contests for 3 or 4 hours so that we can hammer away at the program under real contest conditions!  Say once a month or so.

73 - John - N7GHZ

On Thu, Jan 7, 2021, 7:22 AM Bill Somerville <g4wjs@...> wrote:

On 07/01/2021 14:20, Stephen Malyszka wrote:
> Thanks Bill but my question was for the candidate version. Is the
> problem fixed in that version or do I have to change the FT4 mode
> decode from Normal to Fast there as well???
>
> Thanks,
> Steve

Hi Steve,

as far as I know the issues are fixed in WSJT-X v2.3.0 RC3.

73
Bill
G4WJS.