Having read and seen much of the same. I agree that F/H needs some
work. Andy is spot on about the user base not reading and following
instructions. Therefore, we do need forced compliance with the message
format. Of course there will be a lot of whining about it, but the
Clipperton DXE is a total mess right now. There are WSJT-X operators
that only use WSJT-X for F/H mode and DXEs. They are not aware of the
most current news, information, and operational changes as they don't
participate with the group email lists on a daily basis. The software
needs to help them out.
Honestly, even with daily FT8 operations between all of the short cuts
people are taking with the message format, combined with heavy
filtering, has FT8 a total mess. It's a wonder people get QSLs for
awards it's so messy.
On 1/24/24 09:07, Andy Durbin via wsjt-devel wrote:
As implemented in WSJT-X ver 2.6.1 the hound is able to select TX3 as
their first transmission. One user has posted a screen shot showing
that fox replied with a signal report but the QSO could not be completed.
Since new WSJT-X ops seem reluctant to read the instructions would the
developers please consider making TX3 unselectable until a signal
report has been received.
Thanks and 73,
Andy, k3wyc
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Jeff Stillinger - KB6IBB
KB6IBB Laboratories, Wylie Tx
r/KB6IBBSWLLogger
http://kb6ibb-15.ham-radio-op.net/
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
