Homebrew Equivalent of std::chronos::high_resolution_clock and high_resolution_clock::time_point in the 3ds.h

[delete12345]

In C++, you have this in the standard library:

std::chronos::high_resolution_clock
std::chronos::high_resolution_clock::time_point

What is the equivalent of a high resolution clock value used in ctrulib?

Is it osGetTime()? And that is it?

 

[elhobbs]

In C++, you have this in the standard library:

std::chronos::high_resolution_clock
std::chronos::high_resolution_clock::time_point

What is the equivalent of a high resolution clock value used in ctrulib?

Is it osGetTime()? And that is it?

svcGetSystemTick is good for measuring small amounts of elapsed time with a high resolution, but it is not super accurate over long periods of time.

 

[delete12345]

svcGetSystemTick is good for measuring small amounts of elapsed time with a high resolution, but it is not super accurate over long periods of time.

osGetTime() is therefore more accurate over long periods of time?

 

[elhobbs]

osGetTime() is therefore more accurate over long periods of time?

That depends on what you need for accuracy. Neither one can be used to accurately synchronize a circular buffer for sound playback. But I do believe osGetTime will stay somewhat in sync with the current time. For measuring/comparing elapsed time for things during a frame I would use the tick count. For measuring seconds/minutes I would use os get time.

 

[delete12345]

That depends on what you need for accuracy. Neither one can be used to accurately synchronize a circular buffer for sound playback. But I do believe osGetTime will stay somewhat in sync with the current time. For measuring/comparing elapsed time for things during a frame I would use the tick count. For measuring seconds/minutes I would use os get time.

Ok, because I'm still working on the physics engine, and I need tons of accurate timing.

I'll stick with osGetTime() then, as I prefer stable/less accuracy over unstable/high accuracy.

 

[elhobbs]

Ok, because I'm still working on the physics engine, and I need tons of accurate timing.

I'll stick with osGetTime() then, as I prefer stable/less accuracy over unstable/high accuracy.

Game physics? You don't need much precision for that - either one should work fine. Unless you are running the physics simulation much faster than the typical 60 Hz graphics refresh rate.

 

[delete12345]

Game physics? You don't need much precision for that - either one should work fine. Unless you are running the physics simulation much faster than the typical 60 Hz graphics refresh rate.

It's the physics engine that I'm working on, Pica. But I'll stick with the osGetTime() for now.