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

Layer View Slider #10794

Closed
1 of 2 tasks
donnieval4life opened this issue Nov 11, 2021 · 6 comments
Closed
1 of 2 tasks

Layer View Slider #10794

donnieval4life opened this issue Nov 11, 2021 · 6 comments
Labels
Type: Bug The code does not produce the intended behavior.

Comments

@donnieval4life
Copy link

Application Version

4.12.0

Platform

macOS Monterey (21A559)

Printer

Ender 3 Pro

Reproduction steps

  1. Open Cura
  2. Slice a model
  3. Select preview for layer view
  4. Adjust layer slider

Actual results

When adjusting the layer view slider with the settings dropdown open, it either takes several seconds for the slider to respond to curser movement, or there is no response at all. When the menu is collapsed, the slider is more responsive. The same steps were followed in 4.11.0, 4.10.0, and 4.9.0. 4.9.0 was unaffected by this issue, but 4.10.0 and 4.11.0 were affected in addition to 4.12.0. This slow UI bug seems to extend to the settings dropdown menu, as expanding or collapsing menu items is quite slow in 4.10, 4.11.0, 4.12.0. 4.9.0 is unaffected.
This issue is not limited to any specific sliced model. 50 different models were teste
cura.log
d.

Expected results

The slider should follow the motion of the curser when clicked and dragged. Dropdown menu items should open without excessive lag when clicked (Again, 4.9.0 response times are noticeably more reasonable.)

Checklist of files to include

  • Log file
  • Project file

Additional information & file uploads

I am also attaching my 4.9.0 log fil
cura.log
e.

@donnieval4life donnieval4life added the Type: Bug The code does not produce the intended behavior. label Nov 11, 2021
@fvrmr
Copy link
Contributor

fvrmr commented Nov 12, 2021

Hi @donnieval4life thank you for report.
I tried myself on Monterey with 4.12 but I had no issues. Did you try this in 4.9 and 4.12 with the same model?
Could you maybe share your project file?

@fvrmr fvrmr added the Status: Needs Info Needs more information before action can be taken. label Nov 12, 2021
@donnieval4life
Copy link
Author

All the models I tested were tested in both 4.9 and 4.12. I have attached a video to better showcase the behaviour. There is a little extra lag due to the screen capture (and the quality has been reduced to reduce the file size), but you can see the delay between clicking/dragging the slider and the response of the layer view with the dropdown menu open vs. closed. I am using a random Thingiverse fidget cube model here (http://www.thingiverse.com/thing:1790624), but the behaviour was observed with all the models I have tested so far.

Cura_12.mov

@no-response no-response bot removed the Status: Needs Info Needs more information before action can be taken. label Nov 15, 2021
@Ghostkeeper
Copy link
Collaborator

The next version of Cura will include a performance optimisation for layer view that may help. It prevents the need to re-send vertex data to the GPU with every render.

I don't know if there's really a lot we can do about the performance when the settings list is open though. The settings list has a couple hundreds of settings with a few interface elements each. We did improve performance of that in 4.10 a bit, where we prevented a re-draw of the GUI when only the 3D scene changed, but in your case the layer view slider changes so Qt will re-draw the GUI. We have no real control over what parts of the GUI get re-drawn.

I think we'll wait until the release that contains this rendering performance update.

@donnieval4life
Copy link
Author

4.12.1 has eliminated this issue for me.

@fvrmr
Copy link
Contributor

fvrmr commented Nov 22, 2021

Hi @donnieval4life thank you letting us know that 4.12.1 fixed your issue.
I will close this issue since it is now fixed!

@fvrmr fvrmr closed this as completed Nov 22, 2021
@Ghostkeeper
Copy link
Collaborator

The performance optimisation is only in 4.13 though, not 4.12.1. 4.12.1 just has a bugfix for the arranger and for lightning infill.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

3 participants