Hi Deny
I believe you've pointed out a good point here.
When compiling the wiKPA I try to include in the document all the aspects related to the knowledge and the use of the machine, but try to stay away from FW-related issues, which would stand true for one release or two at most. This way I try to keep the wiKPA as universal and meaningful as possible. I'd otherwise be obliged to add whole chapters which refer to specific FW versions, and remove them as long as FW changes. But my aim is to build a long-term knowledge base.
I see where you come from, being a new owner you perception is somehow limited to your time window, but Zappledan is correct: these issues are strictly FW-related. When designing the wiKPA, I've taken the decision to let these things to the forum, which - by definition - can live of real time issues and is much faster in reacting to anything new.
OTOH, when some issue definitively changes thanks to a FW upgrade, I don't miss to report it. For example, certain file names for the rigs were able to cause a system crash; this issue has been fixed since 1.1.0 (IIRC), and the info is reported in the document.
Your post has made me think that this could be something useful to specify in the introductory chapter, for the new readers.
Thanks for your contribution