You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On the https://github.com/o3de/o3de-atom-sampleviewer/wiki/RHI-Samples#queries it is mentioned that: Enable Timestamp queries (if supported): this will show the time in nanoseconds that the whole drawing process takes. It should be smaller when the red quad is occluded.. This is inconsistent with time units shown on the image, or in Atom Sample Viewer ("us" - microseconds, instead of "ns" - nanoseconds):
This issue also occurs on Windows.
Prerequisites
O3DE engine available.
AtomSampleViewer project built.
Steps to reproduce
Go to Samples > RHI > Queries.
Tick the Enable Timestamp queries checkbox.
Look at the Draw time units.
Expected behavior Draw time units are "ns".
Actual behavior Draw time units are "us".
Found in Branch
O3DE Installer - Stabilization/2305 (26273c22ff71950eb68d137fed25125ebbaa12d6)
AtomSampleViewer - Stabilization/2305 (cee84fa)
Desktop
Device: PC
OS: Linux
Version: Ubuntu 22.04.1 LTS
CPU AMD Ryzen 5 3600
GPU NVIDIA GeForce RTX 2060 SUPER
Memory 16GB
The text was updated successfully, but these errors were encountered:
Describe the bug
On the https://github.com/o3de/o3de-atom-sampleviewer/wiki/RHI-Samples#queries it is mentioned that:
Enable Timestamp queries (if supported): this will show the time in nanoseconds that the whole drawing process takes. It should be smaller when the red quad is occluded.
. This is inconsistent with time units shown on the image, or in Atom Sample Viewer ("us" - microseconds, instead of "ns" - nanoseconds):This issue also occurs on Windows.
Prerequisites
Steps to reproduce
Expected behavior
Draw time units are "ns".
Actual behavior
Draw time units are "us".
Found in Branch
O3DE Installer - Stabilization/2305 (26273c22ff71950eb68d137fed25125ebbaa12d6)
AtomSampleViewer - Stabilization/2305 (cee84fa)
Desktop
The text was updated successfully, but these errors were encountered: