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

Laggy Ui (Hyperpixel 4.0) 3b+ #1113

Closed
jjuuzzii opened this issue Oct 22, 2020 · 17 comments · Fixed by #1114
Closed

Laggy Ui (Hyperpixel 4.0) 3b+ #1113

jjuuzzii opened this issue Oct 22, 2020 · 17 comments · Fixed by #1114

Comments

@jjuuzzii
Copy link

jjuuzzii commented Oct 22, 2020

I‘ve got good animations in fex Files but the settings do lag very much. It’s a non fluid movement.
If I want to change temps in Print mode it’s also very laggy/slow

Hardware: Rapsberry Pi3b+, Hyperpixel 4.0

@TheNeskik
Copy link

What version of Octodash do you use ?
Latest version (2.1.0) doesn't any issue on my Pi3

@jjuuzzii
Copy link
Author

Yea 2.1

@jjuuzzii
Copy link
Author

Is you zu completely fluid ?
Whic screen ?

@UnchartedBull
Copy link
Owner

This could be due to the new background-blurring effect introduced in v2.1.0. I noticed this on my 3B as well in some cases. There is a fix for that, although not fully mature yet. I think I'll remove the blurring for v2.1.1 and then reintroduce it later on.

@jjuuzzii
Copy link
Author

Ok thanks!

@UnchartedBull
Copy link
Owner

v2.1.1 hopefully fixes that, if not please reopen the issue.

@sergejvoronov
Copy link

sergejvoronov commented Oct 22, 2020

I can confirm the issue just after OctoDash update from 2.0 to version 2.1 on Pi 3B+ with Hyperpixel 4.0.

@jjuuzzii
Copy link
Author

How can I update to 2.1.1?

@UnchartedBull
Copy link
Owner

Either use nightly builds linked in the README (although they haven't been updated for some time). Or wait until the official release of v2.1.1 (hopefully later today). You can always build it yourself from master if you prefer that.

@Krontx
Copy link

Krontx commented Dec 2, 2020

I am a total newbie... How do I apply this fix: "remove backdrop filter and add dot animation #1114", my UI is very laggy.

Raspberry Pi 4 Model B, Adafruit 3.5"

@UnchartedBull
Copy link
Owner

The fix is automatically applied. The display you are using is connected via the GPIO headers, right? If so the display just doesn't support a refresh rate of more than 2Hz, nothing I can do about this on OctoDash side.

@Krontx
Copy link

Krontx commented Dec 4, 2020

@UnchartedBull I would happily switch the screen if that'd improve my experience. What screen are you using, what's the minimum recommended refresh rate?

I already checked and my screen comes by default to do 16MHZ with the ability to overclock it to 62MHZ.

I will try to troubleshoot it to find the issue and post the results since I've already seen videos on YouTube showing very fluid animation for videogames.

I will test the following variables:

A) Raspberry Pi 4 performance: Temp, Ram usage, Processor usage

B) Screen config: Overclocking refresh rate, GPIO setup to use GPU if possible, connecting screen to HDMI

C) Octodash: Clean installation, install older versions, switch microSD card.

If you have any other suggestions of where to look at or any support material that would help me with my endeavour (Such as how to install an older version of Octodash) I'd really appreciate it.

Thanks and congrats on such a beautifully developed interface for octoprint.

@UnchartedBull
Copy link
Owner

Probably worth trying out https://www.testufo.com/ in a browser and check what framerate is reported there. I'm running the official 7" screen which does have 60Hz, but 30Hz should work as well.

GPU isn't supported right now since it does create more problems and the animations are plenty smooth with CPU animations only.

You can head over to the releases and download any version you want (with wget) and then just sudo dpkg -i <file>. That should install the downloaded verison.

@Krontx
Copy link

Krontx commented Dec 4, 2020

I fixed the issue, after realizing the problem wasn't the Pi 4 Model B performance itself, I jumped to troubleshoot the screen, it was easier than I though.

All I had to do was:

  1. Overclock the processor a bit (This step might not be completely necessary but why not if you have a fan on your Pi.)
  2. Update the refresh rate from the stock 20MHZ to 62MHZ
  3. Update the FPS from 20 to 60

Anybody using Adafruit 3.5" and a Raspberry Pi 4 Model B please note how to fix the slow/laggy UI, bad performance issuue.

1. Sudo nano  /boot/config.tx
2. Scroll down (Using the arrows) until "#uncomment to overclock the arm. 700MHZ is the default" left the value at arm_freq=800
3.a Continue to scroll down to "dtoverlay" line that is towards the very end of the file (There are few lines containing dtoverlay, pick the one that has speed and FPS)
3.b Switch the values there with the following:` dtoverlay=pitft35-resistive,rotate=90,speed=60000000,fps=60 ` 

@UnchartedBull
Copy link
Owner

Overclocking your screen is definitely next level 👍 Glad you figured it out!

@caesarius
Copy link

So, can I assume that my issue with unresponsive/laggy/random performance is because OctoDash needs more processing power than my RPi 3B and Adafruit PiTFT 3.5" can provide?

My RPi is connected to a Prusa MK2S. Touch UI feedback is shown on screen (tap animation), but it triggers the intended action just randomly or not at all (I can upload a video if that's useful to illustrate this behavior).

I've found out about Octodash and really like it (over TouchUI) mainly because its usability and simplicity, but I'd like to know if my current setup is not enough, hence I need to get a better hardware setup in order to make it work as intended.

If so, just upgrading the screen should be enough? Or do you suggest to upgrade the RPi as well. Thanks!

@UnchartedBull
Copy link
Owner

Raspberry Pi 3B is just fine. I ran that for about 2 years without any issue. I was using a screen connected via DSI and not via the GPIO pins.

I guess a video here would be really useful to debug the issue and fix that. Please also check your system load (either with the Octoprint plugin or with top). Thanks!

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

Successfully merging a pull request may close this issue.

6 participants