hbien

First - a great thank you to Mr. Dowson - you have made it so much easier to communicate with MSFS. Second, my question(s): 1. Is FSUIPC multi-thread safe? That is, can I stack several FSUIPC_Read/Write() and a FSUIPC_Process() in one thread, while concurrently in another thread of the same process perform FSUIPC_Read/Write's() and FSUIPC_Process()? I'm writing a hardware emulator to interface with MSFS using FSUIPC, and it currently has several threads, one of which performs about 10 or so reads followed by a process, and the other doing about 5 writes followed by another process. These threads are run concurrently and asynchronously, so I cannot guarantee that the Process() in one thread will be completed before a Process() in the other thread. 2. Where might I find the error codes as reported from FSUIPC's DWORD result? I'm looking all over the docs but cannot seem to find them. Specifically, once in a rare while I get error code 13 in my loop - what is that? 3. As another user pointed out, I initially wanted to bypass FSUIPC and hookup directly with MSFS, but finding no documentation on how to write MSFS modules, I gave up and went with FSUIPC (its great, but it incurs its own over-head which I'd rather avoid). I see that there are no documentation on writing your own module, is there a reason why? I find it surprising that you had to hack into MSFS to get FSUIPC working. You'd think the least microsoft could've done with all the addon's that rely on MSFS FSUIPC would be to supply you or anyone else with a module SDK. Anyway, thanks for a great product (the overhead, it turned out, is negligible so far and the programs are running fine). Looking forward to your response. Sincerely, Harold Bien