changed diagnostics from seconds to milliseconds

[McSpidey]

Co-authored-by: Alice Cecile [email protected]

Objective

Change frametimediagnostic from seconds to milliseconds because this will always be less than one seconds and is the common unit for game engines.

Solution

• multiplied the existing value by 1000

---

Changelog

Frametimes are now reported in milliseconds

[mockersf]

As someone not accustomed to other game engine, seconds is the natural unit for a duration, not milliseconds. Very quick google search seems to show in seconds for unreal, not sure about unity

[McSpidey]

Unreal and Unity both use milliseconds for frametimes. https://docs.unrealengine.com/4.27/en-US/TestingAndOptimization/PerformanceAndProfiling/Overview/ https://docs.unity3d.com/Manual/ProfilerCPU.html

[mockersf]

You're right, for displaying, milliseconds makes a lot more sense.

I was looking for the unit used when accessing timings from code, for that I found seconds

[cart]

bors r+

[cart]

bors r-

[bors[bot]]

Canceled.

[cart]

bors r+

[bors[bot]]

Pull request successfully merged into main.

Build succeeded:

• build-and-install-on-iOS
• build-android
• build (macos-latest)
• build (ubuntu-latest)
• build-wasm
• build (windows-latest)
• check-compiles
• check-doc
• check-missing-examples-in-docs
• ci
• markdownlint
• run-examples
• run-examples-on-wasm
• run-examples-on-windows-dx12