Kye

Hi there, I would like to make a suggestion for the FSUIPC interface. I'll provide a bit of background info incase my thinking is flawed somewhere: Previously I have been modding/hacking other (non-FS) games for several years. I have come to understand that FSUIPC is one of the main interfaces used for modding FS's internal data. I downloaded the SDK, took a look at the IPC interfaces for accessing FS memory, all was good. However, I wasn't interested in writing an external application to access and modify flight simulator's memory, I wanted to be inprocess like the main FS modules and gauges and avoid the shortcomings of internal latency generated by any form of IPC. This left me with a question I could not answer. Why were gauges and other 3rd party FS modules making use of an IPC interface when they were already inprocess? The answer, which everybody knows, but I didn't at the time, is that FSUIPC provides a convenient and compatible interface to FS's data. Data that may otherwise require months to years of research to locate and document. My suggestion is that FSUIPC carry a secondary interface (exported procedures) which bypasses the IPC and allows developers which are already inprocess to more or less access and modify FS's data in realtime. This should result in considerable framerate/update speed increases. Especially for those using ReadAndProcess or WriteAndProcess techniques.