There is an ongoing discussion in the FS9 forum that is , in part, about VC gauge refresh rates.The OP states that

FS can only handle one vcockpit entry per "cycle". So your VC gauges will always be restricted to your fps divided by number of vcockpit entries

...or

Frame Rate / Vcockpit entries = VC gauge frame rate

I am curious if the experts in this forum agree with those statements.I have not heard this before, but I make no claims of being even an amateur gauge programmer.regards,Joe P.S. this is the topic in question- http://forum.avsim.net/topic/294444-developers-who-still-use-multiple-vcockpit-entries-ifly/page__pid__1820187#entry1820187

While it is certainly true that the more individual [VCockpitnn] entries a model uses decreases performance, that is due primarily to the increase in memory usage (and most especially virtual address space) that the "dynamic memory bitmaps" (that is, the "bitmaps" that're created/refreshed in memory rather than hard disk space) engender.The "refresh rate" however, normally remains fixed at 18Hz maximum, unless the gauge has been deliberately limited to a slower update rate.However, for C++ gauges, it is possible to use a "Windows timer" to increase the speed of computations. Even so, the rendering of the dynamic bitmap to the screen retains the 18Hz max speed, as far as I've been able to determine.