Skip to main content
Game Development

Return to Answer

added 8 characters in body
Source Link
Kromster
Kromster
  • 10.7k
  • 4
  • 55
  • 67

Calls to timeBeginPeriodtimeBeginPeriod/timeEndPeriodtimeEndPeriod won’t result in a Sleep()Sleep() of 1ms. You will get anything but 1ms and possible values as high as 10-15ms. Also, no need to adjust scheduler timeslice for timeGetTimetimeGetTime either, the default will give you accurate enough timing.

Your monitor is fine, the ghosting you are seeing is known as temporal aliasing. If you clear the buffer between moves and correctly implement interpolation, this effect can be mitigated.

Calls to timeBeginPeriod/timeEndPeriod won’t result in a Sleep() of 1ms. You will get anything but 1ms and possible values as high as 10-15ms. Also, no need to adjust scheduler timeslice for timeGetTime either, the default will give you accurate enough timing.

Your monitor is fine, the ghosting you are seeing is known as temporal aliasing. If you clear the buffer between moves and correctly implement interpolation, this effect can be mitigated.

Calls to timeBeginPeriod/timeEndPeriod won’t result in a Sleep() of 1ms. You will get anything but 1ms and possible values as high as 10-15ms. Also, no need to adjust scheduler timeslice for timeGetTime either, the default will give you accurate enough timing.

Your monitor is fine, the ghosting you are seeing is known as temporal aliasing. If you clear the buffer between moves and correctly implement interpolation, this effect can be mitigated.

Source Link
Brett
Brett
  • 114
  • 7

Calls to timeBeginPeriod/timeEndPeriod won’t result in a Sleep() of 1ms. You will get anything but 1ms and possible values as high as 10-15ms. Also, no need to adjust scheduler timeslice for timeGetTime either, the default will give you accurate enough timing.

Your monitor is fine, the ghosting you are seeing is known as temporal aliasing. If you clear the buffer between moves and correctly implement interpolation, this effect can be mitigated.