I can also confirm problem #1. It is the same problem that existed in version 2.6.0 RC1,2,3 and 4.
Since I use WSJT in combination with N1MM+ for logging, I get a "TCP Error" when the program closes. If I'm not using the combo, WSJT just closes. I have not noticed that the closing occurs when using only FT8; it may also occur when using FT4, but there isn't enough activity on FT4 to see if it happens. A couple of additional observations: 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4 with the same dll from 2.5.4. The closing seemed to stop. This only works if your rig is supported by the earlier dll. 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation before it closes. Once it starts closing, it will continually do it. I have not seen the issues with "CQ MAX DIST". Are you sure it's not picking the correct call? 1. Calls without a grid are never selected unless they are the only reply to your CQ. 2. Band/Mode dupes are given a score of zero and only selected if the only caller. 3. Call selection is based on the point score generated by the program calculations; I know SP is further than DL, but if they have the same point total and the DL is before the SP in the decode window, the WSJT will select the DL station to call. Dennis W1UE On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > I can confirm problem 1, as it happened to me less than an hour ago, > including the orphaned JT9 decoding application. Running Win 10 on a > Lenovo X1 Carbon laptop. I had been on FT8 for about an hour when it > happened. > > > > Ed N4II. > > > > *From:* Frode Igland via wsjt-devel <wsjt-devel@lists.sourceforge.net> > *Sent:* Thursday, October 13, 2022 5:06 AM > *To:* WSJT software development <wsjt-devel@lists.sourceforge.net> > *Cc:* Frode Igland <frodeigla...@gmail.com> > *Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max > Dist" doesn't work, "CQ: None" stops working > > > > 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 >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
