I made a copy of the ini file for the condition that connects to Omni-Rig and a
separate ini file copy for the configuration that does not connect to Omni-Rig.
I compared the files using WinMerge. I see no obvious difference that would
explain why one works with Omni-Rig and the other does
" https://wsjtx.groups.io/g/main/message/40301 "
Thanks for that link Martin.
I attempted to change to a previously saved Fox/Hound configuration that worked
fine in ver 2.3.0. It not only came up with a zero and red frequency box but
it also failed to connect to Omni-Rig.
When I switched
The -rc5 release notes say:
- When in Hound mode and click the "H" button again, the frequency
is now kept. This gives the user the following two options to return
to normal FT8 mode:
- Click the "H" button again. Then you will stay on the QRG.
- Click the "FT8" button (or use the
Andy (and all):
There's a thread, started by me a couple of days ago, about issues with the
frequency tables under 2.6.0-rc5 on the WSJT-X forum on groups.io; you'll
find the first message in the thread at:
https://wsjtx.groups.io/g/main/message/40301
As you'll see the issue I've reported
>If Hound is then deselected the Fox/Hound frequencies remain in the
frequency selector.
Hi Andy,
Have you read the related Release notes:
When in Hound mode and click the "H" button again, the frequency
is now kept. This gives the user the following two options to return
to
If WSJT-X 2.6.0-rc5 is closed with FT8 active and Hound not selected it
restarts with standard frequencies available in the frequency selector.
If Hound is selected the standard frequencies remain in the frequency selector.
If WSJT-X is closed and re-started then it opens with Hound active and
