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.

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

is Raylib did not better option for Musializer. #107

Open
ayoubelmhamdi opened this issue Apr 25, 2024 · 0 comments
Open

is Raylib did not better option for Musializer. #107

ayoubelmhamdi opened this issue Apr 25, 2024 · 0 comments

Comments

@ayoubelmhamdi
Copy link

The games use 99% of CPU and it's normal, but if Musializer or another powerful tool acts as a game and uses 10% of CPU when we use 60 or 120 FPS is terrible, so we can't use any Raylib app in daily life, including Musializer, no one wants to use such an app that eats the resources and battery quickly.

I asked Raysan about this problem, he mentioned that the solution is to remove the SetTargetFPS() and hack the EndDrawing(), what's your opinion, could Musializer be optimized for CPU and battery 🔋 life.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant