"I have written my own program that implements a FreeTrack protocol server" <<

This is the clincher for me. As you pointed out in a previously closed ticket, other FreeTrack applications are working just fine with Arma3, and there are videos where people are using FT successfully, so apparently the FreeTrack protocol itself is not the problem.

You also stated previously that your app not only causes Arma3 to crash but also Arma2, which means that your app must be the trigger - it is the only common factor in these crashes.

And your statement that Arma3/2 are the cause of the problem because they are crashing (and not your app) is false. If your app is delivering malformed data, for example, this could cause Arma3/2 to crash but your app would be at fault. Of course, BIS could try to troubleshoot the issue and implement error handling, but I doubt supporting a third party app is currently a priority for them.

Anyway, I'll leave this ticket open for now and let the devs decide how to handle it, but I doubt their stance on this issue will change.

You misunderstand me. I thought I was pretty clear. I said in the previous ticket that other applications (games) work fine with FreeTrack protocol programs, regardless of who made the FreeTrack protocol program, not that other FreeTrack programs work fine with Arma 2/3.
The problem I encounter with Arma 2/3 is exactly the same regardless of whether I use FreeTrack, FaceTrackNoIR or my own program. These crashes occur with all of these programs and Arma 2/3. My program is not the problem. There are many forum posts that show other users with this problem. These crashes do not prevent me from using FreeTrack with Arma 2/3, as is reported by other users. As I stated before, the crash occurs upon the *first* attempted use of Arma 2/3 after starting a FreeTrack serving program. Upon trying Arma 2/3 again, it works fine. If FreeTrack is started after Arma 2/3 is loaded, it works fine. Please just read more carefully.

Ok, looks like I misunderstood you. However, I decided to look around for some more info, and it turns out that the problem really is caused by FreeTrack. See here, in the comments: https://dev-heaven.net/issues/10791

Basically Suma (BI lead developer) says that the crash occurs when they try to call a specific function (FTReportName) in the FreeTrackClient.dll, which fails to return. Since FreeTrack is apparently no longer in active development since 2008, there is nothing they can do about the problem from their side, so the issue has been dropped.

So when Astaroth says "Arma3 does not officially support FreeTrack", he means it. The game retains legacy compatibility, yes, but FreeTrack related bugs cannot be fixed unless FreeTrack itself becomes active.

Closing.