Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The trajectory calculation of Callisto takes a really long time #315

Open
JonasGilg opened this issue Nov 18, 2022 · 0 comments
Open

The trajectory calculation of Callisto takes a really long time #315

JonasGilg opened this issue Nov 18, 2022 · 0 comments
Labels
bug Something isn't working csp-trajectories

Comments

@JonasGilg
Copy link
Member

Describe the Bug

While measuring some performance I noticed, that csp-trajectories takes up the majority of the CPU time. It seems like something is strange with the trajectory of Callistio, since it takes 11 ms to calculate. If I disable VSync it only takes 1.4 ms.

This leads me to believe, that something is wrong, with how the time is measured.

image

Steps to reproduce the behavior:

  1. Go to "Settings" -> "Frame Timings"
  2. Click "Enabled" and "Display On-Screen Statistics"
  3. Have a look at the csp-trajectories timings.

System

Please complete the following information:

  • CosmoScout VR version: Branch feature/csl-node-editor
  • OS: Windows 10
  • Compiler: Visual Studio 2019 x64
  • Graphics Card: NVIDIA RTX 3080 Ti
@JonasGilg JonasGilg added bug Something isn't working csp-trajectories labels Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working csp-trajectories
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JonasGilg