Don't you think you're exaggerating the situation by a huge margin?
What do you mean you got no answers?
You have asked for help last month (your only post) and Neil told you to do something.
#1297976091188920401 message
We have never heard from you about the results of this step. Why do you blame us if it is actually you who didn't report on the progress?
If you had reported then that it had not changed the situation, someone would have certainly contacted you and tried to help you further.
Also, If you take a look at the threads in various support channels, you will find many of them solved. This is because we always try to provide help to the extent of our knowledge and free time. Keep in mind this is an open source project, built and maintained by volunteers. We are not paid and yet we try as best as we can to help everyone who is building their own cockpit as we all are on the same boat. 🙂
Another thing, very important one.
Have you been in contact with CoreFlight?
We don't know that because you never mentioned it.
The supplier/manufacuter/seller of the hardware you bought should be the first place to seek the help. @kind lodge is in this server so he might be able to help you.
On the side note:
Sure, you can buy hardware that rely on manufacturers own software and isn't MF compatible. Ask yourself however what will happen if that company will ditch a software or what worse, will disappear from the market and at some point you will be left with hardware but no software to control it. Unfortunately we have seen such of cases in past.
This is where MF is helping. Sometimes ,compatibility is stright forward aka plug and play. Other times it might require some internal changes to make it compatible with any other software.