QueryPerformanceCounter on efusA9 DualLite

  • Attention to all developers:

    QueryPerformanceCounter() on efusA9 on WEC2013 F&S Version 1.40 seems to return a per-core counter, resulting in start time larger than stop time when a thread which measures short amounts of time runs on one core to get the start time and then on the other core to get the stop time.

    • Are there any plans to fix this?
    • How is GetTickCount() implemented? Does it use QueryPerformanceCounter() (or its time source) for the tick count? Or does it return a some OS counter?